Remote Third-Party Application Creation

If you are attempting to create COM objects on a remote server, you may find that the object fails to create. This could be due to the fact that by default, the AcuConnect service is typically started with 'Local System' permissions, which may be insufficient.

For example, when executing a COBOL program that leverages Microsoft Excel, where both the COBOL and Excel are running on the remote server, the Excel instance creation is attempted with the user credentials that started AcuConnect. The AcuConnect service started with 'Local System' permissions may not have sufficient permissions to create the COM object on the server.

A solution to this issue is to start your AcuConnect service with sufficient user permissions required by the server. You do this by specifying the correct credentials on the Log On tab of the AcuConnect service's properties: