The HTTP library we use has returned ERROR_WINHTTP_INVALID_SERVER_RESPONSE. In our testing we have found this to happen when the migration wizard thinks it should use HTTP when the port specified is in fact HTTPS.
Heres what you can do:
Downlaoad the
WinHttpTraceCfg.exe trace configuration tool (part of windows server 2003 resource kit).
Read the
documentation for the tool.
On the machine running the migration wizard, turn on tracing to a file by executing the following:
Code:
WinHttpTraceCfg -e 1 -l <prefix> -d 0
(replace prefix with something appropriate)
Restart the migration wizard process and try to import again. This time, a log file will be generated with all the traffic. Remove any sensitive information from the log and post it.