Cannot view Job properties in SQL 2005 Ent x64

For some reason, I can't view/modify the properties of the Jobs I have created.  I get the following error:  

TITLE: Microsoft SQL Server Management Studio
------------------------------

Enumerate target servers failed for Job 'DB Index - V2 - User - Tables'.  (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.4035.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Enumerate+target+servers+Job&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

------------------------------

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Cannot perform this operation while SQLServerAgent is starting. Try again later. (Microsoft SQL Server, Error: 14258)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.4053&EvtSrc=MSSQLServer&EvtID=14258&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------


This server is in a clustered environment.  I have restarted the SQL Agent service, but that did not help.  The SQL Agent is started though.  Anyone have a good solution for this issue?  Or need more information?
Chicot_ParkerAsked:
Who is Participating?
 
Chicot_ParkerAuthor Commented:
Ok, I forgot to update this the other day.  It seems that the issue was caused by a database being in 'Recovery Mode'.  I can't necessarily confirm that was the cause, but coincidentally, soon after the database that was in Recovery Mode finished recovering, I was able to view/modify my jobs.  Now this database has been giving us problems, and had been in recovery mode before, and we haven't had issues with the jobs.  But for some reason, it decided to give us problems this time.  Maybe it can be explained, maybe not, but I'm able to view those jobs, and I got rid of the database that was in 'Recovery Mode'.

Thanks for all your suggestions.
0
 
Aaron ShiloChief Database ArchitectCommented:
1.) Using Cluster Administrator, change the SQL Network Name to the new name.

2.) Take the network name resource offline. This takes the SQL Server resource and other dependent resources offline as well.

3.) Bring the SQL Server resource back online.


with many thanks to -Tom Kretzmer

0
 
Chicot_ParkerAuthor Commented:
What do you mean by "new name" in step 1?
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Aaron ShiloChief Database ArchitectCommented:
change the virtual server name

Instructions are at http://msdn2.microsoft.com/en-us/library/ms178083.aspx
0
 
Chicot_ParkerAuthor Commented:
Not to discredit your possible solution, but how will renaming the virtual server name fix this issue?  Also, we are replicating the data via DoubleTake to the other server in the 2-node cluster.  Both of these nodes have their on SAN.  The link you provided states that this will not work if replicating.    
0
 
Aaron ShiloChief Database ArchitectCommented:
>>but how will renaming the virtual server name fix this issue?
Well your not the first with this problem.

>>The link you provided states that this will not work if replicating.
true , i didnt know your using replication BUT you can rebuiled the replication after the change.
0
 
Anthony PerkinsCommented:
>>Well your not the first with this problem.<<
No doubt.  That is why the author is posting the question in the first place.  But I suspect what they are asking for is a reason or even better some documentation to backup your solution.
0
 
Aaron ShiloChief Database ArchitectCommented:
you make me laugth :-)

read this thread
http://www.sqlservercentral.com/Forums/Topic364622-149-1.aspx
0
 
Chicot_ParkerAuthor Commented:
Well your not the first with this problem.
You are correct about that, but I also know that there is probably another, less evasive, solution.

 
But I suspect what they are asking for is a reason or even better some documentation to backup your solution.

Correct.  

There is a business application that runs in the front end that depends on this cluster, and arbitrarily renaming clusters is really out of the question, unless, this is the ONLY way to fix this issue, my gut tells me it is not, in which case, I would like to know how you came to this assumption.
0
 
Aaron ShiloChief Database ArchitectCommented:
hi

ofcourse i understand your problem .

from reading other posts with a similar problem to yours.
i understand that taking other paths upto reinstalling sql server didnt work.

please let us know how you resulved this issue.
i wish you best of luck.
0
 
Anthony PerkinsCommented:
Excellent!  Please go ahead and close the question, by accepting your comment as the solution.
0
 
Chicot_ParkerAuthor Commented:
The issue resolved itself.
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.

All Courses

From novice to tech pro — start learning today.