[Ernie Saylor]

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.

[Ernie Saylor]

Looks like someone had that same problem and had success with a wider cleanup: <a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=1403&#8243; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=1403.

[Ernie Saylor]

I don’t have extensive experience with this, but your question made me curious. I found the following helpful: http://support.microsoft.com/kb/324145. I was able to create a custom event on my workstation, using eventcreate.exe. I was then able to user logevent with the error number I defined. I tried using logvent with just the error number (logevent -e 111) but it threw an error. I found that including a text message made it work (logevent -e 111 “test”).

[Ernie Saylor]

The ability to include a period in the search string. I’ve been unable to search for 5.4.1, for example. I contacted tech support about this and they confirmed that this is a search limitation.

[Author]

Replies