Hey Chan,

Currently we are not certain about the model number to see any compatibility or hardware problems.  Below are the steps you can try to remediate this query. C

1)  We can change the drive modes under the BIOS to AHCI, IRRT etc and see if that helps.
2)  Change the boot sequence was helpful to get rid of this error message. (First boot device to CD-ROM and second boot device to hard disk).
3)   At the final point, I would recommend running the recover and access to get rid of this error message.

Regards
Nitin L

Hi,

Is Symantec aware of this problem?

Have seen this on one customer with few laptops, Windows XP SP3. Laptops used successfully about one month, and suddenly this error when starting up laptop.

Yes, we know how to decrypt laptop's hard disk but that's not an way to correct the actual problem.

Laptops having this error; HP NX8220 and some other HP business model. Drive mode from bios is set to IDE.

We're also starting to see this problem - laptops have been fine for a while but we've had 2 in the last week with this same error. Like you say, we can run the access tool and get the data / image the machine but this is a few hour operation - not something we can afford to do for our critical machines.

I'd be interested to know how widespread this problem is...

We are having this problem too. In the last couple weeks it has happened 5 or 6 times. Please post any updates if you have them and I will do the same.

You mentioned that  you've installed see 7.0.3 in your Enviourment -- thinking about upgrade ! :-) ..... try getting hold of client packages for 7.0.4 from symantec tech support -- install them on the client machines and then see if they resolve the issue ?? You can try what Nitin Lal suggested above too ... 

7.0.4 doens't resolve this issue, have tested with same results. And Nitin's suggestion is not acceptable solution for this problem, because it doesn't fix the actual problem.

What hardware is anyone having the problem on? I notice the first post mentions HP laptops - we're also having the problem on HP  (Elitebook 8530p) so it would be interesting to see if its all down to the same manufacturer...

Different kind of HP laptops, Elitebooks, older NC's and so on...

 
guys if you want you can check with Symantec tech support when 7.0.5 is getting released --- this should fix your concerns

Our quickest method of recovery is using the access utility within a WinPE USB stick and using Ghost (also incorporated into our USB stick) to ghost directly onto a spare disk. Put that into the failed machine and off you go again. It takes about 2 hours (data capactiy depending of course). WinPE boots much faster on the USB than CD.

I have it on good authority that it is fully fixed in 7.0.5 which is due very soon (I heard early March so anytime in the next few weeks I guess). I've also been told that its not down to any specific hardware or setup!

Hope that helps...

I encountered this error too today on Dell OptiPlex 745 running XP and GuardianEdge 9.1.5. 

What  is the resolution Symantec?

I am also getting this error now, on a Sony Vaio TX2XP, running windows XP.

The laptop was encrypted about 4 or 5 weeks ago and has been working fine, then this morning getting the error.

Is there a resolution to this problem?

Regards

Julian

Version 7.0.5 of the SEE resolves this problem.

Thanks David.

What needs to be done to the broken laptop though?  Does it need to be decrypted and re-imaged - or can the update be installed on it somehow?

Thanks again

Julian

I dont beleive there is any way of 'fixing' it - you cant do the update to 7.0.5 without getting into windows, which you can't do. The recover utility can fix it but only as of 7.0.5 anyway! The only way we found was to use the access CD to boot and then get the data you need to take an image. We used the access tools, then ghosted the drive, then ghosted it onto another machine/disk and it boots without encryptiong and is all fine.
Hope that helps

Thanks for the advice :)

I'm experiencing this issue this morning. We all have the same  Lenovo notebooks, but I'm the only one to have experienced this issue. Did I do something accidentally or is this just  a random occurrence? Just curious.

We never worked out exactly the cause. When we asked the official answer was 'an internal consistency in the SEE files' but we were never given anything more precise about the root cause. Some suggestions were around other AV/spyware tools - certainly one occasion that we had the error was shortly after doing a Spyware scan.