I was recently evaluating the web analytic reporting capabilities within SharePoint 2010 and ran into a strange problem.  Although the reports were displaying correctly they would appear blank if I attempted to “Customize” them. After spending a few hours scouring the Internet and reading different posts and solutions I was able to piece together a solution that resolved it for me.

If you attempt to customize a web analytic report in SharePoint 2010 and it comes up blank, make sure you have done the following:

• Started the Claims to Windows Token Service via Central Admin > Application Management > Manage services on server
• Verify the User Defined Function Assemblies via Excel Service Application has a reference to Microsoft.Office.Server.WebAnalytics.UI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c (Assembly Location is Global Assembly Cache).

If any one of these is not setup correctly, your reports will show up blank when you view them via Excel in browser or in client. Once you have these two things configured correctly, reports display perfect!

A really poorly styled Word document lead me to write this blog post today to rant!  Is this really that difficult?  I see it all the time – people constantly screwing around with the numbered lists in documents. They decide to re-number something but they change the number and the rest of the numbers change, sometimes they don’t, and sometimes even half of them change.

I have seen people battle with this problem for hours!  In the end, all this headache could have been avoided with about 1 minute worth of effort up front. Most people will rely on Word’s automatic numbering system to figure things out – it’s not worth the hassle… trust me!

In a new Word document, do the following:

• Click the Heading 1 style and type “Heading 1”
• Click the Heading 2 style and type “Heading 2”
• Click the Heading 3 style and type “Heading 3” (and so on)
• Click on the Define New Multilevel List button

• On the Define New Multilevel List dialog box, click the More button in the lower left corner. Select 1 on the left-top and then on the right select Heading 1 as the style to use for the level. Repeat this for all the levels you have defined (in my example, 3) and then click Ok.

Magically your document will be transformed! You will never have to mess with it again!  If you do then it means you messed something up.

Pro Tip

The default behavior when pressing Enter will change the style back to Normal.  If you want to continue the heading styles instead you can solve this easily by modifying the styles of the headings you want this behavior on.

For example, if I select the Heading 2 style and type “Heading 2” and hit enter and I want it to keep the Heading 2 style, so I can type Heading 3, etc. then simply right-click on the Heading 2 style in the styles box and select Modify. Then change the Style for following paragraph to Heading 2.

Now when I press enter, the style will stay.

If at any point, you want to adjust the settings of the multilevel list, simply right click on one of the numbers and click Adjust List Indent and you will be taken back to the multilevel list dialog box.

I don’t think this is rocket science – if it is, then I guess I am a rocket scientist!

If your organization is rolling out Windows 7 with Office 2010 in your environment but you are still using SharePoint 2007 you might notice that the “Set as default My Site” option is no longer working. Clicking this link is crucial to enabling the Office / SharePoint integration points.

If you do not already know this, each time you click on the Open or Save menus within an Office product it looks for a special registry key under the user profile. This registry key tells Office what SharePoint farm your user is connected to and will retrieve their SharePoint site membership information. Once this information has been retrieved, it will hydrate the “SharePoint Sites” (or “My SharePoint Sites” on Office 2007) folder.

NOTE: If it successfully finds this location in the registry it will not check it again for up to 24 hours.

I have other posts that explains how this membership works in SharePoint and how to effectively use it with Office.

On to the issue – you will notice that if you visit your My Site with Office 2010 installed you may see the “Set as default My Site” display momentarily and the disappear.

If we look closely at the HTML source of the My Site page, you can see that Microsoft is attempting create a new ActiveX object:

objPersonalSite = new ActiveXObject("PortalConnect12.PersonalSite.1");

If you use the developer toolbar and attempt to evaluate objPersonalSite it will return null.

Searching through the registry, I found no mention of PortalConnect12.PersonalSite.1 – I did however find a mention of PortalConnect14.PersonalSite.1. No wonder the ActiveX control is not working – there is no reference to it on the system.

I took the PortalConnect14 keys and duplicated them and changed the values from 14 to 12 using a registry file:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite]
@="PersonalSite Class"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite\CLSID]
@="{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite\CurVer]
@="PortalConnect12.PersonalSite.1"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite.1]
@="PersonalSite Class"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite.1\CLSID]
@="{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}"

I went back to my My Site and the automatic dialog box popped up asking if I want to set this site as my default My Site:

I clicked Yes and went to the registry location I was aware of (HKCU\Software\Microsoft\Office\14.0\Common) but did not see the Portal key I was expecting.  Come to find out, on Windows 7, this is written to another location:

HKCU\Software\AppDataLow\Microsoft\Office\14.0\Common\Portal

At this point, if you fire up any of the core Office applications and click on Open or Save As and wait a few minutes, you should see a “SharePoint Sites” option appear and start hydrating it with all your SharePoint membership sites.

A few years ago I developed a free SharePoint URL Shortener and released it to the community. I have not had much time to go back to it since.  I had some time recently and decided to add a feature that I have wanted to have for a long time and many have asked for.

With the release of 1.0.2, you can now customize the short name before it gets created.  If you do not specify a name then one will be generated for you.

The following screenshots show the process:

If you decide not to customize the name, you simply click “Ok” and one is generated for you:

You can download this solution from my CodePlex site at http://spurlshortener.codeplex.com.

Future plans for this solution include:

• Removing the dependency on Central Admin
• Allowing users to update shortened URLs
• Provide a list of shortened URLs assigned to an item

[Updated]

SharePoint URL Shortener 1.0.3 was released that added initial SharePoint 2010 support.

Throughout my childhood I always felt close to my brothers. But as my older brother and I started our own families that sense of brotherhood fades. We see each other at family events and in passing but we will never really get back to that point where we were as kids. When you finally realize this gap exists it is too late to make up that time. In recent conversations, we bring up fond childhood memories and relive those moments; always putting a smile on our faces. As brothers, we will always have a strong bond but we don’t always tell each other how we feel.

My younger brother has been dealt a pretty shit hand in life but has always risen above it and has always had the love and support of his family. Frankly, I do not think he realizes how much respect I have for him — this letter is to address that and is written for him.

To my youngest brother,

I see the heart and passion you put into everything you do. As a self taught music producer, artist, and video producer, you continue to grow with every new project. You refuse to believe that you have reached some ceiling and continue to strive.

During your recent stay, we had this silly idea to record a video of me playing all the instruments in Rock Band and then you would edit it all together and create an epic music video. There were some moments during that experience that you couldn’t script and made us laugh so hard. This is totally something we would have done as kids. Having that very specific moment with you brought back that childhood feeling — it is a moment in time that I will remember forever.

While driving home the other day, I was listening to your latest album you produced with Nonsense and I felt an immense sense of pride overcome me. "This is my brother’s creation I hear coming out of my speakers" I thought to myself — I just couldn’t believe it. This new album is definitely a high point in your music career and you should be proud of what you have created.

I had no problem laying down my $8.99 for this album — the feeling of passion and creativeness speaks for itself. I have always supported your work but I have never purchased your work. That ended with this album and it was worth every penny!

You have had many struggles and challenges in your life but I know you will achieve great things.

Standing at this fork in your life journey looking back at the broken road you have travelled; remember that it has built a solid foundation and life experience that is invaluable. The journey forward will be smooth sailing. Never look back but always remember where you came from.

With much love and respect,

Your brother,

Paul

Related Links:

Better Late Than never – Nonsense

Limp Bizkit – Re-arranged by Darkside Productionz and Poogle
Five Finger Death Punch – Hard To See by Darkside Productionz and Poogle

SharePoint is a platform I am pretty passionate about and I have been doing it for many years. Unfortunately, over the past year my priorities at work have shifted to other projects and my SharePoint interactions have been limited.

2012 is going to have some new challenges and learning experiences for me. My organization has shifted my focus and I’ll be living and breathing PeopleSoft for the next year or so. This change will undoubtedly limit my interaction with SharePoint yet again.

I have high hopes to return to the SharePoint platform in the future and I will do my best to remain intact with the community and the happenings around SharePoint.

You will more than likely see a shift in my posts from SharePoint to PeopleSoft related content over the next few months (if I feel I have something to contribute).

Thank you for the continued support – SharePoint definitely has one of the best communities out there.

Anyone else in the community have PeopleSoft experience?  Any pro tips?

