PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : PowerScript fails to load after vSphere client upgrade


JLankford
12.04.2010, 17:23
Hello,

I recently upgraded my VI Client to vSphere, and now my PowerScripter plug-in fails to load, even after uninstalling and reinstalling.

The error message I get is:

Could not load PowerScriper plug-in. Exception has been thrown by the target of an invocation. Permission denied.

What do I need to do to fix this?

Thanks,
James

PatrickDreyer
13.04.2010, 15:02
James,

There seams to be something special in your environment.
Could you please send us the log file, so we know where exactly the error occurs?
Please follow the steps below for having the PowerScripter generating the log file:
1. Double click LoggingTrace.reg in the PowerScripter install directory
2. Start your vSphere client as usual
3. Double click LoggingOff.reg in the PowerScripter install directory
4. Send us "My Documents\PowerScripter.log" to our support email

We apologize for the inconvenience.

Best regards,
Patrick

JLankford
03.05.2010, 20:33
Patrick,

Thanks for your reply; I do apologize for the delay. I believe I have determined the issue. Apparently the issue was security related; I had forgotten that our vCenter server had been migrated to a new server a couple of weeks prior to the vSphere upgrade, and I did not have the permissions I did on the old server.

Once I corrected the permissions I no longer received the errors and was able to use the PowerScripter add-in.

Thanks again,
James

PatrickDreyer
04.05.2010, 08:40
Hi James,

I'm glad your issue is solved.
Nevertheless, in case you generated the log file, could you please send it to support at icomasoft dot com.
Actually, PowerScripter should have thought you about the laking permissions, thus, we'd like to know where PowerScripter couldn't correctly detect it.

Best regards,
Patrick

JLankford
26.05.2010, 00:12
Patrick,

At this point I am unable to recreate the issue. If I encounter this issue again I will enabling logging and open a new case with the trace logging file.

Kind regards,
James