How to troubleshoot the error: "Internal error 36000 . . . "

Symantec.com > Enterprise > Support > Knowledge Base

How to troubleshoot the error: "Internal error 36000 . . . "

Question/Issue:
You are using Ghost to move image data from one computer to another. While Ghost.exe, Ghost Multicast, or Ghost Console is moving the data, you see the error message "Internal Error 36000..." The process will not complete.

Solution:
This message indicates that Ghost has encountered a problem that it cannot work around or resolve. The information on the problem is not enough for Ghost to determine the cause of the problem, and Ghost cannot continue.

Because this situation has a variety of causes, no one solution will work in every case. To resolve the problem, try each of the following solutions.

Note: The following solutions often resolve the problem for other error codes also.

If the problem is not resolved after applying the following solutions, see the document Ghost technical support options for a list of on-line support options. When leaving a message with Ask Symantec, please include the following information:

What you want to accomplish. For instance, cloning from one local disk to another local disk, or rolling out an image of a Windows NT system to many computers.
What steps you took to accomplish this, and at what point in this process you saw the error message.
The complete text of the error message.

This information might help Technical Support make additional suggestions for resolving the problem.

Method 1
When launching the Ghost DOS executable file, use the -fni switch:

ghost.exe -fni

This forces Ghost to ignore direct IDE access and choose another access method.

If using a consumer Ghost version, such as Norton Ghost 2002, use Ghostpe.exe instead of Ghost.exe. For a list of the consumer and corporate Ghost versions, see the document How to determine your version of Ghost.

Method 2
If cloning an NTFS partition or a disk that includes an NTFS partition, use the following combination of switches:

ghost.exe -ntc- -fni -ffx -fns -ntil

Note: The dashes on either side of NTC are correct. Use -ntc- and not -ntc

If using a consumer Ghost version, such as Norton Ghost 2002, use Ghostpe.exe instead of Ghost.exe. For a list of the consumer and corporate Ghost versions, see the document How to determine your version of Ghost.

Method 3
If cloning a computer that has Windows 2000 encrypted secure folders, remove the folder encryption or remove the folders before cloning.

Method 4
If the target computer has a prorietary or hidden partition, try deleting all partitions on the target computer with GDisk before restoring the image. The following is an example command line:

gdisk.exe 1 /y /del /all

Method 5
Modify the Config.sys file on the floppy boot disk to include the following line:

shell=command.com /p /e:2048

Method 6
Run Ghost from the command line. That is, when launching the Ghost DOS executable file (Ghost.exe or Ghostpe.exe), use command line switches to instruct Ghost on what tasks to perform.

For instance, to launch Ghost to copy (-clone,mode=pcopy) the second partition of the first local drive (src=1:2) to the first partition of a second drive (dst=2:1), without displaying the normal final warning prompt (-sure), type:

ghost.exe -clone,mode=pcopy,src=1:2,dst=2:1 -sure

For more information on this process, see Appendix A of the Ghost Implementation Guide or Ghost User Manual.

Method 7
Run a defragment utility, such as Speed Disk, and remove temporary files such as Internet Explorer cache files.

Method 8
Detach unnecessary peripherals, such as scanning devices or zip drives, and then run the Ghost DOS executable file (Ghost.exe or Ghostpe.exe) from the floppy disk with only the files necessary for launching Ghost and for accessing necessary devices. For instance, to write an image file directly to a CD-R or CD-RW device, load the DOS system files and Ghost files and do not load drivers for devices such as scanners, printers, and so on. For more information on which files are necessary for running Ghost, see the documents How to create a DOS system disk for Ghost and Which boot disks to use when writing to CD-R/RW drives.

Method 9
The error "Internal error 36000 Processor exception..." has been resolved in some instances in Symantec Ghost 7.0. To upgrade Ghost, see the document How to obtain current version of Symantec Ghost.

Related problems

This error can also be seen when using the Netgear FA310 network interface card. Ghost is not compatible with this card. Although one of the above methods might resolve the problem, Symantec does not support Ghost working with this interface card. Note that in some cases, the problem has been resolved by ensuring that the file Protocol.ini has an entry for the name of the DOS network interface card driver (DOS NIC driver name) in the NIC section. For instance, Protocol.ini might include the following entries:

[nic] drivername=NGRPCI$
Error: "Internal error 36000" and cannot save image files to SCSI DAT tapes
Error: "Internal Error 36000..." when writing an image directly to a CD-R/RW drive

Available Translations:

Document ID: 1999112214191125
Last Modified: 12/14/2007
Date Created: 11/22/1999
Operating System(s): DOS, Windows 95, Windows 98, Windows ME, Windows NT, Windows 2000, Linux, Novell NetWare
Product(s): Symantec Ghost 7.0, Symantec Ghost 7.5, Symantec Ghost 8.0, Symantec Ghost 8.2, Symantec Ghost Solution Suite 1.0, Symantec Ghost Solution Suite 1.1
Release(s): Ghost 7.0 [All Releases], Ghost 7.5 [All Releases], Ghost 8.0 [All Releases], Symantec Ghost 8.2 [All Releases], Symantec Ghost Solution Suite 1.0 [All Releases], Symantec Ghost Solution Suite 1.1 [All Releases]