iDocs - Ultimate Product
Founded in 2016, iCiber delivers expert support for SharePoint, IT Operational improvements, Transition & Transformation Programs, Troubleshooting & Performance challenges. Focus of iCiber is on the Microsoft platforms (e.g. SharePoint, Exchange, Office365, Azure, SQL). Our colleagues from iCiber are Microsoft MVP (Most Valuable Professional) or similar levels. iCiber has significant expertise in delivering operational services from offshore centers.
Areas of expertise: Migration of Service Desk Services, Local Support Services, Cross Functional Services (processes & procedures), Mail Services, File Services, Live Collaboration Services (Skype for business), Computer Device Services (Windows 7/Windows 10), Print & Scan Services, SharePoint Services, Stepping Stone Services and Server Management Services, Performance and Operational improvements large SharePoint environment (>50.000 users), Performance and Operational improvements large Exchange environment (>90.000 mailboxes), SQL, VMware
In this article, I describe the thirteen most prominent pitfalls that I have encountered in the SharePoint migration projects of various organisations.
1. Lack of knowledge
What is SharePoint exactly? Knowledge is the key. It does not matter from which to which version of SharePoint one migrates:
When you run SharePoint management powershell on your SharePoint 2010 server you get the following error:
The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered
Project Name: ADsyncXML script –> http://adimportxml.codeplex.com
Purpose: PowerShell script for (automatically) importing user attribute data into active directory. (source XML, destination AD)
Tested with: Active Directory 2008 (I’am sure it will also works with AD 2012)
To maintain good overall databases performance of the SharePoint 2010 databases I use the following SQL maintenance plan. This plan consist of two main parts: - The configuration of each separate databases and database properties settings - The automated maintenance plan, to perform database maintenance task once a week.
FILESTREAM is a feature of SQL 2008 that supports BLOB file storage on NTFS file shares. This feature is also supported by SharePoint 2010, but first you'll need to enable the feature in SQL 2008R2 server, default the FILESTREAM feature is disabled during the SQL 2008 installation.
To open a PDF document in a SharePoint site (instead of saving the PDF first) you need to change the web application setting: "Web Application General Settings". There is a setting called Browser File Handling and by default it is set to strict. Change this setting to "Permissive" and PDF's open with a PDF reader on the Client.
After installing a fresh SharePoint 2010 standard farm I kept on receiving this error when I try to search something in the search center:
CoreResultsWebPart::OnInit: Exception initializing:
An easy script to backup your SharePoint farm with Windows scheduler. First create a powershell script:
1-Backup a site:
backup-spsite -identity $args -path $args -force
2-Backup the complete farm:
It's a little bit different than SharePoint 2007, you need to change two web.config files instead of one:
In the layouts directory underneath the SharePoint root directory or 14 hive –
If you don't want that disabled accounts will be show in the people picker of MOSS 2007, than run the following stsadm command to add a filter to the peoplepicker query:
stsadm -o setproperty -propertyname peoplepicker-searchadcustomfilter -propertyvalue
I tried to remove a OS cluster with the "Cluster" command but without any succes. After serveral tries I did remove the OS cluster settings from the registry and after a reboot I was able to remove the cluster feature and start all over again to create a new OS cluster.
A little script to do a DPM 2010 restore on item-level to a SharePoint 2010 farm directly after creating the first backup of the SharePoint 2010 environment. Normally every 24 hours, DPM will create a catalogue of the Sharepoint environment in order to allow the item-level recovery.
Receiving the following error in MOSS 2007 when you try to add a new web part?
File Not Found. at System.Signature._GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, IntPtr
Default the "contains" option is missing in the property select field of the Advance Search Webpart in SharePoint 2007. The reason for this is the hugh load on the SQL server if this option is used to query the SharePoint index. So be careful when adding this option.
I experience a rewriting problem with an Juniper VPN Appliance (SA-2500) and a SharePoint website. When I try to access a SharePoint (2007 & 2010) site after connection with the Juniper VPN, the SharePoint site is displayed fine.
I wrote a little script in PowerShell to add users to the Farm Administrator group of a SharePoint environment. You can easily customize this script for other SharePoint groups or import users from a CSV file to import multiple users into a SharePoint Group.
I had been experiencing issues crawling a large document library of over 60,000 items in a SharePoint 2007 farm 64x after the index was corrupt and I had to reset the crawled content. The only error I could find in the crawl log was the error “The item may be too large or corrupt.”
Howto for indexing Adobe PDF documents in a SharePoint 2010 environment:
Download and install Adobe’s 64-bit PDF iFilter: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025
Download the Adobe PDF icon (select Small 17 x 17): http://www.adobe.com/misc/linking.html
After configuring the Search application in SharePoint 2010 I recieved the following error:
The search request was unable to connect to the Search Service.
A few days ago the following errors startud to show up in one off the WFE servers from a SharePoint farm:
Failed to obtain crawl status. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. --->
For MOSS 2007 I used a warm-up script but now with SharePoint 2010 installed on Windows 2008 R2 with IIS 7.5 it is possible to use the warm-up module extensions for IIS 7.5. Download this module at: http://www.iis.net/download/ApplicationWarmUp
I've created the following PowersShell 2.0 script for creating Site Collections in a SharePoint 2010 environment. You can define the following variables:
Create a new Managed path (Explicit or not)
Create a new Content Database or use a existing one
If you create a custom approval workflow in a document library and select this option on the customize workflow screen:
[x] Update the approval status (use this workflow to control content approval)
SharePoint maybe report the following error:
I was building a workflow in SharePoint Designer and sometimes you need some metadata, for extra information or for an e-mail, from a SharePoint user. The problem is SharePoint Designer returns only the username and you cannot do a lookup for the the rest of the metadata from that user.
I used the following two stsadm commands to improve the performance of the MOSS 2007 peoplepicker:
Specify the domains to query:
stsadm -o setsiteuseraccountdirectorypath -path
Server administration programs and the Windows SharePoint Services Web applications on this Web server are not compatible
I got this error when trying to update the peoplepicker query with the stsadm peoplepicker-searchadcustomquery command. In my case I did use a wrong URL, that gave this error.
Removing Invalid SharePoint 2007 Features or features without a feature.xml:
1. Run the WssAnalyzeFeatures tool and view the Problems Log for invalid feature id (guids)
2. Try running STSADM -o deactivatefeature -id %featureIdFromLogFile% -force
3. Try running STSADM -o uninstallfeature -id %featureIdFromLogFile% -force
With the following powershell script you can build webapplications and site collections in SharePoint 2010:
#Include the SharePoint cmdlets
To create and configure a Search Service for SharePoint 2010 with Powershell you can use the following script:
Reviewed this Script 24 september 2010 --> changed some code to create databasesnames without GUID's...
This is a quick tutorial to install SharePoint 2010 on a Windows 7 OS, this is a great way to create a quick development environment for MOSS 2010. Because the default installation works only for Windows Server 2008, you must edit one configuration file and install many of the prerequisites manually.
The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly
This is a rather generic error message and I found out that it generally covers problems communicating with the index server
If a web application is not propogated to all the WFE in the farm you can use the following stsadm option on the WFE where the webapplication is missing:
stsadm -o execadmsvcjobs
If you want FireFox and SharePoint 2007 work with NTLM an SSO authentication, you have to go to your Firefox address bar and type about:config. This will bring up the internal config editor, which allows you to set all kinds of properties that influence Firefox’s behavior.
Why do Site Collections not update with user Profile details?
The main reason for confusion around the updating (sync’ing) of My Profile details into site collections and team sites is that it is now based on if the user is Active. As part of the upgrade to V3 Microsoft introduced the idea of users being active in a site rather than just having access.
To use reportviewer version 188.8.131.52 and reportviewer 184.108.40.206 together with MOSS 2007, add the following rule in the web.config on all WFE:
Disable the IIS loopback check
Follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
Restore the backup from the SharePoint Database into another SharePoint environment, for example the test or acceptation SharePoint environment. Add the restored SharePoint database to a new site collection with this stsadm commando:
The solution to solve the following error in MOSS:
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
If you experience issues with WSS and MOSS timer jobs failing (MOSS Logging) , clearing the configuration cache on the farm is a possible method for resolving the issue. The config cache is where we cache configuration information (stored in the config database) on each server in the farm.
How do I delete the default SSP?
The default SSP can be deleted only if its the only SSP in the farm. To delete it, either type in the URL:
The option to create a page was appearing in their ‘Site Actions’ menu, so this didn’t appear to be a security problem (or this would have been security trimmed), and after inspecting the group permissions which had full control, and the permissions for the group, which allowed the group ‘create page’ permissions