RSExplorer Example

I try to modify the RSExplorer example by using form authentication. I have
create a window logon form. Could anyone can help me how to integrate form
authentication and the sample together ? Actually I don't know how the
report server can regonize the logon user.
Thanksadd this report parameter: =User!UserID
Geert
"May Liu" wrote:
> I try to modify the RSExplorer example by using form authentication. I have
> create a window logon form. Could anyone can help me how to integrate form
> authentication and the sample together ? Actually I don't know how the
> report server can regonize the logon user.
> Thanks|||May,
Please see the thread "How do you set a cookie for axshdocvw".
--
Hope this helps.
----
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
----
"May Liu" <MayLiu@.discussions.microsoft.com> wrote in message
news:2E81EC43-D180-4568-BFC7-686B39F138CF@.microsoft.com...
> I try to modify the RSExplorer example by using form authentication. I
have
> create a window logon form. Could anyone can help me how to integrate
form
> authentication and the sample together ? Actually I don't know how the
> report server can regonize the logon user.
> Thanks|||Where can I find the thread ?
"Teo Lachev" wrote:
> May,
> Please see the thread "How do you set a cookie for axshdocvw".
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ----
> "May Liu" <MayLiu@.discussions.microsoft.com> wrote in message
> news:2E81EC43-D180-4568-BFC7-686B39F138CF@.microsoft.com...
> > I try to modify the RSExplorer example by using form authentication. I
> have
> > create a window logon form. Could anyone can help me how to integrate
> form
> > authentication and the sample together ? Actually I don't know how the
> > report server can regonize the logon user.
> >
> > Thanks
>
>|||I find it !!! Thanks. I will take a look on that.
"May Liu" wrote:
> Where can I find the thread ?
> "Teo Lachev" wrote:
> > May,
> >
> > Please see the thread "How do you set a cookie for axshdocvw".
> >
> > --
> > Hope this helps.
> >
> > ----
> > Teo Lachev, MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > Publisher website: http://www.manning.com/lachev
> > Buy it from Amazon.com: http://shrinkster.com/eq
> > Home page and blog: http://www.prologika.com/
> > ----
> >
> > "May Liu" <MayLiu@.discussions.microsoft.com> wrote in message
> > news:2E81EC43-D180-4568-BFC7-686B39F138CF@.microsoft.com...
> > > I try to modify the RSExplorer example by using form authentication. I
> > have
> > > create a window logon form. Could anyone can help me how to integrate
> > form
> > > authentication and the sample together ? Actually I don't know how the
> > > report server can regonize the logon user.
> > >
> > > Thanks
> >
> >
> >

RS2000: Subscriptions "Logon Failed"

