WMI Troubleshooting

Sriracha uses WMI for many of it's deployment tasks.

In other to allow the Sriracha deployment server access to target machines, you may need to open some firewall holes. See more info here: http://mooneyblog.mmdbsolutions.com/index.php/2013/11/01/accessing-an-amazon-vm-through-wmi/

The object exporter specified was not found

One of the most confusing errors you'll see if "The object exporter specified was not found". This means that you were able to connect, but the server name you're using is not what the target machine is expecting. Usually using the machine name or the machine's IP address is OK, but if you're going through a DNS name or a NATed firewall address, the target machine will get confused and throw this error.

There are a few ways to resolve this. If you can use the target machine's host name or IP address, use that. Even in AWS, if your target machine is not in a Virtual Private Cloud (VPC), you may be able to use the private IP of the target machine.

However, if the private IP doesn't work, you'll have to add an entry to the host file on the Sriracha deployment server (as described in the blog post above), mapping the target machine's host name to the public IP address of the server.

E_ACCESSDENIED

You may get this error when trying to deploy to a remote server using one of the WMI-based tasks:

System.SystemException: Problem connecting WMI scope on [MachineName] with user account [UserName] ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))`

At first this error may seem like it's a probably with the WMI authentication on the target machine. However, there can be access issues running WMI from a Windows Service, so you may have to change the service that it runs under.

To isolate whether this is the actual problem, try running the same deployment from the command line. Get the deployment batch request ID from the URL when you viewing the deployment batch status:

https://[SrirachaServerUrl]/#/deploy/batchStatus/[ThisGuidIsTheDeploymentBatchID]

Then run the Sriracha.Deploy.Service.exe from a command line, passing the --runDeployment parameter:

c:>c:\Sriracha\Service\Sriracha.Deploy.Server.exe --runDeployment [PutTheDeploymentBatchIDHere]

If that succeeds, then the problem is the user account that the Sriracha service is running under. If you can run the Sriracha services under an actual user account on the server, that should resolve the issue. However, if you need to run the service under Local System or Local Service or Network Service, you'll have to follow the following steps:

• TBD