When connecting devices to StudioCom I can only connect x number of devices..
StudioCom server acts as a Proxy to a third party applications. We could potentially be limited by resources, on the outside it could be the obvious, memory, processor and in some cases hard drive space.. The not so obvious is the windows desktop HEAP, referred to as desktop heap exhaustion when the default allocation is used up.. This is particularly related to pre-Vista operating systems.
Here is a link to a blog at msdn.com that goes into detail on HEAP utilization.
If you experience the above symptoms you may have encountered HEAP exhaustion and can potentially rectify the problem with a small registry change..
A copy of my registry settings appears as such:
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16
You will notice the three values in this registry section, 1024,3072,512.. We are primarily concerned with only the third set of digits, 512, the non-interactive value. This number can be increased incrementally by 64 and tested to reach the desired number of connections into StudioCom.
Do not forget to reboot to have the new settings take effect.
You may also want to monitor the HEAP utilization and this can be done with a tool called dheapmon.. This utility and its uses can be found at the below URL.
This document assume the user has in-depth knowledge of the windows operating system and its components. This document also assumes that you have taken the time read the URL blog and comprehend its contents. finally, that you understand the ramifications of improperly adjusting the registry in a Windows environment