I am trying to restore a site using stsadm, I am getting the following error: "The site collection could not be restored. If this problem persists, please makesure the content databases are available and have sufficient free space." I have enough free space in my drives. Please help

Can you give us your stsadm statement (and preferably the backup statement you used as well).

stsadm -o restore -url http://SiteCollectionURL -filename "Path" -overwrite stsadm -obackup -url http://SiteCollectionURL -filename "Path"

An extract from KB: This issue occurs if the computer that is running Windows SharePoint Services has insufficient free disk space that is available to host the restored Windows SharePoint Services Web site. This issue may also occur if the Windows SharePoint Services database has reached its maximum allowed size. http://support.microsoft.com/kb/926061/en-us Are you sure that you hadn't reached the max allowed size?

I have loads of free space on my hard disk and also have set "Unrestricted growth" for my DB files.

Hello, This issue you encountered may be a little complex, in such a case I recommend you to use the following steps to narrow down the problems scope: 1.Check the free space of the partition and the backup folders size. Let me know the details. 2.Check the structure of the backup folder to see if some very large (>1G)sub-folders exist. 3.If possible, modify the location of the backup folder and try to restore from it again. If the problem persists, reproduce it anduse the following steps to collect some logs: 4.Check Event Logs (Run eventvwr.msc) under the Application and System entries, to see if thereare any errorswithin the time frame. 5.Check the ULS logs that were generated during that time frame. The location of ULS logs is: %commonprogramfiles%\microsoft shared\Web Server Extensions\12\LOGS and formatted as SeverName-Data-Timestamp.log For your convenience, I have created a workspace for you. Please upload the log files to the following link. (Please choose "Send Files to Microsoft") Workspace URL: (https://sftasia.one.microsoft.com/choosetransfer.aspx?key=019ad203-09de-4c2e-bd33-1a91df51a376) Password: ^xBuZRbX)Yw!Lg9N Note: Due to differences in text formatting with various email clients, the workspace link above may appear to be broken. Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser. Regards, Lionel

Hi all; I have the same problem, I have two page file of 4GB, the site collection have two contect database in different disk, the space in c:\ is 50Gb y on d:\ is 300 GB, but when Irun ststadm -o restore follow show the same error. Somebody could help me.

Hi Chen,I am getting the same error. The site collection could not be restored. If this problem persists, please make sure the content databases are available and have sufficient free space. "I tried all your stated things but I could not see anything informative. One thing I can see is Console configuration XML exception List does not exist but it does not say which list but after it generates this message it populates 4 more GB of data and then fails over.Did anyone find a fix for that or please give me suggestions on how to fix it. I have over 300 GB of free space left on the server. The thing I noticed is log file (.ldf reaches to 2.5 GB) and then I get the above message I am struggling with this problem since so many days.I hope someone will help me in fixing this. please help meRegardsChandra

OK, why is this accepted as the answer? There is no answer here. This is a request for information.I have the same problem. On Staging Serverstsadm -o backup -url https://domainA/sites/collectionA -filename c:\backup.datc:\backup.dat is a single file that is 430MB in sizetransfer the file to the production server, then:On Production serverstsadm -o restore -url https://domainB/sites/CollectionB -filename c:\backup.datC:\ on the Frontend SharePoint Server has 30+ GB availableDatabase server (SQL Server 2000 Cluster) has 100+GB available where the Content DB is store and all other drives have at least 30 GB available. The Database itself is set for unrestricted filegrowth.No errors are generated on the SharePoint Server or the Database server during this timeframe.What gives? I checked the log area that was mentioned and there was nothing there.

This regularly happens to me as well. Restore fails, even though there is more than sufficient disk and database growth space.I believe this is a bug. I resolve this issue by doing the following: Restart the Windows SharePoint Services Timer service Run iisreset from the command prompt. Restore content database.Works every time.

Hi all,We have just run into exactly the same issueThere's plenty of space on all serversand the bak file is not that big (around 200mb).We can't find anything in the LOG files or event viewer. However, using an earlier backup file worked fine. Can there be something wrong with the site collection backup file? In that case, how come there's no message about it or something that explains what went wrong?I alsonoticed that even though the restore fails, the tables (like dbo.AllLinks), are filled up with links from the site collection. So the restore seems to be incomplete and no rollback was made when it job failed.Thanks,Christoffer

This regularly happens to me as well. Restore fails, even though there is more than sufficient disk and database growth space. I believe this is a bug. I resolve this issue by doing the following: Restart the Windows SharePoint Services Timer service Run iisreset from the command prompt. Restore content database. Works every time. It works. Thanks a lot.

Stopping the Timer and restarting didnt help us.But detaching and reattaching the content data base did work.Regards,Mahesh

Thanks after spending an couple of hours on other solution, this small trick worked. Many Thanks!

Thanks after spending an couple of hours on other solution, this small trick worked. Many Thanks!