Failure Writing To Target File

• Failure Writing To Target File Format
• Error Writing To File
• Import-spweb Failure Writing To Target File

Failure Writing To Target File Format

I am moving serveral seperate SharePoint servers into 1 large farm. Before I can decommision the old servers, I need to move the sites. An excellent way to complete this is by using STSADM -o export and then using STSADM -o import.I am testing on an application server with not much space left (2 gigs) and I have a SharePoint site that has 4 gigs of data. We have plenty of space on the SQL server, which is where the data will ultimately be stored.I have left the files on the old server, created a share, and mapped a drive on the new server to the share. That way I do not have to copy the files to the new SharePoint server.Now before you say DUH!, I will remind you that SharePoint breaks these files into.BAK files for you, so you would think you would be OK. Each individual file will be loaded, decompressed, processed, closed, deleted, and then repeat.

Error Writing To File

Or not?Well, the answer is not. And the error I got was not very intuitive (surprise)! The error message I received is below, but I will get to my point. The error is not that the system was unable to write to the target file, but rather that the system ran out of space. You will need to run Disk Cleanup and try to get some space back. Oh, and if you are running Server 2008, see my post on '.10/9/2009 5:05:57 PM: Start Time: 10/9/2009 5:05:56 PM.10/9/2009 5:05:58 PM: Progress: Initializing Import.10/9/2009 6:41:04 PM: Error: Failure writing to target file10/9/2009 6:41:05 PM: Debug: at Microsoft.SharePoint.Library.SPRequest.ExtractFilesFromCabinet(String bstrTempDirectory, String bstrCabFileLocation)at Microsoft.SharePoint.Deployment.ImportDataFileManager.cDisplayClass2.

Import-spweb Failure Writing To Target File

B0at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)at Microsoft.SharePoint.SPSecurity.cDisplayClass4.