Dynamsoft Forums

The system that the SourceAnywhere service is installed on is not part of a domain. We have VSS respositories on 5 different systems. Some of these systems are part of one of our many NT domains, some are not part of any domain.

Due to this configuration, we are unable to access all of our VSS repositories due to security requirements on each of the systems hosting our VSS repositories (meaning the actual network share). We can work around this for some systems by setting a specific user account for the SourceAnywhere service to run as, but that does not solve the problem we were trying to solve with SourceAnywhere. Are there any known work arounds for this situation? If not, are there any plans to allow setting differet user credentials for each network share that the SourceAnywhere service would be accessing? Making use of the LogonUser API for this would be pretty straight forward...

Hi iwebdev,

In your case, on every system where VSS repository resides, you need to create a local user with exactly the same user name and password as the Log On user account for SAW Service. Also, this user on each system should have enough permission to access to the VSS directory.

This should solve the problem.