***Log in Failed****
-
- Posts: 3
- Joined: Sun Jun 14, 2009 10:01 pm
- Version: 9.4 sp4
- Excel Version: 2003
***Log in Failed****
Hi, I'd like to ask if any of you , have had this error when entering TM1. can help me how to fix this problem
"Log in failed:SystemServerConnectionInvalid"
Hector Fabio
"Log in failed:SystemServerConnectionInvalid"
Hector Fabio
-
- Site Admin
- Posts: 6647
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: ***Log in Failed****
Are the client and server the same version?hector_fabio_s wrote:Hi, I'd like to ask if any of you , have had this error when entering TM1. can help me how to fix this problem
"Log in failed:SystemServerConnectionInvalid"
If not, you can encounter the error as described in the 9.4 "Read Me" release notes.
This thread may also be worth viewing:Incompatible Versions
Using a newer TM1 client with an older TM1 Admin Server and/or TM1 server is not a supported
TM1 environment. If you use TM1 Perspectives/Architect 9.4 with older TM1 servers, you will
experience unexpected behavior; the TM1 client may hang or not even open when started. If the
TM1 client does open, older servers may be listed in the Server Explorer, but the following error
displays when you try to log in: Log in Failed: SystemServerConnectionInvalid.
http://forums.olapforums.com/viewtopic. ... 009&p=5673
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-
- Posts: 3
- Joined: Sun Jun 14, 2009 10:01 pm
- Version: 9.4 sp4
- Excel Version: 2003
Re: ***Log in Failed****
Alan Kirk wrote:Are the client and server the same version? Yes the same versionhector_fabio_s wrote:Hi, I'd like to ask if any of you , have had this error when entering TM1. can help me how to fix this problem
"Log in failed:SystemServerConnectionInvalid"
If not, you can encounter the error as described in the 9.4 "Read Me" release notes.
This thread may also be worth viewing:Incompatible Versions
Using a newer TM1 client with an older TM1 Admin Server and/or TM1 server is not a supported
TM1 environment. If you use TM1 Perspectives/Architect 9.4 with older TM1 servers, you will
experience unexpected behavior; the TM1 client may hang or not even open when started. If the
TM1 client does open, older servers may be listed in the Server Explorer, but the following error
displays when you try to log in: Log in Failed: SystemServerConnectionInvalid.
http://forums.olapforums.com/viewtopic. ... 009&p=5673
-
- Site Admin
- Posts: 6647
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: ***Log in Failed****
Local server, or remote server?hector_fabio_s wrote:Yes the same versionAlan Kirk wrote:Are the client and server the same version?hector_fabio_s wrote:Hi, I'd like to ask if any of you , have had this error when entering TM1. can help me how to fix this problem
"Log in failed:SystemServerConnectionInvalid"
If it's a remote server, do you have the Admin Host setting (File -> Options in Server Explorer) pointing to the server that the Admin Host is running on? Have you checked that the Admin Host is in fact running correctly?
If it's a local server, have you tried restarting the Admin Host service? (This will also involve restarting the TM1 server.)
I've encountered some similar issues with a server running on my notebook after hibernation; not always, but occasionally. Restarting the services sorted it out.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
- Martin Ryan
- Site Admin
- Posts: 1989
- Joined: Sat May 10, 2008 9:08 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2010
- Location: Wellington, New Zealand
- Contact:
Re: ***Log in Failed****
I'll sometimes get this if my connection has timed out and kicked me off. Hitting F5 and sometimes restarting Excel will clear it if this is cause.
Martin
Martin
Please do not send technical questions via private message or email. Post them in the forum where you'll probably get a faster reply, and everyone can benefit from the answers.
Jodi Ryan Family Lawyer
Jodi Ryan Family Lawyer
-
- Posts: 3
- Joined: Sun Jun 14, 2009 10:01 pm
- Version: 9.4 sp4
- Excel Version: 2003
Re: ***Log in Failed****
OK. The error is generated in both local and remote servers and the Admin Host is running correctly. We will try the services sorted it out
- BigDSter
- Posts: 55
- Joined: Thu May 15, 2008 8:02 am
- OLAP Product: TM1
- Version: 9.4.1
- Excel Version: 2007
- Location: Preston
Re: ***Log in Failed****
Hmmm, weird.
Just testing 9.4 MR1 FP1 32 bit on a 64 bit virtual server to see if we can migrate to that soon.
Mostly working okay apart from the odd quirk, but have just hit a problem that I've seen 3 times now.
When the server is restarted through the service everything looks okay in the log, and internal chores that are active are running, according to the log, but tm1top can't connect to it, and when you try and connect through 9.4 MR1 FP1 Architect then it just does nothing.
If I try and connect through my current 8.4.5 client then the password dialog pops up but after entering details and hitting okay you get
"Login Failed: SystemServerConnectionInvalid"
If you then look in the server log everything looks fine apart from this message appearing occasionally.
772 ERROR 2009-12-07 09:54:51.104 TM1.ClientMessage Could not read message header.
2768 ERROR 2009-12-07 09:55:06.869 TM1.ClientMessage Could not read message header.
1228 ERROR 2009-12-07 09:57:48.521 TM1.ClientMessage Could not read message header.
1484 ERROR 2009-12-07 09:57:52.521 TM1.ClientMessage Could not read message header.
1948 ERROR 2009-12-07 09:57:56.209 TM1.ClientMessage Could not read message header.
304 ERROR 2009-12-07 10:01:16.969 TM1.ClientMessage Could not read message header.
I've tried restarting the service and it still does it, but I have had it working, both with the correct client, and through 8.4.5
Strange
**** note there is no admin service set up, just the internal one that TM1 launches for itself.
Just testing 9.4 MR1 FP1 32 bit on a 64 bit virtual server to see if we can migrate to that soon.
Mostly working okay apart from the odd quirk, but have just hit a problem that I've seen 3 times now.
When the server is restarted through the service everything looks okay in the log, and internal chores that are active are running, according to the log, but tm1top can't connect to it, and when you try and connect through 9.4 MR1 FP1 Architect then it just does nothing.
If I try and connect through my current 8.4.5 client then the password dialog pops up but after entering details and hitting okay you get
"Login Failed: SystemServerConnectionInvalid"
If you then look in the server log everything looks fine apart from this message appearing occasionally.
772 ERROR 2009-12-07 09:54:51.104 TM1.ClientMessage Could not read message header.
2768 ERROR 2009-12-07 09:55:06.869 TM1.ClientMessage Could not read message header.
1228 ERROR 2009-12-07 09:57:48.521 TM1.ClientMessage Could not read message header.
1484 ERROR 2009-12-07 09:57:52.521 TM1.ClientMessage Could not read message header.
1948 ERROR 2009-12-07 09:57:56.209 TM1.ClientMessage Could not read message header.
304 ERROR 2009-12-07 10:01:16.969 TM1.ClientMessage Could not read message header.
I've tried restarting the service and it still does it, but I have had it working, both with the correct client, and through 8.4.5
Strange
**** note there is no admin service set up, just the internal one that TM1 launches for itself.
David Newton
Burtons Foods
Burtons Foods
- BigDSter
- Posts: 55
- Joined: Thu May 15, 2008 8:02 am
- OLAP Product: TM1
- Version: 9.4.1
- Excel Version: 2007
- Location: Preston
Re: ***Log in Failed****
Doh, might have something to do with this
MaximumViewSize=2048
posted into the server config rather than the client one ... silly me, working fine again now.
MaximumViewSize=2048
posted into the server config rather than the client one ... silly me, working fine again now.
David Newton
Burtons Foods
Burtons Foods
- BigDSter
- Posts: 55
- Joined: Thu May 15, 2008 8:02 am
- OLAP Product: TM1
- Version: 9.4.1
- Excel Version: 2007
- Location: Preston
Re: ***Log in Failed****
Getting very frustrated with 9.4.1 FP1 now. This client message error
TM1.ClientMessage Could not read message header.
now seems to occur whenever I try to even connect to the server with either the 9.4.1 FP1 Architect or my 8.4.3 Client. As soon as this happens the server is unusable by any user.
Don't know if it's because it is on a virtual machine, but I've not disabled all external chores, so only internal ones run.
Might have to test it out on a physical bit of tin next because I don't know what to do next, completely unusable at the minute.
TM1.ClientMessage Could not read message header.
now seems to occur whenever I try to even connect to the server with either the 9.4.1 FP1 Architect or my 8.4.3 Client. As soon as this happens the server is unusable by any user.
Don't know if it's because it is on a virtual machine, but I've not disabled all external chores, so only internal ones run.
Might have to test it out on a physical bit of tin next because I don't know what to do next, completely unusable at the minute.
David Newton
Burtons Foods
Burtons Foods
- BigDSter
- Posts: 55
- Joined: Thu May 15, 2008 8:02 am
- OLAP Product: TM1
- Version: 9.4.1
- Excel Version: 2007
- Location: Preston
Re: ***Log in Failed****
Well we seemed to have fixed that now. What seemed to be the error was that I'd set ClientMessagePortNumber (a new config field I'd not paid much attention to) to the same as PortNumber
Guaranteed to screw any server up it's set on.
Least it wasn't the virtual machine that was the issue, and I can get back to testing fully again!
Guaranteed to screw any server up it's set on.
Least it wasn't the virtual machine that was the issue, and I can get back to testing fully again!
David Newton
Burtons Foods
Burtons Foods
Re: ***Log in Failed****
Have you checked that the port referred to in the CFG file is open?