Hi,
We get an "Logon Failed" message when running subscriptions;
ReportServer service runs using an domain account. Domain account has
run-as-a-service, logon-locally and "impersonate a client after
authentication" and the apprioriate database rights.
What is the "required privilege" (see below) the reportserver is requiring?
Regards,
Erik Tamminga
ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed. --> System.Runtime.InteropServices.COMException (0x80070522):
A required privilege is not held by the client.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
at
Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
userName, String userPwd, String domain)From here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
Hope it helps
1.. Decide which accounts to use for Report Server services. Reporting
Services requires three accounts:
2.. Report Server Windows service requires an account to log on to the
local system. Microsoft recommends that you use Local System if you are
installing on Windows 2000. For more information about this recommendation,
see Service Account.
3.. Report Server Web service requires an account to log on to the local
system. Because it is an ASP.NET application, it runs using the ASPNET
account. If you are running Windows 2000, you cannot specify a different
account to use during Setup; you must use the account that is defined for
ASP.NET. If you are running Windows Server 2003, the default is Network
Service, but you can choose to run the service as Local System.
4.. Report Server Web service requires an account to log on to the SQL
Server instance that hosts the report server database. You can specify a
domain account, a SQL Server login, or Local System. You can also use the
credentials that the Report Server Web service uses to log on to the system.
For more information, see Report Server Database Setup.
"Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in message
news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Hi,
> We get an "Logon Failed" message when running subscriptions;
> ReportServer service runs using an domain account. Domain account has
> run-as-a-service, logon-locally and "impersonate a client after
> authentication" and the apprioriate database rights.
> What is the "required privilege" (see below) the reportserver is
> requiring?
> Regards,
> Erik Tamminga
> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> Logon failed., ;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> Logon failed. --> System.Runtime.InteropServices.COMException
> (0x80070522): A required privilege is not held by the client.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
> at
> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> userName, String userPwd, String domain)
>|||Thanks Beth,
But; RS is able to start, login to the databases. RS WebApplication works as
expected but only the Subscriptions give me a logon failed when they're
scheduled to run. It seems to have something to do with RS not being able to
render the reports using the account used for subscriptions. Any idears on
how to fix this?
Erik
"Beth" <scratchbakery@.msn.com> wrote in message
news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> From here:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> Hope it helps
> 1.. Decide which accounts to use for Report Server services. Reporting
> Services requires three accounts:
> 2.. Report Server Windows service requires an account to log on to the
> local system. Microsoft recommends that you use Local System if you are
> installing on Windows 2000. For more information about this
> recommendation, see Service Account.
> 3.. Report Server Web service requires an account to log on to the local
> system. Because it is an ASP.NET application, it runs using the ASPNET
> account. If you are running Windows 2000, you cannot specify a different
> account to use during Setup; you must use the account that is defined for
> ASP.NET. If you are running Windows Server 2003, the default is Network
> Service, but you can choose to run the service as Local System.
> 4.. Report Server Web service requires an account to log on to the SQL
> Server instance that hosts the report server database. You can specify a
> domain account, a SQL Server login, or Local System. You can also use the
> credentials that the Report Server Web service uses to log on to the
> system. For more information, see Report Server Database Setup.
> "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
>> Hi,
>> We get an "Logon Failed" message when running subscriptions;
>> ReportServer service runs using an domain account. Domain account has
>> run-as-a-service, logon-locally and "impersonate a client after
>> authentication" and the apprioriate database rights.
>> What is the "required privilege" (see below) the reportserver is
>> requiring?
>> Regards,
>> Erik Tamminga
>> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
>> Throwing
>> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> Logon failed., ;
>> Info:
>> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> Logon failed. --> System.Runtime.InteropServices.COMException
>> (0x80070522): A required privilege is not held by the client.
>> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> errorCode, IntPtr errorInfo)
>> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
>> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
>> at
>> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
>> userName, String userPwd, String domain)
>|||Hi Erik,
i think for the subscription to work you need to have Credentials stored
securely in the report server. Subscription will not work for reports which
dont have this stored credentials. When you run the report it will work, but
subscription will not work. The reason is DataSources for that report does
not have stored credentials i.e it has either have windows credential or no
credential. in order that reports have subscrpiton enabled you have to check
the "Credentials stored securely in the report server" and enter the user
name and pwd. you can either enter a sql login or windows login based on the
authentication type. and finally click Apply button to store it. Then do the
subscrpion it will work.
Bava
"Erik Tamminga" wrote:
> Thanks Beth,
> But; RS is able to start, login to the databases. RS WebApplication works as
> expected but only the Subscriptions give me a logon failed when they're
> scheduled to run. It seems to have something to do with RS not being able to
> render the reports using the account used for subscriptions. Any idears on
> how to fix this?
> Erik
> "Beth" <scratchbakery@.msn.com> wrote in message
> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> > From here:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> > Hope it helps
> > 1.. Decide which accounts to use for Report Server services. Reporting
> > Services requires three accounts:
> > 2.. Report Server Windows service requires an account to log on to the
> > local system. Microsoft recommends that you use Local System if you are
> > installing on Windows 2000. For more information about this
> > recommendation, see Service Account.
> > 3.. Report Server Web service requires an account to log on to the local
> > system. Because it is an ASP.NET application, it runs using the ASPNET
> > account. If you are running Windows 2000, you cannot specify a different
> > account to use during Setup; you must use the account that is defined for
> > ASP.NET. If you are running Windows Server 2003, the default is Network
> > Service, but you can choose to run the service as Local System.
> > 4.. Report Server Web service requires an account to log on to the SQL
> > Server instance that hosts the report server database. You can specify a
> > domain account, a SQL Server login, or Local System. You can also use the
> > credentials that the Report Server Web service uses to log on to the
> > system. For more information, see Report Server Database Setup.
> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> >> Hi,
> >>
> >> We get an "Logon Failed" message when running subscriptions;
> >>
> >> ReportServer service runs using an domain account. Domain account has
> >> run-as-a-service, logon-locally and "impersonate a client after
> >> authentication" and the apprioriate database rights.
> >>
> >> What is the "required privilege" (see below) the reportserver is
> >> requiring?
> >>
> >> Regards,
> >>
> >> Erik Tamminga
> >>
> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> >> Throwing
> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> Logon failed., ;
> >> Info:
> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> Logon failed. --> System.Runtime.InteropServices.COMException
> >> (0x80070522): A required privilege is not held by the client.
> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >> errorCode, IntPtr errorInfo)
> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
> >> at
> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> >> userName, String userPwd, String domain)
> >>
> >
> >
>
>|||Hi,
Thanks for the reply, but all of my data sources already use stored
credentials (sql-server's sa user, ..., yeah I know ...). So I still think
it has something to do with the win2000 environment and rs supplied
credentials. Have another look at the reported error, it talks about
impersonation, tokens and the windows user/password/domain combo wich are
not used by SQL authenticating data sources.
Regads,
Erik
"Bava Mani" <BavaMani@.discussions.microsoft.com> wrote in message
news:5F64E059-6709-4881-85ED-D9612700BB3B@.microsoft.com...
> Hi Erik,
> i think for the subscription to work you need to have Credentials stored
> securely in the report server. Subscription will not work for reports
> which
> dont have this stored credentials. When you run the report it will work,
> but
> subscription will not work. The reason is DataSources for that report does
> not have stored credentials i.e it has either have windows credential or
> no
> credential. in order that reports have subscrpiton enabled you have to
> check
> the "Credentials stored securely in the report server" and enter the user
> name and pwd. you can either enter a sql login or windows login based on
> the
> authentication type. and finally click Apply button to store it. Then do
> the
> subscrpion it will work.
> Bava
> "Erik Tamminga" wrote:
>> Thanks Beth,
>> But; RS is able to start, login to the databases. RS WebApplication works
>> as
>> expected but only the Subscriptions give me a logon failed when they're
>> scheduled to run. It seems to have something to do with RS not being able
>> to
>> render the reports using the account used for subscriptions. Any idears
>> on
>> how to fix this?
>> Erik
>> "Beth" <scratchbakery@.msn.com> wrote in message
>> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
>> > From here:
>> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
>> > Hope it helps
>> > 1.. Decide which accounts to use for Report Server services. Reporting
>> > Services requires three accounts:
>> > 2.. Report Server Windows service requires an account to log on to the
>> > local system. Microsoft recommends that you use Local System if you are
>> > installing on Windows 2000. For more information about this
>> > recommendation, see Service Account.
>> > 3.. Report Server Web service requires an account to log on to the
>> > local
>> > system. Because it is an ASP.NET application, it runs using the ASPNET
>> > account. If you are running Windows 2000, you cannot specify a
>> > different
>> > account to use during Setup; you must use the account that is defined
>> > for
>> > ASP.NET. If you are running Windows Server 2003, the default is Network
>> > Service, but you can choose to run the service as Local System.
>> > 4.. Report Server Web service requires an account to log on to the SQL
>> > Server instance that hosts the report server database. You can specify
>> > a
>> > domain account, a SQL Server login, or Local System. You can also use
>> > the
>> > credentials that the Report Server Web service uses to log on to the
>> > system. For more information, see Report Server Database Setup.
>> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
>> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
>> >> Hi,
>> >>
>> >> We get an "Logon Failed" message when running subscriptions;
>> >>
>> >> ReportServer service runs using an domain account. Domain account has
>> >> run-as-a-service, logon-locally and "impersonate a client after
>> >> authentication" and the apprioriate database rights.
>> >>
>> >> What is the "required privilege" (see below) the reportserver is
>> >> requiring?
>> >>
>> >> Regards,
>> >>
>> >> Erik Tamminga
>> >>
>> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
>> >> Throwing
>> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> >> Logon failed., ;
>> >> Info:
>> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> >> Logon failed. --> System.Runtime.InteropServices.COMException
>> >> (0x80070522): A required privilege is not held by the client.
>> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> >> errorCode, IntPtr errorInfo)
>> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
>> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
>> >> pImpToken)
>> >> at
>> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
>> >> userName, String userPwd, String domain)
>> >>
>> >
>> >
>>|||Hi,
Are you using any custom dataset extension or custom assemblie?
why cant you give a domain\windowuser and pwd and click the check box below
"Use as Windows credentials when connecting to the data source" in the
datasource and try running the report. see if its work.
Bava
"Erik Tamminga" wrote:
> Hi,
> Thanks for the reply, but all of my data sources already use stored
> credentials (sql-server's sa user, ..., yeah I know ...). So I still think
> it has something to do with the win2000 environment and rs supplied
> credentials. Have another look at the reported error, it talks about
> impersonation, tokens and the windows user/password/domain combo wich are
> not used by SQL authenticating data sources.
> Regads,
> Erik
> "Bava Mani" <BavaMani@.discussions.microsoft.com> wrote in message
> news:5F64E059-6709-4881-85ED-D9612700BB3B@.microsoft.com...
> > Hi Erik,
> > i think for the subscription to work you need to have Credentials stored
> > securely in the report server. Subscription will not work for reports
> > which
> > dont have this stored credentials. When you run the report it will work,
> > but
> > subscription will not work. The reason is DataSources for that report does
> > not have stored credentials i.e it has either have windows credential or
> > no
> > credential. in order that reports have subscrpiton enabled you have to
> > check
> > the "Credentials stored securely in the report server" and enter the user
> > name and pwd. you can either enter a sql login or windows login based on
> > the
> > authentication type. and finally click Apply button to store it. Then do
> > the
> > subscrpion it will work.
> >
> > Bava
> >
> > "Erik Tamminga" wrote:
> >
> >> Thanks Beth,
> >>
> >> But; RS is able to start, login to the databases. RS WebApplication works
> >> as
> >> expected but only the Subscriptions give me a logon failed when they're
> >> scheduled to run. It seems to have something to do with RS not being able
> >> to
> >> render the reports using the account used for subscriptions. Any idears
> >> on
> >> how to fix this?
> >>
> >> Erik
> >>
> >> "Beth" <scratchbakery@.msn.com> wrote in message
> >> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> >> > From here:
> >> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> >> > Hope it helps
> >> > 1.. Decide which accounts to use for Report Server services. Reporting
> >> > Services requires three accounts:
> >> > 2.. Report Server Windows service requires an account to log on to the
> >> > local system. Microsoft recommends that you use Local System if you are
> >> > installing on Windows 2000. For more information about this
> >> > recommendation, see Service Account.
> >> > 3.. Report Server Web service requires an account to log on to the
> >> > local
> >> > system. Because it is an ASP.NET application, it runs using the ASPNET
> >> > account. If you are running Windows 2000, you cannot specify a
> >> > different
> >> > account to use during Setup; you must use the account that is defined
> >> > for
> >> > ASP.NET. If you are running Windows Server 2003, the default is Network
> >> > Service, but you can choose to run the service as Local System.
> >> > 4.. Report Server Web service requires an account to log on to the SQL
> >> > Server instance that hosts the report server database. You can specify
> >> > a
> >> > domain account, a SQL Server login, or Local System. You can also use
> >> > the
> >> > credentials that the Report Server Web service uses to log on to the
> >> > system. For more information, see Report Server Database Setup.
> >> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> >> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> >> >> Hi,
> >> >>
> >> >> We get an "Logon Failed" message when running subscriptions;
> >> >>
> >> >> ReportServer service runs using an domain account. Domain account has
> >> >> run-as-a-service, logon-locally and "impersonate a client after
> >> >> authentication" and the apprioriate database rights.
> >> >>
> >> >> What is the "required privilege" (see below) the reportserver is
> >> >> requiring?
> >> >>
> >> >> Regards,
> >> >>
> >> >> Erik Tamminga
> >> >>
> >> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> >> >> Throwing
> >> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> >> Logon failed., ;
> >> >> Info:
> >> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> >> Logon failed. --> System.Runtime.InteropServices.COMException
> >> >> (0x80070522): A required privilege is not held by the client.
> >> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >> >> errorCode, IntPtr errorInfo)
> >> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> >> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
> >> >> pImpToken)
> >> >> at
> >> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> >> >> userName, String userPwd, String domain)
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>

