March 31, 2003 at 8:22 am
We are getting follwoing errors on our SQL Agent log
"2003-03-28 08:37:33 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:37:33 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:40:01 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:40:01 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:40:01 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:40:01 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:42:22 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:42:22 - ! [382] Logon to server 'SQLServer\SQL' failed (ConnAttemptCachableOp)
2003-03-28 08:42:30 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:42:30 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:42:30 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:42:30 - ! [298] SQLServer Error: 11, General network error. Check your network documentation. [SQLSTATE 08S01]
2003-03-28 08:42:30 - ! [298] SQLServer Error: 4, ConnectionWrite (WrapperWrite()). [SQLSTATE 01000]
2003-03-28 08:42:30 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:42:30 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:45:01 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:45:01 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:47:30 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:47:30 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:49:49 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:49:49 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:49:59 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 08:49:59 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 08:49:59 - ! [298] SQLServer Error: 11, General network error. Check your network documentation. [SQLSTATE 08S01]
2003-03-28 08:49:59 - ! [298] SQLServer Error: 4, ConnectionWrite (WrapperWrite()). [SQLSTATE 01000]
2003-03-28 08:49:59 - ! [382] Logon to server 'SQLServer\SQL' failed (ConnAttemptCachableOp)
2003-03-28 11:25:53 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 11:25:53 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 11:25:53 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 11:25:53 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2003-03-28 11:25:53 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)
2003-03-28 11:25:53 - ! [382] Logon to server 'SQLServer\SQL' failed (JobManager)"
SQL server sudently goes busy and it doesnot allow any one to login fro 2-3 minutes and then it goes tyo normal. This problem just started two day ago. Jobs that runs under "SA" some time gets the error like "The job failed. Unable to determine if the owner (sa) of job tsk_za_logdump has server access (reason: Unable to connect to server - check SQL Server and SQL Server Agent errorlogs)."
Any ideas?. We are running SQL SP2 with sql warm patch.
Thanks
March 31, 2003 at 8:44 am
Any errors did you have in SQL Server errorlog?
Any changes implemented to your SQL Server recently? Can you post result of sp_configure
March 31, 2003 at 8:50 am
THat was SQL Agent Log. Here's the SP_Configure
ame minimum maximum config_value run_value
----------------------------------- ----------- ----------- ------------ -----------
affinity mask -2147483648 2147483647 7 7
allow updates 0 1 0 0
awe enabled 0 1 0 0
c2 audit mode 0 1 0 0
cost threshold for parallelism 0 32767 5 5
cursor threshold -1 2147483647 -1 -1
default full-text language 0 2147483647 1033 1033
default language 0 9999 0 0
fill factor (%) 0 100 0 0
index create memory (KB) 704 2147483647 0 0
lightweight pooling 0 1 0 0
locks 5000 2147483647 0 0
max degree of parallelism 0 32 0 0
max server memory (MB) 4 2147483647 2560 2560
max text repl size (B) 0 2147483647 65536 65536
max worker threads 32 32767 255 255
media retention 0 365 0 0
min memory per query (KB) 512 2147483647 1024 1024
min server memory (MB) 0 2147483647 1024 1024
nested triggers 0 1 1 1
network packet size (B) 512 65536 4096 4096
open objects 0 2147483647 0 0
priority boost 0 1 0 0
query governor cost limit 0 2147483647 0 0
query wait (s) -1 2147483647 -1 -1
recovery interval (min) 0 32767 0 0
remote access 0 1 1 1
remote login timeout (s) 0 2147483647 20 20
remote proc trans 0 1 0 0
remote query timeout (s) 0 2147483647 600 600
scan for startup procs 0 1 0 0
set working set size 0 1 0 0
show advanced options 0 1 1 1
two digit year cutoff 1753 9999 2049 2049
user connections 0 32767 0 0
user options 0 32767 0 0
Thanks for looking into.
March 31, 2003 at 9:28 am
Can you check your server application and system logs for any errors?
March 31, 2003 at 9:31 am
I look at the Application and system log of the server but couldnot find any errors that will help.
Thanks
March 31, 2003 at 9:44 am
Which service pack and MDAC version do you have for SQL Server? What network (TCP/IP, Named Pipe or MulitiProtocol) library do you configure on both server and client? What type service account (local or domain) to start SQL Server?
Check this KB too. http://support.microsoft.com/default.aspx?scid=kb;en-us;311111
Edited by - Allen_Cui on 03/31/2003 09:54:25 AM
March 31, 2003 at 9:58 am
Windows 2000 Adv server SP3. MDAC 2.6. Network library is TCP/IP and Named Pipe. SQL service and sql agent service runs unde domain account.
Thanks for your help.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply