Event ID 4008 IMA service not starting

The following errors appears in System log of the Windows server:

Event ID: 4008

The database name and database server name recorded in the DSN file must either be empty or match the values stored in Group policy.

Event ID: 7024:

The Citrix Independent Management Architecture service terminated with Service specific error.

Reason: You will see these errors when you move your farm database to new SQL/Oracle server. DSN file contents are conflicting with Group Policy value of initial database  server name. You will see these errors on provision vdisk xenapp server.

Solution: Assuming that your dsn file has the correct name of the new DB server. Open local group policy on problemed server with Gpedit.msc and modify the value of initial database server name under computer configuration/Citrix policies as shown in figure:

 

 Open command prompt and run following commands:

dsmaint recreatelhc

dsmaint recreaterade

Now start IMA service.

Have a nice day!

 

Application launch disappear after Welcome in Xenapp

The published desktop works fine but the some of the published applications can not launch and they will disappear after welcome screen. You will see following screen before it was disappearing

Reason: Some times, CitrixCseEngine.exe takes longtime to process GPOs. In that case the published desktop application will respond even after logoff check time of application launch. But published application was unable to respond after logoff check time. 

Solution: Increase the logoff check time delay value in registry to 10 minutes:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Value Name: LogoffCheckerStartupDelayInSeconds

Type: REG_DWORD
Value: An integer for the length of time to wait for application start.
Enter the delay time in seconds, up to 10 minutes (600 seconds).

Please use above solution as is based on your decision.

Have a nice time! 

Ravi Challa

Citrix- Users see slowness in running sessions

 Users see slowness during sessions because session reliability service's (XTE service) non paged pool size has reached 4 GB size.

Reason & solution:

XTE Service -(session relaibility) -XTE service's "Non Paged Pool" size reaches 4 GB that means you have some issue with memory. You can check this in task manger by enabling non paged pool in filter.

Solution: Apply the Microsoft hotfix http://support.microsoft.com/kb/936655

Apply the Citrix patch: http://support.citrix.com/article/CTX123956

Have a nice day!

Perf OS Event ID 2012 - Citrix -Not accepting connections after 30 users

In citrix presentation Server 4.5/5.0 environment, the Citrix servers were rejecting user logons/sessions after certain number of active sessions(30 in my case). You can see errors in event log as mentioned below:
Event ID 2012 perfOS
Unable to contact server or XML broker
Server is busy to process request

There two reasons for the above scenario:
1. XTE Service -(session relaibility) -XTE service's "Non Paged Pool" size reaches 4 GB  that means you have some issue with memory. You can check this in task manger by enabling non paged pool in filter.

Solution: Apply the Microsoft hotfix http://support.microsoft.com/kb/936655

Apply the Citrix patch: http://support.citrix.com/article/CTX123956


2. If Free PTEs were less than 50K, then you can see above behavior:
Here is the solution:

Problem: ** Virtual Memory Usage ***

        Physical Memory:     2096923 (   8387692 Kb)

        Page File: \??\C:\pagefile.sys

          Current:  12288000 Kb  Free Space:  11893324 Kb

          Minimum:  12288000 Kb  Maximum:     13312000 Kb

        Available Pages:     1571173 (   6284692 Kb)

        ResAvail Pages:      1995682 (   7982728 Kb)

        Locked IO Pages:         245 (       980 Kb)

        Free System PTEs:        742 (      2968 Kb)

        ********** Running out of system PTEs **************

        ******* 809982 system PTE allocations have failed ******

Reason & Solution:

1.       System is booting up with about 50K PTEs. Usually the system should be have initial PTE of about 190K+. System has lost about ~140K PTEs (573 MB of Kernel VA). The system supports "Hot-Add Memory" feature which allows OS detect additional RAM which gets plugged in without needing a reboot. To allow this OS will reserve the Kernel VA to support the maximum RAM that can be added to the system. BIOS is responsible for notifying the amount of the maximum RAM that the system can support. In this case the BIOS notified the system that it can support up-to 128 GB of RAM but only 8 GB of RAM is currently plugged into the system. Hence OS reserved about ~880 MB of Kernel VA for the PFN DB expansion in case additional 120 GB of RAM gets plugged into the system.

