Home Forums SQL Server 2005 Business Intelligence RS SOLUTION - Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E) RE: RS SOLUTION - Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)

  • ok - i'm sort of understanding this, but would the fact that I have RS loaded & running on my PC constitute a 2nd hop or just a single hop to the SQL Server?

    Everything except the SQL & SP (which are both on the SQL Server) is on my personal PC. (i will be moving it off to a Reports Server probably within the week).

    Jacob - this link didn't work: Configuring Authentication for Reporting Services

    so... i think we're in agreement that since i eventually want others to be able to run these reports, an "Execution Account" is the way to go. i had an Account Name:

    ReportExecution

    and on the SQL Server under Security/Login i created the login:

    ReportExecution

    with the same password i used on the RS Config Mgr under Execution Account.

    should i NOW go into Active Directory & create a UserProfile named

    ReportExecution

    with that same password??????

    Ben Sullins (4/15/2008)


    As I stated in an earlier post if you setup your data source so it uses the 'Credentials stored securely in the report server' option and you provide a domain account and the 'Use as Windows credentials when connecting to the data source' box checked you should be good. Assuming the permissions on the database are setup properly.

    This doesn't require the 2nd hop that Jacob is describing and is generally how I've always configured my shared data sources. If you're pointing to an isolated SQL instance you could also run profiler and see what kind of requests are coming in.

    Hope this helps!