KB: Adding a SAN storage provider in System Center 2012 Virtual Machine Manager fails with SMI-S Error 26100

KB: Adding a SAN storage provider in System Center 2012 Virtual Machine Manager fails with SMI-S Error 26100

  • Comments 2
  • Likes

imageHere’s a new Knowledge Base article we published. This one talks about troubleshooting an issue where adding a SAN storage provider in VMM 2012 fails with SMI-S Error 26100.

=====

Symptoms

When attempting to discover a SAN storage provider in System Center 2012 Virtual Machine Manager (VMM) using the Add Storage Devices Wizard, the action fails with Error 26100:

Unable to contact storage service on %ComputerName;.
Ensure that the storage service is properly installed and running.

Cause

The Microsoft Storage Management Service is not installed properly on the VMM server or is corrupted. The result is that the service is not running and it is not possible to manually start it.

Resolution

To resolve this issue, uninstall the Microsoft Storage Management service on the VMM server and then reinstall it again. To do this, follow the steps below:

1. Close all VMM consoles.

2. On the Virtual Machine Manager server, stop the System Center Virtual Machine Manager service and the System Center Virtual Machine Manager Agent service.

3. Uninstall the Microsoft Storage Management service by running the StorageService.msi from the System Center 2012 Virtual Machine Manager installation media (\amd64\setup\msi\SCXStorage) and choosing the Remove option.

4. Open an elevated command prompt (Run as administrator).

5. In the opened command prompt, change the directory to the VMM installation media. For example: cd D:\amd64\setup\msi\SCXStorage.

6. In the opened command prompt, type and run the following command:

msiexec /i StorageService.msi /L*V c:\temp\install.txt

This will install the Microsoft Storage Management service and put the installation log in the c:\temp folder.

7. On the Virtual Machine Manager server, start the System Center Virtual Machine Manager service and the System Center Virtual Machine Manager Agent service.

8. Verify that the Microsoft Storage Management service is running.

At this point you should be able to discover the supported SAN storage.

More Information

VMM trace shows the following:

WSMAN: URL: [http://SERVERNAME:5985] Verb: [ENUMERATE]; resource[http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/scx/storage/sm/MSFT_SMStorageDiscovery];
WsmanAPIWrapper.cs,2894,0x00000000,Retrieving underlying WMI error to throw. Got string "<f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150858752" Machine="SERVERNAME"><f:Message><f:ProviderFault provider="WMI Provider" path="%systemroot%\system32\WsmWmiPl.dll"><f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150858752" Machine="SERVERNAME"><f:Message>The WS-Management service cannot process the request. The service cannot find the resource identified by the resource URI and selectors. </f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>

=====

For the most current version of this article please see the following:

2744216 - Adding a SAN storage provider in System Center 2012 Virtual Machine Manager fails with SMI-S Error 26100

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I installed enabled the storageservice on the VHD for the VSS 2012 SP1 CTP2 beta (not installed by default), running on some pre-release of WIndows 2012 Server

    SO one could play with all the storage features of VSS, can a storage pool or iscsi target running ON windows server be used as a storage array?

    This would make a nice blog post ... allowing folks to play with all the storage features using ONLY Windows equipment.

  • thank you