Ghost Solution Suite

Hello,

I'm trying to ghost a computer with ghost solution suite 2.5.1. LU2 (11.5.1). I'm getting a weird error I didn't had before on a specific computer:

The following information has been placed on the clipboard. Visit the Ghost forums at https://forums.symantec.com/syment/board?board.id=109 and supply this information to gain help with this error.
Symantec Ghost Client Agent
An exception has occurred of type C0000005
X:\GHOST - X:\GHOST\ngctw32.exe 11.5.1.2266
0x7611C4EC in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\Windows\System32\user32.dll
0x7611C43B in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\Windows\System32\user32.dll
0x76118B7B in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\Windows\System32\user32.dll
0x41B9C3 in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\GHOST\ngctw32.exe
0x4092AF in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\GHOST\ngctw32.exe
0x409950 in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\GHOST\ngctw32.exe
0x40A0E9 in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\GHOST\ngctw32.exe
0x40AA24 in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\GHOST\ngctw32.exe
0x40B1BC in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\GHOST\ngctw32.exe
0x44ECA4 in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\GHOST\ngctw32.exe
0x76623833 in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\Windows\System32\kernel32.dll
0x775BA9BD in \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\Windows\System32\ntdll.dll


In the ghost console log, I have that message:
Date   : Mon Feb 15 19:01:55 2010
Error Number: (643)
Message: The destination disk could not be locked
Version: 11.5.1.2266 (Dec 24 2009, Build=2266)
OS Version: Microsoft Windows XP Professional Service Pack 3 (Build 2600)
Command line arguments: -clone,dst=1,mode=restore,src=@MCGHOST2push7564 -batch -sgb -jm=U -jaddr=192.168.99.10 -sgt
Active Switches :
       AutoName

I've checked on the net and I can't find anything.

Thanks

This is the same error as discussed here: the exception is an error internal to Windows itself, and it's not one that we have seen ourselves here at Symantec or have any information as to how to reproduce so we can understand why this part of Windows is failing and what series of events or environmental conditions are required for it to fail.

The "destination disk cannot be locked message" is new information that no-one has mentioned before and is quite odd; the console task processing isn't supposed to (and in my experience never does) try and run the restore operation from within the target operating system, as it has apparently tried to do - as indicated by the fact the error occurred in Windows XP SP3 instead of Vista (which is where the exception occurs).

No the error is in the Winpe. The computer reboot, then when it does ngctw.exe -console, it start and I get a popup with all that messages, then it exit to command prompt, siting idle. I then open notepad, past the error and reboot to access the net.

Also, I've checked and I do have a x: ramdisk, so it's weird. Problem is, it used to work. Less then a month a go, I've created and deploy images on that computer.

ipconfig /release
start ghost client service
ipconfig /renew

I'm not sure how you have your winpe disc configured, but if the ghost client is starting as a service you will need to edit the dhcp service that your winpe environment runs and make it dependant on NGCLIENT.  this should alleviate your issue. (regedit your winpe hive and make the dhcp service dependant on the NGCLIENT service)

I've yet to get the client throw this error if the host pc does not have an IP.  It will throw the error if the host pc has already gotten an ip and been disconnected from the network (physically) then reconnected after the client service starts (in this case the client will appear happy until the host pc is reconnected physically).

This error cannot be reproduced without fail.  I have taken one good, clean image and applied it to multiple pc's.  In this case, some fail (throwing the c0000005 error with similar results to everyone else here) and others work without issue.  The only difference is that some have -very- slightly different hardware (ie: same Acer model, but with different model description in sys info.. same components but likely a slightly different iteration motherboard).

Everything else in windows works fine, so as I have stated before this has to be an issue with the ghost client only accepting null values for information returned in relation to the dhcp service.  Otherwise the above stated method should not work.  This has to be something to do with changes made by the 2.5.0 - 2.5.1 patch.. I dont know why the error would generate only when the dhcp service has been started, but it seems to be the only common factor.

I'm having the same problem, but in my case I'm trying to pull an image off of a xp machine with a static IP.  Connectivity is fine, it can ping the ghost server from the dos prompt.

In fact, it's starting to look like all 140 of my workstations have the same failure. Makes sense, since they all have the same hardware and are running the same image.

I have done the above mentioned work around, and that alleviated my issue with the machine connected successfully to my ghost console.  However once it is connected and I attempt to start a create task for this machine it dumps on me again, disconnects from the console and throws up the same error message.   Is there anything I am missing?  This machine has been used several times in the past to creat images from and has had no porblems.  It has been a couple months since I created an image of this machine, however that is the case for all of the other 6 machines I have to create images from, and the other 6 worked just fine.  This happens to be the only machine that has an issue, and it is running windows xp sp3.  Anyone have any ideas?

I posted the information about the underlying cause of this in the other thread and there I outline that the underlying cause of this is due to the machine lacking a hardware SMBIOS UUID. The fault can often be resolved by using a manufacturer utility to correct the manufacturing error that left the machine without a UUID.

Hi,

The c0000005 issue has been addressed in Ghost 2.5.1 build 2298. You can find more information on the link given below.

https://www-secure.symantec.com/connect/blogs/ghost-client-error-c0000005-resolved-build-2298