February 16, 2007 at 8:51 am
I am in a tricky sitituation:
We have a sqlslerver 2000, vendor developed apps accessing sql db.
We recently removed sql logins to this db and decided to connect using network logins integrating with AD. A specific AD group was created with user logins. This group has read/write access to one db in the instance. The apps connects with a DSN: we set the dbs to use windows login.
The dsn works fine: test connection was successful, user in the AD group.
Opening the apps we get a login failure. The sql logs says simply : login failure for user ...
What is wrong here ?
February 16, 2007 at 12:51 pm
To diagnose, run SQL profilier and monitor events for logins including failures, sql:batchcompleted and sql:batchstarting
This will capture the exact SQL being issued by the application and any error messages.
SQL = Scarcely Qualifies as a Language
February 16, 2007 at 12:59 pm
found it!. The apps had locked some tables and so the error!.
thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply