November 29, 2004 at 3:03 pm
Hi
Please suggest.
We are using SQL Server 2000 SP3 on Windows 2003. We getting this error message "NT Login failed for User 'Domain\Login'". This account is used by one of our applications. The application works properly, can connect to the database and perform database updates, but we get Login Failed error in the SQL Server log whenever this application is running.
Application is using ODBC connection to connect to SQL Server.
Thanks
Taiyeb
November 29, 2004 at 3:29 pm
The SQL Error Log entries must be caused by something other than your working application. Run Profiler, looking for Login Failure events and capturing as many columns as possible. You may catch the application name and/or hostname of whatever is failing to log in.
Cheers,
- Mark
November 29, 2004 at 9:10 pm
Agree with above. The login failures are being caused by something else if your app is working.
November 30, 2004 at 6:54 am
Thanks all for the reply.
I captured all the information using SQL Profiler. Application name is blank, host name is the name of the same server where the Application is running, Error colum contains 18456.
From this, it is still difficult to find out what is causing this error.
Thanks
Taiyeb
November 30, 2004 at 5:07 pm
Did the captured ClientProcessID provide any help?
Cheers,
- Mark
December 1, 2004 at 8:22 pm
Hi Mccork
ClientProcessId is same as that of working application, but the SPID is different. What can cause 'Invalid Login error'?
Thanks
Taiyeb
December 1, 2004 at 9:48 pm
Maybe another component of your application logging on with invalid credentials or with a different method (eg. trusted instead of standard, or vice versa)?
Cheers,
- Mark
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply