February 9, 2012 at 9:56 am
I did a profiler trace, this time only trace failed login, I caught this user name there.
The application name doesn't tell me much, it just said .netsqlclientdataprovidor
database is master.
So how can I fix this? Does this mean somewhere the user entered a wrong password, but this user is using windows login, mydomain\myusername
I think this may not be related with the detached databases I mentioned earlier
Thanks
February 9, 2012 at 1:08 pm
In the profiler look at the ClientProcessID column. This will give the PID (ProcessorID) of the process from the client application server.
You can get more details about this process from the Task Manager in the Client. If you dont see the PID column in the Processes Tab of Task Manager, click View -> Select Columns and select PID. This should give you more info about the client process that is accesing the SQL Server.
February 9, 2012 at 2:39 pm
Thank you, I found the PID, but in the application server, task manager, how can I find out a processID number?
Thanks
February 9, 2012 at 2:43 pm
Open Tasks Manager.
Go to Processes tab
Click View
Click Select Columns
Select the Check box PID
You will see a new column in the Processes tab called PID. The Image Name column corresponding to the PID will give you the exe of the application. Hopefully this can narrow things down for you.
February 9, 2012 at 2:45 pm
Thanks a lot, I found it.
It is SharePoint Timer Service.
It use this users login to connect to SQL server.
And after I disable the service, then it works fine now.
We don't use the sharepoint service for now, it is an old version wss 3.0. It works.
Thank you very much for the trouble shooting, I really learn a lot from it.
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply