Monday, December 10, 2012

One Note synch password prompt for SharePoint 2010: A password is required to synchronize this notebook. (Error code: 0x80070005)

When synching OneNote Files with SharePoint 2010 our users continually were getting Password prompts on starting OneNote. 

"A password is required to synchronize this notebook. (Error code: 0x80070005)"

After searching high and low I came across this thread on the MSDN forums:

Within that thread a MSFT support person suggests this KB article as a possible fix:  The key point of this was the fact that in my environment we do not use a proxy server, so I am not sure how this will work with a Proxy, but it solved my issue.  The fix is already included in Win7, but you need to create the AuthServer list as follows:

1.       Click Start, type regedit in the Start Search box, and then press ENTER.

2.       Locate and then click the following registry subkey:


3.       On the Edit menu, point to New, and then click Multi-String Value.

4.       Type AuthForwardServerList, and then press ENTER.

5.       On the Edit menu, click Modify.

6.       In the Value data box, type the URL of the server that hosts the Web share, and then click OK.

Note You can also type a list of URLs in the Value data box. For more information, see the "Sample URL list" section in this article.

7.       Exit Registry Editor.
8.    Restart the WebClient Service in Admin Tools|Services|WebClient

Wednesday, September 19, 2012

"Cannot start service SPAdminV4 on computer '.'." error on SharePoint configuration wizard

This entry is for those environments with the June 2012 CU for SharePoint 2010 (And as Mike notes in the comments 2012 December CU) .  This patch causes CRL checks to be enforced, which in turn affects some native functionality of SharePoint AdminV4 service.
When running the SharePoint Product Configuration Wizard, the configuration will fail with the following error:

Failed to create the configuration database.
An exception of type System.InvalidOperationException was thrown.  Additional exception information: Cannot start service SPAdminV4 on computer '.'.

In order to bypass the CRL Check for SPAdminV4 service startup, the following steps need to be completed on each SharePoint server.
1.) Add a new computer policy which alters the options for retrieving certificate validation on a network.
2.) Add host file entries into the local computer host file.
  • Alter the computer policy
    • Click on Start-Run
    • Type in "GPEdit.msc" and click "OK"
    • Expand Computer Configuration-Windows Settings-Security Settings-Public Key Policies
    • Double-click "Certificate Path Validation Settings"
    • Click on the "Network Retrieval" tab
    • Check the box "Define these policy settings"
    • Uncheck "Automatically update certificates in the Microsoft Root Certificate Program (recommended)" and "Allow issuer certificate (AIA) retrieval during path validation (recommended"
    • Click on "OK"
    • Close out of GPEdit.msc
  • Add host file entries
    • Click on Start-Run
    • Type in "C:\Windows\System32\Drivers\Etc" and click "OK"
    • Double-click the file "Hosts"
    • Select "Notepad" as the program to open the file
    • Insert the following lines into the hosts file
    • Save the file and exit notepad

Wednesday, September 12, 2012

SharePoint 2013 Pre-Upgrade Cleanup

SharePoint 2013 Pre-Upgrade Cleanup

I saw this link thanks to my former co-worker, Richard Harbridge, and he mentions the blurb contained in the above link about "Wide Lists".  This was news to me and my team as well. Everyone is aware of the item limitations within SharePoint, but had never heard about the "wide list" caveat.  With items you can throttle those settings but no settings for columns.  Irregardless, the need to perform a clean up of your environments prior to upgrading is a point that can never be made enough.

Monday, August 27, 2012

One Note: An error occurred while attempting to sync this section or notebook

So this is one that comes up often, when attempting to sync up a One Note Notebook with a SharePoint 2010 site, you will get a red icon on the notebook and some variation of: "An error occurred while attempting to sync this section or notebook."

Basically this is due to the fact that "Require Documents to be checked out" is enabled on the library.  From everything I've seen online, this is a known bug with Microsoft, but no fix available that I could find.  Now the workaround of course is to uncheck that setting in the Library Settings/ Versioning Settings, BUT forcing Check out is a huge part of certain governance standards, so make sure you check with the site users so that they can determine which need is more pressing.

Wednesday, August 8, 2012

Office App Store for SharePoint 2013 is now live

One of the new features of SharePoint 2013 is the creation of an "App Store" for custom widgets and templates for all to share either as free downloads or as a pay for model.  The link to the SharePoint specific portion of the office app store is below:

As the Apple vs. Android app stores have shown, the key is consistency of the apps, and making sure that they are vetted properly.  This feature will be a huge component of 2013, but as an admin I potentially see some governance opportunities as to how to handle these.  That would be along the lines of coming up with an approved list or process of allowing these into various environments, and creating an internal app store that our developers can use to share features across farms and platforms.

Tuesday, July 17, 2012

SharePoint 2013 Presentations

With Microsoft Office "Wave 15" and SharePoint 2013 right around the corner, Microsoft has started to post several videos and slides around the upcoming product.  Below is a link to the IT Pro track on Technet, from a high level overview to Architecture and Upgrade modules.
For It Professionals:

Also there is a MSDN link for Developers with the same type of information:

"Value does not fall within the expected range." When activating Microsoft Publishing after 2010 upgrade

We recently did an upgrade from MOSS 2007 to SharePoint Server 2010, and one of the site collections wouldnt allow Publishing to be activated. It either threw a Columns error or the "Value does not fall within the expected range." error when attempting to access. Via STSADM or PowerShell, it would error out as well, including removing completely and attempting to re-install. (note
this problem Site Collection is a legacy WSS 2.0 site collection that had been upgraded to WSS 3.0, MOSS and now to SP2010 which is bad, but we never had the ability to force new sites to be created)

In doing a side by side comparison between the problem Site Collection and one that worked using the Get-SPFeature -url http://SharePointsite, it showed that the Publishing service is actually composed of 3 seperate features.

I enabled them in the above order by running:
Enable-SPFeature -Identity PublishingSite -url Http:://SharePointsite
Enable-SPFeature -Identity PublishingLayouts -url Http:://SharePointsite
Enable-SPFeature -Identity PublishingResources -url Http:://SharePointsite

And that did the trick.