Difference between revisions of "SOP-42Q PCB Troubleshooting Guide"
Jump to navigation
Jump to search
Tools PCB Troubleshooting Version MES15.3.3 Portal 1.0
(One intermediate revision by the same user not shown) | |||
Line 7: | Line 7: | ||
| | ||
− | <center>'''Tools'''</center> <center>'''PCB Troubleshooting'''</center> <center>'''Version MES15.3.3 Portal 1.0'''</center> <center> | + | <center>'''Tools'''</center> <center>'''PCB Troubleshooting'''</center> <center>'''Version MES15.3.3 Portal 1.0'''</center> <center> </center> <center> </center> |
− | |||
− | <center> </center> | ||
{| border="2px" cellpadding="4" cellspacing="0" width="100%" | {| border="2px" cellpadding="4" cellspacing="0" width="100%" | ||
|- | |- |
Latest revision as of 20:54, 14 October 2021
42Q Home > Tools > PCB Troubleshooting Guide
Error Message |
Scenario / Root cause | Suggested actions | Plant Support | MES Support | Developer Support |
42Q APK - Connection Related | |||||
42Q database network connection error! | Connection error with MDS | Check Portal network connection by under same network connection that used in Android (by Plant). | |||
SFDC network connection error! | Connection error with SFDC PC | Check network connection between Portal & SFDC (by Corporate Network/MES Support team). | |||
SFDC services connection error! | Connection error with SFDC PC | Check network connection between Portal & SFDC (by Corporate Network/MES Support team). | |||
MES Portal services connection error! | Connection error with MES Portal | Check network connection between Portal & SFDC (by Corporate Network/MES Support team). | |||
Invalid parameter(s) that returned from MES Portal! | Connection error with MES Portal | Check sfdc-portlet version and Device Maintenance Configuration (by Corporate Network/MES Support team). | |||
Invalid parameter(s) that returned from SFDC! | Connection error with SFDC | Check SFDC PC version (by Corporate Network/MES Support team). | |||
Check your SFDC HOST. | SFDC Host IP error |
Check Options of SFDC at Data Editor: |
|||
Loading SFDC settings from 42Q. | Waiting Message for loading SFDC | Wait until Reloading Button enabled | |||
Establishing 42Q network connection! | Waiting Message for connecting SFDC | Wait until Setting Button enabled | |||
Fail to load Device Maintenance from 42Q. | Waiting Message for loading device maintenance configuaration | Check Device Maintenance portlet at MES Portal to see if Device Type = Android (by Plant). | |||
"Invalid parameter(s) that returned from SFDC!" | 42Q apk 1.12 | Missing to upgrade MES portal with "mes15_sfdc-webservice-1.11.8.160309-1 or higher version" | |||
System busy | 2 or more request before the PC responds / slow connection or network | ||||
42Q APK - PCB Related | |||||
Invalid Work Order! Try again please! | No work order information from MDS | Check Shop Order status under Shop Order Control (by Plant). | Raise SR to release Work Order | ||
Invalid !!2 Command Mode! Try again please! | No command from MDS | Check !!2 Command (by Plant). | |||
Error: The system cannot find the Work Order specified. | No work order information from MDS | Check Shop Order status under Shop Order Control (by Plant). | |||
The system cannot find the PCB instruction specified. | Travler XML retrieving failed | Check Travaler Status for the Shop Order (by Plant). | |||
Invalid parameter(s) that returned from InPlan Traveler XML! | Travler XML does not return valid information | Check Travaler Status for the Shop Order (by Plant). | |||
No route equivalence found for work order | No assigned route from MDS side | Inplan RTGEQUIVID number is different between Oracle Work order and MES, it needs to be re-reported from Inplan system | |||
APK display error : "No traveler found compatible with route equivalence: "396515" " |
Inplan Traveler XML file does not exist for the Part number, or/and Inplan traveler XML file does not exist for that Rtgequivid(oracle_route_id) |
Review if the XML file does not exist in MES as processed or as failed, else verify that the files are being transfer from the PCB FTP, else report to the Inplan team. Note. For further troubleshoot details please review this document : |
x |
x |
x |
PCB troubleshoot error not printing traveler | |||||
MES AUTO process | |||||
Auto-Print label, print label and APK display error : : "No traveler found compatible with route equivalence: "396515" " |
Inplan Traveler XML file does not exist for the Part number, or/and Inplan traveler XML file does not exist for that Rtgequivid(oracle_route_id) |
Review if the XML file does not exist in MES as processed or as failed, else verify that the files are being transfer from the PCB FTP, else report to the Inplan team. Note. For further troubleshoot details please review this document : |
x |
x |
x |
PCB troubleshoot error not printing traveler | |||||
Appgarden (Air-Deployment) Related | |||||
Parse Error: There was a problem parsing the package. | Installation packages download stops by accident | Cancel the Task at portlet to stop the error message Go to AppGarden by clicking the icon Click button Delete Installation files. Reschedule the air-deployment task. |