Clovertech

TclNotifier window class error

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › TclNotifier window class error

  • Creator
    Topic
  • January 29, 2010 at 9:01 pm #51538
    Ernie Saylor
    Participant

      Does anyone know what causes (and how to fix) the following error: “Unable to register TclNotifier window class

      This application has requested the Runtime to terminate it in an unusual way.

      Please contact the application’s support team for more information.”

      We get this sporadically when trying to start a new process. The only fix so far has been a full cleanup and restart of the Cloverleaf service. It’s happening often enough that restarting the service in not a viable option.

      We’re running Cloverleaf 5.7 on Windows Server 2003 SP2 in a clustered environment.

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • March 24, 2010 at 10:17 pm #70702
        Rick Martin
        Participant

          We’ve been getting this error for quite some time and have so far not found a fix.  If anyone knows of one, please let us know.

        • March 24, 2010 at 10:26 pm #70703
          Ernie Saylor
          Participant

            We got a fix from Healthvision development. It involves changing a registry setting in Windows that controls heap size, I believe. Here’s the HV recommendation:

            “Increase the heap size using the registry entry: HKEY_LOCAL_MACHINESystemCurrentControlSetControlSession ManagerSubSystemsWindows

            This registry value will look something like (all on one line):

                          %SystemRoot%system32csrss.exe ObjectDirectory=Windows

                          SharedSection=1024,3072,512 Windows=On SubSystemENGINE=Windows

                          ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3

                          ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off

                          MaxRequestThreads=16

            To increase the heap for interactive desktops you change the value that is shown as 3072 in the above to something larger. The value is in kilobytes. The first value (1024) should not be changed. The third value is for non interactive desktops and maybe should also be increased or removed (removing it make it the same as the second value).

            Note there is still a limit after the change it is just larger.”

            We applied this change with no problems a few weeks ago. We haven’t had a recurrence of the Tclnotifier error since then, but it’s unclear whether the registry change fixed it or whether the other measures we took to reduce threads is keeping it under the resource threshold that is the problem. We’re cautiously optimistic.

          • October 24, 2013 at 5:11 pm #70704
            MiteshBhatt
            Participant

              We are also facing this issue after patching windows server. No idea why this happens.

              Our current registry setting in terms of Shared Section is also on higher side.

              1024, 4096, 1024

              Any thoughts why we face this issue ?

              And the only fix so far has been a full cleanup and restart of the Cloverleaf service. It’s happening often enough that restarting the service in not a viable option.

          • Author
            Replies
          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.