TM1 Upgrade issues

[tomago]

Hi we are currently running TM1 9.1 SP3 (32bit), Production -TM1, Development - SData

We are trying to upgrade to TM1 9.4 and having some issues.
Installation is succcessfull, but the new tm1 Pdata doesn't start. I delete the service, and recreate pointing to cfg file. this starts the service, and i see the tm1server log generate comments.
at the end of startup i am left with this
124 INFO 2012-02-09 23:08:04,795 TM1.Server TM1 Server is ready

I used to see in the other logs it would mention, notifying admin server. Is that the older version or do i have a problem?
When i try and connect to server via client, here is the error - Cannot connect to TM1 Admin Server

Please help

[Alan Kirk]

Hi we are currently running TM1 9.1 SP3 (32bit), Production -TM1, Development - SData

We are trying to upgrade to TM1 9.4 and having some issues.
Installation is succcessfull, but the new tm1 Pdata doesn't start. I delete the service, and recreate pointing to cfg file. this starts the service, and i see the tm1server log generate comments.
at the end of startup i am left with this
124 INFO 2012-02-09 23:08:04,795 TM1.Server TM1 Server is ready

I used to see in the other logs it would mention, notifying admin server. Is that the older version or do i have a problem?
When i try and connect to server via client, here is the error - Cannot connect to TM1 Admin Server

I can't recall what 9.4 wrote into the logs. (And if you're going through the pain of an upgrade anyway, I'd suggest 9.5.2 since it'll give you a longer support window, but I digress.)

However here are some random thoughts:
- Is the Admin Server actually running?
- More to the point, is it running on the server that you have specified in the AdminHost parameter of your TM1S.cfg file?
- What are the port numbers of the various services that you have running?
- Is there any chance that you have duplicated port numbers somewhere?
- Is your client software specifying the correct Admin Host?

I'd start by checking the answers to all of those questions.

[tomago]

Hi we are currently running TM1 9.1 SP3 (32bit), Production -TM1, Development - SData

We are trying to upgrade to TM1 9.4 and having some issues.
Installation is succcessfull, but the new tm1 Pdata doesn't start. I delete the service, and recreate pointing to cfg file. this starts the service, and i see the tm1server log generate comments.
at the end of startup i am left with this
124 INFO 2012-02-09 23:08:04,795 TM1.Server TM1 Server is ready

I used to see in the other logs it would mention, notifying admin server. Is that the older version or do i have a problem?
When i try and connect to server via client, here is the error - Cannot connect to TM1 Admin Server

I can't recall what 9.4 wrote into the logs. (And if you're going through the pain of an upgrade anyway, I'd suggest 9.5.2 since it'll give you a longer support window, but I digress.)

However here are some random thoughts:
- Is the Admin Server actually running?
- More to the point, is it running on the server that you have specified in the AdminHost parameter of your TM1S.cfg file?
- What are the port numbers of the various services that you have running?
- Is there any chance that you have duplicated port numbers somewhere?
- Is your client software specifying the correct Admin Host?

I'd start by checking the answers to all of those questions.

we don't want to go straight to 9.5.2 as it is the newest and still some bugs around.

Admin server is running, Services show that
AdminHost is set correctly
Port number is 12345 - this is configured for production and development
client software is pointing to new host yes.
both production and development have no issues

[Alan Kirk]

Hi we are currently running TM1 9.1 SP3 (32bit), Production -TM1, Development - SData

We are trying to upgrade to TM1 9.4 and having some issues.
Installation is succcessfull, but the new tm1 Pdata doesn't start. I delete the service, and recreate pointing to cfg file. this starts the service, and i see the tm1server log generate comments.
at the end of startup i am left with this
124 INFO 2012-02-09 23:08:04,795 TM1.Server TM1 Server is ready

I used to see in the other logs it would mention, notifying admin server. Is that the older version or do i have a problem?
When i try and connect to server via client, here is the error - Cannot connect to TM1 Admin Server

I can't recall what 9.4 wrote into the logs. (And if you're going through the pain of an upgrade anyway, I'd suggest 9.5.2 since it'll give you a longer support window, but I digress.)

However here are some random thoughts:
- Is the Admin Server actually running?
- More to the point, is it running on the server that you have specified in the AdminHost parameter of your TM1S.cfg file?
- What are the port numbers of the various services that you have running?
- Is there any chance that you have duplicated port numbers somewhere?
- Is your client software specifying the correct Admin Host?

I'd start by checking the answers to all of those questions.

we don't want to go straight to 9.5.2 as it is the newest

Not any more it ain't.

and still some bugs around.

And you think that 9.4 doesn't???

Also any bugs that you encounter in 9.4 will now be met with a single sentence from IBM Support.

"Upgrade to 10.1".

Admin server is running, Services show that
AdminHost is set correctly
Port number is 12345 - this is configured for production and development
client software is pointing to new host yes.
both production and development have no issues

You say that "Port number is 12345 - this is configured for production and development". If that's the case then they can't be running using the same Admin Server. If you have two sessions which have the same port number on the same Admin host, one of 'em ain't gonna work. Which raises the question of what the pData service's port number is, and which admin server / admin host it's pointing to. You can't use 12345 for everything.

[tomago]

we have production server running tm1
we have development server running sdata

and 3rd server running pdata

3 different machines running their own instance, so no issues with conflicting ports.

[Alan Kirk]

we have production server running tm1
we have development server running sdata

and 3rd server running pdata

3 different machines running their own instance, so no issues with conflicting ports.

And you're certain that the tm1s.cfg file for pData is pointing to the Admin Server on its own machine, not to one of the others?

Are you pointing the client's Admin Host to ONLY the pData server, or do you have it pointing to multiple Admin Hosts?

Have you tried proxying on to the pData server and trying to connect from there?

[Alan Kirk]

we have production server running tm1
we have development server running sdata

and 3rd server running pdata

3 different machines running their own instance, so no issues with conflicting ports.

And you're certain that the tm1s.cfg file for pData is pointing to the Admin Server on its own machine, not to one of the others?

Are you pointing the client's Admin Host to ONLY the pData server, or do you have it pointing to multiple Admin Hosts?

Have you tried proxying on to the pData server and trying to connect from there?

Also, if you have the Admin Host specified as the machine name in the client, have you tried using the IP address instead? (Or, less likely, vice versa though I recall someone mentioning that had worked for them before.)

[tomago]

Hey Alan

Here is the config file
[TM1S]
ServerName=pdata
SecurityPackageName=Kerberos
#SecurityPackageName=NTLM
IntegratedSecurityMode=2
PasswordSource=LDAP
#LDAPUseServerAccount=T
UseSSL=T
DataBaseDirectory="D:\Tm1s7\TomagoData"
LoggingDirectory="D:\Tm1s7\TomagoData log"
AllowSeparateNandCRules=T
AdminHost=TACBUD04
PortNumber=12345
Protocol=TCP

MaximumLoginAttempts=10

LDAPPort=636
LDAPHost=domain.com.au
LDAPWellKnownUserName="cn=Tm1service,ou=Service-Accounts,ou=All-Users,dc=domain,dc=com,dc=au"
LDAPWellKnownPassword=applix04
LDAPSearchBase="ou=All-Users,dc=domain,dc=com,dc=au"
LDAPSearchField=sAMAccountName

if the cfg file is wrong, the service doesn't start, and it starts fine.

what do you mean proxy onto the pdata server, try using the client from the server to connect to its pdata?
tried that same problems

are there any tests i can try to find errors?

[Gregor Koch]

ServerName=pdata
AdminHost=TACBUD04
PortNumber=12345

Is pdata running on TACBUD04?
Does any of you other cfg files the same Adminhost and Portnumber like the one you have posted?

if the cfg file is wrong, the service doesn't start, and it starts fine.

Really? You can easily have typos in cfg files, which means the setting will not be changed, and the server will still start fine. So how do you define "wrong" in that context?

what do you mean proxy onto the pdata server, try using the client from the server to connect to its pdata?
tried that same problems

Uhm, are you asking what that means?
proxy onto the pdata server = remote desktop to the machine which is running the pdata TM1 server.
Or have you tried it already?

Have you actually tried not to use port 12345 (some firewalls are not very friendly with this one).

Best you post the other cfg settings so they can be compared.

[tomago]

rather than continue this route with the first road block being the version, i have upgraded to 9.5.2
Installed on the server, default settings.
services running, and log tells me
1356 [] INFO 2012-02-10 02:27:10.812 TM1.Server Notifying the Admin server

Try and connect from the server client to the servers instance of default Sdata and no luck

I have looked into the etldap side of things, as i am checking to make sure this is ok. when i check the TM1 Login test
80: SystemServerClientNotFound

[tomago]

more information
i have the client on my machine, and when trying to connect, i was getting - Cannot connect to TM1 Admin Server


I have gone through errors found and ini files etc and managed to resolve this. ended up being an SSL error to do with the old applix location, couldn't find applixca.pem

anyways, now i click connect, get to the Connect to TM1 Server box
select my server ID - sdata
enter my AD credentials, and error is
N6) Client not registered