November 18, 2008 at 10:01 am
Though the server could still be "pinged" users were starting to complain about connectivity problems over the weekend. Most of the calls are from an IIS machine that handles various websites. I was not able to remote to the SQL Server. Our Network Admin was able to eventually restart the box remotely. Now, I am reviewing the SQL logs and am finding this generalized error affecting multiple spids and could not get enough info by just searching. It seems to be windows not being able to grant SQL Server anymore resources. Has anyone encountered this and has gotten an explanation. Thanks in advance.
BTW. This is on a Windows 2003 machine running SQL Server 2005 SP2 with AWE enabled which I guess is the default when running on Win Server 2003.
Sourcespid58
Message
The operating system returned error 1453(Insufficient quota to complete the requested service.) to SQL Server during a read at offset 0x000000009d0000 in file with handle 0x000005E4. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
November 18, 2008 at 2:31 pm
r.pe (11/18/2008)
Though the server could still be "pinged" users were starting to complain about connectivity problems over the weekend. Most of the calls are from an IIS machine that handles various websites. I was not able to remote to the SQL Server. Our Network Admin was able to eventually restart the box remotely. Now, I am reviewing the SQL logs and am finding this generalized error affecting multiple spids and could not get enough info by just searching. It seems to be windows not being able to grant SQL Server anymore resources. Has anyone encountered this and has gotten an explanation. Thanks in advance.BTW. This is on a Windows 2003 machine running SQL Server 2005 SP2 with AWE enabled which I guess is the default when running on Win Server 2003.
Sourcespid58
Message
The operating system returned error 1453(Insufficient quota to complete the requested service.) to SQL Server during a read at offset 0x000000009d0000 in file with handle 0x000005E4. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
This can be a I/O subsystem error which means that SQL Server cannot communicate with the drive.
Check to see if your data files are located on a SAN or another external drive like ISCSI.
If the drive becomes unavailable for a short time you will see these errors in the error log.
It can also mean that if you're using xp_cmdshell to do file operation you might not have permissions on a mapped drive.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply