Posts tagged "error"

ID: 2912 | Details: Service unavailable (503) (0x801901F7) | NO_PARAM NO_PARAM

During the deployment of a new resource or adding a new resource  there is a possibility that you can face the following error:

An internal error has occurred trying to contact the ” server: NO_PARAM: NO_PARAM.
WinRM: URL: [http://:5985], Verb: [INVOKE], Method: [GetError], Resource: [{1FAA84D0-C551-4410-AB54-0DE094840D37}]

Service unavailable (503) (0x801901F7)

Recommended Action

Check that WS-Management service is installed and running on server ”. For more information use the command “winrm helpmsg hresult”. If ” is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to for more details.

After some investigation this can happen due two circumstances:

1.The VMM Certificate has expired. Check this one in your certificate store.

If the certificate is expired, create a new one:

Then, refresh all VMM Infrastructure servers (including VMHosts) so they get the new certificate.

2.The port is used by another program.

After installing the newest product from Microsoft “Admin Center” on our Library server we faced the same issue.

To solve this: Go to the library server -> Open regedit -> Search for “BITSTcpPort” -> Change the value to an unused Port like (8500).
Restart the SCVMM Agent and refresh your Library share in SCVMM.

VEEAM Task failed Error: Exception of type ‘System.OutOfMemoryException’ was thrown

Last week I had the following error when starting a Veeam backup job. I thought my proxy servers where out of memory, so I rebooted them. Then I started the backup jobs again, with no result.

To solve this issue you must logoff all the other RDP sessions, which have a disconnected session with the Veeam console open. Alternatively, give the Veeam backup server more resources so there is more memory available.

PowerShell: The specified string is not in the form required for a subject

During the creation of a PowerShell SMA Runbook I was getting the following error message. This error appear when sending an automatic mail message with the send-mailmessage cmdlet. It only happens when the subject is filled with a String parameter which contains invalid characters.

After two hours of troubleshooting I formatted the string with the following regex which worked in my case: