Post-Migration Issues: Adeptia Services Fail to Start or Schemas Fail to Load

Summary

After migrating objects from one environment to another, you may encounter errors that prevent Adeptia services (Kernel) from starting or cause Data Mappers using XML Schemas to fail. This article describes the issues, root causes, and resolutions.

Issue 1: Adeptia Kernel does not start/shuts down automatically

Error observed in logs:

Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'dropboxConsumerCredentials' defined in class path resource [dropboxBean.xml]: Could not resolve placeholder 'dropbox.appKey' in value "${dropbox.appKey}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'dropbox.appKey' in value "${dropbox.appKey}"
 

Root Cause:
During migration, some critical configuration files (Adapters.properties, launcher.properties, server-configure.properties, etc.) may get corrupted or replaced with 0 KB files. This causes missing property values that Adeptia Kernel requires during startup.

Resolution:

1. Go to the server configuration directory.
2. Verify the following files:
   • Adapters.properties
   • launcher.properties
   • server-configure.properties
      
3. Ensure that none of these files are empty (0 KB) and that they contain the correct configuration values.
4. If any file is corrupted, restore it from:
   • A backup copy, or
   • The source environment.
     
      

Issue 2: Data Mappers fail to load XML Schema

Error message in Data Mapper:

Unable to load schema due to missing or invalid file reference.



 

Root Cause:
The schema file references inside ServerKernel\web\FileReferences may not have been migrated properly. As a result, the linked .xsd file is either missing from the directory or has become 0 KB during migration.

Resolution:

Navigate to the folder:
ServerKernel\web\FileReferences

1. Locate the schema ID associated with the failing Data Mapper.
2. Check that the corresponding .xsd file exists.
3. Ensure the .xsd file is not empty (0 KB) and contains valid schema content.
4. If missing or corrupted, replace the .xsd file with a valid copy from the source environment.