Question:
Possible reasons for an abnormal abort of CST Studio Suite when it starts
Why does not CST Studio Suite start properly?
Possible reasons for CST
Answer:
1. Unsupported operating system
Startup problems might be caused by an unsupported operating system (OS) and thus we recommend using the software on one of the supported systems. Please click the following link to find the latest hardware and software recommendations for CST Studio Suite versions as well as for the list of supported OS.
(If not working by directly clicking the link, please paste the link in a browser)
2. Corrupted registry (Microsoft Windows)
In order to clean the Registry:
- Close all CST software
- Open the registry editor and go to the entry
- HKEY_CURRENT_USER\Software\CST AG\.
- Delete (or rename) the following key: "CST DESIGN ENVIRONMENT"
3. Graphics adapter not fully OpenGL compatible
In order to check whether the graphics adapter is causing the problem please proceed as follows:
- Switch off hardware acceleration of the graphics adapter
- Check if you are using the latest driver for the graphics card
4. Antivirus issues
- Check whether CST Studio Suite starts up correctly if you switch off the antivirus
- In case the antivirus that causes the problem, you may exclude the CST install path as well as the path where you typically store your CST models from the on-access scan.
5. Desktop heap memory might be too small (Microsoft Windows)
Suggestions to increase the windows heap for distributed computing remote post- processing
- The Microsoft Windows operating system has a known limitation in the so-called desktop heap memory, which e.g. allows only a certain number of opened application windows. This can be a limitation in the number of CST models, which can be simultaneously opened on one PC.
- Also when activating the option "Remote Post processing" on a DC Solver Server it's recommended to increase the default desktop heap memory on the DC Solver Server system.
- The desktop heap memory can be configured in the registry editor in the following place:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems -> Windows
- This key "Windows" contains a very long string, which should be similar to the following lines (next page)
- ObjectDirectory=\W%SystemRoot%\system32\csrss.exe indows
SharedSection=1024,3072,512
Windows=On
SubSystemType=Windows
ServerDll=basesrv,1
ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2
ProfileControl=Off MaxRequestThreads=16
g. In this long string the desktop heap memory is defined under: "SharedSection=1024,3072,512" (third value is not always present).
h. We recommend to change the Shared Section values to: Shared section = 2048,20480,2048
i. This applies to all variants of Windows currently supported by CST Studio Suite
j. After changing the setting, the computer needs to be rebooted in order to activate the changes.
6. Switch on diagnostic output (Microsoft Windows)
- In order to enable the registry debug flags we need to enable in a macro. (images of the macro)
- Log files will be recorded in the CST Studio Suite installation folder (e.g. "C:\Program Files (x86)\CST Studio Suite 20XX"). Please create a support request and attach all created log-files ("Modeler_Start_*.log" and "DS_Start_*.log").
- The logging can be deactivated via the same macro.
NOTE: we recommend attaching the information about your system when creating the service request. This helps us to find problematic components and/or configurations. To get this information proceed as follow:
Microsoft Windows:
Start Menu -> All Programs -> Accessories -> System Tools -> System Information
In the "File" menu of this program select "Save" and send us the created file.
Linux:
Start the cst_system_check tool found in the main installation folder and select the option "Create system report" and send us the created file.