Before You Begin

• You need administrator access on both the server and workstation.
• Verify that no other computer on the network is running a Sybase engine with the same engine name. Duplicate engine names can cause connection conflicts.
• Use Citrix or Terminal Services for supported WAN or VPN connections.

On the Server

Verify the Sage Fixed Assets Service

1. Open Start > Programs > Sage Fixed Assets.
2. Right-click Database Utility - Network Depreciation & Tracking and select Run as administrator.

If the error appears when opening the Database Utility, the Sage Fixed Assets Service is either not running or accepting requests. Start the service manually:

1. Browse to C:\SFAServ\Common.
2. Right-click fassvcmgr.exe.
3. Select Run as administrator.
4. Open Service Manager and verify the service is running.

If the service is already running, stop and restart it to clear any ghost connections.

If the error continues on the server:

1. Click OK and then Next.
2. Change the startup parameter host value to 127.0.0.1.
3. Click Finish.

Example: {HOST=127.0.0.1} -ga -qi

Verify Service Configuration

In Sage Fixed Assets Service Manager, verify the following settings:

Parameters

-gp 4096 -ti 0 -tl 120 -gd all -n SFA_Engine

The -n parameter defines the engine name broadcast on the network. You can use any name that doesn’t contain spaces or special characters other than underscores.

Startup Type

Automatic

Logon Account

LocalSystem

Executable Path

Default location:

C:\SFAServ\Common\dbsrv17.exe

The path is different if you selected a custom installation folder.

Verify Folder Permissions

On the SFAServ share, grant Full Control permissions to:

• SYSTEM
• Administrators
• Fixed Asset Users

Apply permissions to both Sharing and Security settings.

Verify Registry Values

1. Open Registry Editor.
2. Browse to:

HKEY_LOCAL_MACHINE\Software\WOW6432Node\Best Software\NWBESTSYS

1. Record the values for:
   • ENGINENAME
   • LOGICALNAME

You’ll use these values to verify client settings.

Verify install.cfg

Open C:\SFAServ\install.cfg and confirm the following match the registry exactly:

• Enginename matches ENGINENAME.
• BESTSYS matches LOGICALNAME.
• PROTOCOL = TCPIP.
• PARAMETERS contains the server IP address.

Example:

Enginename=SFA_Engine
BESTSYS=C:\SFAServ\BESTSYS.DB
PROTOCOL=TCPIP
PARAMETERS={HOST=xxx.xxx.xxx.xxx} -ga -qi

Repair the Client Installation

Run a repair installation on the affected workstation after verifying the server configuration.

Verify Firewall Settings

If you have the Windows Firewall enabled on the server, create inbound and outbound rules for TCP port 2638.

On the Client

Verify Registry Values

1. Open Registry Editor.
2. Browse to:

HKEY_LOCAL_MACHINE\Software\WOW6432Node\Best Software\NWBESTSYS

1. Verify that ENGINENAME and LOGICALNAME exactly match the values on the server.

Use the server's local path for the database location. Don’t use a mapped drive or UNC path.

Example:

C:\SFAServ\BESTSYS.DB

Verify Firewall Settings

If you have Windows Firewall enabled on the workstation, create inbound and outbound rules for TCP port 2638.

Update the Connection Information

If the Sybase SQL Anywhere dialog appears:

1. Click Next.
2. Select TCPIP.
3. Replace the host value with the server's IP address.
4. Click Finish.

Example:

{HOST=xxx.xxx.xxx.xxx}

Sage Fixed Assets Network 2024.1

A known issue affects some Sage Fixed Assets Network 2024.1 installations.

If the troubleshooting steps above don’t resolve the issue, install the workstation DLL update. See Unable to open the Database Utility or connect remote clients - Network 2024.1. This fix applies only to version 2024.1.