VMM/SIM Cannot enter VirtualCenter credentials

[PeterCole]

Hi all,

I have removed vmm 2.0.2 and installed 2.1.

So far, it's really good in comparison to 2.0.2 purely from the information about the hosts it reveals.

However, when I go to add in the VirtualCenter details, I get prompted about IE showing a mixture of secure and non-secure items, and even when I hit "Yes", it just has a blank in the section where the VirtualCenter details should be and I can't enter the server name, username, etc.

Any ideas at all?

[Rem-8]

I had the same issue and I had to add the host on which the page appears to the Trusted Sites. Hope this works.

[PeterCole]

Thanks for the tip Rem-8, unfortunately there's no difference.

I added the site, and it appears as trusted in IE now, but still displays a blank page.

I also just noticed that if I go to the Upload Drivers section, the exact same thing happens.

I've attached a screen dump of the error, and when I hit "Yes", that whole right hand side is blank.

[Ole Thomsen_1 · Accepted solution]

This, and other blank page/missing menus can sometimes be repaired by re-installing the plug-in.

Ole Thomsen

[PeterCole]

Thanks Ole, but no go there either I'm afraid.

I've left the page there untouched for half an hour at least on one occassion and it definitely never shows up anything, just remains blank.

I'm stumped with this and have no idea how to go forward.

The only thing I can think at this point is removing VMM 2.1 and reinstalling it.

[Ole Thomsen_1]

Well, by "reinstalling the plug-in" I was referring to VMM 2.1 :-)

Ole Thomsen

[PeterCole]

Yeah I figured as much Ole :-)

[PeterCole]

Actually Ole, just realised my reply was actually to a different post of yours altogether!!!

I was referring to the other thread where someone else is having the same issue and you indicated that it takes 30 seconds or so to appear...

So, you can ignore that answer, I haven't reinstalled it yet :-)

[PeterCole]

Cheers Ole, a reinstall fixed the issue :-)

[PeterCole]

Reinstalling the VMM 2.1 package resolved this issue immediately.