DMS Error Sources:
If an error message is returned for a submission, consult the GME EX R1.1 Dealer Communication Codes v0.6.xls document attached to the FS/412 issue.
Aftersales Server Error Sources:
Log on to the Aftersales server and check the ebXML message service is running. Symptoms of its not running would be: MMD and payload files persisting in the MMD and TOGME payload directories.
Communication Errors:
There is the possibility of network outages between the DMS and Aftersales server and between the Aftersales server and the ECT.
Error messages:
Note: If Autoline reports a transaction at Error status, telephone, using the number you have for the Dealer Assistance Centre (DAC):
DAC@net.opel.com
and report the error. If a transaction is left at Pending status for a long time - that is, longer than 35 minutes, please contact Autoline Support.
| Exchange error encountered: Check authorisation request - no authorised transactions found | |
| Cause: | This message may be displayed on the GM Exchange Interface Form when you select Parameters and Controls from the Tools menu on the GM Exchange Transmissions and Receipts Form. |
| Solution: | An authorisation response has not been processed by the Autoline Exchange daemon. If an authorisation request has not been sent, one should be transmitted. On receipt of an authorisation response, the software will complete the set-up. |
| Dealercode parameter not set up | |
| Cause: | If this message appears on the GM Exchange Interface form, either when you select the Set Client Code Page option from the Tools menu on the GM Exchange Transmissions and Receipts form, or when you select the Send Authorisation Request option from the Tools menu on the GM Transmissions and Requests form, the GM Dealer Code field may not have been filled in. |
| Solution: | Click OK ready to check the GM Dealer Code on the Parameters and Controls form. |
| Error creating GM.MS.exmap! or Error: unable to open GM.exmap | |
| Cause: | If any tables were created, or if an error was encountered, the GM Exchange Interface form is displayed. When the option is first selected after a company has been chosen, the data files for the program are validated and, if missing, created. Opened OK might also be displayed in the Detail where the file already exists but others needed to be created. |
| Solution: | If any error messages are displayed, review them and take appropriate action. Successful file creation messages are displayed for information only; no action need be taken. |
| Unable to read daemon parameters | |
| Cause: | The parameters have not been set up, or there is a problem with the parameter table. |
| Solution: | Please log a call with Autoline Support. |
| Error creating Exchange daemon record, or Error reading GM.MS.dmnpa | |
| Cause: | After Table Validation, the daemon parameters are accessed, and, if necessary, auto-created by the software. If they are created, the GM Exchange Interface window is displayed with the Check column heading reading: Generic Daemon. |
| Solution: | If an error is reported, take appropriate action: if the daemon record has been created, the notification requires no further action. |
| Error writing parameter record, or Please set up company parameter record before setting code page | |
| Cause: | These messages could appear on the GM Exchange Interface form when you select the Set Client Code Page option from the Tools menu on the GM Exchange Transmissions and Receipts form. |
| Solution: | Click OK ready to check, and complete, the parameters and controls entry for the current Aftersales Company. |
| Error creating log file directory [error code], or Error creating GM-OUTBOUND directory [error code], or Error creating Payload directory [error code], or Error creating Answerback directory [error code], or Error creating GM-TRANS directory [error code] | |
| Cause: | After validating the data tables, the system continues to check for, and create, the necessary data directories on the Autoline server in use. These messages may be displayed on the GM Exchange Interface Form if the set-up program is unable to create the necessary system directories. |
| Solution: | Check that the data directories are correctly configured in the Manufacturing systems set-up for General Motors. |
In response to Send Authorisation Request, selected from the Tools menu on the GM Exchange Transmissions and Receipts form, the following messages may be displayed:
| Code page not set | |
| Cause: | The client code page may not have been set up. |
| Solution: | Check that the Client Code Page field is filled in on the Parameters and controls form. If it is not, use the Tools menu option to set the client code page.
Warning: Do not edit the code page parameter manually unless you are sure you know what it should be. Use with extreme caution! |
| Unable to locate company GM.exmap entry | |
| Cause: | The system cannot locate the Aftersales Company mapping entry in response to Send Authorisation Request. |
| Solution: | Use the Tools menu option Dealer Branch Mapping to set the Aftersales Company mapping. |
| Unable to locate company parameters | |
| Cause: | An entry for the selected Aftersales Company cannot be located in the parameters and controls table. |
| Solution: | Click OK ready to check, and complete, the parameters and controls. |
| Error sending Authorisation Request | |
| Cause: | An error was encountered while transferring the authorisation request to the Aftersales/ebXML client server. |
| Solution: | Check the connectivity between the Aftersales/ebXML server and the Autoline server. |
