Thursday, September 18, 2014

Method 'Upgrade' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' message

The good admin you are, you just finished deploying the Windows patches for September on your non-SP1'd SharePoint 2013 farm server...rebooted...Central Admin comes up fine...open up PowerShell and kaboom!

  Method 'Upgrade' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.Wor Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation.

There's an update that assumes you already have SP1 deployed - if you go back to Central Admin you'll note the UI changes for O365 & Yammer are now showing up. The fix is to deploy one more hotfix to your server - you can download it from here: http://www.microsoft.com/en-us/download/details.aspx?id=42898

No reboot required - install the update, open up that PS window & you're blissfully error free.

Happy SharePointing!

SharePoint 2013 Site Codes and Descriptions

Below is a list of the out of the box site codes available for SharePoint 2013.  This is for the 1033 (US English) locale:

Site CodeDescription
GLOBAL#0Global template
STS#0Team Site
STS#1Blank Site
STS#2Document Workspace
MPS#0Basic Meeting Workspace
MPS#1Blank Meeting Workspace
MPS#2Decision Meeting Workspace
MPS#3Social Meeting Workspace
MPS#4Multipage Meeting Workspace
CENTRALADMIN#0Central Admin Site
WIKI#0Wiki Site
BLOG#0Blog
SGS#0Group Work Site
TENANTADMIN#0Tenant Admin Site
APP#0App Template
APPCATALOG#0App Catalog Site
ACCSRV#0Access Services Site
ACCSVC#0Access Services Site Internal
ACCSVC#1Access Services Site
BDR#0Document Center
DEV#0Developer Site
DOCMARKETPLACESITE#0Academic Library
EDISC#0eDiscovery Center
EDISC#1eDiscovery Case
OFFILE#0(obsolete) Records Center
OFFILE#1Records Center
OSRV#0Shared Services Administration Site
PPSMASite#0PerformancePoint
BICenterSite#0Business Intelligence Center
SPS#0SharePoint Portal Server Site
SPSPERS#0SharePoint Portal Server Personal Space
SPSPERS#2Storage And Social SharePoint Portal...
SPSPERS#3Storage Only SharePoint Portal Serve...
SPSPERS#4Social Only SharePoint Portal Server...
SPSPERS#5Empty SharePoint Portal Server Perso...
SPSMSITE#0Personalization Site
SPSTOC#0Contents area Template
SPSTOPIC#0Topic area template
SPSNEWS#0News Site
CMSPUBLISHING#0Publishing Site
BLANKINTERNET#0Publishing Site
BLANKINTERNET#1Press Releases Site
BLANKINTERNET#2Publishing Site with Workflow
SPSNHOME#0News Site
SPSSITES#0Site Directory
SPSCOMMU#0Community area template
SPSREPORTCENTER#0Report Center
SPSPORTAL#0Collaboration Portal
SRCHCEN#0Enterprise Search Center
PROFILES#0Profiles
BLANKINTERNETCONTAINER#0Publishing Portal
SPSMSITEHOST#0My Site Host
ENTERWIKI#0Enterprise Wiki
PROJECTSITE#0Project Site
PRODUCTCATALOG#0Product Catalog
COMMUNITY#0Community Site
COMMUNITYPORTAL#0Community Portal
SRCHCENTERLITE#0Basic Search Center
SRCHCENTERLITE#1Basic Search Center
visprus#0Visio Process Repository
ECMWebTemplate#0Enterprise Content Site

Friday, September 12, 2014

Default gateway blank or 0.0.0.0

Ever had your server's default gateway stuck showing either 0.0.0.0, or blank entirely?  Totally ignoring the value you're assigning?  Happened to me when I was bouncing between client Hyper-V on Windows 8.1 and VirtualBox.  The culprit?  All of those prior network connections.  Once you get rid of them, network properties works like a charm.

The catch?  The devices and old connections are hidden.  To show them, open up an administrator command prompt, and enter the command:

set devmgr_show_nonpresent_devices=1

then enter the command

start devmgmt.msc

to start up Device Manager (or launch it from Control Panel).  Then, in the View menu, choose Show Hidden Devices, expand out your Network Adapters and be amazed:


See all of those hidden devices?  The active one, Microsoft Hyper-V Network Adapter #19 is shown with the bold icon, but the others, including the Intel (R) PRO/1000 adapters are somewhat blurred - those are the ones to delete.

Do that, reboot for good measure, set that default gateway and be productive!

Update: I decided to poke around some of the other devices & there were more to remove, when making the VirtualBox to Hyper-V switch.  Expand out some of the other nodes to clear out the old VirtualBox devices.  Having these around wasn't causing problems, but the less clutter the better.

 

Also, be sure you remove either the Hyper-V Integration Services or the VirtualBox Additions from Windows Control Panel Add/Remove Programs, as appropriate.  And if you're switching back to VirtualBox, odds are the Additions are out of date, so go ahead & refresh.