Troubleshooting
Troubleshooting
How to investigate
- Check the service state:
systemctl status stcpgemini-server. - Read the service messages in the system log:
journalctl -u stcpgemini-server. - Query the events and transfers in the Riversoft Console Portal and look up the message code (
MSGnnnn) in Message and event codes. - If you need more detail, temporarily raise the debug level. See Debug.
Startup
| Symptom | Likely cause | What to do |
|---|---|---|
| The Server does not start. | There is no instance with the name set in ApplName. | Create the instance in the Riversoft Console Portal and check the name in ApplName. See Instance. |
MSG0134: serial number blank or incorrect. | Missing or invalid license. | Check the file set in ApplLicense and the license provided by Riversoft. |
| The Server cannot reach the configuration database. | DLLName does not match the DBMS or the libraries are not in the system path. | Check DLLName in Configuration library and the library file in File reference. |
New files appear in stcplog-spool. | The Server cannot write to the log database. | Check the log database availability and credentials. See Contingency spool. |
Connections
| Symptom | Likely cause | What to do |
|---|---|---|
MSG0105, MSG0126: user not registered. | The partner identified itself with a user that does not exist in the instance. | Check the user registration in the Riversoft Console Portal. |
MSG0089: user locked. | The user is locked in the configuration. | Unlock the user, if access is allowed. |
MSG0092, MSG0106: authentication rejected. | Partner credentials differ from the registered ones. | Check the user’s OFTP credentials with the partner. |
MSG0107, MSG0108: mismatched attribute. | The partner’s authentication mode (C_AUTHENTICATION) or connection mode (C_MODE) differs from the configuration. | Align the user’s OFTP parameters with the partner. |
MSG0010, MSG0088: connection limit or session time. | The user exceeded the connection limit or the session time. | Review the user limits and the partner’s simultaneous connections. |
MSG0146, MSG0171: instance session limit. | The instance reached the maximum number of sessions. | Review the instance session limit or spread the connections. |
MSG0125, MSG0168: connection blocked. | The connection was blocked by the filter or outside the allowed hours. | Check the user’s filters and hours. |
MSG0054: outbound connection failure. | Partner address, port, network or certificate unavailable. | Test connectivity with the partner and check the user’s network service. |
Transfers
| Symptom | Likely cause | What to do |
|---|---|---|
MSG0119, MSG0123: file blocked by the filter. | The file name does not match the user’s filters. | Check the user’s file filters. |
MSG0120, MSG0124: file blocked by size. | The file exceeds the user’s maximum size (0 = unlimited). | Review the size limit or split the file. |
MSG0166, MSG0167: file blocked by time. | The transfer happened outside the allowed hours. | Check the user’s hours. |
MSG0021: transmission rejected (NERP). | The partner refused the file and gave the reason in nerp_reason. | Check the reason with the partner and retransmit the file. |
MSG0037, MSG0050: restart point failure. | The transmission could not resume from where it stopped. | Retransmit the file from the beginning. |
MSG0022, MSG0023, MSG0024, MSG0025: invalid file name. | The file name is invalid or exceeds the allowed length. | Adjust the file name. |
Support
If the problem persists, open a ticket with the message code, the date and time of the occurrence and the journalctl messages. See Support.