Using WebLogic Integration - Business Connect
Messages
The following topics are provided about WebLogic Integration - Business Connect messages.
Messages
For information about how to control the message levels WebLogic Integration - Business Connect generates, see Preferences General Tab.
Level 0 Debug Messages
Level 0 messages identify normal events. In addition to the messages documented here, debug messages include reporting of a higher level of detail of events in the server log, which is in the WebLogic Integration - Business Connect logs directory (see Viewing the server.log File in Windows and UNIX).
Turning on debug messages can be helpful in troubleshooting. Novice users might want to generate debug messages to help resolve issues that can occur while learning the application. Experienced users can find debug messages useful for advanced troubleshooting. We recommend that you turn off debug messages when not troubleshooting because generating debug messages slows application performance.
Agent started
Description
An agent has started and is running.
Backup file has been archived
Description
A confirmation that a file was moved successfully from the backup directory to the archive directory.
Backup file has been deleted
Description
A confirmation that a file was deleted successfully from the backup directory during the archiving process.
Duplicate received (automated resend)
Description
WebLogic Integration - Business Connect received more than once a document that a partner resent automatically. WebLogic Integration - Business Connect discards all subsequent documents.
File backed up
Description
A file has been copied to the backup directory.
Partner certificate updated
Description
A partner certificate has been changed, and the database has been updated successfully.
Partner Profile updated
Description
A partner profile has been changed, and the database has been updated successfully.
SKey iteration count level has reached minimum allowable level for partner
Description
The number of S/Key iterations set on the Partner Profile window Firewall tab has been reached. Your partner's firewall administrator should reset the authentication rule, but no action is required on your part.
Level 1 Transaction Messages
Level 1 messages identify transactional and administrative events requiring no action.
A Company profile has been removed
Description
A company profile has been deleted in Administrator.
A Company profile has been updated
Description
A company profile has been updated in Administrator.
A new Company has been registered
Description
A company profile has been created in Administrator.
A new Partner has been registered
Description
A partner profile has been created in Administrator.
A Partner profile has been removed
Description
A partner profile has been deleted in Administrator.
A Partner profile has been updated
Description
A partner profile has been updated in Administrator.
API - NOTIFY - LOCAL
Description
The system has notified a local API client of an event.
API - NOTIFY - REMOTE
Description
The system has notified a remote API client of an event.
API - RECEIVING - REMOTE
Description
An API client has received a document from an HTTP or HTTPS server.
API - SENDING - LOCAL
Description
The system has sent a document for a local API client.
API - SENDING - REMOTE
Description
The system has sent a document for a remote API client.
AQUIRED
Description
The system has acquired a document through the outbound integration set up in your company profile.
Companies started
Description
Server has completed its startup routine.
Companies starting
Description
Server starts all company-based threads (packager, inbound, https servers, and so on).
MDN RECEIVED
Description
The system has received a message disposition notice (MDN), which confirms that the partner has received the document you sent.
MDN SENT
Description
The system has sent an MDN to a trading partner to acknowledge receiving a document from that partner.
NEW
Description
The system has retrieved a new document for outbound processing.
PACKAGED
Description
The system has successfully packaged a document for delivery. Packaged means the document has been encrypted and MIME wrapped.
RECEIVED
Description
The system has received a document from a trading partner.
SENT
Description
The system has successfully sent a document to a trading partner.
Server configuration completed
Description
Server has successfully configured all agents and threads.
Server configuration started
Description
Server starts all agents and threads and also starts building Administrator objects such as companies, partners, certificates and schedules.
Server shutdown completed
Description
Server has successfully shut down all agents and threads.
Server shutdown started
Description
Server begins the process of cleanly shutting down agents and threads.
TRANSFERRED
Description
The system has moved an unpackaged document received from your partner to the inbound integration set up in your company profile.
Level 2 Notification Messages
Level 2 messages are for system events. Some of these messages are informational and some might require action on your part to resolve.
These messages generate notification messages in Tracker. If you have completed the notify e-mail address and alert/notify SMTP server fields on the Company Profile window Preferences tab, the system sends these messages via e-mail.
An Api document listener has been removed
Description
An external API document listener connection has closed. No more document events will be sent to the listener.
An Api event listener has been removed
Description
An external API event listener connection has closed. No more events will be sent to the listener.
Duplicate MDN received
Description
WebLogic Integration - Business Connect received a message disposition notice (MDN) for an outbound document that already has been acknowledged. This is because the original document was resent automatically, so multiple MDNs were returned. Or, the MDN was not deleted from the transport server after it was processed.
New Api document listener registered
Description
An external API document listener connection has opened. All document events will be sent to the listener.
New Api event listener registered
Description
An external API event listener connection has opened. All events will be sent to the listener.
Received duplicate document
Description
WebLogic Integration - Business Connect received an EDI document with a control ID that was the same as a previously received document's control ID. WebLogic Integration - Business Connect detected this because the check box for preserving inbound binary and XML file names is selected for the partner's profile.
Cause 1
Your partner sent you more than one EDI document with the same control ID.
Remedy 1
If necessary, contact your partner for clarification.
Cause 2
The check box for preserving inbound binary and XML file names is unintentionally selected on the Preferences tab for the partner's profile.
Remedy 2
Turn off the selection for the partner's profile.
Received miscellaneous document
Description
WebLogic Integration - Business Connect received a binary or unidentifiable document that could not be associated with a partner. The file was placed in the company's other directory.
Cause 1
WebLogic Integration - Business Connect received a binary document for a partner that has not been configured to receive such documents. In other words, there was no matching partner for the inbound document.
Remedy 1
Examine the received file as necessary. Select a company for this partner in the binary company drop-down list in the partner's profile in WebLogic Integration - Business Connect.
Cause 2
A MIME message does not have body parts. WebLogic Integration - Business Connect received an e-mail message without an attachment for this partner.
Remedy 2
Resend or resubmit this document in Tracker. If necessary, examine the document in the other directory to see whether it is the one you need to receive. You then can manually route it to the appropriate application.
If you want to receive binary documents from this partner, select a company in the binary company drop-down list in the partner's profile in WebLogic Integration - Business Connect.
The currently Active certificate for Company [name] will expire on [date].
Description
A certificate will soon expire. It must be updated to avoid disruptions in trading.
The returned Acknowledgement indicates a message delivery failure.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates a problem resolving a URI on the sent document.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates a SOAP Fault.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates an error in an element content or attribute value.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates an unknown error.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates that a XML element content or attribute value inconsistent with other elements or attributes.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates that a XML element content or attribute value not recognized.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates that a XML element or attribute not supported.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates that an unspecified error occurred processing the document (see the Acknowledgement MCD).
Description
Only used for RosettaNet. The partner rejected the message.
The returned Acknowledgement indicates that the contents of the RosettaNet headers were invalid (see the Acknowledgement MCD).
Description
Only used for RosettaNet. The partner rejected the message.
The returned Acknowledgement indicates that the message security checks failed.
Description
Only used for ebXML. The partner rejected the message.
The returned Acknowledgement indicates that the Message Time To Live Expired.
Description
Only used for ebXML. The partner rejected the message.
The returned MDN indicates that the partner could not authenticate the signature of the sent document
Remedy
Make sure your certificate is valid and active and that the partner has your correct certificate.
The returned MDN indicates that the partner could not decrypt the sent document
Remedy
Make sure your certificate is valid and active and that the partner has your correct certificate.
The returned MDN indicates that the partner could not process the sent document.
Description
Your partner received the document you sent, but cannot process it.
Remedy
Re-send the document. If it fails again, verify that you and your partner are using the same valid certificate.
The returned MDN indicates that the partner could not validate the integrity of the sent document
Description
The sent document was altered between the time it was signed and sent and when it was received and the signature verified. Or the algorithm used to calculate the hash of the document is not the same on both the sending and receiving ends.
Cause 1
The document might have been corrupted in transit.
Remedy 1
Re-send the document.
Cause 2
You and your partner might not have the same certificates.
Remedy 2
Make sure you and your partner are using the same valid certificates. Re-send the document.
The returned MDN indicates that the partner does not recognize the sender of the document.
Description
The partner rejected the document because the sender could not be identified.
Cause
The document was rejected for one of the following reasons:
Unknown partner ID
Unknown partner certificate
Unknown partner e-mail address
Inactive partner profile
Unknown or missing partner secondary ID
Remedy
Troubleshoot the possible causes and re-send the document.
The returned MDN indicates that the partner does not support the packaging format of the sent document.
Description
The partner cannot parse an XML document or the MIME used in packaging the document is invalid.
The returned MDN indicates that the partner expected a signature on the sent document.
Description
The partner expected the document you sent to be signed and rejected it.
Remedy 1
Make sure you are sending documents with the proper security settings on the Partner Profile window Security tab.
Remedy 2
Make sure the mail server supports S/MIME signatures.
The returned MDN mic value was invalid
Description
WebLogic Integration - Business Connect received an MDN with a MIC (message integrity check) that does not match that of the corresponding outbound document.
Cause
A non-trusted party has sent the MDN.
Remedy
Contact the partner to verify the state of the remote servers and network.
Warning: The product license is about to expire.
Description
The user license for WebLogic Integration - Business Connect will expire soon. When this occurs, the application will be unusable.
Remedy
Obtain a new user license file before the old file expires.
Level 3 Rejected Messages
Level 3 messages identify reasons why WebLogic Integration - Business Connect has rejected documents.
These messages generate alert messages in Tracker. If you have completed the alert e-mail address and alert/notify SMTP server fields on the Company Profile window Preferences tab, the system sends these messages via e-mail.
ebXML SOAP FAULT
Description
SOAP faults are error conditions specific to ebXML.
EDI parsing error
Description
WebLogic Integration - Business Connect attempted to process a malformed X12 or EDIFACT document from your translator and rejected it.
Cause 1
Your translator put a malformed EDI document in the WebLogic Integration - Business Connect EDI outbound directory.
Remedy 1
Have your translator resubmit the document. Or, verify whether the rejected file is an EDI file; if not put the file in the correct outbound directory.
Cause 2
WebLogic Integration - Business Connect received a malformed EDI document from a trading partner. The application determines this by checking the document for certain standard information that EDI documents should have.
Remedy 2
Examine the file and contact the partner to resolve the EDI formatting problem.
Insufficient security: not encrypted
Description
WebLogic Integration - Business Connect received an encrypted document from a partner, but was expecting to receive an unencrypted document. Or, WebLogic Integration - Business Connect received an unencrypted document from a partner, but was expecting to receive an encrypted document.
WebLogic Integration - Business Connect requires you and your partner to have identical settings for signing documents, encrypting documents, acknowledging documents and signing acknowledgments.
Cause
You and your partner do not have synchronized settings for document encryption.
Remedy
Make sure you and your partner have the same setting for document encryption on the Partner Profile Security tab for your respective partners. The encrypt documents check box should be either checked or unchecked on both systems. Once the setting is synchronized, have your partner resend the document.
Insufficient security: not signed
Description
WebLogic Integration - Business Connect received a signed document or MDN from a partner, but was expecting to receive an unsigned document or MDN. Or, WebLogic Integration - Business Connect received an unsigned document or MDN from a partner, but was expecting to receive a signed document or MDN.
WebLogic Integration - Business Connect requires you and your partner to have identical settings for signing documents, encrypting documents, acknowledging documents and signing acknowledgments.
Cause 1
You and your partner do not have synchronized settings for document signing.
Remedy 1
Make sure you and your partner have the same setting for document signing on the Partner Profile Security tab for your respective partners. The sign documents check box should be either checked or unchecked on both systems. Once the setting is synchronized, have your partner resend the document.
Cause 2
WebLogic Integration - Business Connect received an unsigned MDN.
Remedy 2
Make sure you and your partner have the same setting for acknowledgments on the Partner Profile Security tab for your respective partners. The acknowledgment check box should be checked on both systems.
Invalid or untrusted certificate was needed to verify message signature
Description
The certificate used to sign the document is not trusted (the certificate root is not in the list of trusted roots) or the certificate is invalid.
MDN received with no matching outbound document
Description
You received an MDN acknowledging a document you sent, but your system cannot match the MDN and the document because the runtime record of the document has been manually deleted or archived.
Cause
A document was sent. After not receiving an expected MDN, the document was sent again. After the document was sent the second time, the MDN was received for when the document was sent the first time. The runtime document record is manually deleted or archived before the second MDN is received.
Remedy
None.
No active partner or unknown partner
Description
WebLogic Integration - Business Connect attempted to process a document for which there is no active partner.
Cause 1
An EDI or XML document was dropped in the corresponding outbound directory. The document's recipient ID does not match any active partner.
Remedy 1
Import and activate the profile of the partner to whom the document addressed. Resend the document in Tracker.
If you do not want to send documents to this partner, make sure your EDI translator or XML application does not place documents in the outbound directories for WebLogic Integration - Business Connect.
Cause 2
WebLogic Integration - Business Connect received a document from an inactive or nonexistent partner.
Remedy 2
If you do not have a profile for this partner, ask the partner to send you one that you can import to WebLogic Integration - Business Connect.
If you have a profile for this partner but it is inactive, activate it in the Partner window in WebLogic Integration - Business Connect.
Packager certificate or signature related error
Description
This is an error from the Crossworks security module.
Remedy
Set the event logging level to debug and check the server log for additional information. Set the event logging level on the General tab in Tools—>Preferences.
Packager decryption error
Description
The document was encrypted and there was an error in decrypting it.
Remedy
Set the event logging level to debug and check the server log for additional information. Set the event logging level on the General tab in Tools—>Preferences.
RosettaNet content validation error
Description
This indicates a problem with the content or structure of the RosettaNet document.
Cause
For example, a missing required element or a value of an element that is not valid.
Signature certificate is not in list of partner's active or valid certificates
Description
The certificate used to sign the document needs to be in the partner's list of active or valid certificates.
Cause
The certificate might be new, and the partner might not have received it yet. Or the certificate might be in a pending or retired state.
The sender and receiver have the same Id
Description
WebLogic Integration - Business Connect received a message from a partner who has an ID identical to yours.
Cause 1
You are trading documents with yourself (that is, testing with a single company exported or imported as the partner).
Remedy 1
Create another company profile with a different ID. Export and import the second company and have the first company trade with the second company.
Cause 2
The transport server (most likely SMTP-POP) has returned or bounced the message.
Remedy 2
Verify the partner's e-mail address and the state of the SMTP-POP server and connection.
Cause 3
There are two real-world companies with identical IDs.
Remedy 3
Create another company profile with a unique ID or ask your partner to do so.
Unlicensed protocol
Description
You are trying to use a protocol that is not authorized under your user license.
Remedy
Use a licensed protocol.
XML parsing error
Description
WebLogic Integration - Business Connect attempted to process a malformed XML document and rejected it.
Cause 1
Your XML application put a malformed XML document in the WebLogic Integration - Business Connect XML outbound directory.
Remedy 1
Have your XML application resubmit the document. Or, verify whether the rejected file is an XML file; if not put the file in the correct outbound directory.
Cause 2
WebLogic Integration - Business Connect received and rejected a malformed XML document.
Remedy 2
Examine the file and contact the partner to resolve the formatting problem.
Level 4 Error Messages
Level 4 messages identify errors that affect document transactions.
These messages generate alert messages in Tracker. If you have completed the alert e-mail address and alert/notify SMTP server fields on the Company Profile window Preferences tab, the system sends these messages via e-mail.
Network error
Description
WebLogic Integration - Business Connect is unable to send or receive documents due to transport protocol or network problems.
Cause 1
The FTP or POP server is offline.
Remedy 1
Verify the status of the POP server or FTP server or both.
Cause 2
The local network is down.
Remedy 2
Verify the network status.
Cause 3
A firewall might be impeding document transport.
Remedy 3
Verify correct connectivity through the firewall for inbound and outbound documents.
No active signer certificate
Description
WebLogic Integration - Business Connect attempted to sign a document or an MDN for a company for which there is no active certificate.
Cause 1
A certificate exists for this company profile, but it is not active.
Remedy 1
In the Certificates window in WebLogic Integration - Business Connect, select and activate the certificate.
Cause 2
There is no certificate for this company profile.
Remedy 2
Generate a self-signed certificate from the Certificates window in WebLogic Integration - Business Connect. Or, import a third-party certificate.
Cause 3
You do not want to exchange signed documents with this partner.
Remedy 3
Clear the sign documents check box on the Security tab for this partner profile in WebLogic Integration - Business Connect.
Resend limit reached
Description
The system has resent the document the configured number of times but has not received an acknowledgement from the trading partner.
Cause 1
If you are sending documents by e-mail, the e-mail address might be incorrect.
Remedy 1
Verify the e-mail address with your trading partner.
Cause 2
The partner's transport server is failing or not in service.
Remedy 2
Contact the partner.
Cause 3
The partner is not online.
Remedy 3
Contact the partner and verify that the partner's trading engine is online.
Cause 4
If you are sending documents by FTP, the FTP information might be incorrect.
Remedy 4
Verify with your partner the FTP inbox and pickup directories and the FTP server.
Retry limit reached
Description
The system has tried unsuccessfully to resend the document for the configured number of hours.
Remedy
See Resend limit reached.
You are not licensed to configure profiles using the API.
Description
Your user license does not authorize you to use the profile management API.
Remedy
Obtain a user license that authorizes you use the API.
You are not licensed to submit documents using the API.
Description
Your user license does not authorize you to use an API client to submit documents to WebLogic Integration - Business Connect.
Remedy
Obtain a user license that authorizes you use the API.
Level 5 Network Error Message
The Level 5 message identifies a network error.
This message generates an alert message in Tracker. If you have completed the alert e-mail address and alert/notify SMTP server fields on the Company Profile window Preferences tab, the system sends this message via e-mail.
Unable to send API Client a System event. Removing API Client from queue.
Description
An attempt was made to send an event to a API client that was registered but no longer exists.
Level 6 Configuration Error Messages
Level 6 messages identify profile configuration errors.
These messages generate alert messages in Tracker. If you have completed the alert e-mail address and alert/notify SMTP server fields on the Company Profile window Preferences tab, the system sends these messages via e-mail.
Active transport for partner has been disabled
Description
The partner is no longer listening on the active transport.
Cause
A partner profile has been electronically updated. In other words, your partner has switched from one transport to another for receiving documents.
Remedy
Activate a new transport for the partner.
Incomplete transport configuration
Description
The connection to be used for sending or receiving documents was not established due to missing or incorrect information in the company or partner profile.
Incomplete transport configuration for binary re-routing
Description
The company is set up to re-route binary documents. A binary document was received and had a secondary ID that is different than the primary ID, but the secondary ID is unknown.
Remedy
Add a secondary partner ID that matches the one used for the binary document or have the partner resend the document with a valid secondary partner ID.
No active transport
Description
WebLogic Integration - Business Connect attempted to send a document or MDN to a partner who does not have an active transport.
Cause
You created or imported a partner profile, but did not activate a transport.
Remedy
Activate a transport for the partner on the Partner Profile Transports tab.
Level 7 Unexpected Error Messages
Level 7 messages identify unexpected errors.
These messages generate alert messages in Tracker. If you have completed the alert e-mail address and alert/notify SMTP server fields on the Company Profile window Preferences tab, the system sends these messages via e-mail.
Crossworks exception
Description
Indicates a problem loading the private keys for the company active certificate.
Password is null
Description
Indicates a missing password while trying to load the private keys for the company active certificate.
Remedy
Delete the current active certificate and generate a new active certificate.
Unable to archive
Cause
Set the event logging level to debug and check the server log to determine the specific cause of this exception. Set the event logging level on the General tab in Tools—>Preferences.
Unable to configure
Description
There are many possible reasons for this. For example, unable to configure the Server upon startup, unable to establish a SMTP connection possibly due to incorrect port, unable to get the certificate fingerprints to load into the HTTPS server for client authentication.
Unable to configure Company Profiles
Description
Unable to configure a company profile from the database to a Server company object.
Unable to configure FTP Integration
Description
Unable to configure the FTP integration as specified in the Company Profile window Integration tab.
Unable to configure IBM MQSeries Integration
Description
Unable to configure the MQSeries integration as specified in the Company Profile window Integration tab.
Unable to configure JMS Integration
Description
Unable to configure the JMS integration as specified in the Company Profile window Integration tab.
Unable to configure Partner Profiles
Description
Unable to load all the partner profiles into the Server.
Unable to configure Post-processing
Description
Unable to configure the inbound post-processing integration as specified in the Company Profile window Integration tab.
Unable to configure Schedules
Description
Unable to configure one or more schedules from the Schedules information viewer.
Unable to configure System Integration
Description
A generic error dealing with configuring integration of one or more of the following types: FTP, MQSeries, JMS, post-processing.
Unable to construct
Description
This error has various reasons:
Error parsing an X12 document
Error creating an Ack or MDN
Error creating a Resend Request object (used to resend documents if the Ack or MDN is not received within a set time)
Error trying to read in the initial content of a document
Error creating the partner transports for a specific company
Error creating the binary-related polling objects for a specific company
Unable to get certificate
Description
This error has various reasons:
Unable to get the active certificate for a company
Unable to get the valid certificate for a company
Unable to get the invalid certificate for a company
Unable to load and start a new instance of the API HTTPS server due to no certificate available
Unable to load and start a new instance of the SOAP RPC HTTPS server due to no certificate available
Unable to initialize
Description
Unable to load and initialize the system parameters.
Cause
The system parameter table in the database might be corrupt.
Unable to package
Description
The Server application cannot package an outbound document.
Cause 1
No active partner.
Remedy 1
Make sure the partner profile is active.
Cause 2
No active certificate.
Remedy 2
Make sure an active and valid certificate is associated with the partner profile.
Cause 3
Out of disk space.
Remedy 3
Make sure adequate disk space is available on your system.
Unable to process documents
Description
This error has various reasons:
Error occurred while an API client tried to submit a document
Unable to log a new outbound document due to a duplicate ID already in the database for this document
Error occurred while trying to unpackage a document
An e-mail message with one or more attachments failed to process all the attachments
Unable to process FTP Integration inbound documents
Description
The Server application cannot run document integration with the back-end system.
Cause 1
A connection failure between WebLogic Integration - Business Connect and the FTP server.
Remedy 1
Make sure there is a working connection.
Cause 2
Integration is not configured properly in the company profile.
Remedy 2
Make sure integration is properly configured.
Cause 3
A problem with the FTP server.
Remedy 3
Check the FTP server.
Unable to process FTP Integration outbound documents
Description
The Server application cannot run document integration with the back-end system.
Cause 1
A connection failure between WebLogic Integration - Business Connect and the FTP server.
Remedy 1
Make sure there is a working connection.
Cause 2
Integration is not configured properly in the company profile.
Remedy 2
Make sure integration is properly configured.
Cause 3
A problem with the FTP server.
Remedy 3
Check the FTP server.
Unable to process IBM MQSeries Integration inbound documents
Description
The Server application cannot run document integration with the back-end system.
Cause 1
A connection failure between WebLogic Integration - Business Connect and MQSeries.
Remedy 1
Make sure there is a working connection.
Cause 2
Integration is not configured properly in the company profile.
Remedy 2
Make sure integration is properly configured.
Cause 3
A problem with MQSeries.
Remedy 3
Check MQSeries.
Unable to process IBM MQSeries Integration outbound documents
Description
The Server application cannot run document integration with the back-end system.
Cause 1
A connection failure between WebLogic Integration - Business Connect and MQSeries.
Remedy 1
Make sure there is a working connection.
Cause 2
Integration is not configured properly in the company profile.
Remedy 2
Make sure integration is properly configured.
Cause 3
A problem with MQSeries.
Remedy 3
Check MQSeries.
Unable to process inbound Post-processing document
Description
The Server application cannot execute post-processing on an inbound document.
Cause 1
The post-processing script is not correct.
Remedy 1
Check the post-processing script for accuracy.
Cause 2
The fully qualified path and file name of the batch file, script or executable file for the post process is not correct.
Remedy 2
Check the post-process name in the company profile.
Cause 3
In UNIX the post-processing script does not have execute permission.
Remedy 3
Make sure WebLogic Integration - Business Connect has execute permission for the script.
Cause 4
WebLogic Integration - Business Connect does not have directory permission where the script is located.
Remedy 4
Make sure WebLogic Integration - Business Connect has directory permission.
Unable to process incomplete inbound documents
Description
Error occurred while trying to process an inbound document that was not previously processed. This only happens during Server restarts or when a company is added or updated.
Cause
Set the event logging level to debug and check the server log to determine the specific cause of this exception. Set the event logging level on the General tab in Tools—>Preferences.
Unable to process incomplete outbound documents
Description
Error occurred while trying to process an outbound document that was not previously processed. This only happens during Server restarts or when a company is added or updated.
Cause
Set the event logging level to debug and check the server log to determine the specific cause of this exception. Set the event logging level on the General tab in Tools—>Preferences.
Unable to process JMS Integration inbound documents
Description
The Server application cannot run document integration with the back-end system.
Cause 1
A connection failure between WebLogic Integration - Business Connect and the JMS server.
Remedy 1
Make sure there is a working connection.
Cause 2
Integration is not configured properly in the company profile.
Remedy 2
Make sure integration is properly configured.
Cause 3
A problem with the JMS server.
Remedy 3
Check the JMS server.
Unable to process JMS Integration outbound documents
Description
The Server application was unable to retrieve a document from a JMS server because of a configuration or connection problem.
Unable to receive documents
Description
Error occurs when attempting to receive documents from the transport connection.
Cause
Set the event logging level to debug and check the server log to determine the specific cause of this exception. Set the event logging level on the General tab in Tools—>Preferences.
Unable to reject
Description
Error occurs when a document is rejected and the document cannot be written to the rejected directory.
Unable to run
Description
This error has various reasons:
The outbound agent thread for EDI, XML or binary cannot run
The outbound agent thread for EDI, XML or binary cannot process new documents
The transport agent thread that sends out documents cannot run
Unable to send
Description
WebLogic Integration - Business Connect cannot send documents due to transport protocol or network problems.
Cause 1
The SMTP or FTP server is offline.
Remedy 1
Verify the status of the SMTP or FTP server.
Cause 2
The local network or Internet connection is down.
Remedy 2
Verify the network status.
Cause 3
The partner's HTTPS server is offline.
Remedy 3
Contact the partner and verify the status of the HTTPS server.
Unable to send API Client an Inbound Document event. Removing API Client from queue.
Description
There was a problem in sending a document to a remote client API listener.
Unable to split document
Description
Error occurs when trying to split an EDI document.
Unable to store
Description
Error occurs when a document cannot be written to disk. This should only occur when a file is being backed up.
Cause
Might be lack of disk space or directory permissions.
Unable to transfer document
Description
Error occurs when document is transferred to the inbound directory or the back-end system.
Cause
Might be lack of disk space or directory permissions.
Unable to update certificate
Description
Error occurs while trying to add a certificate to a partner profile from an incoming electronic certificate update.
Unable to update Company Profile
Description
Error occurs when an incoming partner (not company) profile is processed.
Unable to write
Description
The Server application cannot write a document to the inbound directory on your system.
Cause
WebLogic Integration - Business Connect does not have permission to write to the directory.
Remedy
Make sure WebLogic Integration - Business Connect has write permissions to the inbound directories.
Level 8 Fatal Error Messages
Level 8 messages identify fatal errors that prevent the application from running.
These messages generate alert messages in Tracker. If you have completed the alert e-mail address and alert/notify SMTP server fields on the Company Profile window Preferences tab, the system sends these messages via e-mail.
The license has expired. Shutting down
Description
The user license for WebLogic Integration - Business Connect has expired. The application cannot operate without a valid license.
Cause
The application cannot operate without a valid license.
Remedy
Obtain a valid license file and replace the expired license file.
The license is not active yet. Verify the system date is correct. Shutting down
Description
The time on your computer pre-dates the active period of the user license.
Cause
The time and date on your computer might be wrong.
Remedy
Check whether the time and date are correct on your computer.
There is already an instance running. Shutting down
Description
There already is an instance of Server running on your computer.
Cause
Only one Server session can be active at the same time on a computer.
Remedy
Run only one Server session.
Your license file does not contain the correct hardware platform.
Description
You tried to install WebLogic Integration - Business Connect on a computer with an operating system that is not authorized by your user license.
Remedy
Install the application on the platform authorized by your user license.
Your license file does not contain the correct version number.
Description
Error occurs during the startup sequence and is generated when the license version number does not match the stamped version.
Remedy
Obtain a valid license file.
