Page 1 of 1

Remote server error

Posted: Mon Sep 28, 2009 7:15 am
by glaurens
We are busy setting up various replication servers around Africa and something weird is happening.

When I try to connect to the star server from the planet location as admin I get the message "user does not have permission to browse selected server". Initially I thought that the star couldn't communicate with the planet and that could possibly be the source of the strange message but when I connect using the wrong password I get "Client password is incorrect" (as expected).

This leads me to believe that communication takes place from the planet to the star and from the star to the planet, but I don't understand why I'm getting the "user does not have permission to browse selected server" message when connecting as admin. We aren't using integrated login yet, so at least that is not part of the problem.

Has anybody ever received this error or have some ideas?

Tx

G

Re: Remote server error

Posted: Mon Sep 28, 2009 8:02 am
by Steve Vincent
check the IP/machine names in the config files of both the planet and the star. they need to be registered on the same admin server for replication to work and although the error message doesn't say it, that could be your issue.

Re: Remote server error

Posted: Mon Sep 28, 2009 11:34 am
by glaurens
Hi Steve,

Both IPs are in both cfg files in the correct order, etc. However, I'm not at the replication stage yet and I'm only trying to connect to the star server via Perspectives. Below is what has been sent to IBM, but I hope somebody here will be able to help me sooner:


We are experiencing a situation where Perspectives on a planet server can see the star server (lmalawi). However, when we try to login to the star server (lmalawi) from the planet server using the admin account, we get a message ‘The user doesn’t have permission to browse the selected server’. We can connect to the star server (lmalawi) when using Perspectives locally. We’ve tested the ports 5498 and the server’s port number using telnet and were able to connect from planet to star and from star to planet.

What I find odd, is that in the first screenshot below (taken during a login attempt from the planet (10.121.33.49) to the star server (10.17.0.80)), tm1top on the star server shows the admin user connected, but after a few seconds, it disconnects and the resulting message on the planet server can be seen (second screenshot).

We are using TM1 9.4 SP1 HF2 x64.
1&2.JPG
1&2.JPG (161.36 KiB) Viewed 6081 times

Re: Remote server error

Posted: Tue Sep 29, 2009 1:25 pm
by mattgoff
Anyone know if port 5495 deprecated for 9.1 and later? Or is it still used as part of the negotiation process? Whenever I need to transit a firewall, I always ask for 5495, 5498, and the server port to be opened.

Matt

Re: Remote server error

Posted: Wed Sep 30, 2009 10:14 am
by glaurens
Uninstalled FP2 client and reinstalled FP1 client. Now it is working.

Thanks for the suggestions and Matt, I guess that proves that 5495 is not required anymore.

Tx

G

Re: Remote server error

Posted: Wed Mar 17, 2010 1:33 pm
by jstrygner
Just to add a little in this topic, I experienced the same issue with 9.4.1 FP2 ("User does not have permission to browse the selected server." after giving valid login and password and "Client's password is invalid" after giving valid login with wrong password). I was trying to connect from WinXP Client to AIX 9.4.1 Server.

Downgrade to pure 9.4.1 (without any FPs) also fixed the problem in my case, but installing FP3 took me back where I was with the FP2 :-(

Regards.

Re: Remote server error

Posted: Thu Jul 22, 2010 5:13 am
by thejohnsta
I just upgraded TM1 Perspectives on my own computer to 9.4.1 FP3 and got that same error. What I found however is that I only get the error when trying to login to TM1 instances on our DEV environment - logging into PROD is fine. Eventually, I realised it was because 9.4.1 FP3 hasn't been applied to our DEV TM1 server yet (I used a dedicated server to test the patch prior to deploying to PROD environment).

Thought I'd post incase this helps others too.