Logon failure : (rsInternalError)

On a SQL server 2000 SP4 on XP PRO SP2, I have installed Reporting Services.
I have created an local administrator user and I have given this local
account as "Domain user Account" during installation.
When I try to acces report server, it fails with the message "Logon failure:
unknown user name or bad password. "
In the logfile of Reporting services, I read these informations :
aspnet_wp!library!690!02/03/2006-16:24:09:: i INFO: Call to GetPermissions:/
aspnet_wp!crypto!690!02/03/2006-16:24:09:: i INFO: Initializing crypto as
user: U000103096\ASPNET
aspnet_wp!crypto!690!02/03/2006-16:24:09:: i INFO: Exporting public key
aspnet_wp!library!690!02/03/2006-16:24:10:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
Une erreur interne s'est produite sur le serveur de rapports. Pour plus
d'informations, consultez le journal des erreurs., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
Une erreur interne s'est produite sur le serveur de rapports. Pour plus
d'informations, consultez le journal des erreurs. -->
System.Runtime.InteropServices.COMException (0x8007052E): Logon failure:
unknown user name or bad password.
Can somebody help me to solve this problem ? Thanks for allHi Gaby,
Welcome to the MSDN newsgroup.
From your description, I understand you have installed SQL Server 2000(with
reporting service) on a Windows XP SP2 machine. Also, during the
installation time, you configured the Reporting Service to use a certain
domain account which has been granted the "Local Administrator" role.
However, when you try accessing the report server application, it threw the
following exception:
"Logon failure: unknown user name or bad password. " ,correct?
Based on the log file content you provided, the error occured when the
report server try performing some security operations like reading account
info. I've also checked the error and find some reference in MSDN on the
similiar problem. Are you try viewing a report which use external
datasource and use prompted or stored Windows credentials to connect to the
external datasource? If so, you can have a look at the following
troubleshooting article, and the below section
"Connection error, where login failed for <servername>\ASPNET"
is describing the similiar problem as yours.
#Troubleshooting Server and Database Problems
http://msdn.microsoft.com/library/en-us/rstshoot/htm/trs_tshootdev_v1_3dcz.a
sp?frame=true
Please feel free to post here if there's anything else we can help.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Steven
Thank you for your help but I am sorry to say that your recommendations
didn't work on my PC
I have just installed an SQL Server on my windows XP (SQL server 2000 + SP4)
and the Reporting Services (+ service pack 2). After that, before making any
own report, I have just tried to contact the report server, on this PC, in
an IE5 session with the address : localhost\reports. And then I have received
the error message : logon failed !!
My PC is an "entreprise PC", this a lot of components "masterised" in a
"logically gathered software" and I think that perhaps some authorizations
are not correctly installed for my requirements, but I don't know where I
have to search !!
"Steven Cheng[MSFT]" wrote:
> Hi Gaby,
> Welcome to the MSDN newsgroup.
> From your description, I understand you have installed SQL Server 2000(with
> reporting service) on a Windows XP SP2 machine. Also, during the
> installation time, you configured the Reporting Service to use a certain
> domain account which has been granted the "Local Administrator" role.
> However, when you try accessing the report server application, it threw the
> following exception:
> "Logon failure: unknown user name or bad password. " ,correct?
> Based on the log file content you provided, the error occured when the
> report server try performing some security operations like reading account
> info. I've also checked the error and find some reference in MSDN on the
> similiar problem. Are you try viewing a report which use external
> datasource and use prompted or stored Windows credentials to connect to the
> external datasource? If so, you can have a look at the following
> troubleshooting article, and the below section
> "Connection error, where login failed for <servername>\ASPNET"
> is describing the similiar problem as yours.
> #Troubleshooting Server and Database Problems
> http://msdn.microsoft.com/library/en-us/rstshoot/htm/trs_tshootdev_v1_3dcz.a
> sp?frame=true
> Please feel free to post here if there's anything else we can help.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
>
>
>
>|||Thanks for your response Gaby,
So the problem is somewhat different from that mentioned in the doc. Since
the error stack shows there is some login fail error and also mentioend the
MACHINE\ASPNET account, I think you can try the followings to see whether
it is concerned with account permission:
1. Change the reporting service windows service's identity from the current
account( the one you specified during setup) to Local System.
2. Temporarlily Add the ASP.NET process account (machine\ASPNET) into
local administrators group or just replace the ASP.NET process account
from "Machine" to "SYSTEM", this can be set in the .net framework's
machine.config(under C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG)
After that, restart reporting service to see whether it work.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thank you for your help. At the end, it works. I have just modified the
machine.config file of the current version of the framework (in the CONFIG
Folder), and change, in the processModel parameter, the value of the userName
parameter, from "machine" to "SYSTEM".
By stopping and restarting only the reporting service and the IIS server,
this modification don't work but after the "total reboot" of my computer, all
is OK and I can now see the contents of the folder in the Reports Server
Thank you for all (and I hope that our discussion can help other persons)
"Steven Cheng[MSFT]" wrote:
> Thanks for your response Gaby,
> So the problem is somewhat different from that mentioned in the doc. Since
> the error stack shows there is some login fail error and also mentioend the
> MACHINE\ASPNET account, I think you can try the followings to see whether
> it is concerned with account permission:
> 1. Change the reporting service windows service's identity from the current
> account( the one you specified during setup) to Local System.
> 2. Temporarlily Add the ASP.NET process account (machine\ASPNET) into
> local administrators group or just replace the ASP.NET process account
> from "Machine" to "SYSTEM", this can be set in the .net framework's
> machine.config(under C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG)
> After that, restart reporting service to see whether it work.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
>
>|||You're welcome Gaby,
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)