Subscribe
Accepted Solution

OnCommand 5.0 installation issue

Hi

Was excited over OnCommand getting released before schedule because this promises to bring SMHV Snapvault capability. But maybe too early?

Installing the Core Package on my recently set up DFM server worked flawlessly. But now I'm having trouble installling the the Host Package on the first of a 3-node Hyper-V cluster getting no usable information from the installer that suddenly rolls back after about 20minutes of installing. The MSI logfile as only source for what's going on is huge and I can't seem to find the culprit.

Altough I find the documentation quite lacking I followed all the requirements to no avail and of course beeing so new there's nothing yet in the Knowledgebase.

Moreover my SnapManager for Hyper-V backups on the cluster now fails on this first node and Snapdrive can't list connected LUNs anymore.

Has somebody else started OnCommand 5.0 implementation (testing)?

I've attached the msi-log file if anybody cares to have a look...

Kind regards

     Lyndon

OnCommand 5.0 installation issue

HI Lyndon,

I am sorry you are having an issue,

looks like this might be the problem. 

The SnapDrive components could not be released after waiting 10 minutes.


Retrieved location of C:\System\NetApp\SnapDrive\en-US\SnapDriveRes.dll from the registry.
MSI (s) (64!44) [16:26:39:495]: Creating MSIHANDLE (235) of type 790531 for thread 6212
Silent Install Warning:

The SnapDrive components could not be released after waiting 10 minutes.

this will cause the install to abort.

we had seen on some setups that DNS had a handle on this dll for 2 -3 minutes after the service stop,

, so we increases the timeout to ten minutes.

but for some reason, it is not being release in your env..

some things to try maybe

stop the snapdrive service before you do the install , wait a number of minutes till the handle is released.

( you could check that file has not handles before you retry, using Handle from sysinternals maybe?)

then retry the install..

Let us know if that helps.. I will file a defect against the product so other customers dont have to hit this same issue. Thank you for your help.

thx

jeff

OnCommand 5.0 installation issue

can you tell me what was the pulgin port mentioned while doing silent installtion in hyper-V environment ? . i can see in the log which says the PLUGIN_PORT = 8804. can you change the pulgin port to "PLUGIN_PORT = 8080" in the command line and check if the installtion goes through. also make sure the follwoing port is not blocked by any other process.

OnCommand 5.0 installation issue

Hi Jeff

The installation issue could relly be due to the new SnapDrive version being installed.

I've stopped and even disable all SnapDrive and SnapManager services and checked that all handles were closed with Process Explorer before running the Host Package setup.

Strangely enough the installer waits quite a long time stating stopping the services, then carries on and on some point installs a new version of SnapDrive that I can see many handles of in Process Explorer. Soon after setup breaks off and all services are running and set to automatic.

Any insights?

     Lyndon

OnCommand 5.0 installation issue

Hi arjunan

I am not running a silent install and also left all port settings on it's default. Moreover, before setup there ist nothing sitting on the mentioned ports, so I can't see if this is the source of the problem.

regards

     Lyndon

OnCommand 5.0 installation issue

Thanks Lyndon,,

just so I understand,

when you tried the 2nd time with snapdrive  service disabled and no open handles, You got the same error ?

also, there are no scheduled jobs running durring the upgrade are there?

Do you know process that has a handle on the SD dll files for upgrade?

Could you possibly post the newer Msi log file for the 2nd attempt?  if it is the same error, and we know what process is grabing the handle,  that might

help give you direction..and I can have some other engineers look at that file..

Thanks you for your help and your patience Lyndon.

thx

jeff

OnCommand 5.0 installation issue

Hi Lyndon,

Just wanted to check if you've opened a support case with NGS so they can begin tracking this issue.  Internally we've already started a discussion on this thread but need NGS involved so they can help us collect logs and raise priority to dev/qa if needed.  If you've got a case open, would you mind sending me a PM with the case# and owner?

Thanks,


Allan

Re: OnCommand 5.0 installation issue

Hi Jeff

Yes exactly, I've stopped SD and SMHV services and even set them to disabled, confirmed with ProcessExplorer that no handles are open anymore to any SD and SMHV files. Only after that I ran the host package installer, but still with the same result.

I've observed the installation with ProcessExplorer but couldn't determine the open handle problem since all possible handles on SnapDrive files were created by the new SnapDrive itself. After installation rolled back, all SD and SMHV services were running again on original versions with automatic start setting.

As requested I've attached newest MSI Log file to this post.

Regards

     Lyndon

Re: OnCommand 5.0 installation issue

Hello everybody

As mentioned in a post I've opened a support case with NetApp and no need to provide a big bunch of information also regarding the DFM server. But since I didn't really use yet the DFM server there isn't really alot information in there, especially no host service and VM data.

No I'm wondering if I am actually doing the right thing of trying to install the Host Package on Hyper-V Hosts. Does it also have to be installed first on the DFM server, where the Core Package is installed?

Kind regards

     Lyndon

Re: OnCommand 5.0 installation issue

Hi Lyndon,


Here are my responses:


“I'm wondering if I am actually doing the right thing of tryingto install the Host Package on Hyper-V Hosts.”

Yes, you’re right


Does it also have to be installed first on the DFM server, wherethe Core Package is installed?

No.


Thanks and regards

Shiva Raja