Questions
General
-
Does SourceAnywhere for VSS trial have any limited
functionalities?
-
Is it necessary to reinstall SourceAnywhere for
VSS after purchasing?
-
What are the differences between Professional Edition and
Standard Edition?
-
Can SourceAnywhere for VSS Server be installed on a
machine different from the one with Visual SourceSafe database?
-
Is it necessary to install Visual SourceSafe (VSS) Client on
SourceAnywhere for VSS Server machine?
-
Is it necessary to install Visual SourceSafe (VSS) Client on
SourceAnywhere for VSS Client machine?
-
Can our local team still use Visual SourceSafe (VSS) and our remote team
use SourceAnywhere for VSS on the same database?
-
Can I run SourceAnywhere for VSS Client on Linux or
Mac?
-
Can I run SourceAnywhere for VSS Server on Linux or
Mac?
-
Which proxy types does SourceAnywhere for VSS support?
-
Can I use my network logon name to automatically log in
SourceAnywhere for VSS without a password?
Troubleshooting
-
Why can't SourceAnywhere for VSS service be started?
-
Why can't SourceAnywhere for VSS service be stopped?
-
Why do I get error message "Error connecting to
<IP> : <Port>" when connecting to SourceAnywhere for VSS Server?
-
Why do I get error message "Error opening
database<path to srcsafe.ini>" or "The SourceSafe database <path to
srcsafe.ini> does not exist. Please select another database." when
connecting to SourceAnywhere for VSS Server?
-
Why do I get error message "The client is not
compatible with the server" when connecting to SourceAnywhere for VSS Server?
-
Why do I get error message "File <path to
srcsafe.ini>not found" when I try to login?
-
Why do I get error message "Wrong username or
password" when I try to login?
-
Why do I get error message "The user
'<username>' is not configured in the Server..." when I try to login?
-
Why do I get error message "File does not exist? when
I try to get or view a file?
-
Why do I get error message "Socket is closed by
Server. Error creating local temp file" when I check in or add files?
How To
-
How to check the Logon User of SourceAnywhere for VSS Service?
-
How to check the Security setting of a Windows folder?
-
How to check the Share permission setting of a Windows folder?
- How
to determine the temp directory of SourceAnywhere for VSS server?
-
How to make sure SourceAnywhere for VSS server has
enough permission of the temp folder?
-
How to check SourceAnywhere for VSS Server Log?
-
How to input my serial number?
-
How to allow a Visual SourceSafe (VSS) user to access Visual SourceSafe (VSS) DB through
SourceAnywhere for VSS?
-
How to upgrade to newer version of SourceAnywhere for VSS?
-
How to set the port of SourceAnywhere for VSS server?
-
How to make SourceAnywhere for VSS work with NAT?
-
How to use SourceAnywhere for VSS for automated source
control processing?
-
How to find the "Visual SourceSafe (VSS) DB Analyze" tool?
-
How to configure
SourceAnywhere for VSS
to access a Visual SourceSafe (VSS) database
on another machine?
IDE Client
-
Which IDE integrations does SourceAnywhere for VSS
support?
-
Can I switch freely between SourceAnywhere for VSS and Visual
SourceSafe as SCC provider in Visual Studio IDE integration?
-
How to integrate SourceAnywhere for VSS with Visual Studio 2005?
-
How to integrate SourceAnywhere for VSS with Visual Studio 6.0/ Visual Studio .NET 2003?
Licensing
-
If I already have licenses, can I add more licenses later
when I need it?
-
If I have purchased
5-user serial number, do
I need another 5-user
serial number when I
want to increase the
number of users to 10?
Or do I just need to pay
for the price difference
between 5-user and
10-user serial numbers?
-
Can I use one SourceAnywhere for VSS serial number on more
than one SourceAnywhere for VSS server?
-
To use SourceAnywhere for VSS, do we need proportional number
of Visual SourceSafe licenses from Microsoft?
-
If I purchase SourceAnywhere for VSS Client licenses, do I
need to purchase the Server license or it is included?
-
Where should I input the serial number?
-
We need SourceAnywhere for VSS Professional Edition, but we
purchased the Standard Edition by mistake. What should we do?
Upgrading
-
How much do I need to pay for the upgrades?
-
How to upgrade to a new version of SourceAnywhere for VSS?
Answers
General
1. Does
SourceAnywhere for VSS trial have any limited functionalities?
No. SourceAnywhere for VSS trial is a full functional version
with 30-day trial period.
2. Is it
necessary to reinstall SourceAnywhere for VSS after purchasing?
No. After
purchasing, it is not necessary to reinstall the SAW. Inputting the permanent
serial number will activate the product.
3. What are
the differences between Professional Edition and Standard Edition?
The following table lists the major differences between
Professional Edition and Standard Edition:
|
Professional Edition
|
Standard Edition
|
Cross-Platform
|
Yes
|
No
|
Delta Transfer
|
Yes
|
No
|
Dreamweaver IDE Integration
|
Yes
|
No
|
Command Line Client
|
Yes
|
No
|
For more details about the differences, you can refer to:
http://www.dynamsoft.com/Products/SAW_EditionComparison.aspx.
4. Can
SourceAnywhere for VSS Server be installed on a machine different from the one
with Visual SourceSafe database?
Yes. It can be installed on a different machine from the one
with the Visual SourceSafe (VSS) database, as long as they are connected.
If you get an error message "Error opening database <path to
srcsafe.ini>", please click
here.
5. Is it
necessary to install Visual SourceSafe (VSS) Client on SourceAnywhere for VSS Server machine?
Yes. The SourceAnywhere for VSS Server uses the Visual SourceSafe (VSS) Automation
component (API), so the Visual SourceSafe (VSS) Client component must be installed on the server
machine with SourceAnywhere for VSS Server. Installing the Visual SourceSafe (VSS) Client
also installs the Visual SourceSafe (VSS) API.
6. Is it
necessary to install Visual SourceSafe (VSS) Client on SourceAnywhere for VSS Client machine?
No. The SourceAnywhere for VSS Client is independent so it is not
necessary to install Visual SourceSafe (VSS) Client on the machine.
7. Can
our local team still use Visual SourceSafe (VSS) and our remote team use SourceAnywhere for VSS on
the same database?
Yes. The co-existence of Visual SourceSafe and SourceAnywhere for
VSS is OK. SourceAnywhere for VSS Server behaves like another Visual SourceSafe
Client when it accesses the Visual SourceSafe database, so running
SourceAnywhere for VSS does not affect other Visual SourceSafe users.
Actually, this is the common scenario how our customers use
SourceAnywhere for VSS.
8. Can I
run SourceAnywhere for VSS Client on Linux or Mac?
Yes. SourceAnywhere for VSS Professional Edition has a Java
Client that can run on any platform where Java Virtual Machine can run,
including Windows, Linux, Mac, Solaris, AIX, HP-UX, SCO Unix, FreeBSD and so
on.
9. Can I
run SourceAnywhere for VSS Server on Linux or Mac?
No. SourceAnywhere for VSS Server must be installed on a Windows
machine.
10.
Which proxy types does SourceAnywhere for VSS support?
SourceAnywhere for VSS supports all the proxy types, including
SOCKS4, SOCKS5 and HTTP proxy.
11. Can I use my network logon name
to automatically log in SourceAnywhere for VSS without a password?
No. Even if the "Use Network Name For Automatic User Log In"
option is enabled in Visual SourceSafe (VSS), you still need to use the Visual SourceSafe username
and password to log in SourceAnywhere for VSS.
Troubleshooting
1. Why
can't SourceAnywhere for VSS service be started?
There are several possibilities. The SourceAnywhere for VSS
Server log file gives you valuable information for the troubleshooting. Please
check the log file first. For information about how to check the log file,
please click here.
Please verify the following items:
-
Verify the logged in user account has administrative right to start or stop
service
-
Verify that the TCP/IP is installed on the machine and is set properly.
-
Verify the Visual SourceSafe (VSS) Client is installed on the SourceAnywhere for VSS server
machine. It provides the Automation Component that the SourceAnywhere for VSS
Server uses to communicate with the Visual SourceSafe (VSS) database.
-
Verify that the SourceAnywhere for VSS Service Log On user has access to the
installation directory of SourceAnywhere for VSS Server. For information about
how to check the Log On user of a service, please click here.
2. Why
can't SourceAnywhere for VSS service be stopped?
The likeliest cause of this problem is that the current user does
not have administrative right to start/stop service.
3. Why do I get
error message "Error connecting to <IP> : <Port>" when I try to
connect to SourceAnywhere for VSS Server?
There are four possible causes of this problem. Verify the
following things:
-
Make sure the network connection between the SourceAnywhere
for VSS Server and Client is OK.
-
Make sure the Server IP you are connecting to is correct.
Please check if the IP address is listed in Server
Manager->ServerInfo->General Settings->Server IP.
-
If you have a firewall configured on the Server or Client,
please make sure the firewall does not block the port you specify in Server
Manager->ServerInfo->General Settings, as seen in the following figure
(click to view the full image):

