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.

Tags:  
Categories:   SharePoint
Actions:   E-mail | Permalink | Comments (4) | Comment RSSRSS comment feed

SharePoint 2007 Content Deployment Error: Out of disk space

Wednesday, 13 February 2008 22:04 by RanjanBanerji

Every now and then Microsoft manages to create a design that puzzles the hell out of me.  This time it is yet another issue with SharePoint 2007 Content Deployment.  When setting up your application for Content Deployment you go to the Central Admin and select "Content Deployment Settings".  One of the settings here is the location where SharePoint will temporarily store CAB files while exporting and importing.

One should ensure that there is sufficient disk space available on the drive where you set the Temporary Content Deployment folder.  However, this is not enough.  You can still get an out of disk space error.  You see, Microsoft in its infinite wisdom uses yet another temporary folder.  Content Deployment is carried out by the Timer Service.  In its first step, the timer service gets data from the database and holds it in a temp area.  Once all the data is extracted CAB files are created and stored in the temp folder that you selected in the "Content Deployment Settings" in Central Admin.  The the files are moved to the destination machine to the temp folder selected on the destination machines Central Admin "Content Deployment Settings".  Then the destination machine's Timer Service will take these CAB files and extract their contents to a temp location before loading it into the database.

So what is this temp location that is used by the Timer Service?  Well, guess what?  It's not the location you specified in Central Admin.  It is in fact the default USERPROFILE temp storage location for the user under which the Timer Service is running. 

If the Timer Service is running on Local System then the temp folder used is the system TEMP and TMP folders that defined as your Environment Variables. Usually C:\Windows\Temp.

If the Timer Service is running as a specific user or service account then the temp folder used is the users TEMP and TMP folders that defined as your Environment Variables.  Usually C:\Documents and Settings\The_User\Local Settings\Temp.

You can change these location via a registry change (HKEY_USER) or by modifying the environment variables to point to a drive that you know will always have ample space for your Content Deployment to work.

Also, note, if you ever change the user that runs the Timer Service, you will need to modify that user's TEMP/TMP locations.

ugh!!!!!!!!!!!!!

Tags:  
Categories:   SharePoint
Actions:   E-mail | Permalink | Comments (7) | Comment RSSRSS comment feed