TM1 as a service

[jonathan.d]

Hi,

I am trying to run TM1 as a service using the help files.

After creating the service, I try to start it from services.msc, but it keeps throwing me an error saying...

Error 1068: The dependency service or group failed to start.

I am guessing the dependency is TM1 Admin Server. However, that's already running!

Any ideas?

Thanks!

[Alan Kirk]

Hi,

I am trying to run TM1 as a service using the help files.

After creating the service, I try to start it from services.msc, but it keeps throwing me an error saying...

Error 1068: The dependency service or group failed to start.

I am guessing the dependency is TM1 Admin Server. However, that's already running!

Any chance you can post the command that you used to crate the service, and a copy of your tm1s.cfg file?

[jonathan.d]

Hi Alan,

#Command

tm1sd.exe -install -n ABC -z C:\Path\Data


# cfg file

[TM1S]
ServerLogging=F
SecurityPackageName=Kerberos
IntegratedSecurityMode=2
ServerName=ABC
DataBaseDirectory="C:\Path\Data"
LoggingDirectory="C:\Path\Logging"
AdminHost=
PortNumber=410045
Language=ENG
PerformanceMonitorOn=F
UseSSL=F
Maximumcubeloadthreads=1


Hope this helps...

[Alan Kirk]

[TM1S]
ServerLogging=F
SecurityPackageName=Kerberos
IntegratedSecurityMode=2
ServerName=ABC
DataBaseDirectory="C:\Path\Data"
LoggingDirectory="C:\Path\Logging"
AdminHost=
PortNumber=410045
Language=ENG
PerformanceMonitorOn=F
UseSSL=F
Maximumcubeloadthreads=1

You don't have the AdminHost specified in the config file. According to the 9.1 help file, it's a required entry. I don't think that the server will assume that it should look on the same box as the server is running on for a running admin host. Try specifying the server name in that parameter and see whether it makes a difference.

Also, your PortNumber looks invalid. Valid numbers are 5001 to 49151.

[jonathan.d]

I did make the necessary changes.

Had
Admin Host=the server name (did not work)
and,
Admin Host=computer's ip (did not work)

When trying to start either 'Admin Server' as a service or the 'Server'..they gave the same error message about ".....dependency service failed to start".

Not sure why...

[Alan Kirk]

I did make the necessary changes.

Had
Admin Host=the server name (did not work)
and,
Admin Host=computer's ip (did not work)

When trying to start either 'Admin Server' as a service or the 'Server'..they gave the same error message about ".....dependency service failed to start".

Not sure why...

Hmmm, interesting. But didn't you initially say that the Admin Host was running? But from what you're saying above, you're getting the same error when you try to start that.

OK, next thing; take a look at the server's logs and see whether they yield any clue. (Assuming that you're using Windows; which O/S are you using exactly?)

On the server, right click on the My Computer icon and select Manage, then select Event Viewer, and take a look at the three categories (Application, Security and System) to see whether there are any messages relating to the failure to start the service. Often there will be something relevant there.

I'm assuming that the login that you're using has either admin rights or the necessary permissions to run the services. I noticed that you didn't specify a Windows user name and login when you installed the service so it's presumably running under LocalSystem; I've had problems with that in the past, though they're usually connected with network permissions rather than with starting the service initially.

Anyway, it would be useful to know what the server log messages say.

Also take a look at the tm1smsg.log files to see whether they yield anything useful. (They probably won't if the server isn't starting at all, but it can't hurt to look.)

[jonathan.d]

I finally got it working.

Rebuilt the service.
Changed the "log on as" for the server to match the admin server.
Started them both up.

But the problem was as you predicted, and had to do with permissions.

Thank you heaps Alan!

[paulsimon]

Jonathan

Glad you got the problem resolved but I think that the root cause is in your original command

Code: Select all

tm1sd.exe -install -n ABC -z C:\Path\Data

You are missing the parameters for the Service logon. This should be something like.

"C:\Program Files\Cognos\TM1\bin\tm1sd" -install -nABC -zC:\Path\Data -uDomain\ServiceUser -wServiceUserPwd

Where

Domain is the Domain Name of the Service User eg MOUSE
ServiceUser is the Service User Id eg TM1User
ServiceUserPwd is the Service User Password eg Secret1

Regards

Paul Simon

[jonathan.d]

Thanks Paul!

The fact that I had to change the "log on as" in the services dialog means it's required to specify username and password when using the tm1sd command.

Wish the help files said it was required and not optional.


Thanks again!

[Alan Kirk]

Thanks Paul!

The fact that I had to change the "log on as" in the services dialog means it's required to specify username and password when using the tm1sd command.

Wish the help files said it was required and not optional.

That's because it's NOT required. If it was required the service wouldn't have installed at all. As I said, running under an Administrator login the services run quite well as local services, but they sometimes had issues with network access. Had those services been accessing the server's local hard drive only, it wouldn't have made any difference. In your case, though, I'm guessing that the local service access wasn't sufficient.

As you've found, even if you omit the login and password when you perform the service installation it's still quite possible to change the login that the service uses via the Services list in the management console.

[Suharsh]

Hello Friends,

I am facing an issue with installing an Instance as a service. I am using a Windows 7 Machine and installed Windows XP mode over it to work with a TM1 9.5

Now when I am trying to create a service for this instance, it is not giving any error, but not creating the instance as well.

It keeps saying "StartServiceCtrDispatcher" being called, but does not create the service.
Plz see the below screenshot.

Service Install Issue.jpg (60.36 KiB) Viewed 13154 times

Please advise me on the issue

Thanks

[tomok]

If you are installing anything on Windows 7 you have to run the install program as an Admin. In this case, you have to open the CMD windows as Admin and then key in the commands.

[Suharsh]

The CMD is running on Windows XP. As I said I have installed a virtual machine (Virtual PC XP Mode) on my windows 7 machine, from the below link

http://www.microsoft.com/windows/virtua ... nload.aspx

So I guess in XP it not required to run as administrator.

[Suharsh]

Has anybody got any suggestions to offer on the above mentiones issue......

[Alan Kirk]

Has anybody got any suggestions to offer on the above mentiones issue......

Just that if you have Win 7 Ultimate I wouldn't even bother with XP mode. Although not a supported environment (but then neither is XP...) I've had no problems running 9.5.x servers directly on it as long as they're installed on an Admin account.

10.x is a different matter; servers seem fine though Web isn't working right. Since that was purely a test environment (and not a Web test environment) I haven't chased that one down.

[Suharsh]

Thanks for the informatin Alan. But I think I should try reinstalling the XP Mode onto my Win7 machine as it is not working out for me (may be because of compatibility issues). I have though successfully installed this version of TM1 onto Win XP (When I was using XP Earlier), but not sure why this issue came up in the XP Virtual Machine, as the Virtualization concept itself tells that the Virtual machine layers will be Abstacted from base machine.

Lets see, I will update if I find anything intersting this time.....

Let me know if anyone has any inputs