-
If SourceAnywhere for VSS Server is installed on a Windows XP SP2 or Windows
Server 2003 SP1 machine, please check if Windows Firewall is enabled on this
server machine. If yes, it is likely the Windows Firewall is blocking
connections from SourceAnywhere for VSS Client. In this case, please add a
Windows Firewall exception for SourceAnywhere for VSS Service.
For SourceAnywhere for VSS 5 Professional Server, the path of SourceAnywhere
for VSS Service is "(system disk):\Program Files\DynamSoft\SourceAnywhere for
VSS 5 Professional Server\SAWService.exe". For information on how to add a
Windows Firewall exception, please
click.
4. Why do I get error
message "Error opening database <path to srcsafe.ini>" or "The SourceSafe
database <path to srcsafe.ini> does not exist. Please select another
database." when I try to connect to SourceAnywhere for VSS Server?
Troubleshooting of this problem depends on whether the
SourceAnywhere for VSS Server is installed on the same machine where the VSS
database resides.
If YES, please verify the following thing:
-
The Log On user of SourceAnywhere for VSS service should have read/write
permission of the Visual SourceSafe (VSS) directory.
For information about how to check the
Log On user of SourceAnywhere for VSS service, please click here.
If NO, please verify the following things:
-
If you specify a local user as the Log On user, please verify
this username also exists on the machine where Visual SourceSafe (VSS) database resides and the
passwords of these two users are identical. Meanwhile, you need to verify the
user on the Visual SourceSafe (VSS) machine has read/write permissions and read/change share
permissions of the Visual SourceSafe (VSS) directory.
Please click here for information about how to check
Security setting of a Windows folder, and click here to
see how to check Share Permissions setting of a Windows folder.
-
If you specify a domain user as the Log On user and
SourceAnywhere for VSS Server is installed in the same domain as the one
with Visual SourceSafe (VSS) database, please verify this domain user has read/write permissions
and read/change share permissions of of the Visual SourceSafe (VSS) directory.
-
No mapped driver letter is used to specify the path to
srcsafe.ini, since the mapped driver may not be available for SourceAnywhere
for VSS service.
If you map \\ServerName\ShareName to driver Z:, for example, you should use the
full network path \\ServerName\ShareName\SuorceSafe\srcsafe.ini to specify the
path to srcsafe.ini, rather than Z:\SourceSafe\srcsafe.ini.
5. Why
do I get error message "The client is not compatible with the server" when I
try to connect to SourceAnywhere for VSS Server?
There are two
possible reasons:
-
The versions of
SourceAnywhere for VSS Server and Client are different (or incompatible).
-
The editions of SourceAnywhere for VSS Server and Client are different.
SourceAnywhere for VSS has two editions: Professional Edition and
Standard Edition.
6. Why do
I get error message "File <path to srcsafe.ini>not found" when I try to
login?
The possible cause is that the Visual SourceSafe (VSS) database is corrupted. Run the
Analyze tool first to check the integrity of the Visual SourceSafe (VSS) DB. Please make sure to
backup the Visual SourceSafe (VSS) database before running the tool. For information about how to
find the "VSS Analyze tool", please click here.
7. Why do
I get error message "Wrong username or password" when I try to login?
There are several possible reasons for this problem. Please
verify the following things:
-
Verify the username and password are correct.
-
Verify the user exists in Visual SourceSafe (VSS). Please note adding a user to SourceAnywhere for
VSS does not create the user in Visual SourceSafe (VSS) database. It only specifies which user is
allowed to access Visual SourceSafe (VSS) database through SourceAnywhere for VSS Server.
-
Verify the Visual SourceSafe (VSS) database you are trying to log in is your desired database. The
path of the Visual SourceSafe (VSS) database can be configured in SourceAnywhere for VSS Server
Manager->Database, as seen in the following figure (click to view the full
image):

