Production SQL Agent: Error 5:[SQL-DMO]---EXCEPTION_ACCESS_VIOLATIONError 5:[SQL-DMO

[DLu]

Hi:
--10/10/2008 8 am
found in SQL Agent refresh with following error:
Error 5:[SQL-DMO]Code execution exception: EXCEPTION_ACCESS_VIOLATION

--10/11/2008 9 am Error 5: now [Error 0:]

individual job still running on schedule with success.
SQL2000 Ent SP4.

1. DBCC CHECKDB(MSDB) no error
2. no error found in SQL log, agent log, OS event log
3. restored msdb with a good backup.

still cound not refresh job screen, no with error 0: instead of error 5 exception_access_violation.

thanks for your help.
David

[rmiao]

Don't think it's msdb issue, sounds sql agent has hard time to access msdb. Check sql agent properties to find out how it connects to sql server. By the way, what's sp level?

[DLu]

hi ramiao:

server: SQL2000 Enterprise, SP4.
from sql agent: [100] Microsoft SQLServerAgent version 8.00.2039 (x86 unicode retail build) : Process ID

now, when refresh the job area, get "SQL Server Enterprise Manager" Errror 0:

all other activity options work including new job, view, all tasks --manage job categories;
still no error/warning in SQL agent/SQL log, OS side.

thanks for your info
David

[rmiao]

Did you try this on another machine?

[DLu]

not quite sure about 'try on another machine'?

1. individual job refresh is good.
2. still could create new job, old job still run on schedule
3. just refresh all job function not work with "Error 0:" now.
4. no error on agent log, sql log and OS event

have not tried on restart SQL server service since it is prod.

thanks
-D

[rmiao]

'try on another machine' meas open em on another sql client machine and connect to questioned sql server then try refresh jobs.

[DLu]

Hi Rmiao:

It is caused by the SQL client.
After drop off the sql registration and re-registed the server, the refresh error was gone.

thanks for your help
David