Cannot instantiate Powershell V5 object

Support for all customers who have purchased a SAPIEN PowerShell Studio product license. This forum does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
froaderick
Posts: 36
Joined: Fri Nov 17, 2006 4:38 am

Re: Cannot instantiate Powershell V5 object

Post by froaderick » Fri Apr 28, 2017 9:45 am

Actually, i noticed that. Originally, i had upgraded to PSS 2017 but our license didnt cover it so i uninstalled 2017 and reinstalled 2016. How would i go about updating the assembly to reflect the proper path?

User avatar
DevinL
Site Admin
Posts: 1098
Joined: Mon Aug 17, 2015 2:25 pm

Re: Cannot instantiate Powershell V5 object

Post by DevinL » Fri Apr 28, 2017 9:52 am

Ah hah! In that case, I do believe I have a fix for this. We'll have to remove a few specific registry entries but it should solve the problem.

Let me track down the exact keys and I'll post them here in just a moment.
DevinL
SAPIEN Technologies, Inc.

User avatar
DevinL
Site Admin
Posts: 1098
Joined: Mon Aug 17, 2015 2:25 pm

Re: Cannot instantiate Powershell V5 object

Post by DevinL » Fri Apr 28, 2017 9:57 am

First, I'd like to point out that we're going to be modifying the registry so before continuing on it is best to make a backup that you can revert to in the case of an unforeseen mishap.

That being said, here's a list of the keys we need to have removed (NOTE: The value within the {} might be different on your machine):
  • HKEY_CLASSES_ROOT\CLSID\{00DFED1F-5A55-4B77-8A05-D128D42EAC6E}
  • HKEY_CLASSES_ROOT\CLSID\{23F85780-FD7B-31AD-BA4B-4863AE67BFD1}
  • HKEY_CLASSES_ROOT\CLSID\{2F151623-5235-3CA5-B82D-AC878960E122}
  • HKEY_CLASSES_ROOT\CLSID\{950808CE-3E2D-47B9-9DFE-4B9F763C7390}
  • HKEY_CLASSES_ROOT\CLSID\{BDCC23B8-3B09-3FFE-B9F3-8E2289339294}
  • HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00DFED1F-5A55-4B77-8A05-D128D42EAC6E}
  • HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{23F85780-FD7B-31AD-BA4B-4863AE67BFD1}
  • HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{2F151623-5235-3CA5-B82D-AC878960E122}
  • HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{950808CE-3E2D-47B9-9DFE-4B9F763C7390}
  • HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{BDCC23B8-3B09-3FFE-B9F3-8E2289339294}
Lastly, delete the C:\Program Files (x86)\Common Files\SAPIEN Debugger 2017 folder then launch RegisterControls which is located wherever you installed PowerShell Studio (C:\Program Files\SAPIEN Technologies, Inc\PowerShell Studio 2016 by default) and check the available versions.

After performing these steps, you should be able to launch your scripts within PowerShell Studio as expected. And just in case, here's my original post where I outlined these steps with a bit more information: viewtopic.php?f=12&t=11071&p=59993#p59993
DevinL
SAPIEN Technologies, Inc.

User avatar
froaderick
Posts: 36
Joined: Fri Nov 17, 2006 4:38 am

Re: Cannot instantiate Powershell V5 object

Post by froaderick » Fri Apr 28, 2017 10:09 am

That did the trick!

Thank you for all your help!

User avatar
DevinL
Site Admin
Posts: 1098
Joined: Mon Aug 17, 2015 2:25 pm

Re: Cannot instantiate Powershell V5 object

Post by DevinL » Fri Apr 28, 2017 10:12 am

Awesome! I'm glad to hear that solved the problem :D

If you have any further issues, please don't hesitate to post again.
DevinL
SAPIEN Technologies, Inc.