Archive for the ‘SharePoint Administration’ Category
Creating virtual machines with Azure is a great way of standing up test servers, especially for SharePoint where the installation can be long.
You can create a SharePoint Server 2014 trial server from Azure by first selecting “From Gallery”:
And then select the “SharePoint Server 2013 Trial”
The problem with this is that SharePoint is already installed for a farm installation and therefore cannot be installed as a standalone server. As the description provided by Microsoft states, you will need to create another virtual machine for SQL Server and possibly another for a domain controller with Active Directory.
To circumvent this issue you can:
- Create the VM using the gallery in Azure as shown above
- Install SQL Server Express 2012 on the newly create VM
- Create a new farm using the New-SPConfigurationDatabase PowerShell command
- Run the SharePoint Products Configurations Wizard and join the farm you’ve just created.
The last three steps are described in this excellent blog article: http://blogs.msdn.com/b/suhasaraos/archive/2013/04/06/installing-sharepoint-2013-on-a-single-server-without-a-domain-controller-and-using-sql-server-express.aspx
Recently, I’ve found that a SharePoint farm failed to update when running the “SharePoint 2010 Products Configuration Wizard” or when running PSConfig directly. The PSConfig log file in the 14 hive contained the following exception information:
07/12/2012 16:18:22 9 ERR Failed to install the application content files. An exception of type System.Xml.XmlException was thrown. Additional exception information: Name cannot begin with the '\' character, hexadecimal value 0x5C. Line 5, position 2. System.Xml.XmlException: Name cannot begin with the '\' character, hexadecimal value 0x5C. Line 5, position 2. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos) at System.Xml.XmlTextReaderImpl.ParseElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace) at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc) at System.Xml.XmlDocument.Load(XmlReader reader) at System.Xml.XmlDocument.Load(String filename) at Microsoft.SharePoint.Administration.SPAspSiteMapFile.MergeAspSiteMapFiles(XmlDocument xmldocSiteMap, String strSrcFilePath, String strMergeFilePattern) at Microsoft.SharePoint.Administration.SPAspSiteMapFile.Copy(String strSrcDir, String strSrcLeaf, String strDestDir, Boolean bMergeMaps, Boolean bBackupExistingFile) at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CopyAdminAppDomainDirectories(DirectoryInfo virtualDirectoryPath, OverwriteSetting overwrite) at Microsoft.SharePoint.Administration.SPWebService.ApplyApplicationContentToLocalServer() at Microsoft.SharePoint.PostSetupConfiguration.ApplicationContentTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask() 07/12/2012 16:18:22 9 INF Entering function TaskDriver.NotifyTaskSummary
I suspected that this was caused by a application I had deployed to the SharePoint farm. However, it was not obvious what in the application was causing the problem.
The key to finding the problem was the call to ApplyApplicationContentToLocalServer in the stack trace. Reading up on the documentation for this method indicated that this is responsible for merging all the site map in the 14 hive and placing them in the _app_bin folder for each web application in the appropriate inetpub folders. These sitemap files are XML documents with “.sitemap.” somewhere in the name.
This post is useful in understanding this process: http://sharepointinterface.com/tag/features/
Using this information I managed to find the sitemap file that was causing the problem – the XML document was invalid since in contained a “\” rather than “/”. And yes, it was installed by the application I had deployed.
Now, what I find interesting is that an issue in a site map deployed by an application can cause the SharePoint 2010 Products Configuration Wizard to fail, and therefore stop any updates from being applied. Not only interesting, but worrying too.
Configuring AD synchronization with SharePoint 2010 can be problematic. Here’s a great post on how to configure the services, including ForeFront Identity Manager:
Here’s information on SP1 for SharePoint 2010 Foundation http://support.microsoft.com/kb/2460058. Download from here: http://www.microsoft.com/download/en/details.aspx?id=26640
And for SP1 for SharePoint Server (Enterprise and Standard) information http://support.microsoft.com/kb/2460045. Download from: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26623
Talking of tools (see Favorite SharePoint Development Tools), the SharePoint Diagnostic Studio from Microsoft provides SharePoint performance monitoring functionality. This tool is particularly useful for consolidating the ULS records across servers in a SharePoint server farm. It’s part of the Microsoft SharePoint 2010 Administration Toolkit v2.0.
While useful, the user interface is not particularly polished or easy to use. In particular, the SharePoint Diagnostic Studio must be run with the language set to “US-English”, otherwise date formats will be presented incorrectly and date/time filtering will not work.
Overall Description: http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=971
Global resource (resx) files are stored in the following locations in SharePoint 2010:
- App_GlobalResources folder in the VirtualDirectories folder in inetpub (e.g. C:\inetpub\wwwroot\wss\VirtualDirectories\80)
- Resources folder in the 14 hive (e.g. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Resources)
- Config/Resources folder in the 14 hive (e.g. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Resources)
In general, a single resx file in your solution should be copied into each of these locations during installation. This is how they are used:
- Resources files in App_GlobalResources are used when code in an ASPX page refers to a resource, e.g.
<asp:Label ID="lblNumberingTitle" runat="server" Text="<%$Resources:GlobalSiteResources, AutoNameTitle %>" />
- Resources files in the Resources folder are used when referencing resources using the SharePoint object model, e.g.
btnExport.Text = SPUtility.GetLocalizedString("$Resources:GlobalSiteResources, Tab_Export", "GloablSiteResources", language);
- Resources files in the Config/Resources are copied into the App_GlobalResources folder whenever a new web application is created. By adding the resx files here you will ensure your application will be able to access its global resource files in new web applications.
When performing a Microsoft SharePoint 2007 restore you may receive this error:
Object NG_Documents (previous name: Documents) failed in event OnRestore. For more information, see the error log located in the backup directory.
COMException: The path specified cannot be used at this time. (Exception from HRESULT: 0x80070094)
To fix this problem you may need to apply this hot fix: http://support.microsoft.com/kb/946517
Note that this is a hotfix that is applied to Microsoft Windows Server and not to SharePoint itself.