I was recently doing an export for a pretty big MOSS site and I ran across the following error while using the following stsadm command:
stsadm -o export -url http://servername/site -filename D:\backup\sharepoint.cab -includeusersecurity -overwrite
We verified that the C drive had 1 GB of space and the D drive had 50 GB of space. Simple enought right. Wrong!
After some head scratching, we figured out that the export uses the C drive to store the entirety of the backup files before writing it to the D drive. More specifically, the location pointed to by the TEMP environment variable was being used for the backup.
The solution we found was to change the TEMP and TMP environment variable to point to a temporary folder on the D drive and then do the backup. (I had to also logout and login in order for the variables to take effect).
That solved my issue. Thanks for the help!
Glad it helped you out Robert.
I am having the same problems. could you please tell me how to change the TEMP and TMP environment variable to point to a temporary folder on the D drive.
Hi Kokila. Sorry for the delay in posting back. Temp and TMP are changed in the System Properties | Environment Variables. See http://ask-leo.com/how_do_i_change_the_location_of_windows_temporary_files.html for more info.
I was also facing the same issue.
I had enough space in my drive even though I was getting the “There is no enough sapce in the disk” error.
Moving temporary files to another drive helped me resolving my issue.
Three years later, still helping. Thanks!
Still Helping. Your a lifesaver!
Still valid 🙂
This issues also affects the 2010 Export-SPWeb cmdlet that I have. Hopefully, the tool will improve in future.
Am I missing something because I made these changes as mentioned above and I am still having the same issue. Is there some other setting that tells SharePoint backup or export to write to c:\ that I am missing?
Hi TD. There may be other logs to check. But if you followed the instructions, then it should be all you need. Unless they changed it recently. All I can say, is make sure to run as an administrator when changing the TEMP and TMP environment variables. Hope this helps.
Here are the other logs in SharePoint.
All file based logs can be read by text editors and can be parsed by using popular log parsing tools (Log Parser 2.2 from Microsoft or Funnel Web). It will also be a good idea to read the IIS Logs which are generally saved at (System Drive):\WINDOWS\system32\LogFiles
a) Diagnostics Logs
· Event Throttling Logs – These end up going to the Windows Event Log and can be viewed in the Event Viewer. They show Errors and Warnings.
· Trace Logs – These show detailed line by line tracing information emitted during a web request or service execution. They end up being stored at a known location on the front-end server. Default Location: (System Drive):\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\
b) Audit Logs – They end up in the associated Content Database tables and can be viewed at Site Collection Level as well as Site Level using the web browser. WSS 3.0 and MOSS 2007 use different pages to show Audit Log Reports.
c) Usage Logs – They get stored locally on the front-end servers and get processed both locally and at farm level via SSP (this is based on the setup as I understand the results from the local processing are merged by SSP) and can be viewed at both the Site Level and Site Collection Level. Default Location: (System Drive):\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs
d) Search\Query Logs – These are saved in the associated SSP database but can be viewed at SSP level via the Web Browser and in MOSS at Site Collection Level by going to the settings page.
e) Information Management Logs – Stored in the associated Content Database and can be can be viewed at the Site Collection Level.
f) Content and Structure Logs – This option is only available after one enables the publication feature. This store is saved in the Content Database associated with the Site Collection and can be viewed at Site Collection level by going to the settings page.