Hints

Execution Timeout

If you experience problems concerning timeouts during the download of large delta communication files, you can increase this timeout in the web.config file of each client by editing/adding the line:

<httpRuntime executionTimeout = "350"/>

Installation Checkup

If an error occurs during synchronization, refer to the client's log files. For further information, see Creating a Bug Report.

Check the following items to identify problems caused by a faulty installation:

Aurea CRM win

Configuration module: Start mmcfg.exe to verify that all logins have been correctly imported and that the correct station number is entered.
Directories: Check whether all user directories as well as the .. \< StationNumber > directories for the central station and the user's station were created. After initialization, in .. \<main office>\out a notification file should exist that was created during the import of the initial data stock.
Files: In the .. \system\exe directory only the following executables must be present: mmcfg.exe, mmco.exe, mmim.exe, mmRegServers.exe, mmba.sup and mmri.exe
Furthermore, check the contents the mmdb.ini file in .. \system\sys.

Aurea CRM web

..\system\sys: Aurea CRM web's \sys directory must be identical to Aurea CRM win's \sys directory.
web.config : To see whether web.config file was correctly modified, verify that the tag <clear/> is not present, that there are only two <Add Verb …> tags.
CRM.designer configuration files: After installing Aurea CRM web offline, the default configuration files (Config_0.gz and Config_6.gz) must be present in < XMLStoragePath >. After initialization, all child configurations for the offline user must be present as well. For further details, see CRM.designer Configurations for Offline Clients.
Offline.xml: Check the Offline.xml file for all values provided during setup (station number, URL etc.).

Load Balancing on the Server

If you want to use load balancing on the server, make sure that the load balancer is able to work session-aware.

Explanation: For the synchronization process with the offline clients, mmco.exe is started on the server. Since the communication process can take a few minutes, it is started in background mode (in order not to block other users of the web server). The offline client polls the server's communication status at regular intervals. Since the communication process is only running on one node of the load balancing cluster, session-awareness is required to guarantee that an offline client always polls the same node; this status inquiry would lead to an error on all other cluster nodes and thus abort the synchronization process.

Troubleshooting CRM.launcher

For troubleshooting hints concerning CRM.launcher, see the article “Troubleshooting CRM.launcher 8.2 Feature Pack” at https://support.aurea.com.

Uploading Large Files

For security reasons the upload of files is restricted to 10 MB. When uploading larger files to the server the following properties need to be changed in the web.config file:

<system.web>
    <httpRuntime maxRequestLength="1048576" />
</system.web>
<system.webServer>
    <security>
        <requestFiltering>
            <requestLimits maxAllowedContentLength="1073741824" />
        </requestFiltering>
    </security>
</system.webServer>

Note: The values defined for maxRequestLength and maxAllowedContentLength must match. In the above example, the defined maximum upload size is 1024 MB. Therefore, maxRequestLength has to be set to 1048576 KILOBYTES, and maxAllowedContentLength to 1073741824 BYTES.

For details, see Microsoft Knowledge Base Article <httpRuntime>-Element.