Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Master and Target-Server


Master and Target-Server

Author
Message
Rolando Peters
Rolando Peters
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
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
free_mascot
free_mascot
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3137 Visits: 2235
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."
Satish Nagaraja
Satish Nagaraja
SSC-Enthusiastic
SSC-Enthusiastic (196 reputation)SSC-Enthusiastic (196 reputation)SSC-Enthusiastic (196 reputation)SSC-Enthusiastic (196 reputation)SSC-Enthusiastic (196 reputation)SSC-Enthusiastic (196 reputation)SSC-Enthusiastic (196 reputation)SSC-Enthusiastic (196 reputation)

Group: General Forum Members
Points: 196 Visits: 308
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 :-)
Rolando Peters
Rolando Peters
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
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
Forrestsjs
Forrestsjs
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 105
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search