April 9, 2008 at 10:31 am
Hello there,
I seem to have this message appear in my event log on my server every 10 seconds;
SQL Server Scheduled Job 'Websense_ETL_Job__wslogdb63' (0xD621C5DD30058B43AD587FD350C0306E) - Status: Failed - Invoked on: 2008-04-09 17:21:50 - Message: The job failed. The Job was invoked by Schedule 1 (SCHEDULE). The last step to run was step 1 (STEP1).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I'm not an expert on SQL and can't find anywhere to see where scheduled jobs may be. As far as I know the version is SQL Server 2000
Thanks in advance!
Richard
April 9, 2008 at 1:35 pm
If you open enterprise manager, and look down the bottom of the tree you should see SQLAgent.
Expand that out. The jobs are recorded under there.
Does that help?
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
April 10, 2008 at 2:22 am
The thing is I can't find enterprise manager anywhere! The "websense" part of the error message is to do with a trial of websense which was used here a little while ago thats no longer in use. Can this enterprise manager be installed seperately?
Thanks again,
April 10, 2008 at 2:27 am
Enterprise manager is one of the management tools for SQL Server. It shouldn't be installed on the server, only on client machines. If you have an installation disk for SQL 2000, yuo can ust choose to install the client components.
Do you have any DBAs there?
Do you have any other SQL systems?
If you know that SQL's not been used on that machine (if it was a trial of websense that's not longer in use) then perhaps stop the services (MSSQLSERVER and SQLSERVERAGENT)
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
April 10, 2008 at 2:42 am
I have stopped the services "MSSQLSERVER" and "SQLSERVERAGENT" and the errors have stopped in the event viewer. The only other program which uses sql on this server is Symantec Backup Exec 10d for Windows Servers. This looks like is has its own services "SQLAgent$BKUPEXEC" and "MSSQL$BKUPEXEC" which i haven't touched. Do you think this would be ok then?
I really appreciate your help!
Richard
April 10, 2008 at 3:04 am
Should do. Just keep an eye on it for a while, make sure nothing else breaks
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
April 10, 2008 at 3:07 am
Ok will do!
Thanks again for your help 😎
April 16, 2008 at 2:11 am
Hello again everyone!
After stopping the above services, they seem to kick back in after my backup exec job has finished. Is it possible to view the SQL "scheduler" (not sure if there is one!) and delete this SQL service/job?
I thought there may be like and admin tool for it so i could see what was going on but i can't find anything
Thanks again in advance
Rich
April 16, 2008 at 3:02 am
The admin tool is Enterprise manager, but as already noted, it's not installed on the server. Are there any DBAs there who might have that installed?
The SQL Scheduler is SQL Agent.
Did the services you stopped restart? If so, you can disable them. You can also uninstall SQL server, but if you do, make sure you only delete the default instance, not the named instance that Backup Exec is using.
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
April 16, 2008 at 3:05 am
I think I have sorted it now. I went into Data Sources (ODBC) in admin tools and the two SQL instances were in there. I deleted the one that was causing the trouble and the event logs stopped.
So fingers crossed it won't come up again!
Many thanks for your help 😀
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply