Client error linking to VPartition.dll

What precise version of GSS 2.5 are you running? - and have you run LiveUpdate recently to ensure you have the latest version?
The log suggests an issue with the upgrade of the client not running successfully. I suspect this is what is causing your problem with vpartition.dll.

I have checked the Verson of the Ghost Console and it is version 11.0.2.1573.  I have ran live update and it is telling me neither live update nor Ghost needs to be updated.  Is there anything else that could be causing this error?

williamh,

If the listed version is 11.0.2.1573, then this is Ghost Solution Suite 2, not 2.5. I would recommend upgrading (which you should be entitled to with a support contract) and running all three LiveUpdates for that. Otherwise, the issue you see is likely due to needing to update the DOS driver for the client's network card.  Locate the DOS NDIS2 driver for the card, and add it to the Ghost Boot Wizard. Here are those steps:

Adding or modifying DOS NIC templates in the Ghost Boot Wizard
http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2000011211551725

Then go into the Ghost Console, right-click the entry for that client and click Properties. On the Client tab, choose "Use manually selected template" and select the driver you added. This may resolve it, but I recommend GSS 2.5, which uses a Windows PE boot environment (instead of DOS).

Thank you,

Randy

Is there any quick way to see my version?  What program has the correct version to tell and what version is 2.5?

williamh,

Ghost Solution Suite 2.5 is version 11.5.0.x. You can see this in the Ghost Cnsole (Help > About) or on the first page of the Ghost Boot Wizard.

Ok I have updated from 2 to 2.5.  Now when I upgrade the client, it can not connect to the server anymore.  When I reinstall the old client, it can connect.  What would be causing this?

Ultimately, everything depends on the cause of this entry in the initial logfile:

> Details for: Run product upgrade
> Client version update package did not run successfully 

Without knowing more about your system, such as what version you are upgrading *from* and on what platform, it's impossible to be sure why this is. Running the current client installer manually on a machine may help, since the installer GUI you see when manually running a client install can display more accurate error messages than it will return during an automated or remote attempt to upgrade.

I upgraded from 2 to 2.5 successfully.  Now I have another problem LOL.  When I put in the server name during install of the client manually everything is ok but it is looking for another server that I know for a fact does not exits.  Now to fix this in windows I had to edit the hosts and lmhost file to redirect that name to the server IP.  The problem I am facing now is that when I start an image grab, once in Windows PE, it again looks for that server that does not exits.  How would I fix this, is there a registry entry that might have this computer name in it, so I can delete it (History of servers???)?  I am running version 2.5 in Windows XP Pro, some computers are going thru a WINS server, some are not.  The one I am currently talking about is not going thru the WINS server currently, but when it was it still had this problem.  Please let me know if this helps.

You can do a registry search for the old server name and/or its IP address.
You can also ensure that it's not due to the local DNS cache storing out of date information by running IPCONFIG /FLUSHDNS from a command prompt.

I did a reg. serach and found nothing, plus a did the DNS flush and i am still getting this when in Windows PE and it is trying to find the server.

Do a search on your system for any INI files which may also have server information within them.

Where would I search?  There are ALOT of .ini files in windows LOL

Search for ALL of them, then check first for any files in the application folder, and also in the Windows folder. Check the Application Data folder in the user profile as well, as configuration information is often hidden away in there, and not necessarily in INI files, although those would be my first port of call.

The other thing you can try is running PROCMON while your app is searching for this elusive server, and see where your machine is looking for this information.

I can not find anything that tells me where this machine is.  When I install the ghost client, can I just put the IP of the server in there, or can it only be the server name?

Where you have servers with static IP addresses, using the IP address avoids any issues with DNS/WINS not being fully up to date.

So I can use my IP and everything should be ok?