topic Re: Can not access launcher for va7400 on windows client after upgrade in Disk Enclosures

Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Mon, 09 Dec 2002 16:25:59 GMT

Upgraded from CommandView 1.02 to 1.05 and now can not execute launcher using Internet Exployer on my Windows client. Receiving the following messages:
Fatal initialize error
Init error for device: host name: serial no of va7400
Init error: Initial Device Exception Failed to open target hostname: WaitFor Logon Failed NOT BOUND IN REGISTRY

Launcher on the Unix server does get to the va7400.

Anyone had this problem. Any idea as to fix?

Re: Can not access launcher for va7400 on windows client after upgrade

David Bell_1 — Mon, 09 Dec 2002 16:58:04 GMT

Kathy,

Please try to "rediscover" the array using "armdiscover". This should resolve the problem. You can find the process in the users manual located here:

http://h200004.www2.hp.com/bc/docs/support/SupportManual/lpg28818/lpg28818.pdf

You may also find helpful information on page 189 of this manual.

HTH,

Dave

Re: Can not access launcher for va7400 on windows client after upgrade

Ian Hillier — Mon, 09 Dec 2002 18:04:05 GMT

Verify on the server that the file /opt/sanmgr/hostagent/config/access.dat has the IP of the machine you are accessing launcher from.
If you don't save this file before you upgrade I think it overwrites it.

John

Re: Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Mon, 09 Dec 2002 18:17:41 GMT

The Launcher worked fine prior to the upgrade of the controller firmware and prior to the upgrade of the CommandView SDM software.
The access.dat file is as it was prior to the upgrade. We have 3 windows client machines specified in the access.dat file and all three are unable to access the va7400.
I tried the armdiscover command. I still can not get the Launcher to work from the windows client machines.
The java applet executes and the va7400 icon displays. When I move the cursor over the icon the correct information (like the serial number) is displayed for the va7400 except the status shows as unknown.

Re: Can not access launcher for va7400 on windows client after upgrade

Eugeny Brychkov — Mon, 09 Dec 2002 18:38:10 GMT

Kathy,
stop hostagent and opendial services, remove DeviceDBFile in CommandView directory, then start opendial and hostagent services and issue armdiscover
Eugeny

Re: Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Mon, 09 Dec 2002 18:43:37 GMT

Eugeny,
I've tried that too - A couple of times. I just uninstalled java 1.3.1 and reinstalled. Still no luck. HELP

Re: Can not access launcher for va7400 on windows client after upgrade

Eugeny Brychkov — Mon, 09 Dec 2002 19:11:06 GMT

Then try to create file
c:\sanmgr\hostagent\config\commIpAddr.txt
and simpy write IP address of LAN card you want to use for access then restart hostagent (this recommendation if you have more than one NIC card in the server).
Which server you have directly connected to VA - hpux or windows? Does local access work? Do you get this error in Internet Explorer?
Do you use http://server-ip:4096/Launcher.html ? What do you see if you issue http://server-ip:4096/ ?
Eugeny

Re: Can not access launcher for va7400 on windows client after upgrade

Eugeny Brychkov — Mon, 09 Dec 2002 19:22:16 GMT

Look at this one also http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x298985079106d71190050090279cd0f9,00.html . Very good reply from Kris Rombauts
Eugeny

Re: Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Mon, 09 Dec 2002 20:22:01 GMT

I've read the Trouble shooting in the CommandView SDM user's guide.
With CommandView SDM 1.02, the file commIpAddr.txt was empty, this morning I did try to add the IP address of the server(UNIX) but the launcher still does not work from the win client.
The CMD software is on a UNIX server.Yes, I can execute the launcher from the server but not from the windows client.
I've tried everything in the troubleshooting guide. No luck here.
Thanks, for the replies.

Re: Can not access launcher for va7400 on windows client after upgrade

Eugeny Brychkov — Mon, 09 Dec 2002 20:37:29 GMT

So if you can run web-access from hpux servers and can not from windows servers I guess it's windows' problem. Try to reinstall latest java plugin (JRE - Java Runtime Environment). You may try in the following seq: remove JRE, then try web-access. I think it should ask for 'install java' and then install it by itself, but if it will not ask you install java manually. Try clearing IE cache and files (in 'Internet options'), setting it to 'check for newer versions'='every visit to the page' in 'Settings...'. BTW, do you use latest IE (at least 5.5)?
Eugeny

Re: Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Tue, 10 Dec 2002 15:41:11 GMT

Yes, I removed the java on my windows client and then brought up the launcher and I received the request to install jave. Java was downloaded and installed but I am still receiving the error. Environment). I tried clearing the cache and the files in 'Internet options' before reinstalling java.
I'm running IE v.0.2600 and it is set to 'check for newer versions'='every visit to the page'.

Re: Can not access launcher for va7400 on windows client after upgrade

Eugeny Brychkov — Tue, 10 Dec 2002 17:00:03 GMT

