How to create a simple website in Citrix

Sometimes a simple website is needed to launch a Publish Application. The option to create an html file with a linked ica file has been in the CMC since day one.

Open CMC | Applications | Application property | Create html file

Read More

How to set per Application settings in Citrix

edit the default.ica file loacted by default in /Citrix/MetaFrame/Conf

In the [wfclient] section add the AppDN of your Publish Application, like [notepad] but remember the value is case sensitive to what you have used in the CMC!
Now add any Application specific setting you like. For instance adding TWIMode=Off will result in a none seamless session for the Publish Application notepad

Read More

How to use the multilanguage footer function in citrix

Close any Access Suite Console (ASC) that might be open and enabled the footer manually through the webinterface.conf file that is located by default in /Citrix/MetaFrame/Conf

Change the following lines

# FooterTextDefaultLocale=[language code]
# FooterText_<lang-code>=[Customized footer text in the specified language]

to something like

FooterTextDefaultLocale=en
FooterText_en=This is a example.
FooterText_de=Dies ist ein Beispiel.
FooterText_fr=Cela est un exemple.

Read More

How to speed-up Web Interface logins in Citrix

When somebody tries to open the Web Interface login page early in the morning, then it might take some time before the page is loaded. Additional requests are fast and is due to the fact that in the background the worker processes needed to be started. If they are idle for 20min, then they get closed and new logins will again take some time. Now this behaviour can be disabled.

This can be done with the Internet Information Server (IIS) that comes with Windows 2003. Open the IIS Manager | Application Pools | Disable idle timeout for “worker processes”  for CitrixWebInterface4.xAppPool.

Read More

Citrix XenApp failed to connect to the Data Store

We had an issue with one of the Citrix servers in our farm after a reboot. The server came up fine, however, the IMA service would not start. The following errors showed up in the event log in succession every time we tried starting the service.

1. Citrix XenApp failed to connect to the Data Store. ODBC error while connecting to the database: S1000 -> [Microsoft][ODBC Microsoft Access Driver] Cannot open database ‘(unknown)’.  It may not be a database that your application recognizes, or the file may be corrupt.
2. Failed to load plugin C:\Program Files\Citrix\System32\Citrix\IMA\SubSystems\ImaPsSs.dll with error IMA_RESULT_FAILURE
3. Failed to load plugin C:\Program Files\Citrix\System32\Citrix\IMA\SubSystems\ImaRuntimeSS.dll with error IMA_RESULT_FAILURE
4. Failed to load initial plugins with error IMA_RESULT_FAILURE
5. The Citrix Independent Management Architecture service terminated with service-specific error 2147483649 (0×80000001).

The reason why the IMA service would not start was due to an issue with the Local Host Cache database. The Local Host Cache database is used in a Citrix farm to allow a Citrix server to function even if it loses temporary access to the data store. It is an MS Access database named lmalhc.mdb and is stored by default in <ProgramFiles>\Citrix\Independent Management Architecture\ folder.
The solution for this issue was to recreate the LHC database using the dsmaint command. Before you run the dsmaint command, double check and ensure the following is true:

1. The Citrix IMA Service isnt running (duh!)
2. The datastore is available.

Once you have checked both the above, run the following command to recreate the LHC database.

dsmaint recreatelhc

This command performs the following:

1. Renames the existing LHC database.
2. Creates a new database.
3. Modifies the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Runtime\PSRequired key to 1. Setting the value PSRequired to 1 forces the server to establish communication with the data store in order to populate the Local Host Cache database. When the IMA service is restarted, the LHC is recreated with the current data from the data store.

Once the command has been run, restart the IMA service and it should start normally now.

Read More

The qfarm /load Command Displays the Server Load Level Value as 20000

Symptoms

When you run the qfarm /load command from the command prompt to verify the load of a server, the value of the load that is displayed is 20000.

The following is the sample output of the qfarm /app command for your reference:

The following is the sample output of the qfarm /load command for your reference:

Resolution

The following are the causes for the error in the value of the server load and the probable resolutions for the error:

• Cause: A MetaFrame Presentation Server 3.0 server, Standard Edition does not contain the Load Balancing functionality. Load balancing is only available with the Advanced and Enterprise Editions. Therefore, when you run the qfarm /load command from the command prompt of a Standard Edition server, the expected server load is 20000.

Resolution: A server load value of 20000 indicates that a Load Balancing license is not available. This is as expected for a Standard Edition server.



• Cause: There might be an error in the server load value if the Citrix Management Console contains an incorrect product code, a Product License mismatch, or an incorrect value for both the product code and the product license.
A server load value of 20000 indicates a Load Balancing license is not available. Therefore, this is expected on a Standard edition server.
Resolution: Remove the product code from a server and run the qfarm /load command



• Cause: The MetaFrame XP Product License might not have an unlimited server count.
Resolution: Contact the Citrix Technical Support team and provide details of the License Sets, as shown in the following screen shot:

Posted in Citrix

Load Manager values

• 0 to 9998: This is the normal range for Load Manager.
• 99999: No load evaluator is configured.
• 10000: Load is at 100 percent (full load).
• 20000: The Presentation Server Console contains an incorrect server edition or a license mismatch.
• 99990: Results when a custom administrator with restricted rights runs the following QFARM commands:
  
  QFARM SERVER /APP
  QFARM /APP
  QFARM /APP <appname>
  QFARM /ZONEAPP
  
  Note: The QFARM command may not return any results when a custom administrator runs the following queries:
  
  QFARM /DISC
  QFARM /LOAD
  QFARM /ZONELOAD

The following are explanatio

ns of the load levels:

9999 = No load balancing installed

0 to 9998 = "normal" load level

10000! = Application is disabled for this server

10000 = Load is at 100%

10001 = Out of licenses

10002 = Indicates that no ICA connections are available on that server. A
few other conditions also cause this code to be returned:
If logons have been disabled on the server

If the server is out of swap space

If the application is disabled

Read More

MFCOM Service

In our Citrix Enviornment, we have two servers(for example). Both the servers will be up and running fine but one of the server's status in citrix access management console will be Unavailable, whereas the server will be up and running. Now if we check the services.msc in second server(which one is showing as unavailable in citrix access management console), citrix MFCom Service status will be starting.. This is the problem.

Now follow the below steps:
Start Task Manager
kill mfcom32(or mfcom) process

Go to Services
Take Citrix MFCOM service to MANUAL

Open CMD and run followings:
dsmaint recreatelhc
dsmaint recreaterade

Go to Services
Start Citrix IMA Service

Open "Citrix Delivery Console" and check if it's ok or else manually start MFCOM service.
Wait until Citrix MFCOM starts (it will go to stopping status and will start but it takes time, after it does take it to Automatic)

Reboot the server

If you still face the issue, follow the below process:

IMA and MFCOM services are unresponsive during the Starting state due to data store corruption.

Cause

This issue occurs when there is a corrupt data store. Database corruption can be from a hard reboot of the XenApp server with an open connection to the data store.

Resolution

Verifying the Issue
To analyze the issue, you must verify the following:

1. Verify in the event log if the IMA or MFCOM service is unresponsive(hanging), as shown in the following screen shot:

2. You notice that the services, which are in the Starting state, are in an unresponsive state.

3. You can also verify it by opening the registry and navigating to HKLM>SOFTWARE>Wow6432Node>Citrix>IMA>RUNTIME and observe the CurrentlyLoadingPlugin key. If no details are displayed, then it might be a datastore corruption, or a service issue.

Note: An admin can verify if the database is corrupt.

Verifying for Data Store Corruption

To verify if it is a data store corruption and resolve it, complete the following procedure:

1. An admin can typically verify a data store corruption by completing the following tasks:
   - Running the dsmaint recreatelhc from the command prompt
   - Starting the service
   If you still experience issues, you must check for corruption in the datastore.



2. Create a new database and point the server in question to a new farm using the new database. If the server does not change the farm, you might have to check the data store integrity.


3. Run dscheck to get more details such as, where the corruption occurs. Refer to the Knowledge Center article CTX124406 – DSCHECK - XenApp Data Store Checker Tool Commands for more information about running dscheck command.
   
   In the following sample, you can observe that the dscheck /full servers was run and stopped prematurely at server Prod4. You can also observe that the following server after Prod4 is Prod6. In this example, you can notice that Prod6 has been powered down in the event viewer manually, potentially still having an open connection to the datastore, causing the corruption when it was rebooted. The Local Host Cache might have updated with the corrupt information. Therefore, the grace period of the IMA service is not activated because the system can still partially read the LHC file.

4. After restoring the datastore from a back up , run the dscheck /full servers once again. You can notice from the output that Server Prod6 is now displayed. This server had caused the corruption.

The IMA and MFCOM services are in Started state on all the servers.

Read More