Startup errors
Startup is completed successfully if the export process manages to build all the tsv files the system needs in the mmgr\share directory. Typical errors are:
| Error condition | Reason |
|---|---|
| Export runs fine but there are no files in the mmgr\share folder. The tsv files are then found in the mmgr folder, some of them preceded with the string %export_dir%. | This means that the user failed to properly configure the Launcher Resource Registry (mrc and/or mrn files) and/or the Launcher Administration tool. The Launcher Administration tool has to point to a user-created mrc file that in turn has to point to the mmgr.mrn file provided with CM |
| Export runs but fails with "Source Not Available". | The back end database is not properly configured, usually an error in the startup.mdq file. Adding "-t" to the database card will generate a database trace that can be used to determine the problem. Both MessageManager and RunMaps have to be re-deployed once the mdq file has been corrected. |
| Export runs, but creates a reject file indicating all run maps failed with return code 3. | Run Maps have not been deployed. |
| Export runs, but creates a reject file indicating some or all run maps failed with return code 12 or similar. | Run Maps have not been deployed after fixing the update.mdq file, or the database creation failed. |
| Export runs, but creates a reject file indicating that a dll/so is either not found or the wrong version. | Message Manager requires two dll/sos: cmsvc and cmsvu. They have to be deployed in binary mode and their properties have to be defined as executables. On Windows the dlls have to be in the mmgr folder, on UNIX the so's have to be in the DSTX libs folder. |
| Export runs, but creates a reject file indicating HIPAA components are missing. | If you select HIPAA validation, the export process verifies that the components required by Trading Manager from the HIPAA Pack have been deployed. Two maps from the HIPAA Pack (x4010hipaasegmentdataaudit.mmc and x12type6qualifier.mmc) have to be deployed into the mmgr folder on the server. Additionally, one file (hipaa_x12_type_6_value.dat) has to be deployed into the mmgr\share folder on the server. See Validating HIPAA X12 Data the IBM WebSphere Transformation Extender Pack for HIPAA EDI documentation. for more information. |
| Launcher starts up fine but nothing is running, the Management Console is blank. | The Launcher did not find any msl Launcher Control file. Either Trading Manager was not deployed or the location in the deployment definition is incorrect. Redeploy and review the MSEDploy.TXT file to verify where the maps and *.msl file are being deployed. |
| Launcher startup, customer maps are running, but files are piling up in the mmgr\mail folder. | See previous error condition. |