Kathy,
could you please attach the following data in one file:
- "armdsp -a" output for VA;
- "armtopology" output;
- PanConfigParams.txt file;
- full IE version you use;
- JRE version you have installed;
Please also confirm that ALL hpux hosts (how many?) can run Launcher, but ALL win hosts can not.
Please post what do you see in browser window when trying "http://ip-address/" (w/o "Launcher.html")?
Eugeny

Re: Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Tue, 10 Dec 2002 19:15:13 GMT

Eugeny, See the attached.

Re: Can not access launcher for va7400 on windows client after upgrade

Eugeny Brychkov — Tue, 10 Dec 2002 20:07:47 GMT

Thanks. The only things I found are:
- battery firmware should be updated to 4.3;
- VA in private loop: either directly connected or hub-connected. If switch connected it should be in fabric (but of course depends on hosts' config if they support fabric).
PanConfigParams.txt, IE version, JRE are ok.
I see here's a little misunderstanding. Please enter in address field of IE (or Netscape)
http://10.15.1.18:4096/
and look what it will show you. Normally it should display page 'Copyright Hewlett-Packard'. Try entering it on windows hosts and on hpux host and tell me the results.
I see you're talking about launching Launcher from hpux host graphical console. Are you sure running it you use web-access, but not directly accessing java code? To check if local hpux web access works enter http address I mentioned above in netscape of hpux server. You may also try
http://localhost:4096/
Eugeny

Re: Can not access launcher for va7400 on windows client after upgrade

David Bell_1 — Wed, 11 Dec 2002 15:33:42 GMT

Kathy,

One other thing to try. I have found that with IE version 6.0 there are several problems. One of which is what you're describing. If you have a pc available that is using IE 5.5, try using that one. We have also found some problems associated to using IE 6.0 and downloading using binary in which it places spurious characters throughout the file.

HTH,

Dave

Re: Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Wed, 11 Dec 2002 15:51:05 GMT

Dave,
All our PCs standard software are loaded by our Software admin branch through an agency software update process. I really have no control over what version of IE or netscape is on my desktop. (Agency Standards and all) Unless I can download IE v 5 and install to a completely different directory?? BUT IE v 6 is what I was using prior to the update of the controller firmware and update of the commandview software from 1.02 to 1.05. When commandview 1.02 was originally installed (when the va7400 was installed) I was told netscape would not work and to use IE. Is that still true.
I would also like to thank everyone that has replied to my question. You all have been great to take the time to provide helpful feedback. I just wish I could get this installed. I really wish I had not allowed the local HP engineer to upgrade. But he told us HP was having problems with the old firmware and cmd1.02. Well, with the upgrade now we are having problems.

Re: Can not access launcher for va7400 on windows client after upgrade

Eugeny Brychkov — Wed, 11 Dec 2002 15:57:38 GMT

Dave, some years ago I was using Netscape and managed to kill disk by upgrading firmware with file corrupted during download (Netscape inserted extra characters). From that time I do not use Netscape.
Kathy, did you try what I asked in my last reply?
Eugeny

Re: Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Wed, 11 Dec 2002 17:28:21 GMT

Eugeny,
Yes, the http://10.15.1.18:4096/
displayed the page 'Copyright Hewlett-Packard'. The Unix host does not have the java 1.3.1 installed because I received the following from netscape on the unix host:
need java plug in. Yes, when I'd execute the launcher on the host it would be at the command prompt not from netscape. Even with the commandview 1.02 version it was not using Netscape.

Re: Can not access launcher for va7400 on windows client after upgrade

Eugeny Brychkov — Wed, 11 Dec 2002 19:24:41 GMT

Good. Try then
http://10.15.1.18:4096/cmdviewVA.html?prod1.mem.dcaa.mil:/dev/rscsi/c8t14d0
or
http://10.15.1.18:4096/cmdviewVA.html?10.15.1.18:VA-1
In this string you tell html page to connect to host "prod1.mem.dcaa.mil" and look for VA-1.
I also remember one funny case when there was Virtual Array having alias "VA" and we discovered that so short name was cause of problems with CommandView. Kathy, try to realias VA to more compex name, for example "VA7400_1". I do not think it will help, but who knows...
Please tell me results if these links above work or not
Eugeny

Re: Can not access launcher for va7400 on windows client after upgrade

Helen Herring — Thu, 12 Dec 2002 19:33:11 GMT

To all who responded, thanks so much.
I found the problem yesterday afternoon.
When CommandView SDM 1.05 was installed evidently it pulled the host name from /etc/hosts. My PC hosts file had the alias for the host specified. When the VA7400 was originally installed and CommandView SDM 1.02 was installed the host name was specified as the alias. I changed the hosts file on my pc to the full host name and the Launcher works fine just like it did with 1.02. I spoke with HP and was told CommandView SDM 1.04 was changed to pull host name from /etc/hosts.
Thanks again to all.