Integration Failure Caused by Incorrect CSXINTEGRATION Database Configuration

Integration Failure Caused by Incorrect CSXINTEGRATION Database Configuration

Problem Description

The iVend integration service fails to process transactions or sync data with the ERP system. Investigation reveals that the integration is pointing to the wrong CSXINTEGRATION database — either the database name is incorrect in the connection configuration, or the integration service is connecting to a test/staging database instead of the production database.

Symptoms

  • Integration service reports connection errors or fails silently
  • Transactions do not appear in the ERP system after processing at POS
  • Integration logs reference an unexpected or incorrect database name
  • The CSXINTEGRATION database being targeted does not contain expected records

Environment / Prerequisites

  • Applies to iVend Retail environments integrated with SAP B1 or other ERP systems
  • Issue typically arises after a server migration, database rename, or environment cloning

Root Cause

The integration service connection string references an incorrect CSXINTEGRATION database. This can occur when the server is migrated, a new environment is set up by cloning an existing one, or the database is renamed without updating the integration configuration.

Resolution Steps

  1. Open the iVend Integration Service configuration file (typically IntegrationService.exe.config).
  2. Locate the connection string for the CSXINTEGRATION database.
  3. Verify the database server name, instance name, and database name are correct for the production environment.
  4. Update the connection string to point to the correct CSXINTEGRATION database.
  5. Restart the integration service.
  6. Trigger a test transaction at the POS and confirm it appears in the ERP system.

Verification

To verify: Integration service starts without errors. A test POS transaction is successfully posted to the correct ERP database.

Prevention / Notes

When cloning environments, always update all connection strings before starting services. Maintain a checklist of all configuration files that reference database names to update during environment migrations.

Source

generated from support ticket #24615