I try to move dataCRM 1.2 from a old server to the new one using the
redeployment tool. I'm sure I didn't make any mistakes when doing the
backup steps. But when I get to step 5 and want to import the two
XML-files with the tool on the new server I get this error:

"The wizard could not write to file C:\....\deployment.xml. Make sure
the file is not a read-only file or try specifying a different file."

I'm logged on as administrator and none file is read-only. The tool has
already made some entries before the error appears.

The log-file ends with these messages:

12/12/2005 19:02:12 Membership updated
12/12/2005 19:02:12 Update completed
12/12/2005 19:02:12 Update completed
12/12/2005 19:02:12 Saving mapping file C:\...\mapping.xml
12/12/2005 19:02:12 Saving OU file C:\...\deployment.xml
12/12/2005 19:02:12 Mapping file created
12/12/2005 19:02:12 Entering GetXmlForUsers()
12/12/2005 19:02:12 ADObjectMapping::ToXmlString() called
12/12/2005 19:02:12 Mappings total : 31
12/12/2005 19:02:12 Mappings saved : 2
12/12/2005 19:02:12 ADObjectMapping::ToXmlString() completed
12/12/2005 19:02:12 Leaving GetXmlForUsers()
12/12/2005 19:02:12 Mapping file saved
12/12/2005 19:02:12 OU file created
12/12/2005 19:02:12 Organizational info saved
12/12/2005 19:02:12 Entering GetXmlForNonUsers()
12/12/2005 19:02:12 ADObjectMapping::ToXmlString() called
12/12/2005 19:02:12 Mappings total : 31
12/12/2005 19:02:12 The wizard could not write to file
C:\...\deployment.xml. Make sure the file is not a read-only file or
try specifying a different file.
12/12/2005 19:03:23 Import ended


We work on small business server 2003.

Any ideas are wellcome!

TIA
Stefan

Forgot to mention that there are only the administrator and one user as
CRM-user. Shouldn't be too much! About 1200 contacts and 2000 contracts
with details. All the rest is not in use. What is the problem????

Stefan

Solution was not to install the tool on the server but on a client-PC
in domain and run it from there.
Following microsofts instruction exactly was the wrong way! At least on
SBS2003.

Stefan

Hey Stefan,
I'm about to do this today. You're saying that with SBS, you could
only run the export tool successfully if it was on a client which as
you indicate is not consistent with the documentation?

Has anyone else confirmed this? In any case, I'm going to follow per
the documentation and will post an update if it works, or not.


-Rob