8.
Why do I get error message "The user '<username>' is not configured
in the Server..." when I try to login?
Please verify the following things:
-
The user has been added in SourceAnywhere for VSS Server Manager, as seen in
the following page (click to view the full image):

-
The status of this user is active.
-
After you added this user in Server Manager, you restarted SourceAnywhere for
VSS Service.
9. Why do I
get error message "File does not exist" when I try to get or view a file?
The possible cause is that the Visual SourceSafe (VSS) database is corrupted. Run the
Analyze tool first to check the integrity of the Visual SourceSafe (VSS) DB. Please make sure to
backup the Visual SourceSafe (VSS) database before running the tool. For information about how to
find the "Analyze VSS DB" tool, please click here.
10. Why do I get
error message "Socket is closed by Server. Error creating local temp file" when
I check in or add files?
The cause of this problem is that SourceAnywhere for VSS server does not
have read/write permission of the temp folder. For information about how to
make sure SourceAnywhere for VSS server has enough permission of the temp
folder, please click here.
How To
1. How to check the
Logon User of SourceAnywhere for VSS Service?
This setting is in Control Panel->Admin
Tools->Services->Dynamsoft SourceAnywhere for VSS
5->Properties->Logon tab, as seen
in the following figure:

2. How to
check the Security setting of a Windows folder?
Please follow steps below:
-
Right click the Windows folder and click Property
- In the Folder
Properties dialog box, select the Security tab, as seen in the following
figure:

