If it is failing at 95%, that means the clone has finished and it is working on the conversion. At this point it inserts the VMware drivers into the file system and the registry. It uses boot.ini to "find" Windows.
If you did not delete the VM, you can use a helper VM to mount the C: drive of the candidate and edit boot.ini. Just add the hard disk to a working VM that is running Win2K or Win2k3. It will mount as the D: or E: drive.

Your boot.ini looks like this:

 
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect 

This indicates that you have a diagnostic or utility partition on the physical server. This is not cloned as part of the conversion process and will cause this type of failure.

Change both lines to:
default=multi(0)disk(0)rdisk(0)partition(0)\WINNT

Dave Convery
VMware vExpert 2009
http://www.dailyhypervisor.com

Careful. We don't want to learn from this.
Bill Watterson, "Calvin and Hobbes"

DOH!!!! You are right Ulli!! Sorry.

They are getting errors similar to this one:

Error 3 (error loading hive: The system cannot find the path specified (3))

I am assuming it is an issue finding the windows installation, registry, etc.

Dave Convery
VMware vExpert 2009
http://www.dailyhypervisor.com

Careful. We don't want to learn from this.
Bill Watterson, "Calvin and Hobbes"