Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Ghost Console crashes during inventory task

Updated: 21 May 2010 | 3 comments
Ifixcomputers's picture
0 0 Votes
Login to vote

I'm running Ghost Console 2( 11.0.2.1573). When running an inventory task the ghost console client crashes. I've pasted the symantec Diagnostics below.


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 Configuration Server
An exception has occurred of type 80000003
C:\Program Files\Symantec\Ghost - C:\Program Files\Symantec\Ghost\ngserver.exe 11.0.2.1573
[ Limited backtrace only ]
0x7C90120E
0x3C30000
Library::Gc::GCMarkCopy::scanPointerIn+0x10F
0x8B560C24

 

Discussion Filed Under:

Comments

Krish Jayaratne's picture
18
Nov
2008
0 Votes 0
Login to vote

Hi, 

 

Does this happen in a one or one model of a machine? 

 

Krish 

 

Ifixcomputers's picture
19
Nov
2008
0 Votes 0
Login to vote

The error appears when attempting to inventory a 100 or more machines. The machines appear to be various different makes and models. It appears that it's a similar issue to this post https://forums.symantec.com/syment/board/message?board.id=109&message.id=13124

 

 

Thanks

 

M

Krish Jayaratne's picture
19
Nov
2008
0 Votes 0
Login to vote

Hi, 

Though the error is the same, cause may not be the same. In your case, this is happening in 2.0 while most of the users in other thread are using 2.5. 

Most of the times, this was caused by garbage characters (or unterminated strings) in some of the device descriptions. Usually this does not depend on the number of machines, but one (or more) machines that has such characteristics. When the inventory refresh task is executed, inventory data is send to the server and stored it as a file. The likely issue is server being unable to interpret the file.  

Having said that, by any chance if this only happens when trying the task with large number of machines, it could be a different problem. Would you be able to isolate it by running refresh on a smaller subset? 
 

Krish