What do you see when you do a JAVA -SHOW at the server console?

Also, try unloading (BESTOP) and then reloading (BESTART) to see if
this helps. It might also be worth trying a different windows
workstation to see if this is a problem on the admin client.

"Chris" wrote:
>What do you see when you do a JAVA -SHOW at the server console?
>
I see the following:

Classname
ID
================================================ =============
vrts.hro.net.rmi.server.ServerMain................ ........................
571
org.apache.catalina.startup.Bootstrap............. ......................
458
org.apache.catalina.startup.Bootstrap............. ......................
466

Total Running: 3

>Also, try unloading (BESTOP) and then reloading (BESTART) to see if
>this helps. It might also be worth trying a different windows
>workstation to see if this is a problem on the admin client.

I have tried BESTOP & BESTART to see if that helped & it didn't. Right now
I have a backup running still so, I need to wait until that finishes.

Thank you for getting back to me.

That looks ok to me. Do you see any errors on the 'Backup Exec Java
Application Server' screen when you attempt to connect using the admin
console?

"Chris" wrote:
>That looks ok to me. Do you see any errors on the 'Backup Exec Java
>Application Server' screen when you attempt to connect using the admin
>console?

Now that you mention it I forgot to check there & yes I am seeing some interesting
items there. These are the messages that are popping up:

Logout Unsuccesful STATUS: false
Logout Unsuccesful STATUS: false
Logout Unsuccesful STATUS: false
java.rmi.ConnectIOExeception: Exception creating connection to xxx.xxx.xxx.xxx;
nested exception is:
java.net.SocketTimeoutException: Connect timed out


The xxx.xxx.xxx.xxx is the IP address of my Windows work station. The "java.rmi.ConnectIOException..."
error repeats three times afterwards.

I am in the process of trying it from another PC as we speak.

Zac wrote:

> I am in the process of trying it from another PC as we speak.


OK, let me know how this goes..

Ok... this was weird (to me at least). The Admin console I have on the other
computer is the unpgraded 9.1 console. For grins & giggles I tried it thinking
it would kick me out... well it did & it didn't. These were the results:

Server to be login into: SERVERNAME
Is Server a BEP server: true
Login Succesful
java.rmi.Connect.IOException: Excetption creating connection to xxx.xxx.xxx.xxx;
nested exception is:
java.net.SocketTimeoutException: Connect timed out

The "java.rmi.Connect.IOException..." error repeats gonna try to upgrade
this to the correct 9.2 version & see what happens.

"Chris" wrote:
>Zac wrote:
>
>> I am in the process of trying it from another PC as we speak.
>
>
>OK, let me know how this goes..
>

Hmm, ok. Can you check that name resolution is working in BOTH
directions? In other words, can you ping by host name (not ip address)
from the workstation to the server and vice versa? If not, update the
hosts file on both sides and try again. Also, do you have any firewall
or VPN software on the windows client? If so, this should be disabled.

OK,

For the 9.1 Admin client on the second computer I checked the Windows, firewall
& I hadn't put in the exception for the javaw.exe file. Doing this let me
run the program fine. I'm still scratching my head a little thought because
I thought the fact that it's the old 9.1 Admin client it should not work
with the 9.2 running on the server.

Do you think I could copy the contents of the admin client from the second
PC to the first PC and run the client that way?

"Chris" wrote:
>Hmm, ok. Can you check that name resolution is working in BOTH
>directions? In other words, can you ping by host name (not ip address)
>from the workstation to the server and vice versa? If not, update the
>hosts file on both sides and try again. Also, do you have any firewall
>or VPN software on the windows client? If so, this should be disabled.

Zac wrote:

>
> OK,
>
> For the 9.1 Admin client on the second computer I checked the
> Windows, firewall & I hadn't put in the exception for the javaw.exe
> file. Doing this let me run the program fine. I'm still scratching
> my head a little thought because I thought the fact that it's the old
> 9.1 Admin client it should not work with the 9.2 running on the
> server.

Not sure about this. It's probably not advisable to run the 9.1 admin
console against a 9.2 media server. However, you've found the real
problem (adding an exception for javaw.exe) so you may as well update
to 9.2.

> Do you think I could copy the contents of the admin client from the
> second PC to the first PC and run the client that way?

Don't know about this. I wouldn't recommend it though. I suspect you
have a similar problem here with a firewall/proxy server. Take a look
at: http://support.veritas.com/docs/252914.

>Don't know about this. I wouldn't recommend it though. I suspect you
>have a similar problem here with a firewall/proxy server. Take a look
>at: http://support.veritas.com/docs/252914.

I updated the second Windows Admin client to 9.2 & it's working fine now.
I'm not sure that the orignial problem is a firewall proxy problem though,
just because it was working before I made the changes & there was already
an exception in the firewall. I checked that exception again & it's set
up exactly the same way as the other computer.

One thing I did notice between the two computers. The one with the working
Admin console has a Java Updata listed as 9/18/05 (it's a laptop not used
much), while the one with the non working Admin console has a Java Update
listed as of 6:18pm 3/21/06... this would coincide around the time that the
Admin console stopped working on this particular computer. I'm still going
to poke around and see if I can figure anything out, but at least at this
point I have one computer that I can run the Admin console from (it's just
not the primary one).

Thanks for the help & pointing me in directions I didn't think to look into.

I have some