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

Failed to retrieve data for the request - Jobs SQL Server 2008

Hello all,
I created a Job on SQL Server 2008 to run a stored procedure ever 45 minutes for 3 days. The database itself is kept on SQL Server 2005 but I use 2008 to connect to it.
Once the job was created I then went to review the job and clicked the 'explode' icon beside SQL Server Agent.

Then when I clicked the 'explode' icon beside 'Jobs' after a short wait I got the error in the image below. From querying the tables involved it doesn't seem like the job is running which isn't a major issue. It's the fact that if the Job was creating a problem I'd have no way of terminating it.

The people on SQL 2005 don't see the job listed in their client consoles. However in 2005, the jobs are listed under the database whereas on 2008 they're listed under the Server. Neither I nor the others have SysAdmin rights on the database in question though we do on others on the network.

Can anyone help me to:
1. Fix it so I can review the job(s)
2. Suggest how I might delete the job?
10-08-19-ScrnShot-Job-Error-EE.JPG
0
Seamie_
Asked:
Seamie_
1 Solution
 
8080_DiverCommented:
The people on SQL 2005 don't see the job listed in their client consoles.
That would be because the job is actually on the SQL Server 2008 instance.
However in 2005, the jobs are listed under the database whereas on 2008 they're listed under the Server.
That really has no bearing on the issue . . . except that it can create a little bit of confusion in finding the job when you are looking for it.
Neither I nor the others have SysAdmin rights on the database in question though we do on others on the network.
This is the crux of the problem.  How did you get the job created on the SS2008 instance in the first place?  It may be that you didn't really get the job set up and/or enabled (which would be why it isn't running).  Since it isn't running on the 2008 instance, have you considered setting it up and running it on the 2005 instance?  (That may be aat least a short term solution.)  
Can anyone help me to:
1. Fix it so I can review the job(s)

You will need to get more advanced privileges.  (Unfortunately, I am a Development DBA and not an Admin DBA, so I always ask our Admin DBA to give me permissions to do [fill in the blank] and he does . . . but he doesn't tell me what they were. ;-) ]
2. Suggest how I might delete the job?  
You may need to ask the Admin DBA to delete it for you.
It's the fact that if the Job was creating a problem I'd have no way of terminating it.
That is an issue that would probably need to be addressed by a policy.  If the Admin DBA doesn't let you have permission to access the jobs and their history, then the Admin DBA has to accept responsibility for making sure that the jobs run and run correctly or that they get disabled and the appropriate developer notified so that the problem can be corrected.
Good luck.
0
 
Seamie_Author Commented:
Given the time limits on outstanding questions and with this being the silly-season (summer leave etc.) I can not test the suggestion currently. However, what has been written makes sense and follows along the same thoughts I had on the issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

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