• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3537
  • Last Modified:

SQL Server Agent will not start Websense ETL job

I recently reinstalled our Websense filtering service. The filtering is working properly, but the reporting is not. I'm pretty sure this has something to do with our SQL Server Agent job not starting. The error from the Event Viewer is listed below. I've been unable to find any resources to help me with this.
Event Type:	Warning
Event Source:	SQLSERVERAGENT
Event Category:	Job Engine 
Event ID:	208
Date:		4/9/2009
Time:		10:52:40 AM
User:		N/A
Computer:	APPSERVER
Description:
SQL Server Scheduled Job 'Websense_ETL_Job__wslogdb63' (0xC0CE31BEF891124AA1DFC9D01C2EDC07) - Status: Failed - Invoked on: 2009-04-09 10:52:40 - Message: The job failed.  The Job was invoked by Schedule 3 (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.

Open in new window

0
leviatdr
Asked:
leviatdr
  • 5
  • 5
1 Solution
 
Jim P.Commented:
Open up the SQL Server Management Studio and log into the SQL Server that this job is on. Drill down to the SQL Server Agent --> Jobs --> Websense_ETL_Job__wslogdb63 job.

Right click and go into the Properties. Go to Steps and then Edit. In the Edit window, hit the Parse button.
0
 
leviatdrAuthor Commented:
I do not have Jobs as one of the sub-folders of the SQL Server. The options are: Databases, Security, Server Objects, Replication, Management. I am using SQL Server Management Studio Express. Do I need to install a different piece of software?

Screenshot attached.
SQL-Screenshot.png
0
 
Jim P.Commented:
Your image indicates that you are running SQL Server 2000 SP3/SP3a.  Even some MS consultants I talked to said that SP3 should never have been released. You may want to get to SP4.

You should have a SQL Server Agent icon below the Management entry in the left pane. That means that either you are running MSDE (SQL 2000 Express) or that the SQL Server Agent is not installed or disabled. (You can check if disabled in the services.msc console.)

If it is MSDE, then I'm not sure what the answer is. I've never used it.

How do I know which version of SQL Server I'm running?
http://sqlserver2000.databases.aspfaq.com/how-do-i-know-which-version-of-sql-server-i-m-running.html

Microsoft SQL Server 2000 Service Pack 4
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5&displaylang=en
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Jim P.Commented:
>> I've never used it.

I mean never used Websense.
0
 
leviatdrAuthor Commented:
8.0.760.0 = SQL Server 2000 SP3 / SP3a 1

This instance of SQL is installed as part of Websense. I'm afraid that changing the version of SQL might cause the other applications in Websense to stop working.
0
 
Jim P.Commented:
You might want to take a look at the link below. The note says:

Note
You can upgrade to SQL Server without detaching the Log Database. Read the section on Upgrading from MSDE to SQL Server in the Websense Enterprise Reporting Installation Guide .
---------------------------------------------
Known issues - database
http://www.websense.com/docs/releasenotes/v6.3.1/WSE_Reporting_ReleaseNotes.htm#0_pgfId-2377618
0
 
leviatdrAuthor Commented:
I installed SQL Server Management Studio through the SQL Server 2008 Evaluation and folowed the steps to parse the Job. The Job parsed sucessfully The command in the failing job is "EXEC dbo.USP_ETL_DRIVER" and the Run As: is blank.

I verified that the dbo.USP_ETL_DRIVER exists. I'm still very lost.

Anything else I can look at to get more information?
0
 
leviatdrAuthor Commented:
I think I figured it out. The failing job is Websense_ETL_Job__wslogdb63. But I changed the database to newlogdb63. So the old one doesn't exist anymore, causing this error. I've disabled the wslogdb63 jobs and my event log is clear. This still doesn't fix the original problem. Let me know if this sounds correct.
0
 
leviatdrAuthor Commented:
This error resulted from old jobs left over from the old transaction database. I didn't do a complete uninstallation before reinstalling.
0
 
Jim P.Commented:
The jobs and such are kept in the MSDB database. Apparently when you re-installed the Websense, it saw the jobs as existing in the MSDB and  didn't update them.

I've seen similar things happen with other applications that schedule its own jobs.

Glad to be of assistance. May all your days get brighter and brighter.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now