TM1 Forum

Hi,
on Windows 2008 R2 SP1 64-bit I have installed Cognos TM1 Server 10.1.1 and also TM1 Architect both from the same 64-bit installation file. After installation I opened IBM Cognos Configuration. In Local Configuration | Data Access | TM1 Server | right click | New resource | TM1 Server instance and type in my server name e.g. CubeServer. Click on CubeServer and set "TM1 Server configuration path" to ../samples/tm1/CubeServer and right click and Start. TM1 CubeServer directory was created with all default configuration files, tm1s.cfg is set-up, Windows service is up and running. So far no problem.

Then I did: Local Configuration | Environment | TM1 Admin Server | right click and Start. Info message displayed that TM1 admin server is registered and started, so error! Then I looked into Windows Services and I see IBM Cognos TM1 Admin Server x64 is created but stopped. I tried to start service, but I get error: "The IBM Cognos TM1 Admin Server x64 service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."

Any idea what is wrong? Why doesn't TM1 Admin start? Do I need to configure something else? In tm1_install\logs directory there is no error. Is there any log I can check for errors or something?
Thanks

Is that the error you are getting from the services GUI? Have you checked the logs in the event viewer? you can sometimes get more details from there.

Try the old fashion way of registering the TM1 Server as,
tm1sd.exe -install -n tm1server_name -z <location of the config dir>

Then start it. I had problems with all of my TM1 Servers not starting correctly because the GUI has "some issue" dealing with the config since they all use LDAP. The above method worked fine.

I had a similar error and found this: http://www-01.ibm.com/support/docview.w ... wg21607792

After a re-install it ran ok though the guy who did the original install swears he ran it as admin.

HTH,
Martin

I am 100% sure I installed TM1 as Administrator, because I am logged in as Administrator. There is no info in Windows Event Monitor. Now I have uninstalled TM1 and installed it again. Now in Cognos Configuration I have configured TM1 Admin Server first start it and then go to the TM1 Server settings. Everything is working fine.

I can't confirm this now, but reading through the Cognos Installation and Configuration Guide I found out what may be the problem at my first installation attempt: If I understand correctly what has happened at my first installation attempt is the following:
1. In Cognos Configuration I first configured Cognos TM1 Server and started the server. Because there was no TM1 Admin according to documentation Admin Server was automatically created and started.
2. When I tried to start TM1 Admin server it was most probably already started (because of step 1). Most probably trying to run on the same network port which is obviously not allowed.

So it looks like it is VERY IMPORTANT the order of configuring servers in Cognos Configuration!

Thanks for help and ideas. I hope this will help someone...
Regards

abcuser wrote:Because there was no TM1 Admin according to documentation Admin Server was automatically created and started.

And as part of your debugging you didn't check to see what processes were actually running on your machine?????? That's Troubleshooting 101.

I just came across it again after a re-install and successfully starting three instances. Adding a fourth instance failed. It appears to be because the admin server was running as an application. I'm not sure when this occurred. But from what I can gather this prevent the admin server running as a service, but the new instance (running as a service) didn't want to use the application version of the admin server.

I'm only 75% sure this is what the cause is. As is often the case with bug hunting I did various things including trying to start the admin server as an application. When it didn't pop up in the system tray I went looking for it and discovered it was indeed running, but I still couldn't start the new instance. Once I killed the application though I was able to start the admin server as a service and then run up my instance.

I'm sure tomok will also look down at me from his high horse for the same oversight as abcuser, but I believe (if my description is actually accurate) that the admin server starting as an application of its own volition after an install is unexpected or at the very least new behaviour in 10.1

I've just verified that this is the case. I did a server restart after Windows updates and one of my four TM1 services didn't restart. I tried manually restarting and got the error about a dependency not being able to start. I opened task manager and killed two instances of the admin server application. I was then able to restart the fourth instance which automatically kicked off the admin server service. The other three didn't require any attention - they didn't seem to notice their admin server application(s) had disappeared and happily switched over to the service.

Martin

I can also verify that 10.1.1 install doesn't automatically start the admin service. A bit annoying as you go to Cognos Configuration and try to start the admin service and it won't start. On one server I found this was because a TM1 admin application was running so kill with task manager then all fine. On another instance I found that the old admin service from 9.5.2 hadn't been removed and so the path was pointing to the old location (thanks IBM for changing the install location to root of "IBM"), this was a bit of a headache in the end I just deleted the old service with sc delete in cmd and found that Cognos Configuration will then automatically recreate the TM1 admin service with correct parameters - handy! It does something useful after all.

@abcuser: First start Cognos Admin Server then Excel Services then your Cognos Data Servers as a best practices. And for shutdown follow the reverse order.

Hi, Man

Yes, I have same problem. I can confirm that after killing the admin process in the task manager and start the admin service. All good.