Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
6 replies Latest Post - ‏2011-06-14T14:24:38Z by GertW
GertW
GertW
29 Posts
ACCEPTED ANSWER

Pinned topic MKS XServer hang causes an IBM Rational Statemate failure to start

‏2011-04-19T16:06:35Z |
After installation of the latest Security Update for Microsoft Windows XP provided in the April 12th, 2011 patch KB2506212, the MKS XServer hangs when started resulting in an inability to start IBM Rational Statemate.

Content

As a result of the Security Update for Microsoft Windows XP MS11-024 provided in the April 12th, 2011 patch KB2506212, the MKS XServer hangs when started. While the MS XServer runs in the background, the icon in the task bar is not visible and Rational Statemate cannot be started. Additionally, the configuration tool will fail to respond.

This issue has been identified and logged under APAR ID: PM37221. The Microsoft patch KB2506212 has been determined to be a direct cause of the problem.

Following are two solutions to resolve this problem on machines exhibiting failure to start behavior:

Uninstall the Microsoft patch KB2506212 (if allowed by system administration)
Use an alternative XServer
Updated on 2011-06-14T14:24:38Z at 2011-06-14T14:24:38Z by GertW
  • GertW
    GertW
    29 Posts
    ACCEPTED ANSWER

    Re: MKS XServer hang causes an IBM Rational Statemate failure to start

    ‏2011-04-20T13:27:02Z  in response to GertW
    a patch for customers under maintenance will be provided in the next days
    • JeanZ
      JeanZ
      4 Posts
      ACCEPTED ANSWER

      Re: MKS XServer hang causes an IBM Rational Statemate failure to start

      ‏2011-04-21T05:15:19Z  in response to GertW
      Hi Gert

      Thank you for this information.
      I have a question, if we choose other XServer other than MKS XServer, like Cygwin XServer for Statemate.
      Do we need to take other configurations on Statemate?
      How does Statemate aware of this change?

      Please advice the necessary setting for Statemate directing to other XServer.

      Thank you
      • screen_FF
        screen_FF
        2 Posts
        ACCEPTED ANSWER

        Re: MKS XServer hang causes an IBM Rational Statemate failure to start

        ‏2011-04-21T05:38:39Z  in response to JeanZ
        Hi Jean,

        Our experience is that you just need to launch any other Xserver. Statemate will detect automatically. We use Xming for example.
        But still we are really waiting for the patch for MKS...

        Regards,
        • JeanZ
          JeanZ
          4 Posts
          ACCEPTED ANSWER

          Re: MKS XServer hang causes an IBM Rational Statemate failure to start

          ‏2011-04-26T06:59:41Z  in response to screen_FF
          Thank you, screen FF.

          Appreciate your help. I also tried Cygwin/X and just as you mentioned, Statemate can automatically detect availabe XServer.

          Hope statemate patch would be available in this week.

          Regards.
  • GertW
    GertW
    29 Posts
    ACCEPTED ANSWER

    Re: MKS XServer hang causes an IBM Rational Statemate failure to start

    ‏2011-05-03T11:51:55Z  in response to GertW
    until MKS and IBM will publish an official patch you can use follwing workaround:

    Copy the old versions of mfc42.dll and mfc42u.dll from C:\WINDOWS\$NtUninstallKB2506212$
    to C:\Program Files\Common Files\MKS XServer.
    For Windows XP, these files are dated 2010/09/18, version 6.2.8073.0.
    Reboot your machine.

    Gert
  • GertW
    GertW
    29 Posts
    ACCEPTED ANSWER

    Re: MKS XServer hang causes an IBM Rational Statemate failure to start

    ‏2011-06-14T14:24:38Z  in response to GertW
    The official fix is available from:
    http://www.ibm.com/eserver/support/fixes/fixcentral/swg/quickorder?brandid=3&productid=IBM+Rational+Statemate&vrmf=4.6.1&fixes=RAT-STM-WIN-XServer-iFix

    You first have to install MKS XServer 8.5 patch 2 and afterwards to replace Dbserv.exe.
    Don't forget to delete the old DLLs mfc42.dll and mfc42u.dll which were copied as to "C:\Program Files\Common Files\MKS XServer" as workaround.