TM1 Forum

Hi All,

Windows services

When we are trying to start the server services, it is throwing error 32.
We deleted and created the server services again, but no success.


Application Services

When we are running it as an application services, it is running fine.


Error seems to be very simple, but we are unable to find out where exactly file is being used and which one.
Thanks in advance

You should check that no other TM1 instance (either application or Windows service) is trying to access the tm1s.log file that lives in the logging directory of the instance you are trying to start. Check the different tm1s.cfg files for conflicts - if no logging directory is specified then tm1s.log will live in the data directory.

It may also be a security issue with the account the service is running on? Not sure that the error messages are that accurate.

Hi rmackenzie,

Thanks for your reply,
There is only one .cfg file on server. It used to run properly thru windows services, but all of a sudden started giving error 32.

Hi Steve,

Thanks for response,
Previously it was running fine with same service account. So I feel there shouldn't be security issue with respect to service account.

Regards,
Deepak Jain

Check to see whether there is any anti-virus or anti-spyware tool running on the Server, in particular if either tool has an 'On-Access' scanner.

Process Explorer shows you information about which files processes have opened or loaded.
· Download Process Explorer from the Microsoft site ( http://technet.microsoft.com/en-us/sysi ... 96653.aspx ) and run the program.
· Click the Find menu, and choose Find Handle or DLL...
· Type the file name (name of the file which is locked by some process.)
· After typing the search phrase, click the Search button
You should see the list of applications which are accessing the file.

Hi Friends,

Still no success. Can someone pls help.

Regards,
DJ

You can try some third party tools like Lock Hunter or Unlocker and run them against the logging directory to see if anything has a hold of the log file. Have you checked permissions to the data and logging directories as states by other users above?