Can't get Powershell v3 to be recognized by PowerShell Studio 2012

Post by **barberta** » Fri Dec 14, 2012 4:09 am

Installed PSS 2012 Windows 2008 R2 server, and then installed Powershell 3.0 when I found out it was not on the server. Uninstalled PSS 2012 and reinstalled. The v3 button is grayed out on the menu. How do I get PSS 2012 to recognize that Powershell 3.0 is installed?

Post by **davidc** » Fri Dec 14, 2012 4:26 am

PowerShell Studio builds a cache before you can see the cmdlets and enable the v3 button. If the process was interrupted then you will need to press the 'Refresh' button in the PowerShell Panel.

Once the cache completes, please verify that you can select the V3 button.

David

Post by **barberta** » Fri Dec 14, 2012 4:38 am

Thanks for the info. There was a message stating the 64-bit process was interrupted. When the processing finally completed, I have only 32-bit listings when I choose v3 for Powershell. Is there a way I can force PSS 2012 to rebuild the caches again?

Post by **barberta** » Fri Dec 14, 2012 4:46 am

The refresh button will only allow me to refresh the 32 bit cache, because that's the only one PSS 2012 has listed under the Platform part of the ribbon when the v3 indicator is lit. Under the Powershell v2 indicator, I have both 32 and 64 bit options.

Post by **davidc** » Fri Dec 14, 2012 4:48 am

Yes, press the Refresh button in the PowerShell Explorer (First tab of the Object Browser Panel) when you have the 64Bit platform selected.

If you can't select the platform, then you will have to manually delete the cache:

C:ProgramDataSAPIENCachedData 2012

David

Post by **barberta** » Fri Dec 14, 2012 5:16 am

It appears the cache generator executable crashes every time when trying to build the 64 bit cache files. Looks like it's caused by a Null Exception in Microsoft.Exchange.Diagnostics. I would assume this is because I have the E2010 Exchange module added? Any ideas as to how I fix this issue?

Post by **davidc** » Fri Dec 14, 2012 5:23 am

What version of PowerShell Studio do you have installed?

David

Post by **barberta** » Fri Dec 14, 2012 6:36 am

I just purchased Powershell Studio 2012 two days ago, so I would think it's the newest version.

Post by **davidc** » Fri Dec 14, 2012 9:00 am

I have a few questions for you:

1. Can you verify if the Exchange Module is the cause? Can you temporarily remove the snapin?
2. Can you post any Windows Log Errors?
3. What versions of .NET do you have installed?
4. Look in the install folder of PowerShell Studio and check if the following files exist:

CacheBuilder.exe.config
CacheBuilder64.exe.config

Thank you,

David

Post by **barberta** » Thu Dec 20, 2012 1:59 am

Sorry for the delay. I can't really remove the snapin without uninstalling the Exchange Admin tools. Since this server is used for many scheduled scripts, I really can't remove the tools.

Here's the Cachebuilder error:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: cachebuilder64.exe
Problem Signature 02: 2.1.13.0
Problem Signature 03: 507f3318
Problem Signature 04: Microsoft.Exchange.Diagnostics
Problem Signature 05: 14.1.438.0
Problem Signature 06: 50b94221
Problem Signature 07: 57e
Problem Signature 08: c
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional Information 1: 644e
Additional Information 2: 644e9d1a4c67345f9180e6d69ee4795d
Additional Information 3: 7d77
Additional Information 4: 7d7709096c6d61157236226377cc050c

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:Windowssystem32en-USerofflps.txt

---------------------------------------------------------------

Here are the .NET frameworks installed:
2.0.50707
3.0
3.5
4.0

and yes, the Cache Builder config files are in the install folder.

SAPIEN Technologies