We have the same issue on our environment. All the sub-plugins are failing during installation with an 1603 error code. The vCenter OS is W2K8 R2 standard.

Please advise how we can solve this.

These situations are supported and no additional steps should be required for successful installation, so something odd must be at play here. Since it is hard to troubleshoot this without logs it would be great if you both could open up an EMC support request with the installer logs (will be in the temp directory). This way it will be escalated to the proper people and we can help you more efficiently.

Thanks!

Cody

Cody Hosterman
SVPG Partner Engineering
Symmetrix & Virtualization Product Group
EMC Corporation

Hi. I'm the engineer responsible for this code. Since engineers never do anything wrong, clearly you have placed a hex upon the installer. Try using a ward of disenchantment on the installer and see if that works.

Just kidding : )

Clearly there is an issue, and we certainly want to help you track it down. The 1603 error is being reported via the Windows Installer Service, the daemon responsible for processing the MSI databases that the bootstrapper EXE contains. The bootstrapper invokes each MSI using a log option and that log is written to the installing user's personal temporary directory.

Steps to Gather Logs

1. The easiest way to access this directory is to strike the Windows key in combination with the R key. This will bring up the run box.
2. Then type "%temp%" and this will open a Windows Explorer window to the correct location on the file system.
3. Select the "Details" view for the file view and sort by modified date with the most recent files first.
4. The installer logs should be obvious. Simply zip them up and post them to this thread.

I know you opened an SR case, thank you. I don't know why that hasn't reached me. I'll be looking into that, but in the meantime you sending me these logs will be the quickest path to a resolution. I'll append the SR case with whatever data we gather here.

Thanks again!

--

-a

Here's the log files:

=== Logging started: 1/5/2011  8:04:54 ===
Action start 8:04:54: INSTALL.
Action start 8:04:54: FindRelatedProducts.
Action ended 8:04:54: FindRelatedProducts. Return value 0.
Action start 8:04:54: AppSearch.
Action ended 8:04:54: AppSearch. Return value 1.
Action start 8:04:54: LaunchConditions.
Action ended 8:04:54: LaunchConditions. Return value 1.
Action start 8:04:54: ValidateProductID.
Action ended 8:04:54: ValidateProductID. Return value 1.
Action start 8:04:54: CostInitialize.
Action ended 8:04:54: CostInitialize. Return value 1.
Action start 8:04:54: FileCost.
Action ended 8:04:54: FileCost. Return value 1.
Action start 8:04:54: CostFinalize.
Action ended 8:04:54: CostFinalize. Return value 1.
Action start 8:04:54: InstallValidate.
Action ended 8:04:54: InstallValidate. Return value 1.
Action start 8:04:54: InstallInitialize.
Action ended 8:04:54: InstallInitialize. Return value 1.
Action start 8:04:54: RemoveExistingProducts.
Action ended 8:04:54: RemoveExistingProducts. Return value 0.
Action start 8:04:54: ProcessComponents.
Action ended 8:04:54: ProcessComponents. Return value 1.
Action start 8:04:54: UnpublishFeatures.
Action ended 8:04:54: UnpublishFeatures. Return value 1.
Action start 8:04:54: RemoveRegistryValues.
Action ended 8:04:54: RemoveRegistryValues. Return value 1.
Action start 8:04:54: RemoveFiles.
Action ended 8:04:54: RemoveFiles. Return value 0.
Action start 8:04:54: RemoveFolders.
Action ended 8:04:54: RemoveFolders. Return value 1.
Action start 8:04:54: CreateFolders.
Action ended 8:04:54: CreateFolders. Return value 1.
Action start 8:04:54: InstallFiles.
Action ended 8:04:54: InstallFiles. Return value 1.
Action start 8:04:54: WriteRegistryValues.
Action ended 8:04:54: WriteRegistryValues. Return value 1.
Action start 8:04:54: RegisterUser.
Action ended 8:04:54: RegisterUser. Return value 0.
Action start 8:04:54: RegisterProduct.
Action ended 8:04:54: RegisterProduct. Return value 1.
Action start 8:04:54: PublishFeatures.
Action ended 8:04:54: PublishFeatures. Return value 1.
Action start 8:04:54: PublishProduct.
MSI (s) (D4:64) [08:04:54:246]: Product: EMC Virtual Storage Integrator (VSI) for VMware vSphere -- Error 1316. A network error occurred while attempting to read from the file: C:\Users\admin\AppData\Local\Temp\1\EMC Virtual Storage Integrator (VSI) for vSphere4.msi

Error 1316. A network error occurred while attempting to read from the file: C:\Users\admin\AppData\Local\Temp\1\EMC Virtual Storage Integrator (VSI) for vSphere4.msi
Action ended 8:04:54: PublishProduct. Return value 3.
Action ended 8:04:54: INSTALL. Return value 3.
MSI (s) (D4:64) [08:04:54:264]: Windows Installer reconfigured the product. Product Name: EMC Virtual Storage Integrator (VSI) for VMware vSphere. Product Version: 4.0.0. Product Language: 1033. Reconfiguration success or error status: 1603.