3.
How to check the Share permission setting of a Windows folder?
4. How to
determine the temp directory of SourceAnywhere for VSS server?
The temp directory of SourceAnywhere for VSS server can be
specified in SourceAnywhere for VSS Server Manager->Server Info->General
Setting->Temp Path, as seen in the following figure (click to view the full
image):

If the temp directory is not specified, SourceAnywhere for VSS
server will use the default temp directory. The default temporary directory of
SourceAnywhere for VSS Server is the 'temp' folder under the installation
directory.
5. How
to make sure SourceAnywhere for VSS server has enough permission of the temp
folder?
Please follow steps below:
-
Determine the temp path of SourceAnywhere for VSS server. For
information about how to determine the temp path of SourceAnywhere for VSS
server, please click here.
-
Check the Log On user of SourceAnywhere for VSS Service. For
information about how to check the Log On user of SourceAnywhere for VSS
Service, please click here.
-
Check security setting of the temp folder. Make sure the Log On
user of SourceAnywhere for VSS Service has read/write permission of the temp
folder. For information about how to check the security setting of a Windows
folder, please click here.
6. How to
check SourceAnywhere for VSS Server Log?
The SourceAnywhere for VSS Server log file gives you valuable
information about the system. In many cases, you may need to consult the log
file.
The log file can be viewed from: SourceAnywhere for VSS Server
Manager->Server Info->System Log->View log, as seen in the following
figure (click to view the full image):

7. How to input my
serial number?
SourceAnywhere for VSS serial number can be input on the
server-side from SourceAnywhere for VSS Server
Manager->ServerInfo->Serial Numbers, as seen in the following figure
(click to view the full image):

8.
How to allow a Visual SourceSafe (VSS) user to access VSS DB through SourceAnywhere for VSS?
Please follow steps below:
-
Add the VSS DB in SourceAnywhere for VSS Server Manager, as seen in the
following figure (click to view the full image):

Add the Visual SourceSafe (VSS) user in SourceAnywhere for VSS Server Manager, as seen in the
following figure (click to view the full image):

