When deploying content through content deployment jobs you may want to check how much space you have available.
Not so well documented is the fact that content deployment jobs will require you to have some space available on the drive where the account running the SharePoint Timer service has its local temp folder (in the user profile). I only realised this today when investigating a content deployment failure, what happens during a content deployment is the following:
- Timer collects the content deployment data from SQL and stores this in the accounts temp folder (usually in the c: if you have not change environment variables)
- Data is then extracted and dumped in the folder specified as the content deployment folder in Central Admin.
- Extracted data is moved to the content deployment folder on the target machine.
- Timer on destination machines extracts the data to its local temp folder and dumps it in SQL
Wow, lots of space needed and if you have not changed the envrionment variables, this may casue some space issues on the servers.
Now what I found interesting is that the user profile temp folders were not being cleared out after this whole process - OUCH, better create a scheduled task to clear this out.
- This may be due to the failed deployment job - so double check. In fact, even if it is because of this that means content for failed jobs is still hanging around.
Some Ideas:
- If you are installing a clean environment, be sure to change the environment variables for the account that will be running the SharePoint Timer service.
- In existing environment, try changing the temp folder location in the reg (HKEY_USER)
An event you may encounter:
The following event description may crop up if there is not enough space left to uncompress the deployment files:
"Failed to read package files"
- You will also see it in the deployment job failure message
Regards,
Doug "bob the builder" McCusker