Unable to start TM1 application service after VM patch update

[karthik.g]

Hello Guys,

We are experiencing a serious issue in our production environment.
TM1 application service is in stopped state after a patch upgrade in VM and we are not able to start application service from windows services.
when we try to start we are getting an error message saying

windows could not start the IBM Cognos TM1 application server on local computer. For more information, review the system event log.

In the event log, we can see

The IBM Cognos TM1 application server service entered the stopped state

In the error log, we see

The IBM Cognos TM1 application server service terminated with the following service-specific error:
The operation completed successfully

Another issue we had is unable to launch Cognos configuration as well.

Tried below solutions but it didn't work:

· Restored the VM backup before the patch upgrade and tried restarting the application server. Except application service all the other TM1 services are started and running fine.
· Stopped and tried restarting all TM1 services but still unable to start application server.
· Found locked files under Configuration folder & deleted (cogstartup.lock) but still unable to launch IBM Cognos configuration
· Tried some IBM recommended solutions but still it didn’t work out.
· Changes made in tm1s.cfg files (In ServerCAMURI removed fully qualified server name to simple server name)
· Ensure that the server name is correct in the .model and .security files in path: \tm1_64\webapps\pmpsvc\WEB-INF\applications
· Tried to reconfigure a new default instance for pmpsvc service by removing the adminhost value in tm1_64\webapps\pmpsvc\WEB-INF\configuration\fpmsvc_config.xml.

Are we missing something here? Any help is much appreciated!!

Thanks

[declanr]

I know it wont be the answer you want but are you in a position to do an uninstall/reinstall?
Sometimes when things go wrong and its not quickly obvious as to why; the best thing can be to do a reinstall instead of wasting time trying to rectify something that may never happen again... now after that; if it does happen a second time - you would know that any time spent investigated is worthwhile.

[karthik.g]

I know it wont be the answer you want but are you in a position to do an uninstall/reinstall?
Sometimes when things go wrong and its not quickly obvious as to why; the best thing can be to do a reinstall instead of wasting time trying to rectify something that may never happen again... now after that; if it does happen a second time - you would know that any time spent investigated is worthwhile.

Thanks Declanr. The reinstallation solved the issue but wouldn't know what had caused this issue.