Problem

On occassion, a smart-client may terminate abnormally (i.e., crash, disconned from server), but the smart-client server does not terminate. How can we investigate the cause for the smart-client termination.

Solution

We will require full-memory dumps for the smart-client crash. To facilitate this, update the adplus.config file that resides in the APM smart-client server’s bin folder.

NOTE: If you have a thick-client environment, you can often replicate the crash on the thick-client, rather than using a smart-client connection to a server.

Backup the adplus.config file, in the "bin" folder, and add the following lines to the adplus.config file in the same "bin "folder, immediately before the “</Exceptions>” line:

      <!--Do a full dump on a first-chance access violation exception.-->
      <Exception Code="av">
         <Actions1>FullDump</Actions1>
      </Exception>

If you make the change to the server’s adplus.config, you will need to restart the server. If you are using a thick-client, simple start the thick-client after making the change to the local adplus.cofig.

Proceed to replicate the crash, and compress (i.e., zip) & upload the dump(s) and all log files to Bentley's ShareFile folder.

If you do not already have a ShareFile link (e.g., https://bentley.sharefile.com/r-r17a293d938a4acca), previoulsy provided by the Suppor Rep, please request one.

After you have produced the dumps for the crash, please restore the backed up adplus.config file to the "bin" folder.

See Also

N/A.