Tuesday, January 3, 2017

Cannot start Tigerpaw tsiTimers service after moving database to new server

We are using the Tigerpaw CRM software (v 12.1.08). After moving the Tigerpaw database to a new server, I was unable to restart the required tsiTimers service. Checking the Windows Event Logs, I found that the problem was that the service was immediately terminating because it detected evidence that a copy of the service was running on another computer:

Error starting service tsiTimers
Error in routine: StartService
This service is running on another machine

It turns out that unless the service is stopped and the database is shut down before migrating it to a different server, values referencing the name of the original server remain in the database, so when the new instance of the service starts it believes the old server is still running.

More specifically, the database contains a table named tblSysServiceStatus. In my case that table contained just two rows, both of which contained the old server name in the column "MachineName". The old server name was FUJIV1; the new server name is WHITE. A quick SQL statement put things to right:

UPDATE  tblSysServiceStatus
SET MachineName = 'WHITE'  WHERE  MachineName = 'FUJIV1';

Once I committed the above change, I was able to restart the tsiTimers service successfully.

2 comments: