<< SharePoint 2007 Content Deployment Error: Out of disk space | SharePoint 2007 Content Deployment: Deploying Large Applications >>

SharePoint 2007 Content Deployment - Error: Missing DLL, Web part, Feature, etc

Thursday, 14 February 2008 00:14 by RanjanBanerji

During Content Deployment one source of errors is when the destination server is not built up with all same custom code as the source server. It is important that you deploy all your solutions, features etc to the destination servers before you start a Content Deployment. Always use solutions to deploy your code. (A subject for another post).

But what if you installed all your custom code and you still get errors like:

2/13/2008 3:12 AM Could not find WebPart Microsoft.SharePoint.dll v2.0.50727 in the safe controls list.
2/13/2008 3:12 AM Could not find WebPart Microsoft.SharePoint.Portal.dll v2.0.50727 in the safe controls list.
2/13/2008 3:12 AM Could not find WebPart Microsoft.SharePoint.Publishing.dll v2.0.50727 in the safe controls list.
2/13/2008 3:12 AM Could not find WebPart Microsoft.Office.Server.Search.dll v2.0.50727 in the safe controls list.

Note these DLLs are not even custom code. Thoss errors will look like:

2/13/2008 3:12 AM Could not find WebPart abc.dll v2.0.50727 in the safe controls list.
2/13/2008 3:12 AM Could not find WebPart [Unknown: e00c1c31-ev55-ceu2-8c9c-69ee3dh5b1dc] in the safe controls list.
2/13/2008 3:12 AM Could not find WebPart [Unknown: 1274a4fy-c7h6-mbcc-c55n-d08e2d4c7f6b] in the safe controls list.
2/13/2008 3:12 AM Could not load file or assembly 'qwerty, Version=1.0.0.0, Culture=neutral,

Why would this happen if you deployed all your code? And why would you get errors about missing SharePoint DLLs?

It happens when you do not start the Windows SharePoint Services Web Application on the machine running Central Administration. If you do not start this service then any solution deployed, will not be added to this machine. Since Content Deployment is setup as a process between the two CA servers it is important that the web application is turned on. You do not have to use this machine for the purpose of being a WFE, but the service should be started. Once you do so all your custom code will get deployed to this server too and you will not get these errors during Content Deployment.