I had also experienced this on an upgrade in my lab a few days ago and after some persistence was able to resolve it only as follows. I chose to uninstall everything (from within vSphere Client and then Add/Remove Programs) and start from scratch. However, as you'll read and as you also experienced, curiously even that is not enough. The key is to rerun the original installer for any that fail with the error message above. Only then does the specific feature get removed completely and properly let you install the new.
I am doing this from memory and arguably is probably more than necessary having identified the specific issue, but I'll share what worked for me.
1) Uninstall plug-ins from within vSphere Client
a) From the vSphere Client Home view, select the "VSI" button
b) First note the version of the EMC VSI features currently running
c) Right-click on each feature and select "Uninstall"
2) From Add/Remove, uninstall the VSI framework and supporting components:
a) Uninstall "EMC Virtual Storage Integrator (VSI) for VMware"
b) Uninstall "EMC Solutions Enabler" (if running locally and dedicated to the VSI Storage Viewer plug-in)
c) Uninstall "EMC Unified Storage Access Control for VMware" (if installed)
This next step is the key (and may be enough instead of doing a complete uninstall of everything as I did during my troubleshooting having now identified the specific issue):
3) For the specific plugin that returned the error message when trying to upgrade, rerun the installer of the version that was running originally.
a) Download the original versions of VSI features from PowerLink as noted in step #1 above
b) Rerun original installer only for any of the new features that return the error above
c) You will be prompted with an option to "Uninstall/Remove" which you'll want to perform.
NOTE: For me, even though I had older versions of all 3 VSI features running (USM, SV, and PM), I only needed to concern myself with USM (tried to upgrade from v5.0.0.86 -> v.5.1); however, it may be possible that the other features if upgrading will experience the same behavior and the remedy should be the same.
4) Install the latest VSI features
Due to another bug which I experienced but turned out is actually documented, you'll want to first install any feature that includes the v5.1 framework first (as of this writing): Unified Storage Management or Storage Viewer (Path Management feature is still at v5.0 and should not be installed first if you choose to uninstall everything).
emc285999: "After an upgrade to version 5.1 the VSI Storage Viewer returns error "Unable to load DLL ‘SEWrapper.dll’: The specified module could not be found. (Exception from HRESULT: 0x8007007E)"
Alternatively, as noted in the KB article you could install the Microsoft Visual C++ 2010 Redistributable Package (x86) if you get the error as I did when I chose to reinstall the Path Management feature first.
5) Verify that the VSI plug-in is enabled
a) Within the vSphere Client, from the "Plug-ins -> Manage Plug-ins" menu bar, verify "EMC Virtual Storage Integrator (VSI) for VMware" is enabled
b) If not, right-click and select "Enable"
6) Rediscover the arrays
a) From the "Home" view, select the VSI plug-in
b) For both the Storage Viewer (test the local Solutions Enabler connection also) and the Unified Storage Management feature, rediscover the arrays
Even though VSI 5.0 was not showing up in add remove programs any longer it did show up in Fix it and after I told it to remove it I could then install 5.1 and it is working.
As you and I reproduced, there is an issue with the upgrade/overinstall (at least 5.0.x -> 5.1) and requires either using the cleanup tool you mentioned, or using the same installer as currently running so that instead of detecting an upgrade is required let MSI detect the same version is installed and then provide the "Remove" (and Modify) options. As you point out, we don't expose an Add/Remove entry to do the same.
Thank you for following-up and sharing; I really appreciate the feedback.
Hi,im still getting a "the instance name specified is invalid" error when installing the USM part, i tried to completely removed the componenets using both the add/remove and the microsot fixiit software..
are you still seeing this error? if so, then try downloading the latest VSI USM zip file from Powerlink, we have updated the link to address this install issue.
Also VSI v5.2 will be uploaded to Powerlink within the next day or so......
christopher_ime
4 Operator
•
2K Posts
0
January 27th, 2012 00:00
I had also experienced this on an upgrade in my lab a few days ago and after some persistence was able to resolve it only as follows. I chose to uninstall everything (from within vSphere Client and then Add/Remove Programs) and start from scratch. However, as you'll read and as you also experienced, curiously even that is not enough. The key is to rerun the original installer for any that fail with the error message above. Only then does the specific feature get removed completely and properly let you install the new.
I am doing this from memory and arguably is probably more than necessary having identified the specific issue, but I'll share what worked for me.
1) Uninstall plug-ins from within vSphere Client
a) From the vSphere Client Home view, select the "VSI" button
b) First note the version of the EMC VSI features currently running
c) Right-click on each feature and select "Uninstall"
2) From Add/Remove, uninstall the VSI framework and supporting components:
a) Uninstall "EMC Virtual Storage Integrator (VSI) for VMware"
b) Uninstall "EMC Solutions Enabler" (if running locally and dedicated to the VSI Storage Viewer plug-in)
c) Uninstall "EMC Unified Storage Access Control for VMware" (if installed)
This next step is the key (and may be enough instead of doing a complete uninstall of everything as I did during my troubleshooting having now identified the specific issue):
3) For the specific plugin that returned the error message when trying to upgrade, rerun the installer of the version that was running originally.
a) Download the original versions of VSI features from PowerLink as noted in step #1 above
b) Rerun original installer only for any of the new features that return the error above
c) You will be prompted with an option to "Uninstall/Remove" which you'll want to perform.
NOTE: For me, even though I had older versions of all 3 VSI features running (USM, SV, and PM), I only needed to concern myself with USM (tried to upgrade from v5.0.0.86 -> v.5.1); however, it may be possible that the other features if upgrading will experience the same behavior and the remedy should be the same.
4) Install the latest VSI features
Due to another bug which I experienced but turned out is actually documented, you'll want to first install any feature that includes the v5.1 framework first (as of this writing): Unified Storage Management or Storage Viewer (Path Management feature is still at v5.0 and should not be installed first if you choose to uninstall everything).
emc285999: "After an upgrade to version 5.1 the VSI Storage Viewer returns error "Unable to load DLL ‘SEWrapper.dll’: The specified module could not be found. (Exception from HRESULT: 0x8007007E)"
Alternatively, as noted in the KB article you could install the Microsoft Visual C++ 2010 Redistributable Package (x86) if you get the error as I did when I chose to reinstall the Path Management feature first.
5) Verify that the VSI plug-in is enabled
a) Within the vSphere Client, from the "Plug-ins -> Manage Plug-ins" menu bar, verify "EMC Virtual Storage Integrator (VSI) for VMware" is enabled
b) If not, right-click and select "Enable"
6) Rediscover the arrays
a) From the "Home" view, select the VSI plug-in
b) For both the Storage Viewer (test the local Solutions Enabler connection also) and the Unified Storage Management feature, rediscover the arrays
bhcengage
15 Posts
0
January 27th, 2012 07:00
I actually got it working at the end of the day. I ended up using Microsoft Fix it - http://support.microsoft.com/mats/Program_Install_and_Uninstall/
Even though VSI 5.0 was not showing up in add remove programs any longer it did show up in Fix it and after I told it to remove it I could then install 5.1 and it is working.
christopher_ime
4 Operator
•
2K Posts
0
January 27th, 2012 07:00
That makes sense also.
As you and I reproduced, there is an issue with the upgrade/overinstall (at least 5.0.x -> 5.1) and requires either using the cleanup tool you mentioned, or using the same installer as currently running so that instead of detecting an upgrade is required let MSI detect the same version is installed and then provide the "Remove" (and Modify) options. As you point out, we don't expose an Add/Remove entry to do the same.
Thank you for following-up and sharing; I really appreciate the feedback.
itzikr
28 Posts
0
February 21st, 2012 03:00
Hi,im still getting a "the instance name specified is invalid" error when installing the USM part, i tried to completely removed the componenets using both the add/remove and the microsot fixiit software..
1 Attachment
usm-error.png
kendcollins
40 Posts
0
March 12th, 2012 09:00
Itzik,
are you still seeing this error? if so, then try downloading the latest VSI USM zip file from Powerlink, we have updated the link to address this install issue.
Also VSI v5.2 will be uploaded to Powerlink within the next day or so......
Ken