Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12345»»»

RS SOLUTION - Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E) Expand / Collapse
Author
Message
Posted Monday, April 14, 2008 7:08 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 09, 2011 3:56 PM
Points: 10, Visits: 64
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.
Post #484374
Posted Monday, April 14, 2008 9:13 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, October 25, 2010 10:10 AM
Points: 297, Visits: 267
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...
Post #484469
Posted Monday, April 14, 2008 9:51 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 09, 2011 3:56 PM
Points: 10, Visits: 64
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
Post #484500
Posted Monday, April 14, 2008 10:00 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, October 25, 2010 10:10 AM
Points: 297, Visits: 267
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...
Post #484507
Posted Monday, April 14, 2008 10:15 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 09, 2011 3:56 PM
Points: 10, Visits: 64
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!
Post #484513
Posted Monday, April 14, 2008 10:37 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, October 25, 2010 10:10 AM
Points: 297, Visits: 267
Yeah so if you're data set(s) read directly from the database then you need to make sure the account you're using has db_datareader on whatever DB's it is reading from. If you're calling a stored proc (recomended) then the user account must have execute privileges on the stored proc and must also be a db_datareader in the databases from which the stored proc calls.

Hope this helps!



Cheers,

Ben Sullins
bensullins.com
Beer is my primary key...
Post #484528
Posted Monday, April 14, 2008 11:07 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 09, 2011 3:56 PM
Points: 10, Visits: 64
i did what you recommended... - I also went into the Props of the SP & added "reportexecution" to the list of execution users for the sp. still the same problem.
i went back to the Report Mgr and changed the Props of the Data Sources to use "Credentials supplied by the user running the report". Since i am a System Administrator so i SHOULD have permissions all over the place, i am the owner/creator of the SP, i can run the report in BIDS, yet i still get this 8007052E error.
i appreciate your patience here. this is my company's first foray into Reporting Services; I see the Potential of things that can be done over our present Crystal Reports and i just want to start moving along with this.

Ben Sullins (4/14/2008)
Yeah so if you're data set(s) read directly from the database then you need to make sure the account you're using has db_datareader on whatever DB's it is reading from. If you're calling a stored proc (recomended) then the user account must have execute privileges on the stored proc and must also be a db_datareader in the databases from which the stored proc calls.

Hope this helps!
Post #484547
Posted Tuesday, April 15, 2008 3:25 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, March 06, 2014 6:13 PM
Points: 318, Visits: 1,183
Ben Sullins (4/14/2008)
Yeah so if you're data set(s) read directly from the database then you need to make sure the account you're using has db_datareader on whatever DB's it is reading from. If you're calling a stored proc (recomended) then the user account must have execute privileges on the stored proc and must also be a db_datareader in the databases from which the stored proc calls.


Not to take away from what Ben is saying, but watch out with this. db_datareader grants select permissions to all tables and views in the database. For most environments this is not appropriate, especially if you are granting users access via their Windows logins. It's just asking for someone to steal your data - a least permissive model with only EXEC on reporting procs and minimal direct SELECT access to tables/views is generally better.

Regards,

Jacob
Post #484833
Posted Tuesday, April 15, 2008 3:32 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, March 06, 2014 6:13 PM
Points: 318, Visits: 1,183
@rholt:

It sounds like you may be running into a Kerberos delegation issue. Are your RS server and the source DB server running on different boxes? If so you may not have your RS server setup to correctly delegate the users' credentials to the DB server, so that final "2nd hop" connection is coming through as anonymous. This has been discussed a few times in various threads, the latest I recall was in a linked server context here. aureolin posted a link partway through the thread (http://msdn2.microsoft.com/en-us/library/aa905162(SQL.80).aspx) that gives you the details on correctly configuring your servers.

Regards,

Jacob
Post #484836
Posted Tuesday, April 15, 2008 7:24 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 09, 2011 3:56 PM
Points: 10, Visits: 64
Point well taken, Jacob. for now, i am the sole recipient of all reports run through RS, but i will close down what i need to before i allow others to run them.
Russ

Not to take away from what Ben is saying, but watch out with this. db_datareader grants select permissions to all tables and views in the database. For most environments this is not appropriate, especially if you are granting users access via their Windows logins. It's just asking for someone to steal your data - a least permissive model with only EXEC on reporting procs and minimal direct SELECT access to tables/views is generally better.

Regards,

Jacob[/quote]
Post #484993
« Prev Topic | Next Topic »

Add to briefcase ««12345»»»

Permissions Expand / Collapse