This morning I received an interesting support ticket.  The reported issue was that when clicking a document from SharePoint it would completely freeze the browser and Word.  I tried it from my desk and was able to reproduce the issue. It was only occurring with a specific document.

Immediately I thought this form must be corrupted. I saved it to my local desktop and was able to open the file without any issues. Bizarre – I click the File menu (I am running Office 2010 but problem exists on both 2007/2010) and all of a sudden Word froze and I received the “Not Responding” message in the title bar. I finally had to kill the process; tried it again, same issue.

I extracted the contents of the DOCX file and started investigating the content.  I noticed that the document had metadata columns from SharePoint with some values in them. One metadata column stood out from the rest because it had about 20 blank spaces at the end of it.

I deleted all the blank spaces, re-compiled the DOCX file, and tested it and the problem was gone.

I thought to myself there had to be something special about this document. So I decided to create a brand new SharePoint library with a couple metadata columns and then created a brand new Word document. When I edited the Word document, I immediately went into the Document Properties panel, keyed in some text, and then added about 20 blank spaces. When I clicked the save button, word hung again with a “Not Responding” message.

Decided to do a few more iterations; I added 1 trailing space, worked fine, 2, worked fine, 3, worked fine. I started to notice that the more spaces I added the slower the “Save” dialog got until I eventually hit about 13 spaces and it no longer returned and Word completely froze.

Under normal circumstances, you should never have this many spaces trailing your metadata but I think this user cut and paste the text from another location and selected too much.

In the past, I have had numerous issues that involved Word freezing when saving or opening but never knew the root cause. We generally fixed it by re-creating the document. I at least now have another location to check before we resort to re-creating a document.

Check it for yourself – you will no doubt have the same issue.

It appears the User Profile Database growth issue I posted about previously has been resolved with the February cumulative update for SharePoint 2010.

In my previous post, a temporary solution was provided that involved creating a stored procedure and running it on a scheduled basis to clean up the appropriate tables. In reviewing the KB Article 2597150, it states:

This hotfix package provides store procedures that clean up the Forefront Identity Manager (FIM) history tables during profile synchronization jobs.

If you implemented the workaround, I would encourage you do remove it and then install the February CU.

Here is a link to the February 2012 CU for SharePoint 2010:

http://blogs.technet.com/b/stefan_gossner/archive/2012/03/07/february-2011-cu-for-sharepoint-2010-has-been-released.aspx

I was recently attempting to setup a very specific security model in a SharePoint 2010 environment that I have used in a SharePoint 2007 environment. After I configured the necessary permission levels and SharePoint groups, I went to create a new site and found out that the interface was not displaying the options as I expected.

After clicking Site Actions > New Site and then More Options, I expected to see the option Use same permissions as parent site disabled. Instead, it was defaulted and I could easily switch between Use unique permissions and Use same permissions as parent site without any problems.

Without changing anything related to permissions, I decided to disable Silverlight and revert SharePoint 2010 to the old interface and test it that way.  To my surprise, it worked as expected.

After enabling Silverlight again I decided to experiment with the Permission Levels and discovered that if I unchecked the Add and Customize Pages option, the Silverlight interfaced would then display correctly.

Notice the Use same permissions as parent site is currently disabled.

Does anyone know why the Add and Customize Pages permission level would impact the Silverlight UI in this manner or is there something else I am doing wrong?  This seems like a bug in my opinion.

I am running SharePoint 2010 14.0.6120.5000 (KB2687564).

I ran into a strange problem today in SharePoint and thought I would share it with anyone else just in case you have the same issue.

I was in a SharePoint environment that was working as expected. I had a content database that had 8 site collections in it. I detached the database and then re-attached the exact same content database and received the following error message:

<database> on <server> contains user-defined schema.  Databases must be empty before they can be used.  Delete all of the tables, stored procedures and other objects or use a different database.

After a number of attempts, I could not get the database to add.  I created a brand new content DB, detached, re-added it and received the exact same message.

I finally executed the stsadm addcontentdb command with the assignewdatabaseid and the error went away and the database was added successfully. The odd thing is the Current Number of Sites was now showing 0. I queried the sites table and saw the 8 sites in there so I knew everything was good.

I tried the clearing the SharePoint cache without success.

