Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Master and Target-Server Expand / Collapse
Author
Message
Posted Wednesday, April 22, 2009 4:55 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 4, 2010 10:18 AM
Points: 3, Visits: 25
Hi all

I created a Maintenance-Plan on a Master-Server and deployed this plan to serval Target-Server. At the definded Target-Server I could see the deployed Maintenance-Plan and this Job and all works fine.

Well, at one Target-Server i can see just the deployed Job but not the deployed Maintenance-Plan and when I start his Job its quit with an error:

"Unable to open or read TSX cache file 'E:\MSSQL.5\MSSQL\JOBS\TSXCACHE.BIN' (win32 error code: 2)"

The Master-Server is:
SQL Server 2005, SP3

Target-Server are:
SQL Server 2005, SP3

Has someone an idea?

Regards
Roland

Post #702201
Posted Wednesday, April 22, 2009 5:01 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, July 21, 2014 2:56 AM
Points: 2,603, Visits: 2,061
Looks like permission problem or the file is used by some other process:

Are you able to access the location 'E:\MSSQL.5\MSSQL\JOBS\' from the other server?


---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Post #702206
Posted Wednesday, April 22, 2009 5:06 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 4:57 AM
Points: 168, Visits: 271
If this specific to one target server only, try the steps below

- Try creating dummy plan and check if you are getting the same error message.
- Also check if the account from which you are creating this plan is a valid windows account on the server and is part of sysadmin in SQL server.
- If all the above holds good, you want to start of again try the link below to delete the existing jobs and later recreate it again.
http://gudenas.com/2007/04/20/sql-server-2005-delete-maintenance-plan-error/

Sat


Cheer Satish
Post #702208
Posted Thursday, April 23, 2009 4:35 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 4, 2010 10:18 AM
Points: 3, Visits: 25
Hello Grasshopper

Thanks a lot for your answer. You are my hero! It works fine!

The reason was that the creater of the Maintenance-Plan was not member of Sysadmin-Role.


Have a nice day.
Best Regards

Roland
Post #703023
Posted Wednesday, September 28, 2011 12:05 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 21, 2014 2:21 PM
Points: 6, Visits: 96
Just to confirm. I have been having similar issues enlisting targets and subsequently pushing master jobs to the targets.

When adding the service account for the target to the master server logins, the documentation seems to indicate all it needs is Connect SQL and membership in the "targetserversrole" in the master server msdb database.

This does not seem to be the case.
I can only enlist targets if I make the target server service account a sysadmin on the master server instance.
Also, I can seemingly only push new jobs to the target if the targer server service accoutn is a sysadmin on the master server instance.

I tried just granting view server state instead of full sysadmin, but that does not work. There must be a few more perms necessary. I hope someone at MS can eventually clarify what rights are needed by the target service account so that we do not have to keep adding the target server service accounts as sysadmin on the critical master server.
Post #1182726
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse