Hi,
I am trying to add our vCenter to RDM as a dashboard entry, so I can view VM statuses and open remote consoles etc.
I have PowerCLI installed from the PS Gallery (not MSI), and have confirmed the Get-View command in the KB article works as is expected.
When trying to connect to my dashboard using any console type (embedded/external and PowerCLI, Player or VMRC etc), I get the below error:
"The server returned an error. Error in deserializing body of reply message for operation 'RetrieveProperties'"
Have found on Vmware forums this is a known bug in an older MSI install of PowerCLI, so not sure why I am getting this?
Cheers
James
Hello James,
Could you try to set the API Mode to Experimental in your "VMWare Dashboard" entry to see if it helps? If it does not, what version of vCenter are you using?
Best regards,
Richard Boisvert
Hello James,
Could you try to set the API Mode to Experimental in your "VMWare Dashboard" entry to see if it helps? If it does not, what version of vCenter are you using?
Best regards,
Hi Richard.
Unfortunately, I don't get that option when adding a Vmware Dashboard entry.
Is it an RDM version thing? I am running 2022.3.31.0
Thanks
James
Hello James,
Your version of RDM should see the field. When you create a new VMWare Dashboard entry, it is the last field at the bottom:
Best regards,
Richard Boisvert
Unfortunately I don't see this:
Hello,
As a test, would it be possible for you to create a portable installation of the latest version of RDM and see if this issue still occurs? To do so, you will need to do the following:
1- Download the .zip file below:
https://remotedesktopmanager.com/home/thankyou/rdmbin
2- Create a new folder on your Desktop
3- Extract the content of the .zip file into the folder created at #2
4- Go to this folder once the .zip file has been extracted and run remotedesktopmanager.exe
5- Try to add the VMWare Dashboard entry again
This test will allow us to rule out your local installation of RDM as a possible cause for this issue.
Best regards,
Richard Boisvert
I'm afraid even from the portable version, that box is not available to me
Hello,
After verification, the API mode selector is only available internally, that explains why you cannot see it, my apologies.
The dashboard does not use PowerCLI anymore, it uses the API directly. You should have more details in your Application Logs, available under the Help tab. Could you please export them and send them to service@devolutions.net so we can analyze them? Please mention this forum post in your message.
Best regards,
Richard Boisvert
Hello,
I cleared previous logs to get a fresh capture.
When I generate the error now by creating a new dashboard entry and connecting, nothing logs to the application log area.
Am I filtering incorrectly?
I cannot get any results to display ready for export.
Thanks
James
Hello James,
According to the engineer that made the integration the logs should have been present there. Could you try to use the profiler instead, set the level to 3 and launch the VMWare Dashboard again?
Here are the instructions: https://kb.devolutions.net/rdm_debugging.html
Best regards,
Richard Boisvert
Hi Richard,
The profiling doesn't give me masses of info, but one line that catches my eye is this:
Silent: System.ServiceModel.CommunicationException: Error in deserializing body of reply message for operation 'RetrieveProperties'. ---> System.InvalidOperationException: There is an error in XML document (93, 3273). ---> System.InvalidOperationException: The specified type was not recognized: name='FaultToleranceSecondaryConfigInfo', namespace='urn:vim25', at <ftInfo xmlns='urn:vim25'>
Vim25 looks like a VM ID from vCenter. I will have a look to see if anything unusual about that VM, but in the meantime should I just send this to the address you mentioned previously?
Cheers
James
Hello,
The property that the profiler reported is not supported by the dashboard. We have created an internal ticket to fix the issue in the 2023.1 release, I will update this thread once it is available.
Thank you for troubleshooting you performed.
Best regards,
Richard Boisvert
Latest update from 13th March 2023 seems to have solved the issue :)
Thank you
James
Hello James,
Glad to hear it is working with the latest release!
Best regards,
Richard Boisvert