There are multiple places where the database PC name and service PC name need to be specified properly for everything to work right. Usually the Service PC name is the same as the Database PC name, but since the Enterprise edition has the option of installing the service on a different PC, that's not always the case.

 

The Wasp MobileAsset Windows Service is the component that the mobile devices (Windows Mobile/CE, Android, iOS) use to communicate to the database. The MobileAssetWindowsService.exe.config file contains the settings that correspond to the PC client's License Server and Server registry entries.

 

MobileAsset client software settings registry path:

64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wasp Technologies\MobileAsset\Options

 

If a mobile device is giving connection errors, the service's configuration file is probably (but not always) the problem, not the device.

 

Path to the service's configuration file:

64-bit Windows: C:\Program Files (x86)\Wasp Technologies\MobileAsset\Services\MobileAssetWindowsService.exe.config

32-bit Windows: C:\Program Files\Wasp Technologies\MobileAsset\Services\MobileAssetWindowsService.exe.config

 

	Database PC	Service PC
Standard edition registry	Server: DB PC name\instancename example: SERVER01\WASPDBEXPRESS	License Server: same as DB PC example: SERVER01
Professional edition registry	Server: DB PC name\instancename	License Server: same as DB PC
Enterprise edition registry	Server: DB PC name\instancename example 1: SERVER01\WASPDBEXPRESS example 2: SERVER01\SQLPROD example 3: SERVER01	License Server: Service PC name example 1: SERVER01 example 2: APPSERV02
Mobile device's Service URL		http://ServicePCname:10008
Mobile device's service.config file		Lines 3 & 4: Service PC name
MobileAssetWindowsService.exe.config	Line 10: Data Source=DBPCname\instancename	Lines 24 & 32: <add baseAddress="http://ServicePCname:10008...
WaspConfig database, application_databases table, db_server_name column	DB PC name\instancename