RS SOLUTION - Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)

Question

RS SOLUTION - Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)

Jeff Modzel

Ten Centuries

Points: 1020
More actions
September 6, 2006 at 7:47 am

#192093
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 11, 2006 at 8:00 am

This was removed by the editor as SPAM

Viewing 15 posts - 1 through 15 (of 41 total)

You must be logged in to reply to this topic. Login to reply

Nathan Griffiths-187644 SSC Journeyman Points: 89 More actions · Answer 1

I had the same issue on a dev machine - turned out I head used my own domain account as the Execution Account and when I changed my password it caused this error - and the moral of the story is never use your user account when installing software!

cheers

Puja-306040 SSC Journeyman Points: 90 More actions · Answer 2

Puja-306040

SSC Journeyman

Points: 90

March 22, 2007 at 8:57 am

#696393

Thanks for the solution!

Brian Egerton SSC Journeyman Points: 89 More actions · Answer 3

Jeff,

Thanks for this - I had just about run out of hair!

Bidyut-437210 Valued Member Points: 71 More actions · Answer 4

Bidyut-437210

Valued Member

Points: 71

October 12, 2007 at 12:31 am

#741446

This solution really works....

Rachel Blum Valued Member Points: 63 More actions · Answer 5

Rachel Blum

Valued Member

Points: 63

December 21, 2007 at 12:04 pm

#762268

Yes. this works, thank you.

delmar.stewart SSC Rookie Points: 47 More actions · Answer 6

I tried this, but have not had any luck. I have reviewed my RS Logs and restarted the server/services several times over the past few days and de-selected the Execution account but still no luck. Just

"

Logon failed. (rsLogonFailed)

Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)

"

If anybody has any otehr ideas, let me know.

rene-500237 Hall of Fame Points: 3769 More actions · Answer 7

rene-500237

Hall of Fame

Points: 3769

February 7, 2008 at 8:12 am

#776037

😀

Thanks for your help!!

knahm Valued Member Points: 53 More actions · Answer 8

Awesome. Thanks for the tip. Saved me lots of frustration! 😀

rholt-710769 Mr or Mrs. 500 Points: 560 More actions · Answer 9

i have have had the same problem - i have the RS on my PC but i'm trying to access a report from a SQL instance on a different SQL Server.

it took me quite a while to get the two to see each other - my password changed & now i although the reports show up on my site & i've gone into Rpt Mgr to change the ReportExecution password - still the same error.

Ben Sullins-437405 SSCertifiable Points: 5397 More actions · Answer 10

I've been working with SSRS for years now and still come across this error from time to time. Generally the issue I find is that there are domain/networking issues that prevent the SSRS server from accessing the database server. In some instances if there is no transitive trusts between the domains than you'll need to create a local user on the db server with the same username/password as the account you're trying to use to connect.

Delmar - Can you provide some more details about your network setup in regards to the SSRS and DB servers? This will help with any suggestions on resolving your connectivity issues.

Generally for the data source config I choose to use 'Credentials stored securely in the report server' with a domain account and the 'Use as Windows credentials when connecting to the data source' box checked...

Hope this helps!

Cheers,

Ben Sullins
bensullins.com
Beer is my primary key...

rholt-710769 Mr or Mrs. 500 Points: 560 More actions · Answer 11

my knowlege of most of this is limited.

but would it help to let you know that the SQL server is running SQL2005 on a MS-Server2003 OS and the server is in Cluster configuration.

i'm not sure where to go on the SQL Server in order to add the credentials.

i have ReportExecution as the user name & at one time had the proper credentials to get the reports running from the server, until my own username/password changed.

again, i think i just need to know where on the SQL Server i need to go to add this user/password combination?

thanks for your help. i've spent way too many hours trying to get over this hump and start becoming productive again.

Russ Holt

Ben Sullins-437405 SSCertifiable Points: 5397 More actions · Answer 12

Hey Russ,

Are you using shared data sources? Make sure the connection string has the correct servername and that from the SSRS server you can telnet into the DB server. This should resolve at least any networking issues. Then I would say make sure whatever account you are using for your data source credentials has access to the database(s) where your query/stored proc pulls from. This needs to be done through SQL Server Management Studio.

Also, are the SSRS and DB servers on the same domain? That might cause some problems as well...

Cheers,

Ben Sullins
bensullins.com
Beer is my primary key...

rholt-710769 Mr or Mrs. 500 Points: 560 More actions · Answer 13

my feeling is that i'm missing one "simple" piece.

i opened SQL Serv. Mgmt Studio

drilled down to Security/Logins to ReportExecution.

right-clicked & opened properties.

re-input the password to double check that it was/is correct.

are there "server roles" or "user mappings" that need to be checked?

both my pc (where reporting services is installed) and the server are on the same domain.

oy!