/
Solution Support Issues and Diagnostics

Solution Support Issues and Diagnostics

Issue

Symptom

Diagnostic Steps

Description

Resolution and document link

Preventive Measure

Issue

Symptom

Diagnostic Steps

Description

Resolution and document link

Preventive Measure

Drive clean up([IN217641] PROD 2 Box ( 10.77.145.204) Drive D is full)

Transaction get failed

To resolve this, unnecessary files can be deleted, and if necessary, an issue can be escalated to the Server team by creating an SR.

Monitoring the production environment and reviewing drives, we escalate issues to the Client server team or handle unnecessary file deletion internally.

Monitoring the production environment and reviewing drives, we escalate issues to the Client server team or handle unnecessary file deletion internally.

Daily monitoring of the drive is in place.

API, Load balancer Cert expired

In case of certificate expiry, access to the Adeptia Connect application becomes unavailable.

The certificate validity can be verified, and a request can be made to the Client security team for a new license. Importing a new certificate into the production environment (both external and internal load balancer) and performing SSL handshaking is essential.

The Client load balancer certificate expires annually, necessitating renewal.

https://docs.google.com/document/d/1LuaHEjxKFvW4bxUG1TvVHy5aIuFNOfXjo6KPwfC_xz0/edit

A notification has been set up, and clients are reminded to provide a license two weeks before expiry.

Integration fail due to special character[IN1267471]Data mapping failure(USINT0844)

Tavant integration fails at data mapping due to special characters.

Removing special characters from the file and reprocessing the data is the solution.

Integration failure is caused by special characters, leading to data mapping failure[IN1267471].

A list of special characters causing issues has been sent to the Tavant team for resolution before processing.

Communication has been sent to the Tavant team to address the issue.

[IN1211336] - WsMessageCall failure for Tavant USINT0844, USINT0811, USINT0841

Frequent WsMessageCall failures occur in Tavant flows.

When WsMessageCall API failures occur, the Tavant team is notified to rectify the issue.

Frequent WsMessageCall failures for Tavant USINT0844, USINT0811, USINT0841 are addressed by reprocessing pending files due to outages.

FTP connection in integration based on FTP [IN1275581] - Connection reset Failure in FTP Events

During FTP outages, the respective owner and client are informed to resolve the issue.

FTP connection issues due to connection reset failures in FTP events are resolved by reprocessing files after successful FTP connection.

Requesting the root cause of the outage to connect with the appropriate personnel for a prompt resolution.

Tavant Integration Failure Due to Expired CRM Certificate(IN359905)

CRM integration 850 fails due to certificate expiry, resulting in PKIX path building failure.

Verification of the issue involves checking the schema ADSCUSINT0850TavanttoCRM. Accessing the table confirms the issue, requiring fetching the certificate from "Client.crm.dynamics.com" and applying it to cacert.

Importing the new CRM certificate into cacert is necessary to resolve the CRM integration 850 failure due to certificate expiry.

https://adeptiamanagedservices.zendesk.com/agent/tickets/6012

[IN40475] IO device error(Adeptia production box 10.77.145.155)

All transactions fail due to IO device error.

Escalation of the issue to the server team is required.

IO device error in Adeptia production box 10.77.145.155 necessitates contacting the server team for resolution.

Notifying the server team to reboot the drive or take appropriate action based on the issue.

[IN508947] DataMapping Failed for (USINT0600)

Data mapping failures occur due to errors in the CHILDDESC column, causing parts to get stuck.

Providing a script to the DBA for reprocessing the stuck parts is the solution.

DataMapping failures for (USINT0600) lead to parts getting stuck in Adeptia DB or Teamcenter DB, requiring a script for reprocessing stuck parts.

https://docs.google.com/document/d/1j6qmA5O1gQoztRrGJ7V_-LkIkYvOgxlm1jxIbLGqEBY/edit?hl=en&forcehl=1

[IN373113] BOS_PF_USINT0989_TOGETHER_API_HEADER_LINE(WsRestConsumer failed due to certificate expiry)

USINT989 transaction failures occur due to an expired certificate.

Notifying Sukrut or Rakesh Arte via email and importing a new certificate into cacert is the resolution.

USINT989 transaction failures due to certificate expiry require notifying Sukrut or Rakesh Arte and importing a new certificate into cacert.

https://docs.google.com/document/d/1SaJzhbZOGI2GYD0RNqMa1QIUdsKkcPVdl4MzYriv2rQ/edit

EDIOutboundProcessor failed

EDIOutboundProcessor fails due to Element LIN04 exceeding the expected length with value: 26586844.

Reporting to Bill Weiman is necessary upon encountering such issues.

EDIOutboundProcessor failures due to Element LIN04 exceeding the expected length with value: 26586844 require reporting to Client team spoc.

Reporting to Bill Weiman is necessary upon encountering such issues.

EDIInboundProcessor failed

EDIInboundProcessor fails due to an error in the SQL Query, resulting in no records to update.

This issue arises when there are no records to update; the flow should handle this scenario without failing. Shilpa is currently working on a fix.

Error Type: Transaction/ CustomPlugin failed Error Description: <![CDATA[ (Transaction #1)Error in record : {FLD2=4738, W1STS=20, CMNT5=, CMNT4=na} Error in SQL Query : update "HUSFIL"."OTBEDIF" set CMNT4=?,CMNT5=?,W1STS=? where FLD2 =? No Records to update. ]]>

Shilpa is working on a fix to prevent errors when there are no records to update.

Datamapping failed for ERP_PF_USINT0602_AdeptiaStaging_to_ERP_Mapics

Error : The application requester cannot establish the connection. (Connection timed out: connect)]

To address this, all Publish IDs are fetched to obtain the Event ID for providing a query to reprocess pending parts.

In case of a recurrence, noting down the Publish IDs and fetching the Event ID from Parts monitor to provide a query for execution by Client Implementer is necessary.

UPDATE PLM_ITEMCOMPONENTS_STG Set STATUS = 'I' where eventid in (511879655, 511879669, 511879744,511879788,511879972,511879978,511879989,511880027,511880129,511880246,511880358,511880457,511880496);

Related content

Adeptia Cloud (4.x) Issues and Diagnostics
Adeptia Cloud (4.x) Issues and Diagnostics
Read with this
Karmak - FTP Design and Setup
Karmak - FTP Design and Setup
Read with this
AC Cloud End-To-End Customer Onboarding Process
AC Cloud End-To-End Customer Onboarding Process
Read with this
Troubleshooting Adeptia Connect
Troubleshooting Adeptia Connect
More like this