RS Install killing me w/ 'NT AUTHORITY\ANONYMOUS LOGON' error

Hi - my config is as follows:
- RS Standard on Windows Server 2003 (server1)
- SQL Server 2000 for repository on a different server server2 (same domain)
- I am logged onto server1 as domain admin (full SQL perms to server2)
- I have successfully installed other RS repositories to server2 (different
db names of course)
Installation fails at the "Configuring Microsoft SQL Server" part with error
message: "SQL Setup failed to connect to the database service for server
configuration. The error was: Login failed for user 'NT Authority\Anonymous
Logon'. "
It appears to be losing my interactively logged on credentials.
Here is info from the log:
SQL_ERROR (-1) in SQLDriverConnectW
sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
user 'NT AUTHORITY\ANONYMOUS LOGON'.
Error 29545. SQL Setup failed to connect to the database service for server
configuration. The error was: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'.
Refer to the Server error logs and setup logs for more detailed information.
MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
Standard Edition -- Error 29545. SQL Setup failed to connect to the database
service for server configuration. The error was: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
Refe
r to the Server error logs and setup logs for more detailed information.
--
Thoughts?
thanksHow are permissions configured for server2? I've had some problems in the
past connecting from a local machine account to a domain sql server
(configured with mixed security). I was attempting SQL authentication. It
started working when I changed the service to run with a domain user
identity rather than a local machine user; then it connected with SQL
authentication just fine. That was odd, because I expected SQL
authentication to work regardless of the windows login identity.
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
news:576C839C-156B-4648-B9D2-DE56EB7EA60A@.microsoft.com...
> Hi - my config is as follows:
> - RS Standard on Windows Server 2003 (server1)
> - SQL Server 2000 for repository on a different server server2 (same
> domain)
> - I am logged onto server1 as domain admin (full SQL perms to server2)
> - I have successfully installed other RS repositories to server2
> (different
> db names of course)
> Installation fails at the "Configuring Microsoft SQL Server" part with
> error
> message: "SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT
> Authority\Anonymous
> Logon'. "
> It appears to be losing my interactively logged on credentials.
> Here is info from the log:
> SQL_ERROR (-1) in SQLDriverConnectW
> sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Error 29545. SQL Setup failed to connect to the database service for
> server
> configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS
> LOGON'.
> Refer to the Server error logs and setup logs for more detailed
> information.
> MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> Standard Edition -- Error 29545. SQL Setup failed to connect to the
> database
> service for server configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Refe
> r to the Server error logs and setup logs for more detailed information.
> --
> Thoughts?
> thanks|||Hi Jeff - Just to clarify my understanding of the installation process as a
baseline assumption so we're on the same page - it's the ID of the
interactively logged on user performing the install who the repository
database is created under.
Regarding permissions for server2, the user I am logged onto server1 as is
domainA\userA. This user is a domain admin and has full admin to server1 and
server2, as well as SQL Server on server2.
regards
"Jeff A. Stucker" wrote:
> How are permissions configured for server2? I've had some problems in the
> past connecting from a local machine account to a domain sql server
> (configured with mixed security). I was attempting SQL authentication. It
> started working when I changed the service to run with a domain user
> identity rather than a local machine user; then it connected with SQL
> authentication just fine. That was odd, because I expected SQL
> authentication to work regardless of the windows login identity.
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
> news:576C839C-156B-4648-B9D2-DE56EB7EA60A@.microsoft.com...
> > Hi - my config is as follows:
> >
> > - RS Standard on Windows Server 2003 (server1)
> > - SQL Server 2000 for repository on a different server server2 (same
> > domain)
> > - I am logged onto server1 as domain admin (full SQL perms to server2)
> > - I have successfully installed other RS repositories to server2
> > (different
> > db names of course)
> >
> > Installation fails at the "Configuring Microsoft SQL Server" part with
> > error
> > message: "SQL Setup failed to connect to the database service for server
> > configuration. The error was: Login failed for user 'NT
> > Authority\Anonymous
> > Logon'. "
> >
> > It appears to be losing my interactively logged on credentials.
> >
> > Here is info from the log:
> >
> > SQL_ERROR (-1) in SQLDriverConnectW
> > sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> > user 'NT AUTHORITY\ANONYMOUS LOGON'.
> >
> > Error 29545. SQL Setup failed to connect to the database service for
> > server
> > configuration. The error was: Login failed for user 'NT
> > AUTHORITY\ANONYMOUS
> > LOGON'.
> > Refer to the Server error logs and setup logs for more detailed
> > information.
> > MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> > Standard Edition -- Error 29545. SQL Setup failed to connect to the
> > database
> > service for server configuration. The error was: Login failed for user 'NT
> > AUTHORITY\ANONYMOUS LOGON'.
> > Refe
> > r to the Server error logs and setup logs for more detailed information.
> >
> > --
> >
> > Thoughts?
> > thanks
>
>|||I had the same problem when I installed RS yesterday. For some reason the
credentials are not passed correctly and I had to run the setup program from
the command line and explicitly pass it credentials with which to run the
setup program. The command to run setup ends up looking something like this:
setup /i "setup\rsrun.msi" RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
I've been told you can use any credentials you want (domain administrator,
etc.), but I just used the sql sa account, and that worked correctly.
I had the same problem when installing sp1. I had to manually extract the
.cab file and run setup from the command line once again:
sp1setup RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
Hope this helps.
David
"ISGADMIN" wrote:
> Hi - my config is as follows:
> - RS Standard on Windows Server 2003 (server1)
> - SQL Server 2000 for repository on a different server server2 (same domain)
> - I am logged onto server1 as domain admin (full SQL perms to server2)
> - I have successfully installed other RS repositories to server2 (different
> db names of course)
> Installation fails at the "Configuring Microsoft SQL Server" part with error
> message: "SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT Authority\Anonymous
> Logon'. "
> It appears to be losing my interactively logged on credentials.
> Here is info from the log:
> SQL_ERROR (-1) in SQLDriverConnectW
> sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Error 29545. SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'.
> Refer to the Server error logs and setup logs for more detailed information.
> MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> Standard Edition -- Error 29545. SQL Setup failed to connect to the database
> service for server configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Refe
> r to the Server error logs and setup logs for more detailed information.
> --
> Thoughts?
> thanks|||> Installation fails at the "Configuring Microsoft SQL Server" part
with error
> message: "SQL Setup failed to connect to the database service for
server
> configuration. The error was: Login failed for user 'NT
Authority\Anonymous
> Logon'. "
>
Another fix for this - add the 'NT Authority\Anonymous Logon' account
as Local Admin on the SQL Server box and then be sure
Builtin\Administrators has SA access on the SQL Server.
Run the install and then change the dbowner to "sa" and remove the
account.
That's how I finally got it installed on a Win2003 box...
-Annette