Please note adding a user to SourceAnywhere for VSS does not
create the user in Visual SourceSafe (VSS) database. It only specifies which user is allowed to
access Visual SourceSafe (VSS) database through SourceAnywhere for VSS Server.
9.
How to upgrade to newer version of SourceAnywhere for VSS?
For the answer to this FAQ, please click here.
10. How to set the
port of SourceAnywhere for VSS server?
The ports through which the Server communicates with the Client
can be specified in SourceAnywhere for VSS Server
Manager->ServerInfo->General Settings, as seen in the following figure
(click to view the full image):

11. How to make SourceAnywhere
for VSS work with NAT?
To make SourceAnywhere for VSS work with NAT server,
- Configure the NAT server to map the public IP/port to SourceAnywhere for
VSS server IP/port.
- Set the default gateway of SourceAnywhere for VSS Server to the internal
IP of your NAT server.
- On SourceAnywhere for VSS Client, use the public NAT IP/port as the
SourceAnywhere for VSS IP/port. The NAT server will transfer all the packages
to your SourceAnywhere for VSS server.
For example, there are the following settings:
-
IP/port of your local SourceAnywhere for VSS server is 198.168.2.50:8877
-
Public IP of NAT server: 82.165.242.265
-
Internal IP of your NAT server: 192.168.2.2
-
Port for SourceAnywhere for VSS server on your NAT server: 8877
And you'll
need to make the following
configurations:
- Use NAT server to map
82.165.242.265:8877 to 198.168.2.50:8877.
- Set the default gateway of
SourceAnywhere for VSS Server to 192.168.2.2.
- In the Connect to Server dialog
box, fill in the public IP/port of NAT server as the SourceAnywhere for VSS
Server IP/port, as seen in the following figure:

12.
How to use SourceAnywhere for VSS for automated source control
processing?
You can write script to use SourceAnywhere for VSS Command Line
Client (provided by Professional Edition only) for automated source control
processing. SourceAnywhere for VSS Command Line Client supports all the
major operations.
13. How
to find the "VSS DB Analyze" tool?
The Analyze VSS DB tool can be found in the program group of
Visual SourceSafe (Start Menu->All Programs->Microsoft Visual
Studio->Microsoft Visual SourceSafe->Analyze VSS DB).
14.
How to configure SourceAnywhere
for VSS to access a VSS database
on another machine?
The path to VSS database can
be configured through the
Databases tab of SourceAnywhere
for VSS Server Manager, as seen
in the following figure (click
to view the full image):

If the VSS
database is located on a
different machine from the one
with SourceAnywhere for
server, the path to srcsafe.ini
should be a UNC pathname of the
shared VSS database, for
example, \\192.168.1.13\Shared\VSS\srcsafe.ini.
To avoid some common issues that
may occur during this
configuration, we recommend you
verify the following things
before configuring the Database
tab:
-
If you
specify a local user as the
Log On user, please verify
this username also exists on
the machine where VSS
database resides and the
passwords of these two users
are identical. Meanwhile,
you need to verify the user
on the VSS machine has
read/write permissions and
read/change share
permissions of the VSS
directory.
Please click
here
for information about how to
check Security setting of a
Windows folder, and click
here
to see how to check Share
Permissions setting of a
Windows folder.
-
If you
specify a domain user as the
Log On user and
SourceAnywhere for VSS
Server is installed in the
same domain as the one
with VSS database, please
verify this domain user has
read/write permissions and
read/change share
permissions of of the Visual SourceSafe (VSS)
directory.
-
No mapped
driver letter is used to
specify the path to
srcsafe.ini, since the
mapped driver may not be
available for SourceAnywhere
for Visual SourceSafe (VSS) service.
If you map \\ServerName\ShareName
to driver Z:, for example,
you should use the full
network path \\ServerName\ShareName\SuorceSafe\srcsafe.ini
to specify the path to srcsafe.ini, rather than
Z:\SourceSafe\srcsafe.ini.
IDE Client
1. Which IDE integrations
does SourceAnywhere for Visual SourceSafe (VSS) support?
SourceAnywhere for Visual SourceSafe (VSS) supports all MSSCCI compatible IDE integrations such as
Microsoft Visual Studio, Microsoft Visual Studio .NET, Borland JBuilder,
Borland Delphi and IBM Rational Rapid Developer.
Also, SourceAnywhere for Visual SourceSafe (VSS) Professional Edition supports DreamWeaver
integration.
2. Can I switch freely between
SourceAnywhere for VSS and Visual SourceSafe as SCC provider in Visual Studio
IDE integration?
Yes. But there is one exception:
In Visual Studio.NET, web projects must be created using Visual
SourceSafe. For these projects, you can freely switch between SourceAnywhere
for VSS and Visual SourceSafe.
If a web project is initially created using SourceAnywhere for
VSS, only Visual Studio.NET with SourceAnywhere for VSS Integration can load
the project. Visual Studio.NET with Visual SourceSafe Integration will not be
able to load the project.
3. How to integrate SourceAnywhere for VSS with Visual Studio 2005?
To integrate SourceAnywhere for VSS with Visual Studio 2005:
- Start Visual Studio 2005.
- Click menu Tools-> Options.
- Click the "Source Control" node in the left side tree.
- Choose "Dynamsoft SourceAnywhere for VSS" in the "Current source control plug-in" combo box, as seen in the following figure (click to view the full image):
4. How to integrate SourceAnywhere for VSS with Visual Studio 6.0/ Visual Studio .NET 2003?
To integrate SourceAnywhere for VSS with Visual Studio 6.0/ Visual Studio .NET 2003,
change the SCC provider to SourceAnywhere for VSS in SCC Provider Manager, which can be launched
from the program group of SourceAnywhere for VSS Client, as seen in the following figure:

