Windows cannot open Help and Support because a system Service is not running

Windows cannot open Help and Support because a system Service is not running 



Windows cannot open Help and Support because a system Service is not running

---

We have seen a rash of these problems on Windows Server 2003. Research seems to indicate the problem is related to the installation of Windows Server 2003 Service Pack 2 (SP2).
The simplest fix we have found is this:

• Open a Command Prompt
• Run the following commands
  • %SystemDrive%
  • CD %windir%\PCHealth\HelpCtr\Binaries
  • start /w helpsvc /svchost netsvcs /regserver /install

The service should install and start automatically.

The Citrix XML Service service on Local computer started and then stopped

CITRIX XML SERVICE :

If you ever do any research on what port to use for the XML service in a Citrix XenApp environment, you’ll notice that there are options to share port 80 with IIS, use port 443 with SSL on IIS and finally port 8080.  I haven’t really found any official documentation on what is best practice but I was able to find forum posts where Citrix engineers recommend the use of port 8080 and not to rely on IIS.

The process of changing the XML service port to 8080 is quite easy but since I know I’m bound to forget after not having to perform the configuration on a regular basis, I thought it would be good to write a blog post so I can reference it in the future.

Begin by logging onto your XenApp server and stop the Citrix XML Service:

Once the service has been stopped, proceed with opening up the command prompt as an administrator an executing the following command to unregister the Citrix XML Service port:

ctxxmlss /u

Once the command completes successfully, proceed with executing the following command to register the port to 8080:

ctxxmlss /r8080

Once the command successfully completes, proceed with starting the Citrix XML Service:

… then open up the registry to confirm that the changes have been applied via the following registry key:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\CtxHttp

Name: TcpPort
Type: REG_DWORD
Data: 0x00001f90 (8080)

Once the port change has been confirmed, log onto your Web Interface server and reconfigure the farm settings for your websites:

Troubleshooting ICA Client / PNAgent Error 2306

Program Neighbourhood Agent / PNAgent Error 2306

On setting up the ICA Client 10.105 I received the following error on trying to connect via the applications listed under the PNAgent.', 'On setting up the ICA Client 10.105 I received the following error on trying to connect via the applications listed under the PNAgent:

This was being caused because the ICA file was being deleted before the PNAgent had finished reading it… very strange. After browsing a few forum posts I found that by modifying my local workstation registry I could resolve the issue by changing the ‘RemoveICAFile’ entry to equal false:

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Client Engine\ICA File

Alternately, if you are an Administrator wanting to resolve this for all of your PNAgent users and Web Interface users simply follow these instructions:

Modify the \Inetpub\wwwroot\Citrix\MetaFrame\conf\default.ica on all of your Citrix Servers that have the web interface.

Change the line "RemoveICAFile=yes" to "RemoveICAFile=no"

Windows could not start the Citrix XTE server on the local computer.

Error: Windows could not start the Citrix XTE server on the local computer. The service terminated with a service-specific error 1

Cause: Session Reliability port (2598) is not configured.
Solution:
Step 1: Verify the Session Reliability port is configured by using the below command 
C:>netstat -an |find /i “2598″
Step 2: Take the backup of httpd.conf file
Step 3: Edit the C:\Program Files\Citrix\XTE\conf\httpd.conf (64 bit OS: C:Program Files (X86)
copy the following content in httpd.conf file
#CGP Listen Port
Listen 2598
# Log Level
loglevel emerg
Save the file and start the Citrix XTE Server service.

                                                                         OR

Rename httpd.conf file in the path C:\Program Files\Citrix\XTE\conf and export from any of the working server. Then start the Citrix XTE Server service.

The Citrix SMA service on Local Computer started and then stopped

The Citrix SMA service on Local Computer started and then stopped

“The Citrix SMA service on Local Computer started and then stopped. Some services stop automatically if they
have no work to do, for example, the Performance Logs and Alerts service.”

Resolution 1:

To resolve the preceding issue, complete the following procedure:

• Stop the SmaService.exe service by using the Task Manager.
• Citrix SMA Service Properties and under the Log on tab, selectLocal System Account.
• Set the SMA  Service to Manual and restart it, once the service started
• Change Citrix SMA Service Properties and under the Log on tab, select Local Service Account.
• Set the SMA  Service to Automatic and restart it

Resolution 2:

Please create a folder named " Active" in the path C:\Program Files\Citrix\Sma and try to start the service

4 States of Citrix Session

Here are the 4 states and the differences between them:

• Active - a user is active within a remote desktop session, for example, running applications, web browsing or similar stuff that involves using a mouse or keyboard.
• Idle - User is considered idle after a period of mouse/keyboard inactivity in the RDP session. The user will be considered idle if there is no activity (e.g. keyboard strokes or mouse movement) in the configured time period. The default Terminal Services idle timeout is 1 minute, and the default for the Terminal Services Log is 5 minutes.
• Disconnected - When a user is disconnected from the session but the session is still running. User could have been disconnect due to network or other failure or did not use proper log out procedure and just closed the Remote Desktop session window with the Close button [x]. This session is still running on the server and consuming resources, the users can reconnect and resume their disconnected session.
• Remote Control - user is in remote control state if a user is remote controlling another user (also known as shadowing on Citrix servers).

0 people found this useful. - Be the first!

Citrix Client Error 2320 (AllowHotKey)

Error: "Citrix online plug-in Configuration Manager: No value could be found for (AllowHotKey) that satisfies all lockdown requirements. The lockdown requirements in force may be conflicting"

The solution was a bit tricky, I tried several fixes from Citrix forums and articles, but I ended just deleting the Citrix key under the user part of the registry on the clients (HKEY_Current_user\software\Citrix). After deleting everything worked like a charm.