September 25, 2008 at 9:40 am
"Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login failed for user ''. The user is not associated with a trusted SQL Server connection."."
I have been up & down the web and can't find my scenario although there are many posts.
I get this error intermittently but lately several times a day. I get it while attempting to log into SSMS with my A/D username or as 'sa'. It doesn't matter if I log in via RDP or my client machine. Sometimes it works; others not.
I also get it - sometimes - when running SQL Agent jobs calling SSIS packages. The username launching the job is the same one that created the SSIS package.
One reference suggested since the username is NULL that is has to do with a domain controller or some other network issue. My LAN/SAN guy says "No" and points to an error in the logs that says "Not enough space available".
Has anyone seen this from both scenarios and where it's intermittent?
Muchas gracias!
September 25, 2008 at 9:56 am
I had a similar "simple matter disappearing" issue. In my case it was SPN problem. The fact that your connectivity sometimes works and sometimes doesn't is saying that you probably have the same...
Show it to your LAN guy:
http://poseidom.wordpress.com/2007/12/16/set-spn-for-sql-2005-sccm-remote-sql-fix/
September 25, 2008 at 9:57 am
DonKo (9/25/2008)
One reference suggested since the username is NULL that is has to do with a domain controller or some other network issue. My LAN/SAN guy says "No" and points to an error in the logs that says "Not enough space available".
It is usually a network/AD issue. It means that the domain identy could not be confirmed with the DC
Which log is showing an out of space issue and what's the full entry?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 25, 2008 at 1:17 pm
Gail, the error messages appearing on the Windows System log are:
[font="Verdana"]"This computer was not able to set up a secure session with a domain controller in domain [name] due to the following: Not enough storage is available to process this command. This may lead to authentication problems. Make sure that this computer is connected to the network."[/font]
...also:
[font="Verdana"]"The kerberos subsystem encountered a PAC verification failure. This indicates that the PAC from the client [username] in [domain name] had a PAC which failed to verify or was modified."[/font]
Thanks for any additional insight you can provide!
September 26, 2008 at 12:41 am
I'm no AD expert, however those are not SQL-related errors. They point at a problem communicating with the DC. If that was my server, I'd be passing those over to the server admin to resolve.
Check the server in question, make sure there's free space on the C drive.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 26, 2008 at 5:16 am
SPN is a service principle name. SPN problem is indicating a problem with registering SPN in AD.
The article I referenced giving you (your network manager) a step by step instructions on how to diagnose and resolve it...
September 26, 2008 at 7:15 am
Thank you, Glen. I did show it to my LAN guy but will empasize that the solutions described in it will correct the problem. I appreciate the confirmation!
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply