Closed Bug 50169 Opened 24 years ago Closed 24 years ago

Profile Migration is Not Happening

Categories

(Core Graveyard :: Profile: Migration, defect, P3)

Product:
Core Graveyard
Component:
Profile: Migration
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: sol, Assigned: dbragg)

References

Details

Using Build 2000-08-24-04, profile migration is not happening. I did a "clean" 
install of the build, the profile manager screen came up with a list of my 4.x 
profiles, I selected an existing profile and hit "Start Netscape 6". Instead of 
seeing the profile migration progress dialog, I was immediately taken to the 
Activation page. After Seamonkey started, I went into Mail, and none of the 
email or news accounts I had set up in my 4.x profile were present in Seamonkey.

Build 2000-08-24-04 on WinNT (commercial).

Steps to reproduce:
0. Delete the "Netscape 6" and "Users50" folders and their contents, delete 
mozregistry.dat.
1. Install Seamonkey (I did a "Complete" install).
2. At the profile manager screen, select a profile that exists in Communicator 
4.x (I am using 4.72).
3. Hit "Start Netscape 6".

Expected: The profile migration progress dialog box appears, and after migration 
is complete, an Activation screen appears.

Actual: The profile migration progress dialog does not appear - you are taken 
immediately to Activation. Note that after Seamonkey starts, and you then go 
into Mail (Tasks | Mail) none of your 4.x email or newsgroup accounts have been 
migrated.
Sol,
Try removing HOME\mozilla\registry.dat file - HOME may be c:\winnt.
this file is recording profile data now and may have your profile data from last
migration.

Grace - thanks - that did the trick.

Did something change in the last couple of days? I've never had to delete 
"registry.dat" before to invoke profile migration.
yes, profile information now stored in $HOME/mozilla/registry.dat - so when 
doing a new migration this file must be removed for seamonkey to look to 4.x 
registry (changes in last week- 8/16 or so- still changing)

Don, why not mark this worksforme?
Marking INVALID since this is really a test case problem and not really a 
WORKSFORME (since I get the same results as Sol if I don't delete the 
registry.dat file)
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
vfy
Status: RESOLVED → VERIFIED
*** Bug 50530 has been marked as a duplicate of this bug. ***
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.