Ghost Code 19903

Posted on 2009-02-22
Medium Priority
Last Modified: 2013-12-02
I'm using Ghost Solution Suite 2.0
I want to gather an image of a  Client Machine. PXE booting work fine. Ghost Client and Driver loads fine. No problem there...
Once the multicast starts, a dialog appears saying " Ghostcast session failed with ghostcode error 19903.."
This thin DOS client that Symantec have chosen to "cling" on, is annoying to say the least.
Having done some reading on other forums, it appers the problem may be memory related.
I've tried recreating the boot files using  MSDOS (win98 se) and adding the following lines into


No go. Same error.
Help appreciated
Thanks in advance
Question by:Beeshoring
LVL 63

Expert Comment

ID: 23718019
1) Do you have the latest GSS 2.02 or 2.5 ?

2) Have you tried doing a Local Netork backup via a bootable Ghost CD to see if that works OK ?

I hope this helps !

Author Comment

ID: 23763734
Apologies for the late reply.
GSS 2.02 seems to equate to build
The Ghost32.exe version on my CD says (Its' a compiled CD made by my former company)

I will try the CD as suggested, now that I  have the NIC drivers.

Accepted Solution

jeffb67 earned 2000 total points
ID: 24024222
Not sure If you've managed to solve this yet but the solution I found was to use the newest version of the MS-Dos (not the pc dos version) himem.sys file that I could find.  I just injected it into the ghost.dsk vfi and it worked quite happily.  

Its worth noting that I also had no luck using any of the extra switches for loading things into higher memory or making dos load high, not even things like emm386 allowed me to access larger amounts of memory.  Looks like its a flaw with the way pcdos tries to access extended memory.

This link might give you some extra background info which you dont *really* need but its handy to have: http://www.symantec.com/connect/forums/ghostcast-session-setup-failed-ghostcode-19903

So yeah long story short, inject the newest msdos version of himem.sys into your pcdos virtual floppy and things should be apples.

This fix worked for me on 2.0, 2.02 and 2.5 versions of the solution suite.  Let me know how you get on.
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Expert Comment

ID: 24050599
Don't know if this will help anybody, but I had the exact same thing happen to me. Without all the tech talk and wasted explanation, to make things easier for the next person. I had to take a copy of the Himem.sys file from a Windows 98 boot disk that was larger than the himem.sys file that is injected with the msdos version from ghost. Once I injected the 33kb size file over the 14kb size one that came in ghost, I was able to get my image from the Ghostcast session. Good Luck!

Author Comment

ID: 24299089
Thanks Jeffb67 and MrDynomyte. Ok I'll take both your suggestions into account and give it a try. I've been using imageX and WDS which seems to offer many more options. Saying that I've got the Symantec licences so it would be a shame not to use them.  Will let you know how I get on.

Author Comment

ID: 24792190
The himem.sys from the Win98 boot disk did the trick

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…
Suggested Courses

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question