How to troubleshoot Sybase SQL loop


  • Service provider loop
  • Unable to create name resolvers
  • Affecting all clients
  • Unable to connect to the system database.
  • SQL Loop
  • Sybase SQL Anywhere
  • Error: “An error occurred while attempting to open the selected database.”
  • The database was installed on a Member Server
  • Unable to launch the Client.
  • Cannot connect to the server
  • Unable to create name resolver
  • I start the service, select the server try to connect then the program shuts down.
  • Sybase anywhere
  • Client unable to connect after server reboot
  • Service is not running
  • Database upgrade
  • Will not start.
  • Fas.db is an asset database
  • Unable to launch client.
  • Sybase SQL Anywhere screen keeps looping after entering database path and parameters
  • Error: “Unable to connect to the system database. Please contact your system administrator” when launching Sage Fixed Assets client
  • New client install will not open.
  • Launching program freezes at initializing


Operating System Warning
This solution requires advanced knowledge of your computer’s operating system. Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions.


This is not an error, the Sybase SQL Anywhere dialog indicates the Sybase service is unavailable to the client.


Warning: The following requires Administrative access to the server where the Sage Fixed Assets – Depreciation Network was installed, and may require Administrative to the client system as well.
Note: The following contains the default installation and engine settings for a new installation of the service for Sage Fixed Assets – Depreciation Network version 2013.1 and above and assumes no other installations of the Sage Fixed Assets Network Server components exist on the network.
Is the engine running on the server?

  1. On the Server, go to Windows Start, Programs, Sage Fixed Assets, Tools, then right click the Database Utility – Network Depreciation & Tracking and select Run as administrator.
  2. Select Service Manager button.
    Note: If the service is running, Stopping then Starting the service may drop any ghost connections and allow the Clients to connect. See Article ID 16880: “How to clear ghost connections?”
    When running the Database Utility – Network Depreciation & Tracking, if the Sybase SQL Anywhere dialog appears again, the service is not running or no longer taking request. To start the Sage Fixed Assets Service, either user Administrative Tools\Services or run the service manager executable directly: In Windows Explorer browse to C:\SFAServ\Common\ then right click the fassvcmgr.exe and select Run as administrator
  3. In the Sage Fixed Assets Service Manager, ensure the following:
    • Check the Parameters, the default parameters are: -gp 4096 -ti 0 -tl 120 -gd all -n SFA_Engine
      Note: The -n parameter specifies the Engine Name being broadcast on the network. It can be set to anything without spaces or special character other than underscores
    • The Start up type is set to Automatic
    • The Logon account is LocalSystem
    • The Executable path is correct. The default is C:\SFAServ\Common\dbsrv16.exe. (Note: The path may vary based on selection made during the current or prior installations.)
  4. On the Share, ensure the following: The SYSTEM account, Administrators, and Fixed Asset Users have Full Control of the SFAServ share for both Sharing\Permissions and Security.
  5. The connection setting of the Database Utility – Network Depreciation & Tracking is the same as that of the remote client should use. To get these setting go to the Registry at HKEY_LOCAL_MACHINE\Software\wow6432node(for 64-bit machines)\Best Software\NWBESTSYS
    Write down the Data values for the following keys (include upper/lowercase letters to match exactly):

    • LOGICALNAME (verify that the path in LOGICALNAME correctly points to the BESTSYS.DB file)
    • Protocol: Use tcpip, and add the IP address of the server (without leading zeros)
  6. Lastly, Check the Windows Firewall in Control Panel on the server: If the Windows Firewall is on, enter exceptions Port 2638 for both Inbound and Outbound rules to allow the Sybase engine through the firewall. See Article ID 54275: “How to add firewall exceptions?”
  7. If the Server is Windows 2012 make sure the Network Awareness is turned On.

On the Client:

  1. In the Registry of the Client system go to: HKEY_LOCAL_MACHINE\Software\wow6432node(for 64-bit machines)\Best Software\NWBESTSYS, Enter in the values from the server for ENGINENAME, LOGICALNAME
    Note: The default and recommended connection path to the Bestsys.db is a Drive letter path connecting to the server. i.e. C:\SFAServ\BESTSYS.DB which is a server relative path: The C: is the C: where the dbsrv16.exe (the Sybase Engine) is running (see Executable path above)

  2. Check the Firewall on the Client: If the Windows Firewall is on, Enter exceptions Port 2638 for both Inbound and Outbound rules to allow the Client program through the firewall. See Article ID 54275: “How to add firewall exceptions?
  3. If the Sybase SQL Anywhere dialog appears again, select Next
  4. Select tcpip, Replace the X’s from {HOST=XXX.XXX.XXX.XXX} with the IP of the server, Select Finish.