Errors in application event log

This section describes error messages that might be displayed in the application event log.

<server> unable to connect to master <TMS master>

Logged every 5 minutes while master can't be reached.

Verify that TMS is running on the TMS Master Server.
- TMS Master is configured through TMS and can be verified in TMS. See Configuring the TMS Server.

In the Windows Registry, check the MasterServer value in:

32-bit:


HKLM\Software\TeaLeaf Technology\TLMgmtSrv

64-bit:


HKLM\Software\Wow6432Node\TeaLeaf Technology\TLMgmtSrv

If the TMS Master Server is the same server hosting the Portal, set this value to localhost.

Check rest of error message for information.

Check rest of error message for more information.

Check rest of error message for more information.
This error may be encountered when reinitializing the data store from the command line.
- You can manually reinitialize the data store. See Configuring the TMS Server.

Check rest of error message for more information.
Most likely encountered on slave - error sending data to master.
Most likely you must delete data store on slave, which then reloads from the master.

Check rest of error message for more information.

On TMS Master - either server was renamed or TMS Master server name was entered incorrectly.
In Windows Registry, check MasterServer value in HKLM\Software\TeaLeaf Technology\TLMgmtSrv for correct server.
Reinitialize data store using TLMgmtSrv -reinit command.

May occur if TMS was uninstalled and then reinstalled without removing the old TMS data store (Tealeaf\System\TMSStore directory).
Reinitialize data store to fix.
- See Configuring the TMS Server.