Citrix Licensing Error - Event ID 1001,1004,11706

Please check out www.kaztechsolutions.co.uk for more of my technical posts, alternately please call us on 01932 268289. 

Recently I had an issue where our Licensing server was throwing the following warning/errors and it turns out it was an issue with SCOM 2007 R2 agent installed with Citrix MP 5.0 on the licensing server.

The version of licensing server that was running was 11.6 and once we removed the SCOM agent and restarted the the License server all of these error stopped.

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Detection of product '{EE7A694A-15EE-4551-A267-EBF5904DD49D}', feature 'CitrixLicensingProductFeature' failed during request for component '{D0EBE218-FC25-5A69-A95A-C5C79CC68186}'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Detection of product '{EE7A694A-15EE-4551-A267-EBF5904DD49D}', feature 'CitrixLicensingProductFeature', component '{213B3304-A395-438C-9510-BC621D799083}' failed. The resource 'HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\LicenseServer\Install\Debug' does not exist.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11706

Product: Citrix Licensing -- Error 1706. An installation package for the product Citrix Licensing cannot be found. Try the installation again using a valid copy of the installation package 'CTX_Licensing.msi'.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 45 45 37 41 36 39 34 {EE7A694
0008: 41 2d 31 35 45 45 2d 34 A-15EE-4
0010: 35 35 31 2d 41 32 36 37 551-A267
0018: 2d 45 42 46 35 39 30 34 -EBF5904
0020: 44 44 34 39 44 7d DD49D}

How to delete a PVS

From any PVS server in the farm, browse to the C:\Program Files\Citrix\Provisioning Services Console directory via command prompt and run the following

mcli run markdown /p servername="name"

replace the "name" with the server that is no longer used, once you do this browse through the console, find the server, right click, delete.

Helpful LINUX Commands

This is just some LINUX commands that i have been using on both ESX and XenServer

Control + R - Use this command if you cannot remember commands you have previously run on a host.

history | tail -n40 - Display the last 40 commands you have typed.

ls -lrt | grep "Mar 8" - List all file modified a certain date.

pwd - Shows current working directory.


df -h - displays size usage

Changing pool master

Go to the slave server that you want to use as pool master.

First disable HA on your XenServer Pool.

#xe pool-ha-disable

Now list UUID for all the hosts

#xe host-list

To designate a slave XenServer as the new pool master

# xe pool-designate-new-master host-uuid=("enter UUID number - without quotes"

If your pool master is down or unavailable, log in to a slave XenServer and enter the command below.

#xe pool-emergency-transition-to-master

Nopw you need to re-establish all connections to the slaves from the new pool master.

# xe pool-recover-slaves

VM won't start and now is in a Stuck State

From time to time Vm's can get stuck in a state where you cannot start, shutdown, reboot or even force a reboot or shutdown. When this happens from the console type: xe-toolstack-restart (note that your XenCenter will loose connection when you do this. Nothing will however happen to your running VMs)

Reconnect with XenCenter (or let it reconnect by itself) and you should see your VM no longer in a stuck state

Appliance lock Regkeys

When using the Citrix Appliance lock if you ever need to disable the Windows logon settings to stop using the PNAAgent at log on change the following reg key from

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
"Shell"="C:\Program Files\Citrix\ICA Client\pnagent.exe"

To

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
"Shell"="Explorer.exe"

This will enable Windows Explorer to start during Windows logon and not the PNAAgent.

XenServer Storage Test VM

Please check out www.kaztechsolutions.co.uk for more of my technical posts, alternately please call us on 01932 268289. 

PerformanceVM is a XenServer virtual machine that helps troubleshoot performance related issues such as poor performance casued by storage I/O and network I/O. The VM built on Debian Linux equips with following test utilities and is accessible via a web based user interface:

Disk I/O performance utility
It can be used to conduct the following disk I/Os to measure: sequential read/writes and random read/writes with various specified block sizes.

Network I/O performance utility
It is essentially a modified version of netperf. Additional information about netperf can be found at http://www.netperf.org. Netperf runs on the backend and provides end-to-end request/response round trip latency and TCP/UPD throughout tests.

download the VM from the following locations http://xenbits.xensource.com/export/1/perfmon/PerfVM1_0.zip and Import the VM in to XenCenter.


Running PerformanceVM

Access the console
1. SSH into the PerformanceVM’s IP address.
2. Enter the 'root' user name and password. The root user log on credentials are:
User name: root
Password: xensupport

Start the web server
1. Start the web service using the script and the IP address of the virtual machine:
/start.sh [XenPOOLMASTERAddress]
2. When prompted for a password, enter:
The password for [XenPOOLMASTERAddress]
3. A prompt to inflate thin provisioned VDIs will be presented. Answer yes or no.

Note: If the Disk I/O test returns values that are off of the graph, then the above steps
probably need to be run in order to accurately reflect the performance.

4. In a web browser, enter http://[PerfVMAddress ]:8888/ to start testing.

Note: If XenServer hasn’t reported the VM’s IP address yet to XenCenter, the scripts will fail to run.

Network I/O Performance Utility
Running the Network utility requires that Netserver be installed on a remote system. This can be downloaded from the Network I/O utility page. Netserver can be installed on a Linux VM or dom0 at a remote site, where the destination testing will occur. Start Netserver before running any network performance tests.

Disk I/O performance utility
Running the Disk Utility will show real time performance of the specified disk. Access to Dom0 is required to access the performance data, but Dom0 is not modified. It can be run on master or slave machines.

Additional results are provided and will show up to the last 10 minutes of a test period. This will include various other counters along with the Disk results. Final results are graphed on a separate results page.

How to increase XenServer HA TimeOut

Use the following two commands from CLI to increase the HA timeout on your XenServer, first you have to disbale HA then re-enable HA via the CLI with the timeout switch. I've found that 120 seconds works best but it all depends on your environment and what suits your needs best.

xe pool-ha-enable heartbeat-sr-uuids=ad1983ed-66cb-8fd7-1ef5-66a41c9d4345 ha-config:timeout=XX

Obviously change the SR UUID to the UUID of your own SR and where =XX change this to the number of seconds to wait until HA kicks in by default, it is 30 seconds.

NOTE: to get your list of SR UUID's type xe sr-list in the console

Separating the Roles of DDC's in a XenDesktop Farm

Each Desktop Delivery Controller machine in the farm can potentially become the farm master in an election process. This election process can be influenced by settings on the various server machines, and one (or more) machines can be indicated as preferred as being farm master, and other machines only take on the farm master role if the preferred machines are unavailable. This preference indication is achieved by use of registry entries on the various server machines. Each machine can be configured to have one of four possible settings:

• Master – servers with this setting are preferentially chosen as the farm master. Often, only one server in the farm would have this setting.

• Backup - servers with this setting are preferentially chosen as the farm master when the master server is unavailable.

• Member - servers with this setting are normally not the farm master, but can assume the farm master role when none of the master or backup servers are available.

• Slave Only - servers with this setting are not eligible to be the farm master.

To configure a server machine to one of these settings, perform the following steps.

Caution! This procedure requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may 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. Back up the registry before you edit it.

1. Set the HKLM\Software\Citrix\IMA\RUNTIME\UseRegistrySetting DWORD registry entry to 1

2. Set the desired master ranking value in the HKLM\Software\Citrix\IMA\RUNTIME\MasterRanking DWORD registry entry to one of the following values:

• 1 indicates ‘Master’
• 2 indicates ‘Backup’
• 3 indicates ‘Member’
• 4 indicates ‘Slave Only’

3. Restart the server

Enabling better PVS Logs

ere how to turn on better logging:

Console log file: “c:\documents and settings\all users\application data\citrix\provisioning server\eeapi.log”
Config file: “c:\program files\citrix\provisioning server console\enterpriseaccess_log.config”

Stream process log file: “c:\documents and settings\all users\application data\citrix\provisioning server\stream.log”
Config file: “c:\program files\citrix\provisioning server\stream_log.config”

Soap server log file: “c:\documents and settings\all users\application data\citrix\provisioning server\soapserver.log”
Config file: “c:\program files\citrix\provisioning server\soapserver_log.config”

MCLI log file: “c:\documents and settings\all users\application data\citrix\provisioning server\mcli.log”
Config file: “c:\program files\citrix\provisioning server\mcli_log.config”

In each case, the .config file controls the level output according to the “level value” entry towards the bottom of the file:




The three levels are ERROR, DEBUG and TRACE with ERROR being the default value installed with the product. DEBUG will be the most useful for diagnosing customer issues. The corresponding service does not require restarting after the log level has been changed.

Get some logs and we can start to troubleshoot.