Checking Pinned Status causes files to appear in System32

[aseyer]

We have are running the latest version of Source Offsite (4.1.2), and have a problem where files are appearing in our windows\system32 folder.

We have managed to root cause this to only occur to files that this message occurs:

6/18/2006 11:13:34 PM - 9: Enter GetFileList()
6/18/2006 11:13:34 PM - 9: Ignore remote dates = False
6/18/2006 11:13:34 PM - 9: GetFileList project:
6/18/2006 11:13:34 PM - Enter PinStatus()
6/18/2006 11:13:34 PM - File *might* be pinned.
6/18/2006 11:13:34 PM - Exit PinStatus()
6/18/2006 11:13:34 PM - Enter PinStatusConfirm()
6/18/2006 11:13:34 PM - File is NOT currently pinned...it can be checked out.
6/18/2006 11:13:34 PM - Exit PinStatusConfirm()
6/18/2006 11:13:34 PM - 9: Exit GetFileList()
6/18/2006 11:13:34 PM - 9: Time to execute: 0 minutes, 0 seconds, 328 milliseconds.

Anytime PinStatus is called(), files appear in the c:\windows\system32 folder. Please advise remedy.

[lbauer]

This is a known issue, which will be fixed in our next release.

When SOS tried to determine if a file was pinned, it gets the
file through the Automation Component and writes it to the SOS
Server Service account's temp directory. In the case of the SYSTEM
account, that is the System32 directory.

We have fixed this in the code, but it won't be out until the next
release, probably this summer.

In the meantime, the workaround is to use a different account for the
SOS Server service and to deny that account Write access to System32. This configuration is in Control Panel->Admin Tools->Services->SourceOffSite Server->Properties->Logon.

[aseyer]

Are there any rights this account needs to have? Can it be a normal user (non admin) with read/write access to the source safe databases? Will this account need a source safe account?

[lbauer]

The account does not need a VSS user account, but it does need read/write access to the location of the VSS database and the srcsafe.ini file.