Posts Tagged ‘.NET’

Can’t Find PowerShell Modules Shortcut

The new server build process seemed to have changed slightly for my most recent SharePoint 2010 server. Everything looked for the most part as it should, but there were still a couple of minor things here and there that just seemed slightly different.

Fast forward in time – I have SharePoint installed, patched, and configured. Now I need to run some PowerShell commands to check a few things – but there aren’t any PowerShell items under All Programs > Administrative Tools as there is on my other servers. Sure, I have the basic “Windows PowerShell” folder under “Accessories,” but that’s about it.

Normally I’d say “ok, no problem” and move on, but I wasn’t even able to add my SharePoint snapin in a normal PowerShell window as a work around:

PS C:\>add-pssnapin microsoft.sharepoint.powershell
The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.

After a bit of research I found that it’s an issue with some combination of Windows Server 2008 R2 SP1, .NET 4, and PowerShell 3. Doesn’t Microsoft make all 3 of these? Why can’t they play well?

Anyway. No need to uninstall .NET 4 or any crazy work-arounds. Just go to Control Panel > Uninstall a Program > View installed updates > and search on “Windows Management Framework.” You’ll likely have “Microsoft Windows Management Framework 3.0 (KB2506143)” installed.

Uninstall Windows Management Framework 3

Uninstall it and reboot when finished.

Like magic, I now have my “Windows PowerShell Modules” app link that loads everything I need, as well as the “SharePoint 2010 Management Shell” under the SharePoint folder!

Thanks to Trevor’s answer in this thread for saving my day. I figured I’d post this here for my own future reference, and also because my scenario started out slightly different than original topic in that thread.

SharePoint 2010 ‘allowInsecureTransport’ error

I’ve been working with SharePoint 2010 and Word Automation Services quite a bit these days. I recently ran into an error that I just could not figure out. There’s very little out there on teh interwebs, and the only solution that I found sounded perfect. At first.

When attempting to convert a file from .docx to .pdf via Word Automation Services we were receiving:

Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (D:\Program Files\Microsoft Office Servers\14.0\WebServices\WordServer\Proxy.config line 77)

This was a brand new SharePoint install and everything appeared to be configured correctly. The ONLY solution that I could find was to apply a .NET hotfix (KB976462). It made sense. It sounded perfect! However… the .dlls that the hotfix wanted to apply were at an older version than what was already on the SharePoint server. At this point, we opened a case with Microsoft… (more…)

ASP Parser Error

More “dreaded” errors in SharePoint. We started receiving the this fun error when loading one of our portals:

Server Error in ‘/’ Application.
Runtime Error
Description: An application error occurred on the server.[…]


Ajax CalendarExtender Cropping Off Days

I’m currently working on a project to extend SharePoint’s capabilities with some C# .NET stuff. This is been quite the learning experience for me, since I’m not a developer or programmer by any stretch of the terms.

The latest oddity that I’ve run into is with the CalendarExtender. It’s supposed to look like this:

However, at some point it started looking like this:

ASP.NET v2.0 Not Appearing in IIS

Lately I’ve started performing more server builds with MOSS 2007 installs and I’ve noticed a trend.

SharePoint requires the ASP.NET v2.0 to be registered in the IIS Web Service Extensions and set to “Allowed.” If this is not the case, the SharePoint installation will error out – simple as that. It seems pretty common to find .NET 2.0 installed but not displaying in IIS. I’ve found the solution a number of times over across the ‘net (quick and easy!) but not the answer to “why did this happen on this server but not the other?” (more…)