Error: User Interface Failure. The Logon User Interface DLL Ctxgina.dll failed to load. Contact your system administrator to replace the DLL, or restore the original DLL

When rebooting a MetaFrame Presentation (XenApp) Server, you receive the following error message:

"User Interface Failure. The Logon User Interface DLL Ctxgina.dll failed to load."

Causes

Potential causes of this error message include:
Corrupted or deleted *GINA.DLL,
Failed installation (or uninstallation) of Metaframe Presentation (XenApp) Server or its corresponding service packs, hotfix rollup packs, or hotfixes.
An install conflict with applications such as the Novell Client, PCAnywhere, or any key that modifies the HKLM\Software\Microsoft\WindowsNT\Current Version\Winlogon\GinaDLL value.
Incomplete or missing Path statements set in Environment Variables


Resolution

Caution! This fix requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it





Boot the problem server until you see the error message but do not click Restart; then try the following steps until the issue is resolved:
Remotely mount the problem server’s file system (or boot into safe mode with networking) and replace %SystemRoot%\system32\CTXGINA.DLL on the problem server with a copy from a known working server.
Remotely verify and correct the problem server’s registry:

a. Connect to a computer in the same domain as the MetaFrame server.

b. Run regedit and connect to a remote server (the MetaFrame server).

c. Verify HKLM\Software\Microsoft\WindowsNT\Current Version\Winlogon\GinaDLL = C:\WINDOWS\system32\ctxgina.dll and HKLM\Software\Microsoft\WindowsNT\Current Version\Winlogon\CtxGinaDLL = msgina. If either of those are incorrect or missing, correct it. If the server still does not boot, rename both values to something like \GinaDLL.bak and \CtxGinaDLL.bak so that server boots using the Windows GINA and you can at least log on to the server.
See also MS KB 329316 Error Message: User Interface Failure: The Logon User Interface DLL Msgina.dll Failed to Load
PATH Environment Variables can be found at: Start > Control Panel > System > Advanced Tab > Environment Variables button > System variables (scroll down to Path) > Edit Button (on bottom) > Variable value

Note: You might want to right-click in Variable value, choose Select All + Copy, and paste into Notepad (with word wrap) to modify content.

Default Path Variables for Windows Server x86 (2003 and 2008): %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Common Files\Citrix\System32\;C:\Program Files\Citrix\System32\Citrix\IMA;C:\Program Files\Citrix\System32\Citrix\IMA\Subsystems;%SystemRoot%\System32\Citrix\IMA;C:\Program Files\Citrix\system32;C:\Program Files\Common Files\Citrix\System32

Default Path Variables for Windows Server x64 (2003 and 2008): C:\Program Files (x86)\Citrix\System32\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files (x86)\Common Files\Citrix\System32\;C:\Program Files (x86)\Citrix\System32\Citrix\IMA;C:\Program Files (x86)\Citrix\System32\Citrix\IMA\Subsystems;%SystemRoot%\System32\Citrix\IMA;C:\Program Files (x86)\Citrix\system32

User is unable to take print, while printing user is getting error massage

To resolve this issue need to download "VSPDF.OCX" and VSPRINT7.OCX" from internet and paste it in c:\windows\system32 that register in registry through below command :-
c:\regsvr32 filename
c:\regsvr32 VSprint7.ocx
c:\regsvr32 vspdf.ocx

These fileds are Activex controllers.

https://picasaweb.google.com/104024887167449947215/CitrixMaster?authkey=Gv1sRgCJPWi8265oWzpAE#5623595769052419410

The SSL Server You Have Selected is not accepting connections

Troubleshooting “The SSL Server You Have Selected is not accepting connections” error message

Make sure that a connection is being made to the server running Secure Gateway.

• Set the logging to maximum on Secure Gateway so that all events, including informational, are logged.

• Attempt to connect.

• Make sure that there is a connection in the application log on the server running Secure Gateway:

CSG0401 Accepted connection from client >client ip address<.

• If no connection is logged in the event viewer, make sure that Secure Gateway is started and that the firewall is allowing access to that server.

• Make sure the client can resolve the FQDN of the server running Secure Gateway.

• If you are attempting to use IIS and Secure Gateway on the same server, make sure you followed CTX799332 - Running Citrix Secure Gateway and IIS/NFuse on the same server ; there are two IP addresses, each with its own SSL certificate; and Debug.asp CTX052061 - Citrix Web Server Debugging & Analysis Tool shows that DisableSocketPooling is set to True. Verify that IIS is not trying to run a Web site on the same IP address as Secure Gateway.

Ensure that the server running Secure Gateway can access the MetaFrame server on the IP address specified.

• Set the logging to maximum on the server running Secure Ticket Authority (STA) so that all events, including informational, are logged by editing the ctxsta.config file and changing the logging level to 3. Then run IISRESET.

• Attempt to connect.

• Check the STA logs to see what address the STA is sending to the server running Secure Gateway  they are in the \inetpub\scripts folder by default.

Check for an entry resembling this:

INFORMATION 2002\11\15:14:24:54 CSG1305 Request Ticket - Successful 97CA7F83085BD179B08EDC1F0DC316FC MetaFrame address:port

• The server running Secure Gateway must be able to access the given IP address on the port specified.

To test, telnet to that address from Secure Gateway or make a connection using the Citrix ICA Client.

If the server running Secure Gateway and the MetaFrame server are separated by a firewall performing Network Address Translation (NAT), you may need to configure an alternate address on the MetaFrame server and then set Use alternate addresses of MetaFrame servers in the server-side firewalls settings. The internal firewall must be configured to allow the traffic on port 1494 from the server running Secure Gateway to the MetaFrame server.

Additional Information

CTX103343 - Error: Cannot connect to the Citrix MetaFrame Server. Server location address must be specified as fully qualified domain names to allow SSL connections to succeed.