Error restoring a site from another SharePoint 2007 website

No, I only have the original backup file.

I often see this problem when someone has applied manual customization to the site (like new web parts) without using Sharepoint Deployment Solutions.  Did your site have any customization?

Quite possibly, I didn't create the oroginal site, so I can't be sure. Is there anything I can do? Would importing through stsadmin be any better? Is there some log I can look at or anything to help determine the issue? Or am I just out of luck here?

If they are cmp files, you can use stsadm -o import and name the first .cmp file during the import.

:-)

I get the same old error like this:

"Could not find the file C:\WINDOWS\TEMP\f611fafc-73d8-4b48-bc1e-f9ef6d7cb991\Exportsettings.xml"

Wait a minute.  stsadm has two sets of complimentary commands.  Backup/Restore OR Export/Import.  You can't Import a Backup and you can't Restore a Backup.  I'm wondering if that is your problem.

Sorry, there was a type, you can't Restore and Export.

Are there any other thoughts?

Did you mix a Backup with a Import? Or, did you mix up a Export with a Restore?  That would cause this problem.

It seems that this is not an uncommon problem, and without the original site, you are in a bit of trouble. Do you have any of the original SQL DB's? Or at least backups of the SQL DB's?

:-)

All I have is the CMP file, and I nolonger have access to the original site. That's why I'm trying to restore the backup file =) I figured a "backup" would be a safe option, but it seems restoring backups doesn't work so well.

If I did have access to the old site, what would I have needed to have done differently?

You should always have backups of the SQL DB's. You would also be better off using stsadm to backup your sites. It works far better than the SPD backup, although in essence they are one and the same.

:-)

Ah, I reread your message.  I assumed you used stsadm not Sharepoint Designer.  Robbie is correct, use stsadm and SQL backups.  Sharepoint Designer doesn't do a good job.

Robbie: I understand what you're saying, and deciding what to do with a question where the answer isn't exactly what I'm looking to hear isn't easy. All I can say for sure is that people here have been unable to help me import the file that I need. That doesn't mean that it is not possible to import the file still. I would agree however that you both deserve something for all the effort that you've put into your responses, because I do appreciate that. But I don't feel that any of the above should be selected as a resolution to the issue. I based that on the question I ask myself when I am in this position. If I hadn't posted the question, but was having the same problem, and I found this post, would I take the answer as the solution or would I keep looking. And in this case, I will keep looking.

We're having a SharePoint vendor come in to do some work in the next couple of months. If they are unable to import the file, I will accept that as the solution. If they are able, I will post the resolution for importing the file.

I don't want to offend anyone by saying that I need a third opnion before I consider it truth, it's just too important to stop searching.

I absolutely agree. I hope they can find a solution. No offence taken.

:-)

The asker was told 'no' that isn't possible.  It appears that they did not have everything they needed to restore the backup.  I do not believe they should receive a refund.

Please leave it open. I'm still waiting for my second opinion from a hired vendor. We just haven't gotten to that item in the process yet. I will post the results of that once the vendor has concluded the issues is resolvable or not.

Sorry, I'm with Tedbilly on this one.

:-(