Fix for Errors with Connections and Sync to GoldMine 9.2

  • Updated

Issue

Riva connections to GoldMine 9.2 may experience the following critical error:

  • GoldMine 8.x or 9 upgraded to GoldMine 9.2. After GoldMine is upgraded to version 9.2, when the Riva sync service tries to connect to GoldMine, the service reports a critical stop due to a "System.AccessViolationException: Attempted to read or write protected memory" error.

  • New GoldMine 9.2 Installations. After Riva is installed and a connection to GoldMine is configured and submitted, a Windows fault occurs, and Riva closes and reports a "System.AccessViolationException: Attempted to read or write protected memory" error.

Examination of Log Files

Examination of the Riva\Logs\ log(date).txt or crmex-log (date).txt files reveals an error similar to:

2012-08-21 12:43:14,703 ERROR [3272] [(null)] Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

 

Cause for the Critical Error

The GoldMine 9.2 client LoadAPI cannot interact with the Riva connection processes.

Solution

Riva is working with GoldMine to implement a permanent fix. A temporary fix has been added to Riva that allows Riva to make single-threaded connections and enable data sync.

Temporary Fix: This fix enables the core sync of contacts, calendar items, and tasks. SmartConvert of email is not supported by this fix: as a result, all existing Riva sync policies must be modified to disable SmartConvert.

 

New Riva installations

For new Riva installations, prepare a new Riva server for GoldMine 9.2.

For existing Riva installations

For Riva connecting to GoldMine systems recently upgraded to GoldMine 9.2, use the following procedure.

  1. In the Riva Service Monitor application, stop the service.

  2. Upgrade Riva On-Premise to the latest public release.

  3. Create a RivaApp.exe.config file to enable support for GoldMine 9.2, and add the following XML code to the file:

    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
      <appSettings>
        <add key="Crm.GoldMine.IsVersion92" value="true" />

      </appSettings>
    </configuration>

     

  4. Save the file to the Riva\Application\<version> folder.

    Note: Steps 3 and 4 will prevent errors when creating a GoldMine connection.

  5. Do one of the following:

    • If connecting to Exchange, create an "Omni.Riva.CrmAgentEx.exe.config" file.

    • If connecting to GroupWise, create an "Omni.Riva.CrmAgent.exe.config" file.

  6. In the file you just created, add the following XML code:

    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
      <appSettings>
        <add key="
    Crm.GoldMine.IsVersion92" value="true" />
        <add key="Crm.ThreadPool.MaxThreads" value="1" />
      </appSettings>
    </configuration>
  7. In every Riva GoldMine sync policy:

  8. In the Riva Service Monitor application, start the service, and monitor data sync activity to ensure that there are no errors.

Applies to

  • Riva for GoldMine 9.2.
  • Riva releases 2.4.31.13840 or higher.

Was this article helpful?

/

Comments

0 comments

Article is closed for comments.