Hi,

I am at an installattion with w2000 and sql2000
Sometimes the following error on the server:

sort.exe - Application error.
the application failed to initialize properly (0xc0000142). Click on ok to terminate the application.

I know that the user session where the error was caused hangs until I give some enters on the server.

What can this be?
Anyone has seen this before?

Thanks
Fred

Forgot to refer that the Porting set is 6.1c.06.05

We encountered this same problem. W2000/SQL2000 BaanIVc4, Porting set 6.1c.06.02.

In our situation it was to do with a Registry Setting regarding memory allocated to desktop heap. We had to increase ours to 1024 KB(was 512 KB as described below, which was too low for our # of users).

Please confirm the following procedure with Baan Support (Solution 109404) before changing your registry!!!

The solution description was:

1. Run the Registry Editor (RegEdt32.exe).
2. Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey:
\System\CurrentControlSet\Control\SessionManager\

SubSystems\Windows
The default data for this value will look something like the following (all on one line):
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,3072 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16
In SharedSection=1024,3072, 3072 represents the heap size for desktops associated with the interactive Window station. Scan along the line until you reach the part that defines the SharedSection values and add ",512" after the second number. This value should now look something like the following:

%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
The 512 specifies the desktop heap for desktops associated with non- interactive window stations. This tells the system to allocate 512 KB of heap for each desktop.

After making this change, close Regedt32 and restart the server.
***********************************************************************************************************************************

Note that while the above excerpt recommends that this value be decreased Baan requires this to be increased. On some systems the 3rd numerical entry in this string was set to 512. This allowed only about 40 to 45 users to log in. By increasing this number it was determined that a corresponding number of additional users were able to access the system. In the systems that are experiencing the 505 there would be a 3rd entry that has a value below the required number. By inserting a comma (,) and a valid number in increments of 512 with no spaces between the numbers and the commas you will specify the size of this desktop memory pool. BE VERY CAREFUL WHILE CHANGING THIS VALUE!!! Any modification to the registry can cause problems system wide. A value that is too high will result in using up too many resources. A value of 1024 may be loosely translated to about 50-100 users. Windows 2000 may require a higher setting.

You should always do a backup of your registry before performing this procedure.

Thanks BBailey for your prompt answer.

The site has a 42 user licence. The errors were appearing with #of logged on users above 35 or so....

Increased the value to 1024.
We'll see the results in the next few days...

Will post the results here.


Thanks
Fred

Hi again.

It is now 3 or 4 days after the parameter changing. The problem did not appear again.

Thanks for your help
Fred

I have the same problem as above, but it hasn't been solved yet!

I have the same problem as above, but it hasn't been solved yet!

What are your settings and how many users do you have? Feel free to increase the parameter even further. Not a factor 100 or so, but 2048 is not a bad value.

Let us know your results,
Dick