I finally found the root cause of the problem. It appears someone installed a SharePoint patch into the environment but never ran the configuration wizard. So although SharePoint was operating correctly, when re-attaching the database is knew something was run.

I executed the following command which applied the outstanding patch:

psconfig –cmd upgrade –inplace b2b –wait –force

After this, I was able to add and remove the content databases as I expected too without any issues.

If you ever try to import a site using STSADM –o import within SharePoint and you receive the following error message it could be caused by permissions. However, I have come across this issue when thicket files/folders are involved.

FatalError: Object reference not set to an instance of an object.
   at Microsoft.SharePoint.Deployment.FolderSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
   at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)
   at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)
   at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
   at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
   at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)
   at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
   at Microsoft.SharePoint.Deployment.SPImport.Run()

A thicket file/folder structure is generally created if you save an Office document or Outlook MSG as a HTML file. When these are saved to SharePoint it can be very misleading because you will not see the thicket folder structure from within SharePoint as shown below:

If you have thicket files and experience this problem then I recommend converting the file to another format such as PDF. Once you do this the export/import will complete successfully.

SharePoint does not handle thicket files very well and it would be my advice to try avoid storing them in SharePoint at all.

Upgrading your SharePoint environment?  Need to find declarative workflows through all your content databases for analysis and testing purposes during the upgrade?  The following SQL query can be run against your SharePoint environment and it will display information to help you discover these types of workflows.

SELECT wa.Name,ui.tp_Login, w.FullUrl
  FROM WorkflowAssociation wa
       JOIN UserInfo ui 
         ON wa.SiteId = ui.tp_SiteId AND wa.Author = ui.tp_Id
       JOIN Webs w 
         ON cast (wa.WebId AS UNIQUEIDENTIFIER) = w.id
 WHERE (Configuration & 64) = 64

You can then also use this in conjunction with sp_MSForEachDb to loop through all the databases and execute the query.  This is useful if you have a lot of content databases in your farm. For example:

sp_MSForEachDb 'Use ?; select ''?'' as [Database], wa.Name, ui.tp_Login, w.FullUrl
  from WorkflowAssociation wa
  join UserInfo ui
    on wa.SiteId = ui.tp_SiteId
   and wa.Author = ui.tp_Id
  join Webs w
    on cast(wa.WebId as uniqueidentifier) = w.id
where (Configuration & 64) = 64';

For those of you wondering where the # 64 came from, here you go. If you look at Microsoft.SharePoint.Workflow.SPWorkflowAssociationCollection you’ll see an enum called Configuration with the following values:

public enum Configuration
{
    None = 0,
    AutoStartAdd = 1,
    AutoStartChange = 2,
    AutoStartColumnChange = 4,
    AllowManualStart = 8,
    HasStatusColumn = 16,
    LockItem = 32,
    Declarative = 64,
    NoNewWorkflows = 128,
    MarkedForDelete = 512,
    GloballyDisabled = 1024,
    CompressInstanceData = 4096,
    SiteOverQuota = 8192,
    SiteWriteLocked = 16384,
    AllowAsyncManualStart = 32768
}

You can see that 64 is Declarative – so there you have it.

