SOLUTION - Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
I've been pulling my hair out with this problem. I can create reports in BI Studio and see them return data. After I deploy them to the Report Server I get this error message when I try to execute the report:
Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
I played with the data source and tried every conceivable credential option. Here's the fix (which I picked up on another forum):
Goto Reporting Services Configuration (in Start Menu->Programs->Sql Server->Config Tools.
Click on Execution Account
Uncheck "Specify an execution account"
That's it.
September 6th, 2006 4:38pm
We can update the password for the given account as well :) Thanks Jeff. This saved a lot of time
Free Windows Admin Tool Kit Click here and download it now
December 20th, 2006 3:01pm
Hi Jeff,
thanks very much, I was trying all kinds of account settings etc.. But nothing worked. This solution actually worked.
I've got one question though: does this pose some kind of security problem?
Regards,
Bert
April 16th, 2007 3:22pm
Thank you for finding this solution!
Another option to solve this problem is to leave the Execution Account checked and select the following credentials in the data source:
Unattended report processing account.
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2007 10:40pm
Thank you for finding this solution!
Another option to solve this problem is to leave the Execution Account checked and select the following credentials in the data source:
Unattended report processing account.
May 17th, 2007 10:40pm
Thanks a lot Jeff. Could you please let me know what makes the difference, when i uncheck that?
Though, it works for me as well.
Free Windows Admin Tool Kit Click here and download it now
May 31st, 2007 1:40pm
Well, according to Books Online....
Setting this account is optional, but not setting it limits your use of external images and connections to some data sources. When retrieving external image files, the report server checks to see if an anonymous connection can be made. If the connection is password protected, the report server uses the unattended report processing account to connect to the remote server. When retrieving data for a report, the report server either impersonates the current user, prompts the user to provide credentials, uses stored credentials, or uses the unattended processing account if the data source connection specifies None as the credential type. The report server does not allow its service account credentials to be delegated or impersonated when connecting to other computers, so it must use the unattended processing account if no other credentials are available.
May 31st, 2007 3:39pm
Another way we solved this problem was to check the "Use as Windows credentials when connecting to the data source" box in the data source definition.
Home -> Data Sources
Click on the data source
In the "Connect using" section, click the radio button for "Credentials stored securely in the report server
Enter the appropriate values in the "User name:" and "Password" boxes
Check the box "Use as Windows credentials when connecting to the data source"
HTH
Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2008 1:06am
Man, thank you. I never thought that will interfere with the non automatic execution. I almost feel like a retard cause I never try that obvious thing. THANKS!!!
October 20th, 2009 6:02pm
Thanks a lot, it is working for me
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2010 2:17am
Thanks a lot, it is working for me
May 19th, 2010 2:17am
Thank you Mr Modzel!
The permissions on Reporting Services are an absolute nightmare to deal with when you're first getting to grips with it but you've got me up and running.
Cheers
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2010 6:29am
Thank you so much!!! I do benefit from that!
January 13th, 2011 3:42am