2.       This behavior of OS can be controlled via the registry key documented in the article below, where we can specify the amount of RAM that OS should anticipate and reserve space for. Usually we set this value to 1.

913568        Decreased performance, driver load failures, or system instability may occur on Hot Add Memory systems that are running Windows Server 2003

http://support.microsoft.com/default.aspx?scid=kb;EN-US;913568

Recommendations:

================

1.       Set the Registry value documented in the Workaround section of the above mentioned KB article to 1 and reboot the system and the observe what is the value of Free System PTEs at the boot.

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

REG_DWORD DynamicMemory 0x1

 

2.       Also set the SystemPages value to 0 (ZERO)

 HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

REG_DWORD SystemPages 0x0

 

I am not repsonsible for any failures while applying above fixes.

Have a nice day!

Slowness while accessing/launching application in Citrix

Slowness while accessing/launching application in Citrix for all users or certain group of users




1. Check GPOs – any certificates are included..

http://support.citrix.com/article/CTX131825/


2. Check any drive mappings existed for old drives (which are retired) in user properties in Active Directory/ Login Script or in GPOs

3. Check any printers are mappings which are not existed/retired

4. Configure printer mappings after application launching in Citrix policies

4. Troubleshoot application performance issues
http://support.citrix.com/article/CTX105314/

5. Check this
http://maxwindows.wordpress.com/2011/06/19/troubleshooting-citrix-slow-performance-issues/


Have a nice day!

Citrix - Windows cannot access \\client\c$\documents and settings\user\desktop or Error Code:0x80070043 or C:\Users\temp\Desktop is not accessible or Word has insifficient memory or Microsoft office excel cannot access the file

 In Citrix, you might get these errors while saving a file
Error 1:
C:\Users\temp\Desktop is not accessible
The network path was not found
Error 2:
Windows cannot access file://client/c$/Documents and Settings\User1\Desktop

      But if we login (RDP) to the Xenapp servers as the test user and launch the citrix session, all published applications are working fine and there are no errors while saving the data in apps. The data is saving in respected redirected folders on file://server1/

Error3:

Error Code:0x80070043

The network name cannot be found

Error 4:

Word has insifficient memory. Do you want save Document1 as rescued document?

Error5: Microsoft office excel cannot access the file "C:\program files\File Directory\Folder1\file.xls. There are several reasons

The filename or path does not exist

The file is being used by another program

The workbook you are trying to save has the same name a a currently open workbook.

Folder redirection has been enabled and there was no errors found. user permissons and prifile is good.  It works fine for Citrix client 10.2 (Old client).  Giving errors for any other clients – 11.2, 12.1, 12.3 & 13.1 (Citrix receiver). Citrix desktop is working fine for any client.

Solution:

 Open Webinterface --> Open Web interface management console

Open Session settings ---> Go to Local Resources ---> Uncheck Provide Special folder Redirection to all users under Special Folder Redirection.

Have a nice day!

The Windows Installer Service Could Not Be Accessed

Error:
"The Windows Installer Service Could Not Be Accessed" error message when you install a program in Windows XP/2003/?

Solution:


To resolve this issue, follow these steps:


Log on to your computer as an administrator.

Click Start, and then click Run.

In the Open box, type cmd, and then click OK.

At the command prompt, typemsiexec.exe /unregister, and then press ENTER.

Type msiexec /regserver, and then press ENTER.

Verify that the SYSTEM account has full control access permissions to the

HKEY_CLASSES_ROOT

hive in the Windows registry. In some cases, you may also have to add Administrator accounts. To do so:Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/ )

How to back up and restore the registry in Windows

Click Start, click Run, type regedit in the Open box, and then click OK.

Click the following registry hive:

HKEY_CLASSES_ROOT

On the Edit menu, click Permissions.

If SYSTEM is not listed in the Group or user names list, click Add, make sure that the local computer name appears in the From this location box, type system in the Enter the object names to select box, click Check Names, and then click OK.

Click SYSTEM in the Group or user names list, and then select the Full Control check box under Allow in the Permissions for SYSTEM box.

Click Apply, click OK, and then quit Registry Editor.