Microsoft has documented the supported options for HA and DR for SharePoint 2013 databases (http://technet.microsoft.com/en-us/library/jj841106.aspx) but did not have it in a format that was easy to print and review with other teams.

Here is a link to a spreadsheet version of that data: http://sdrv.ms/17zvRf4

I ran across an issue in our organization a few weeks ago involving Explorer View in SharePoint 2007 and SharePoint 2010. The user stated that when they clicked on Explorer View from the View dropdown on a SharePoint library they would get the following error:

Windows cannot access “sharename”.

Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.

Error code: 0×80070035
The network path was not found.

I ran Office Diagnostics and Repairs without any success.  After a few days of troubleshooting I found the solution. It was related to the networking binding order.  One of the WiFi Network Connections on the laptop was disabled and the other one was enabled but the disabled one was first in the order. Once I moved the active adaptor above the inactive one everything worked.

To change the order on Windows 7, you can do the following:

1. From the Network and Sharing Center, click on Change adapter Settings
2. Press ALT to display the menu and then click Advanced and then Advanced Settings.

Use the arrows to change the order of your adapters.

SharePoint 2010 and SharePoint 2013 have moved over to claims based authentication hast he recommended authentication method. If you do any programming against the object model here are a few things you need to be aware of.

Consider the following scenario:

• The web application is setup for claims based authentication.
• You have a user account mydomain\user1.
• You are programmatically added them to the site collection.

The code made look something like this:

using (var site = new SPSite("http://mysharepointsite"))
{
    using (var web = site.OpenWeb())
    {
        web.SiteUsers.Add("mydomain\\user1", "user@mydomain.com", null, null);
    }
}

SharePoint will actually add mydomain\user1 to the site collection and when given the appropriate access, the user will be denied access. Why? Because the Add method does not convert the domain\user to a claims login.

Consider the following code:

using (var site = new SPSite("http://mysharepointsite"))
{
    using (var web = site.OpenWeb())
    {
        web.EnsureUser("mydomain\\user1");
    }
}

SharePoint will actually convert this to a claims login and store i:0#.w|mydomain\user1 and the user will be able to access the site without any issues.

The indexers of objects such as AllUsers and SiteUsers will only work if you pass in the appropriate login.

The following example shows a common scenario that will fail:

using (var site = new SPSite("http://mysharepointsite"))
{
    using (var web = site.OpenWeb())
    {
        web.EnsureUser("mydomain\\user1");

        SPUser matchingUser;
        matchingUser = web.SiteUsers["mydomain\\user1"]; // This will throw a User Not Found exception
        matchingUser = web.SiteUsers["i:0#.w|mydomain\\user1"]; // this will find the matching user
    }
}

The first matching user line will generate a Microsoft.SharePoint.SPException: User cannot be found whereas the the second one will find the user correctly.

There is a great write up on TechNet wiki that explains SharePoint 2010 and SharePoint 2013 Claims encoding. Give it a read: http://social.technet.microsoft.com/wiki/contents/articles/13921.sharepoint-2013-and-sharepoint-2010-claims-encoding.aspx

If you are running SharePoint 2013 and SSRS 2012 in SharePoint integration mode and you attempt to do anything related to SSRS such as Editing Data Source, you might receive the following error:

The permissions granted to user ‘domain\username’ are insufficient for performing this operation. —> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user ‘domain\username’ are insufficient for performing this operation.

This could be caused if your SSRS account has not been granted access to the web application. To resolve this issue, simple run the following PowerShell commands:

$webApp = Get-SPWebApplication –Identity http://yoursharepointapp
$webApp.GrantAccessToProcessIdentity(“domain\SSRSAccount”)

At this point, you should be good to go.

Ever since upgrading from Windows RT 8.1 Preview to Windows 8.1 released, I’ve been experiencing horrendous battery life on my Surface RT. I’d use it for 5 minutes, set it down, and then the next day pick it up it would be completely dead. I did some searching around and came across this post from Microsoft outlining the battery and power for the Surface RT and Surface 2 devices. Near the bottom of the post, you’ll see a section that specific outlines an issue that occurs on devices that where upgraded from Windows RT 8.1 preview. (Source: http://www.microsoft.com/surface/en-us/support/hardware-and-drivers/battery-and-power)

I followed the steps outlined and it completely solved my problem.

Surface RT only: Battery issue when updating from Windows RT 8.1 Preview

If you updated Surface RT from Windows RT 8.1 Preview to Windows RT 8.1, you may notice a decrease in battery life. During the update, the wireless adapter power policy isn’t migrated. Instead, the power policy is set to a default value that consumes more power both during use and in the connected standby state.

To restore the wireless adapter power policy to the correct settings, open an administrator command prompt:

Step 1:
Swipe in from the right edge of the screen, and then tap Search.
(If you’re using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Search.)

Step 2:
In the search box, enter command prompt.

Step 3:
Touch and hold (or right-click) Command Prompt to bring up the context menu. Tap or click Run as administrator.

Step 4:
On the User Account Control dialog box, tap or click Yes.

Step 5:
At the Administrator: Command Prompt, enter the following:
powercfg -setdcvalueindex SCHEME_CURRENT 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 12bbebe6-58d6-4636-95bb-3217ef867c1a 3

Step 6:
Then enter
powercfg -setactive scheme_current

We ran into an issue this week in which the SharePoint 2013 Cumulative Updates installed on the servers did not match what the SharePoint farm thought it was. We had the March 2013 Cumulative Update installed and we were attempting to install a December Hotfix. When running the executable for the hotfix, we received the error message: “The expected version of the production was not found on the system”. The only requirement for this hotfix was that the March 2013 CU was installed.

Both the patch status screen within SharePoint and the Installed Updates within Windows showed the March 2013 CU was installed and nothing we seemed to do could get us going again.

We have no idea how it got in this state… we don’t know if the wizard didn’t get run at some point or what and a call to Microsoft came up empty too and they were stating that we may have to rebuild the whole environment from scratch.

I decided to try a few things before throwing in the towel. The following is a list of the things I did that eventually got the environment to a nice stable and healthy place.

1. Detach All Content Databases (this step is optional)
2. Clear the SharePoint Configuration Cache (I recommend using http://spcachecleaner.codeplex.com/)
3. On the server hosting Central Admin, execute and wait for it to finish to 100%:

   psconfig –cmd upgrade –inplace b2b –wait –force

4. Execute the above command on the remaining servers in the farm one at a time.
5. Install the cumulative update (or hotfix) on each server and reboot if requested.
6. On the server hosting Central Admin, run the SharePoint 2013 Product and Configuration Wizard and wait for it to finish 100%.
7. On the remaining servers in the farm, run the wizard and complete the upgrade.
8. Repeat steps 5-7 for any remaining updates.

At this point, everything should be installed correctly and your updates should now match what is installed.

Today I discovered an interesting change to the security model in SharePoint 2013. Create a new team site with the three (3) default groups: Visitor, Members, and Owners.  Without observing this too closely I noticed that people I added to the Members group were able to completely change all the pages and delete lists.

I thought to myself, “wait a minute – contributors should not have this level of access. All they should be able to do is add, update, or delete content on existing lists.”  I check the permission levels for Contribute and saw it was setup how I expected. Baffled.

After some further analysis, I determined that in SharePoint 2013 there is new permission level called Edit and it is assigned to the member group by default. The Edit permission level states:

Can add, edit and delete lists; can view, add, update and delete list items and documents.

This seems extremely strange and I just do not feel this should be the default setting for a member group. I have no discovered the reason why Microsoft has made this change yet or what benefit it is serving.

I decided to take a look at what the code is doing so I can figure out if there is a way around it. I discovered the following check in the PermissionSetupPage code within Microsoft.SharePoint.ApplicationPages.dll.

sPGroup = this.OwnerParam.Create(currentUser, nums, nums1, PermissionSetupPage.GroupType.Owner);
sPGroup1 = this.MemberParam.Create(sPGroup, nums, nums1, PermissionSetupPage.GroupType.Member);
sPGroup2 = this.VisitorParam.Create(sPGroup, nums, nums1, PermissionSetupPage.GroupType.Visitor);
SPRoleType sPRoleType = (SPUtilityInternal.ShouldUseEditRole(base.Web) ? SPRoleType.Editor : SPRoleType.Contributor);
if (this.CanGrantPermission)
{
    this.GrantPermission(sPGroup, SPRoleType.Administrator);
    this.GrantPermission(sPGroup2, SPRoleType.Reader);
    this.GrantPermission(sPGroup1, sPRoleType);
}

Take note of the SPUtilityInternal.ShouldUseEditRole method that is being called. I followed the trail to this method and found the following code:

internal static bool ShouldUseEditRole(SPWeb web)
{
    if (web.RoleDefinitions.GetByTypeNoThrow(SPRoleType.Editor) == null)
    {
        return false;
    }
    return web.UseEditRole;
}

So it is simply checking for the existence of the Edit permission level in the web and if it doesn’t exist it returns a false and then the calling code will use Contribute instead.

Solution

So if you want to force your SharePoint 2013 environment to use the old method, simply do the following steps:

1. Change all the Members groups from Edit to Contribute.
2. Delete the Edit Permission level

Moving forward – all new sites will now use Contribute instead of Edit. I may consider writing a custom solution in the near future to allow SharePoint Administrators to simply install and change the default behavior but I need to make sure I understand why Microsoft made this drastic change.