=== Logging stopped: 1/5/2011  8:04:54 ===

Thank you for attaching the log. I have a few questions and things I would like you to try:

1. Phil - You're running Windows 2008 Server x64 SP2, correct? Stijn said he is running Windows 2008 Sever x64 R2, so I just wanted to make sure that what you two are running is actually different and no one mistyped.
2. Phil - You mentioned installing the Unified Storage Management Feature first, and then others. Was the order you mentioned correct?
3. Both - Are you two attempting to install the Features in parallel or serially? The bootstrapper *should* prevent parallel installations, but I thought I would ask.
4. Both - Does this problem occur if you do *not* install the Unified Storage Management Feature at all and then install the other Features?
5. Both - Does the file "EMC Virtual Storage Integrator (VSI) for vSphere4.msi" exist in the location that the log file implied it should?

I'm sorry you're these issues are preventing you from using the software, and I promise we'll find a quick and painless resolution. Thanks!

1. Phil - You're running Windows 2008 Server x64 SP2, correct?  Stijn said he is running Windows 2008 Sever x64 R2, so I just wanted to  make sure that what you two are running is actually different and no one  mistyped.
   • in the meantime I also tried the installation on a windows 7 x86 enterprise laptop. We have the same error/issue on this laptop.
2. Phil - You mentioned installing the Unified Storage  Management Feature first, and then others. Was the order you mentioned  correct?
3. Both - Are you two attempting to install the Features  in parallel or serially? The bootstrapper *should* prevent parallel  installations, but I thought I would ask.
   • We do a serial install.
4. Both - Does this  problem occur if you do *not* install the Unified Storage Management  Feature at all and then install the other Features?
   • We're only able to install the VSI Unified Storage Management. The other feature fail to install. They also fail when the VSI Unified Storage Management isn't installed.
5. Both - Does the file "EMC Virtual Storage Integrator (VSI) for vSphere4.msi" exist in the location that the log file implied it should?
   • that msi exist. I attached the content of the %TEMP% dir in the zip file.

1. Task - The Task item in the Plug-ins window in the vSphere client, I believe, is something the Unified Feature registers with the vCenter server. I'll check with those engineers and find out. Thank you for letting us know about the issue when an install attempt is made using its entry.

2. From both of your responses the commonality I've detected is that the Unified Storage Management Feature is being installed first and then the fun begins. Stijn, you mentioned that you're uninstalling the Unified Feature, but I wonder if it is uninstalling properly. Here's what I'd recommend. Read my blog post at https://akutz.wordpress.com/2010/11/03/get-msi/ and use the PowerShell script to fully remove the Unified Feature and the VSI Framework. Then try installing *other* Features without the Unified Feature and see what happens. I'm going to be busy trying to replicate the issue.

Thanks!

1. I am running Windows 2008 Server x64 SP2 Enterprise

2. Yes, I installed "EMC VSI for VMware vSphere Unified Storage Management v4.0.0.45.exe" first and it is installed in vcenter.  You can open the EMC pane in the VI Client.  If you go to manage plugins in vcenter, the "EMC Virtual Storage Integrator" is installed and enabled.  BUT, I just noticed that there is an available plugin called "task", the vendor is EMC Coproration, the version is 1.0 and it gives me the option to download and install.  When I click this, the install goes to 100%, but then fails and I am given an error message (see attached plugin graphic).  Closing and reopening the plugins screen shows that the plugin is still available.

3. serially.

4. did not test this

5. This may be part of the issue --  I am double clicking the install file from c:\users\admin\desktop\dropbox\ .  See screenshot attached called "temp-file-screenshot".  Top folder is install location and bottom folder is the temp file.  Note that the two EMC* files appear after I run the exe files and they error out.

I have 2 sites and haven't modified the vcenter at the other site yet.  This other site (will reference as "GV") has the same environment and OS.

I just attempted an install of "emc-vsi-sv-4.0.0-vmware-vsphere-WINDOWS-x86.exe" first and it prompted for the "solutions enabler" install (never saw this before) and I did that as well.  Everything completed successfully with this file.

I then installed the "SPM" and "PM" files successfully also.

I then installed the VSI USM file last.  It did prompt for the navisphere CLI installation.  I had to go fetch this from powerlink.  I installed this CLI file: "NaviCLI-Win-32-x86-en_US-7.30.0.4.75-1.exe"

Just opened up the VI client and everything is good.  As a note:  The "task" plugin is not listed here at the GV site at all in the VI client.... mmm.

Next, I'll try the steps to uninstall at the original site and follow the above process.

Phillip

FWIW, Solutions Enabler is a tool that the Storage Viewer Feature uses to communicate with different back-end storage devices.