Licensing
1. If
I already have licenses, can I
add more licenses later when I
need it?
Yes. You can purchase additional licenses and
add them in Server Manager. For information about how to input the serial
number, please click here.
For example, you purchased a 5-user serial number and now you need to add 2
additional licenses. In this case, you can purchase another 2-user serial
number and add them to SourceAnywhere for VSS. Thus, the total number of
permanent licenses becomes 7.
2. If
I have purchased 5-user serial
number, do I need another 5-user
serial number when I want to
increase the number of users to
10? Or do I just need to pay for
the price difference between
5-user and 10-user serial
numbers?
We take
the different order as the
separated one. You need to
purchase another 5-user serial
number rather than just pay for
the price difference.
3. Can
I use one SourceAnywhere for VSS serial number on more than one SourceAnywhere
for VSS server?
No. One SourceAnywhere for VSS serial number
can be applied on only one SourceAnywhere for VSS server, even if the users on
different SourceAnywhere for VSS servers are actually the same users.
4.
To use SourceAnywhere for VSS, do we need proportional number of Visual
SourceSafe licenses from Microsoft?
Yes. To use SourceAnywhere for
VSS, you must be a licensed user of Microsoft Visual SourceSafe. Please refer
to the Microsoft Visual SourceSafe license agreement for specific details.
However, if you already have a VSS license,
you do not need an additional VSS license to use SourceAnywhere for VSS.
5. If I purchase SourceAnywhere for VSS Client licenses, do I
need to purchase the Server license or it is included?
It is included. SourceAnywhere for VSS is licensed on a per user
basis. The Server does not take a license.
6. Where should I input the serial number?
SourceAnywhere for VSS licensing
is configured exclusively on the server-side from the Serial Numbers page of
the Server Manager, as seen in the following figure (click to view the full
image):

7. We need SourceAnywhere for VSS
Professional Edition, but we purchased the Standard Edition by mistake. What
should we do?
We provide upgrade to
SourceAnywhere for VSS
Professional Edition from same
version Standard Edition.
For details
about the upgrade, please purchase the
upgrade at SourceAnywhere for VSS purchase page:
https://www.dynamsoft.com/Secure/SAW_BuyIt.aspx
Upgrading
1. How much do I need to
pay for the upgrades?
We provide free upgrade from version 6.x to version 6.x.
Upgrade from previous versions can be ordered on the purchase page:
https://www.dynamsoft.com/Secure/SAW_BuyIt.aspx
2. How to upgrade to
a new version of SourceAnywhere for VSS?
To upgrade to a new version, please follow the steps in this article: