April 22, 2009 at 4:55 am
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
April 22, 2009 at 5:01 am
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."
April 22, 2009 at 5:06 am
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 🙂
April 23, 2009 at 4:35 am
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
September 28, 2011 at 12:05 pm
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.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply