October 14, 2009 at 11:59 am
Windows group ID gets this error in development but not in production server, set up the same way. Ive looked throught he forums and have not found an answer to fix this. I found that named pipes in dev was disabled and am enabling them now. is there anything else i can check?
Error:
Cannot connect to SErvaname\INstance.
------------------------------
ADDITIONAL INFORMATION:
Login failed for user 'xxx\xxx. (Microsoft SQL Server, Error: 18456)
Any help appreciated!
¤ §unshine ¤
October 14, 2009 at 12:14 pm
sunshine-587009 (10/14/2009)
Error:Cannot connect to SErvaname\INstance.
------------------------------
ADDITIONAL INFORMATION:
Login failed for user 'xxx\xxx. (Microsoft SQL Server, Error: 18456)
Any help appreciated!
You may have already read this post, but there should be an entry after or prior to the error you provided in the SQL Error logs that gives you the details about why the login failed. If you can provide that entry of the error log we can provide you a little bit more assistance.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
October 14, 2009 at 2:38 pm
Yes, I apologize I thought I added it.
Message
Error: 18456, Severity: 14, State: 11.
¤ §unshine ¤
October 15, 2009 at 5:45 am
Well State 11 seems to show it is a valid login but does not have the proper access to log into the server.
If you take the group login on the production server, open the properties and see if you can script the login to a query window. Then do the same to the group login on the dev server.
See if you see anything different.
How are the users within this group trying to connect to the database/server?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
October 15, 2009 at 7:14 am
They are set exactly the same. I actually took the dev script and ran it in production and it works fine in prod, not in dev. Now, this is a group rather than an individual. But when I take one of the individuals from the group and add it to the server and databases, exact same properties, they can get it in. I thought it might be some type of configuration that is missing in dev or a windows configuration.
They have tried both logging in through vpn and rdp directly.
¤ §unshine ¤
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply