ginastub.dll falied to load during GSS 2.0 User Migration:Capture

[Migration User]

Created a task to capture a registry key that I want to capture and restore after re-imaging.

 

Set the capture package to save on the clients.

 

Ran the task, systems (2) reboot and then both come back up with a dialog box that reads "c:\program files\symantec\ghost\ginastub.dll failed to load".

 

Googled for this error and found some info directing me to copy msgina.dll to ginastub.dll and change a registry entry, but I certainly don't want to have to do that on every target machine or every time I need to re-image.

 

Also - after restarting and bringing up windows, I go to the ghost directory and the ginastub.dll file IS there.

 

Any advice? Thanks.

[Migration User]

Hi Mathew

I'd like to get some more information from you to assist in diagnosing the issue:

1. The task execution steps reported for the failed task
2. Which step was reported as failed
3. The exact and full text of the error message dialog displayed on the client screen, including the message title
4. The registry key you are capturing
5. Details of any additional login mechanisms you may have (finger recognition etc)
6. Client operating system and  approximate patch level

Thanks,
Xan

Message Edited by Xan Todd on 04-10-200708:52 PM

Message Edited by Xan Todd on 04-10-200708:54 PM

Message Edited by Xan Todd on 04-10-200708:55 PM

[Migration User]

I've discovered that the task actually completes successfully, but leaves the clients with the 'unable to load' / Restart dialog. While not the 'prettiest' finish, the registry key capture does actually complete which is good and as long as I hit Restart and don't simply turn off the clients when done, the machine works when restarted (If I turn off the machine at that dialog, I am in trouble as it does not reset the logon to point at msgina instead of ginastub). Here's the data you asked for:

1. Log file contents:

Task Name:

User: mhtaylor

Execution Time: 4/6/2007 8:46:39 AM

Number of client machines: 2

Clients finished OK: 2

 

Task warnings:0

 

Task process listing

CMPC - Administrator 00-03-0D-53-8F-7B Changing Logon Settings 4/6/2007 8:47:16 AM Success

CMPC1 - Administrator 00-03-0D-5D-30-E9 Changing Logon Settings 4/6/2007 8:47:18 AM Success

CMPC - Administrator 00-03-0D-53-8F-7B To target operating system 4/6/2007 8:48:47 AM Success

CMPC - Administrator 00-03-0D-53-8F-7B Send user migration options 4/6/2007 8:48:47 AM Success

CMPC1 - Administrator 00-03-0D-5D-30-E9 To target operating system 4/6/2007 8:48:51 AM Success

CMPC1 - Administrator 00-03-0D-5D-30-E9 Send user migration options 4/6/2007 8:48:51 AM Success

CMPC - Administrator 00-03-0D-53-8F-7B Make user migration package 4/6/2007 8:49:47 AM Success

CMPC - Administrator 00-03-0D-53-8F-7B Changing Logon Settings 4/6/2007 8:49:47 AM Success

CMPC - Administrator 00-03-0D-53-8F-7B Finish 4/6/2007 8:49:47 AM Success

CMPC1 - Administrator 00-03-0D-5D-30-E9 Make user migration package 4/6/2007 8:49:51 AM Success

CMPC1 - Administrator 00-03-0D-5D-30-E9 Changing Logon Settings 4/6/2007 8:49:51 AM Success

CMPC1 - Administrator 00-03-0D-5D-30-E9 Finish 4/6/2007 8:49:51 AM Success

--------------------------------------------------------------------------------

 

Console log export – END

 

2. No step failed in the log

3. On the client, there is a Dialog box with title: “User Interface Failure”

Contents of the dialog box are: The Logon User Interface DLL C:\Program Files\Symantec\Ghost\ginastub.dll failed to load. Contact your system administrator to replace the DLL, or restore the original DLL.

There is a Restart button as well.

4. I can't tell you the full key name. It is part of registry the HKEY_CLASSES_ROOT

5. No odd logon procedures.

6. XP Pro SP2

[Migration User]

It is interesting the failure occurs after the task has completed successfully. I would like to get to the bottom of this.

Let's start by seeing if the data in the gina entry is consistent with what is being reported by the error dialog. While the error dialog is displayed on the screen (before clicking Restart), Let's connect to the client registry remotely and inspect the value of the gina entry to see if it is pointing where the error dialog indicates it is:

Regedit -> File -> Connect Network Registry

Key:    HKLM\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon
Value: GinaDLL
Data:  C:\Program Files\Symantec\Ghost\GinaStub.dll

If that data isn't what we expect it to be there are a few different possibilites. Some other application or service may be attempting to chain our gina, and causing the load to fail. If that turns out to be the case we would need to know what that application or service is. If the registry data is different, that should point us right to it.

There are a few applications which use alternative gina's. One which comes to mind is the Novel Netware client. Regarding NN, NN must be installed first, then Ghost, to get the chain in the right order.

For your interest, there is little bit of background on Gina chaining here: http://entkb.symantec.com/security/output/n199852785735.html

Separately, although I would not expect it in your case, I would expect some antivirus solutions to prevent writes to this area of the registry by some applications.

If the data is what we expect, to rule out all possiblities, let's also connect to the c: drive remotely at the same time and see if the ghost ginastub.dll is also where we expect it to be at that time.

Thanks,
Xan

[Migration User]

Hi Matt

If everything does look normal for the last steps I provided, and there are no surprises there you need to let us know about based on those steps, let's move on to the next level and look at other issues which could cause a load failure. Let's install dependency walker from http://www.dependencywalker.com/, and use it to analyse dependencies for ghost\ginastub.dll. If nothing dead obvious jumps out at you (like a competely missing or regressive dependency) send an export from that tool to my gmail account xan dot todd at gmail dot com, and we'll take a closer look at this end.

I'd really like to get to the bottom of this issue.

Thanks,
Xan

[Migration User]

Has no one found a solution to this problem. After doing a disk-to-disk I get the mentioned error. I can't boot into safe mode to change the suggested registry entries. And this would be no solution to a 50 computer disk-to-disk task. Having to stop and boot/changeentries/ect kinda defeates the purpose of Ghost.

Tom Wallin