| Author |
Upgraded EAS to 5.3, Can't connect to EAServer Manager
|
|
| AJ Rodriguez 2006-03-05, 8:42 pm |
| I recently upgraded from EAServer 4.2 to 5.3 but now I can't connect to
EAServer Manager. Keep getting "Connection Refused" message. Is there a
way to reset security outside of EAServer manager? I know I am using the
correct server listner and port number.
| |
| Peter Abbott 2006-03-05, 8:42 pm |
| Connection Refused would imply that the server is not running or you are
trying the wrong hostname. If it is a security issues the message you
was see is something along the lines of "invalid username/password"
At the start of the jaguar log it will say what is being use to start
the listeners up with. Sometimes you will find that EAS cant listen on
the hostname you define and fallback to localhost, so maybe give
localhost a go as well.
You should check the jaguar log file first if you havent done so
already, but in the Jaguar.props file there is a property for the
jagadmin password that you can delete the value from and if you are
using JAAS there is a couple of jaas related properties in the same file.
Pete
AJ Rodriguez wrote:
> I recently upgraded from EAServer 4.2 to 5.3 but now I can't connect to
> EAServer Manager. Keep getting "Connection Refused" message. Is there a
> way to reset security outside of EAServer manager? I know I am using the
> correct server listner and port number.
>
>
| |
| Jim Egan 2006-03-05, 8:42 pm |
| aw_rodriguez@cox.net wrote...
> I recently upgraded from EAServer 4.2 to 5.3 but now I can't connect to
> EAServer Manager. Keep getting "Connection Refused" message. Is there a
> way to reset security outside of EAServer manager? I know I am using the
> correct server listner and port number.
Make sure Jaguar is really running. There is a file that I think the name is
jaguar_boot.log. It will contain the boot info when EAS tries to start. I had a client
that performed the upgrade from 5.0.0 to 5.2. The easclient.jar and easserver.jar files
somehow got whacked during the upgrade so the server wouldn't start. The regular
jaguar.log file was not getting updated when we started the service but the jaguar_boot.log
file did. The solution was to apply the upgrade again.
--
Jim Egan [TeamSybase]
Sybase product enhancement requests:
http://www.isug.com/cgi-bin/ISUG2/submit_enhancement
| |
| Chris Pollach 2006-03-05, 8:42 pm |
| AJ;
Are you using the "machine name" or "localhost" in your connection
parameters?
Thanks ... Chris
"AJ Rodriguez" <aw_rodriguez@cox.net> wrote in message
news:44064e81$1@foru
ms-2-dub...
> I recently upgraded from EAServer 4.2 to 5.3 but now I can't connect to
> EAServer Manager. Keep getting "Connection Refused" message. Is there a
> way to reset security outside of EAServer manager? I know I am using the
> correct server listner and port number.
>
>
| |
| AJ Rodriguez 2006-03-05, 8:42 pm |
| I tried both the machine name and "localhost".
I was trying to connect through my company's Virtual Private Network (which
used to work using 4.2). But it looks like that does not work anymore. But
I was able to connect fine when I was directly connected to the company
network.
I guess I won't be doing that from home anymore...
A.J.
"Chris Pollach" <cpollach@travel-net.dot.com> wrote in message
news:44070ad9@forums
-1-dub...
> AJ;
>
> Are you using the "machine name" or "localhost" in your connection
> parameters?
>
> Thanks ... Chris
>
>
> "AJ Rodriguez" <aw_rodriguez@cox.net> wrote in message
> news:44064e81$1@foru
ms-2-dub...
>
>
| |
| Chris Pollach 2006-03-05, 8:42 pm |
|
Weird ... sounds like a VPN issue vs EAS Driver.
"AJ Rodriguez" <aw_rodriguez@cox.net> wrote in message
news:4407e960$1@foru
ms-1-dub...
> I tried both the machine name and "localhost".
>
> I was trying to connect through my company's Virtual Private Network
(which
> used to work using 4.2). But it looks like that does not work anymore.
But
> I was able to connect fine when I was directly connected to the company
> network.
>
> I guess I won't be doing that from home anymore...
>
> A.J.
>
> "Chris Pollach" <cpollach@travel-net.dot.com> wrote in message
> news:44070ad9@forums
-1-dub...
a[color=darkred]
the[color=darkred]
>
>
| |
| Jim Egan 2006-03-08, 8:25 pm |
| aw_rodriguez@cox.net wrote...
> I tried both the machine name and "localhost".
If you are connecting through the network then localhost isn't going to work. It will only
work when you are at the server trying to connect JagMgr to a service running at at that
same machine.
>
> I was trying to connect through my company's Virtual Private Network (which
> used to work using 4.2). But it looks like that does not work anymore. But
> I was able to connect fine when I was directly connected to the company
> network.
>
> I guess I won't be doing that from home anymore...
Do you have the right listeners set up for Jaguar? Post what you have and we should be
able to tell if they are right or not. For a PC on the network to connect the service must
listen either using the IP address or the machine name.
--
Jim Egan [TeamSybase]
Sybase product enhancement requests:
http://www.isug.com/cgi-bin/ISUG2/submit_enhancement
|
|
|
|