March 19, 2009 at 10:49 am
"Only administrators may connect at this time" started popping up in the log for both SQL and Domain logins.
I see "SQL Server is now ready for client connections." and then database recoveries, but nothing else denoting that the server was started in single user mode.
A couple other errors looked out of place:
Windows cannot open the 64-bit extensible counter DLL MSEIDRDA in a 32-bit environment. Contact the file vendor to obtain a 32-bit version. Alternatively if you are running a 64-bit native environment, you can open the 64-bit extensible counter DLL by using the 64-bit version of Performance Monitor. To use this tool, open the Windows folder, open the System32 folder, and then start Perfmon.exe.
and
An unrecoverable path failure occurred on SCSI address (2.0.5.3). Disk 600508B40010616C00012000053D0000 is still accessible over redundant path(s).
which corrected itself with these entries:
HP MPIO DSM for EVA4000/6000/8000 family of Disk Arrays is attempting an operation on \Device\MPIODisk3. The Type is noted in the dump data.
The DSM has completed remove processing for path (SCSI address (2.0.5.3)) to multipath capable disk 600508B40010616C00012000053D0000.
Added device to \Device\MPIODisk3. DumpData contains the current number of paths.
HP MPIO DSM for EVA4000/6000/8000 family of Disk Arrays is attempting an operation on \Device\MPIODisk4. The Type is noted in the dump data.
I appreciate any tips you might have on this.
March 19, 2009 at 5:22 pm
Hmm I am not sure .. just an idea.
Since you are having I/O Subsystem issues, SQL Server loses its communication to AD. So locks it down because it cannot confirm/deny if the clients coming into SQL Server are valid.
Thanks.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 19, 2009 at 6:12 pm
Thanks for your feedback.
How would the IO subsystem effect communication with our domain controller? I don't see why it would choose to let administrators in during that scenario either - seems like that would be the last account you would want in if you had doubts.
We do have AD issues from time to time, but we start getting sev 20 errors with SSPI handshake failures. Also, we, as admins can't get in when that happens(when a PDC gets patched and reboots, handing off to another DC).
I'd love to flip it back over and see if it happens again, but can't do that.
March 19, 2009 at 11:21 pm
As I said it was just an idea I was throwing to the table...
The reason I am taking a guess AD communication issue is happening because of error message; that error message is logged because either you db is getting put in restricted mode (jobs?) or SQL Serve can't talk to AD because is SQL Server is busy trying to access the HDD, CPU is getting pinged network communication drops.
Do you only allow windows authentication? If so then okay that makes sense; but if you also Mixed Authentication .. then hmm my logic has few holes :hehe:.
Does you message indicate which database state changed? Maybe implement a job that logs database states between the time they have an issue? To see if it is someone or all dbs?
Again throwing ideas on table ... Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
October 11, 2011 at 1:40 am
Hi,
Please let me know if you were able to find the solution for this issue. We have similar situation and cannot get any solution even from microsoft.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply