Friday, December 14, 2012

WMI error retrieving object MetaFrame_DisconnectedSession_Happening: Received error: 0x80041002: Not found

In Eventvwr under Application Log  WSH


Citrix Monitoring Script Event 2
Citrix MetaFrame Compute Event Rate:
WMI error retrieving object MetaFrame_DisconnectedSession_Happening:
Received error: 0x80041002: Not found 

Event Type: Error
Event Source: WSH
Event Category: None
Event ID: 1 
 Description:
Citrix Monitoring Script Event 2
Citrix MetaFrame Compute Event Rate:
WMI error retrieving object MetaFrame_DisconnectedSession_Happening:
Received error: 0x80041002: Not found 


SOLUTION:

Recompile the complete WMI repositories and then run the following commands for recreating these files.
  • Recompile Microsoft Windows .MOF files:
  • net stop winmgmtc: cd %systemroot%\system32\wbem rd /S /Q repository
    regsvr32 /s %systemroot%\system32\scecli.dll regsvr32 /s %systemroot%\system32\userenv.dll
    mofcomp cimwin32.mof mofcomp cimwin32.mfl mofcomp rsop.mof mofcomp rsop.mfl for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s for /f %s in ('dir /b *.mof') do mofcomp %s for /f %s in ('dir /b *.mfl') do mofcomp %s 


  • Recompile Citrix .MOF files:
  • cd %programfiles%\citrix\system32\citrix\wmi for /f %s in ('dir /b *.mof *.mfl') do mofcomp %snet start winmgmt

    Sunday, December 9, 2012

    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:
    clip_image002
    image
    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
    image
    Once the command completes successfully, proceed with executing the following command to register the port to 8080:
    ctxxmlss /r8080
    image
    Once the command successfully completes, proceed with starting the Citrix XML Service:
    clip_image002[6]
    … 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)
    clip_image002[4]
    Once the port change has been confirmed, log onto your Web Interface server and reconfigure the farm settings for your websites:
    image

    Wednesday, December 5, 2012

    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"