There have been other similar posts, but this is my issue: I have set up database mirroring with a witness, and failover works properly. I have also installed the login id's and their original SID's onto the mirror server. When I run a Reporting Services report against the primary database, it runs properly. When I failover to the mirror server and run the report again, I get a "login failed for user" error. As I have already said, the SQL login that the Reporting Services report uses was installed on the mirror server with the original SID. Any ideas as to what else might be wrong
Login Failure
Hot Topic
- Invalid length parameter passed to the substring function.
- How to Deploy .mdf Files
- Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- Newbie questions SQL Server2005 Reporting Service-Urgent
- Problems Creating Instance in SQL 2005 management studio
- rsAccessDeniedToSecureData
- Error description
- S Drop Default values in Columns
- group by
- Unable to start T-SQL Debugging. Could not attach to SQL Server process on
SQL Server
- How can I print table structures in SQLExpress
- Time dimension MDX
- Foreach Loop Issue
- Performance issue in MDX query
- Snapshot executes but subscription does not email to user
- YTD again
- Encryption - Protect from attacks by programmers?
- Newbie Trying to connect to Adventure Works db on local desktop
- Clone DB
- SQLEVN70.rll error
Login Failure
ajpurkiss
My first suggestion would be to check the permissions of the user who is attempting to log in.
-Matt
salah chebaro
Can you check the SID on master and user databases similarity
Also specify a valid, available database in the connection string. To avoid the error when the user's default database is unavailable, log on as a user who can modify logins. Then, change the user's default database to a database that is currently available for a connection.