Ghost Solution Suite

 View Only
Expand all | Collapse all

Errors after Installing Upgrade of Symantec Ghost Solution Suite on Windows 2003 Server

  • 1.  Errors after Installing Upgrade of Symantec Ghost Solution Suite on Windows 2003 Server

    Posted Feb 27, 2009 04:02 PM

    Here is a Message I got after Upgrading from Version 8.2 to Solution Suite 2.0 (v.11.??)  Please advise why I am getting multiple SQL Errors during the Installation and Errors Starting Up?  I can't get into the Ghost Console becuase It tells me: "Unable to Connect to Database. Retry?"

     

    The first Set of Entries is from the original installation.  The Second Set of Errors is after I tried doing a Liveupdate to fix it to Version 2.02.  No luck though.

     

    The following information has been placed on the clipboard. Visit the Ghost forums at http://forums.symantec.com/discussions/forum.jspa?forumID=109 and supply this information to gain help with this error.
    Symantec Ghost Configuration Server
    An exception has occurred of type C0000005
    C:\Program Files\Symantec\Ghost - C:\Program Files\Symantec\Ghost\ngserver.exe 11.0.0.1502
    [ Limited backtrace only ]
    e:\depot\ghost\gsstrunk\ghost\configureagent\library\src\gc\hashmap.cpp#126:Library::Gc::SHashMap::at
    e:\depot\ghost\gsstrunk\ghost\configureagent\server\database.cpp#1229:l_loadTasksForClientInitiation
        unsigned int clientViewId = 25
        unsigned int taskId = 22
        unsigned int passwordHash = 0x35608264
    e:\depot\ghost\gsstrunk\ghost\configureagent\server\database.cpp#4962:g_loadClients
        unsigned int mask = 0xFFFFFFFF
    e:\depot\ghost\gsstrunk\ghost\configureagent\server\database.cpp#5209:g_dbInit
        unsigned int event = 232
    e:\depot\ghost\gsstrunk\ghost\configureagent\library\src\thread\worker.cpp#289:Library::Thread::QueueWorkerThread::dispatcher
        unsigned int param = 0x100FD5C
        void * token = 0x43137B


    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 C0000005
    C:\Program Files\Symantec\Ghost - C:\Program Files\Symantec\Ghost\ngserver.exe 11.0.2.1573
    [ Limited backtrace only ]
    e:\depot\ghost\gss2.0\ghost\configureagent\library\src\gc\hashmap.cpp#129:Library::Gc::SHashMap::at
    e:\depot\ghost\gss2.0\ghost\configureagent\server\database.cpp#1235:l_loadTasksForClientInitiation
        unsigned int clientViewId = 25
        unsigned int taskId = 22
        unsigned int passwordHash = 0x35608264
    e:\depot\ghost\gss2.0\ghost\configureagent\server\database.cpp#5012:g_loadClients
        unsigned int mask = 0xFFFFFFFF
    e:\depot\ghost\gss2.0\ghost\configureagent\server\database.cpp#5261:g_dbInit
        unsigned int event = 228
    e:\depot\ghost\gss2.0\ghost\configureagent\library\src\thread\worker.cpp#328:Library::Thread::QueueWorkerThread::dispatcher
        unsigned int param = 0x110FEE0
        void * token = 0x4380BB



  • 2.  RE: Errors after Installing Upgrade of Symantec Ghost Solution Suite on Windows 2003 Server

    Posted Feb 28, 2009 02:24 AM
    The GP faults described in the NGERROR.TXT are simply follow-on consequences of the SQL errors; it will help to see those original SQL errors since they describe what has actually gone wrong.

    That said the the most likely cause for those is a failure of some kind during the upgrade process; during the upgrade, the V2.x installer has to transcribe all the data out of your original database into one that is laid out for the new server and console. Perhaps this process has failed somehow; or, perhaps one other alternative is that you have transferred your original v8.2 database - the SYMANTECGHOST.DB file - by hand into your new GSS 2.0 install (which cannot possibly work - the database transcription process performed by an in-place upgrade is absolutely necessary).

    Once we can be sure (from the SQL error) quite what has gone wrong we can suggest how to resolve it; usually though, that will involve recreating the v8.2 install and re-running the in-place upgrade so that it successfully transcribes your old data into a database laid out for the GSS 2.0 product.