topic Re: Identity Safe is messed up in 360 in Norton 360

Identity Safe is messed up in 360

upAcreek — Fri, 12 Mar 2010 05:52:44 GMT

somebody has got to help me with this.

I am a staunch Norton supporter, but after using this product for two years I deleted the "user" on my computer and created two other users named snowflake and admin. Unfortunately it has been discovered the new "users" have none of the passwords stored that I have gathered over the last two years.

It appears as if Identitiy Safe was reset when I created new users, I figured it out because I was prompted to set up new password information. Is there any database where I might be able to get my stored information, since I am a Norton Account holder? Or is it gone for good?

Where exactly did my identity safe logins and passwords go?

Re: Identity Safe is messed up in 360

Thalir — Fri, 12 Mar 2010 07:13:54 GMT

Identity safe profile is unique to each windows user account. In general, if you wish to transfer the IDsafe data from one user to the other you can,

1. Backup the IDSafe data to a .npm file from one user

2. Switch to the other user and create a new profile

3. Restore the backed up .npm file

The Identity safe's datastore is available in the following location,

C:\Documents and Settings\All Users\Application Data\Norton\{random_numbers}\Norton\IdentitySafeDataStore\{random Number}\IDDStore.dat

In your case, check if you have the this DAT file for the old user. If you find it then it could be copied in to the new user's data sotre folder.

Re: Identity Safe is messed up in 360

kishorec — Fri, 12 Mar 2010 07:08:44 GMT

Hi upAcreek

Please follow the below steps to recover your stored logins

1.Turn off the “Norton Product Tamper protection”(Open the main UI of N360 ->click the settings->Norton Tamper protection->turn off)

2.In windows folder option try to check the “Show hidden files ,folder and drives”

browse the below location

For Win7 :c:\ProgramData\Norton\{0c55c096-sdfsd-dfsf-dfsd…….}\N360_version\IdentitySafeDatastore\s-1-5-21-2231807130…….. here there might two folders check the time stamp which is older based, then locate the folder you can find the IDDStore.dat

3.copy the IDDStore.dat and paste it to the recent time stamp modified location (c:\ProgramData\Norton\{0c55c096-sdfsd-dfsf-dfsd…….}\N360_version\IdentitySafeDatastore \s-1-5-21-2231807131_

For Xp :c:\Documents and settings\All Users\Application Data\Norton\\{0c55c096-sdfsd-dfsf-dfsd…….}\N360_version\IdentitySafeDatastore\s-1-5-21-2231807130\IDDStore.dat

Now try to login to the IDD you can find the logins and password

Hope this will help you, please let me know for any assistance

Re: Identity Safe is messed up in 360

upAcreek — Fri, 12 Mar 2010 21:35:24 GMT

I am going to remember this for the future

Re: Identity Safe is messed up in 360

upAcreek — Fri, 12 Mar 2010 21:41:20 GMT

Ok, at first I forgot to make the hidden files visible so I went there and did not see the necessary folders. :smileyhappy:

So i was wondering instead of copying the files and screwing it up, is it possible to rename the folder that I want? would that be good enough to rename it the name of the other one?

There are also two types of folders in there. There are two that are these long digits

0c55c096.........

And another two that are numbers 84 and 86.

Two sets of two's

Re: Identity Safe is messed up in 360

upAcreek — Fri, 12 Mar 2010 23:29:43 GMT

Dance of joy.

There are Four Folders in there with long numbers. one is from a long time ago and I see cricket wireless and a bunch of accounts in there. woo Hoo!! I added screen shots but took them away, hence the empty spaces where I commented. Just trying to figure out how to get the data out without ruining it. :smileytongue:

Re: Identity Safe is messed up in 360

huwyngr — Sat, 13 Mar 2010 02:24:31 GMT

upAcreek.

I don't know if it applies to the logs you have located but looking at another log created by a Norton product it looks as if the numeric file name is based on ID of application / date/time ....

2010 17 5 0 127 03 12 10...... I've put in spaces to make the grouping clear.

If your logs use a similar code then it should be easy to ID the most recent.

Hope that helps -- if it was already obvious to you my apologies.