Laeeq Qazi's Exchange Server Blog

Exchange Server blog

No snap-ins have been registered for Windows PowerShell version 3

Hi,

I was developing an app to manage exchange mailboxes and having the error when running the app in VS 2010.

No snap-ins have been registered for Windows PowerShell version 3

It turned out that I was targeting x86 platform in project properties, and I think due to which app was trying to pick 32 bit powershell. I changed the target cpu to “Any CPU” and then error disappeared.

Also please look at http://blogs.msdn.com/b/pareshj/archive/2010/07/30/error-msg-no-snap-ins-have-been-registered-for-windows-powershell-version-2.aspx

Hope it helps someone else too.

Note: To develop apps for Exchange 2013 preview using Exchange PowerShell sdk, you would have to use VS 2010, becuase Exchange server 2013 have been developed using .net 4.0, and you cannot add .net 4.0 DLL references in VS 2008 or lower versions.

Regards,

Laeeq Qazi

Advertisements

October 2, 2012 - Posted by | Exchange 2010, Exchange 2013 | ,

4 Comments »

  1. Wonderful exchangegeek.wordpress.com. I used to generally be checking constantly this exchangegeek.wordpress.com and I am impressed! Extremely useful information particularly the closing section I offer with such data much. I used to generally be looking for this selected information for your quite long. Thank you and beneficial luck.

    Comment by SafjQyek14 | November 14, 2012 | Reply

  2. Excellent stuff from you, my friend. Ive scan your exchangegeek.wordpress.com before and you??£¤re just Awesome! I enjoy what you??£¤ve got listed here, take pleasure in what you??£¤re saying and also the way you say it. You make it entertaining and yet you still manage to continue to keep it smart & to the point. I cant wait to browse additional from you. This is certainly in fact a excellent & pretty perfectly exchangegeek.wordpress.com!

    Comment by XeusFtik34 | November 18, 2012 | Reply

  3. The Windows Server 2008 R2 PowerShell fix for me was to copy the PowerShell registry key from a working server to the one that was having problems.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\

    Problem solved. The SharePoint PowerShell snapin is now Registered and the one that gets installed with SharePoint works.

    Comment by arnoldvilleneuve | January 23, 2016 | Reply


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: