>> Sorry that it didn't work for you. It's perfectly OK to leave
Bugzilla aside and ask for help here, though. From experience I can tell
that almost any case of aborted profile migration can be fixed by a
knowledgeable person with direct access to the computer, but
unfortunately it's hard to analyze such problems remotely. <<
Thanks for the response... as you can probably deduce, that was a very
frustrating process and the frustration was still at high levels when I
made the post.
>> Just to be sure:
1. <profilename> exists as a SM2 profile?
2. you ran that command while SM was closed?
<<
Affirmative on both counts, confirmed by using Task Manager as well.
>> I see that you tried the Import option from the MailNews window
partly successfully so you probably still have your registry.dat around,
which, as the Profile Migration Knowledge Base entry states, is a
prerequisite for automatic migration. <<
To restate, one suspicion that I have is that the failure was due to the
fact that the profile folder was not in the default location.
Another possible factor is that SeaMonkey 1.x was not installed in the
"default" (C:\Program...) folder. The initial SM2 install attempt was
in the old seamonkey location, but when that proved difficult and
futile, uninstalled and reinstalled in the "default" location.
I made attempts with;
Profile folder in original location
Profile folder moved to the SM2's default location with NEW SLT folder NAME
Profile folder moved to the SM2's default location OLD SLT folder NAME
Profile folder moved to a different drive... on the assumption that I
might be asked to point to the profile location
>> That sounds really strange. It could be that only parts are migrated
because SM ran into a problem during migration, which could explain that
your mails/addresses were not imported. That part could probably be
worked around by manually setting up the accounts again and copying the
actual data over from the old profile (address book and message formats
haven't changed / are updated automatically when found). <<
Think I'm done for the moment. The reason for the attempt to upgrade
was to beta test a Logitech web app that will not run on SM1.x
...During the above attempts, I determined that the app did not run on
SM2.0.4 despite assurances that the app would run on FireFox 3.1 Both
versions throw an XML error message. (see below)
>> The part that I cannot explain is that you say the changes are gone
after a restart. Assuming that your profile is not write-protected, of
course. <<
Nope... everything was just dandy when I uninstalled SM2 and reinstalled
1.1.17
Thanks for your support.
Hope this info ends up being of value to someone.
Beverly Howard
=======Seamonkey xml error========
XML Parsing Error: junk after document element
Location: http://www.myharmony.com/
Line Number 5, Column 1:<html xmlns="http://www.w3.org/1999/xhtml";>
note, http://www.myharmony.com/ runs in IE6
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
