I have an SQL Server 2008 R2 Environment in wich im implemented a MSX/TSX Configuration. I have one MSX Instance and two TSX Instances. However all works fine but I noticed in the Errorlogs of the TSX SQL Server Agents that there is a record wich says following:
Date 07.02.2012 12:48:29
Log SQL Server Agent (Current - 07.02.2012 12:48:00)
 Unable to open or read TSX cache file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSTANCE0\MSSQL\JOBS\TSXCACHE.BIN' (win32 error code: 2)
When I go to the given Location I cant see a file with this name. Also I found nothing usefull so far in the internet or microsoft forums.
If anybody has a solution or informations please let me know it would be very usefull.
Thank you. Peace Luca
- 已编辑 Luca Müller 2012年2月7日 17:17
We can help you out.
Did you ever receive an answer to your question? We are experiencing a similar problem and not having much luck finding an answer.
No luck so far. No Answers or tipps or anything. I guess we have to wait. Strange thing is that my msx/tsx environment is working without any problems, so no maintenance plans or job (of course multi-server) that are crashing or something.
So can you help me out please? Or can you give some hints or adives?
2012年2月23日 6:24I also have this. My theory is that this is a file used while Agent is running, but which is deleted when agent stops. And this is why the file isn't there at startup. I.e., that message tools like a bug to me. Just a theory, though. Did you report this at connect? IF not, consider doing that and post back here so we also can vote. (My MSX environment is at my client's site.)
Yes your theory sounds very plausible but my agents are running for a week now and no file is there on either of the servers. So the problem is to find out when SQL Server Agent creates this file... But I will post the issue in a seperate Supportcase by Microsoft because as a silver platform partner you have a cretain ammount of support cases. If I got an answer I will post it back here. Have a nice day. Peace Luca
Can you report this issue to SQL feedback https://connect.microsoft.com/sqlServer/feedback
Sethu Srinivasan [MSFT]
2012年11月27日 22:00I have this problem occasionally. In our case, the answer is to reset the perms on this folder to inherit from the parent so taht the sql service/or at least your agent service has rights to it. Typically, if you use a domain user/un privileged acct as your service user, there are some cases where a few perms on the SQL install have to be set. In our environment for consistency, we use GPOs to enforce folder perms for the SQL locations. However, during a SP apply or if your perms aren't quite right in the first place, the SQL installer edits the perms on this folde to be restrictive(it has tended to do this on the DATA folder too). If you are using GPOS as it our case, the inheritance flags perhaps a little more limited when using a GPO may not be working exactly the way you want. Essentially, it is a permissions problem, and you just need to make sure your service acct has rights all the way down to this folder. You probably have to check it after you apply a SP also. An oddly, like some others said, it continues working it seems despite the constant error so I'm not sure what that cache file really does.