Difference between revisions of "SOP-42Q PCB Troubleshooting Guide"

From 42Q
Jump to navigation Jump to search
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  
−
<small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[Tools|Tools]] > PCB Troubleshooting Guide</small><br/> [[File:42Q Logo.jpg|RTENOTITLE]]
+
<small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[Tools|Tools]] > PCB Troubleshooting Guide</small><br/> &nbsp;
  
 
&nbsp;
 
&nbsp;
Line 7: Line 7:
  
 
&nbsp;
 
&nbsp;
−
<center>'''Tools'''</center> <center>'''PCB Troubleshooting'''</center> <center>'''Version MES15.3.3 Portal 1.0'''</center> <center>'''Work Instruction&nbsp;'''</center>  
+
<center>'''Tools'''</center> <center>'''PCB Troubleshooting'''</center> <center>'''Version MES15.3.3 Portal 1.0'''</center> <center>&nbsp;</center> <center>&nbsp;</center>  
−
&nbsp;
+
{| border="2px" cellpadding="4" cellspacing="0" width="100%"
−
<center>This Work Instruction is 42Q's corporate standard.</center> <center>This document is under revision control. The latest revision is located on Intranet.</center> <center>Once printed it is an uncontrolled copy. All alterations to this work instruction require approval.</center> <center>Contact the IT Global Education and Training Department to submit suggested alterations and or updates.</center>  
+
|-
−
''This edition applies to MES15 Portal 1.10 and all subsequent releases and modifications until otherwise indicated in new revisions.''
+
| style="background:#ADD8E6" |
−
 
+
'''Error Message'''
−
&nbsp;
 
  
−
{| border="1" cellpadding="0" cellspacing="0" dir="ltr"
+
| style="background:#ADD8E6" | '''Scenario / Root cause'''
 +
| style="background:#ADD8E6" | '''Suggested actions'''
 +
| style="background:#ADD8E6" | '''Plant Support'''
 +
| style="background:#ADD8E6" | '''MES Support'''
 +
| style="background:#ADD8E6" | '''Developer Support'''
 
|-
 
|-
−
| data-sheets-value="{" | Error Message
+
| style="background:yellow" | 42Q APK - Connection Related
−
| data-sheets-value="{" | Scenario / Root cause
+
| style="background:yellow" | &nbsp;
−
| data-sheets-value="{" | Suggested actions
+
| style="background:yellow" | &nbsp;
−
| data-sheets-value="{" | Plant Support
+
| style="background:yellow" | &nbsp;
−
| data-sheets-value="{" | MES Support
+
| style="background:yellow" | &nbsp;
−
| data-sheets-value="{" | Developer Support
+
| style="background:yellow" | &nbsp;
 
|-
 
|-
−
| data-sheets-value="{" | Cirrus APK - Connection Related
+
| data-sheets-value="{" | 42Q database network connection error!
−
| &nbsp;
 
−
| &nbsp;
 
−
| &nbsp;
 
−
| &nbsp;
 
−
| &nbsp;
 
−
|-
 
−
| data-sheets-value="{" | Cirrus database network connection error!
 
 
| data-sheets-value="{" | Connection error with MDS
 
| data-sheets-value="{" | Connection error with MDS
 
| data-sheets-value="{" | Check Portal network connection by under same network connection that used in Android (by Plant).
 
| data-sheets-value="{" | Check Portal network connection by under same network connection that used in Android (by Plant).
Line 74: Line 70:
 
| data-sheets-value="{" | Check your SFDC HOST.
 
| data-sheets-value="{" | Check your SFDC HOST.
 
| data-sheets-value="{" | SFDC Host IP error
 
| data-sheets-value="{" | SFDC Host IP error
−
| data-sheets-value="{" | Check Options of SFDC at Data Editor:<br/> OPTIONS URL_WEB_SERVICE NAME=EMANUAL_URL_INTERNAL VALUE=[http://10.180.1.12 http://10.180.1.12]
+
| data-sheets-value="{" |  
 +
Check Options of SFDC at Data Editor:<br/> OPTIONS URL_WEB_SERVICE NAME=EMANUAL_URL_INTERNAL VALUE=
 +
 
 
| &nbsp;
 
| &nbsp;
 
| &nbsp;
 
| &nbsp;
 
| &nbsp;
 
| &nbsp;
 
|-
 
|-
−
| data-sheets-value="{" | Loading SFDC settings from Cirrus.
+
| data-sheets-value="{" | Loading SFDC settings from 42Q.
 
| data-sheets-value="{" | Waiting Message for loading SFDC
 
| data-sheets-value="{" | Waiting Message for loading SFDC
 
| data-sheets-value="{" | Wait until Reloading Button enabled
 
| data-sheets-value="{" | Wait until Reloading Button enabled
Line 86: Line 84:
 
| &nbsp;
 
| &nbsp;
 
|-
 
|-
−
| data-sheets-value="{" | Establishing Cirrus network connection!
+
| data-sheets-value="{" | Establishing 42Q network connection!
 
| data-sheets-value="{" | Waiting Message for connecting SFDC
 
| data-sheets-value="{" | Waiting Message for connecting SFDC
 
| data-sheets-value="{" | Wait until Setting Button enabled
 
| data-sheets-value="{" | Wait until Setting Button enabled
Line 93: Line 91:
 
| &nbsp;
 
| &nbsp;
 
|-
 
|-
−
| data-sheets-value="{" | Fail to load Device Maintenance from Cirrus.
+
| data-sheets-value="{" | Fail to load Device Maintenance from 42Q.
 
| data-sheets-value="{" | Waiting Message for loading device maintenance configuaration
 
| data-sheets-value="{" | Waiting Message for loading device maintenance configuaration
 
| data-sheets-value="{" | Check Device Maintenance portlet at MES Portal to see if Device Type = Android (by Plant).
 
| data-sheets-value="{" | Check Device Maintenance portlet at MES Portal to see if Device Type = Android (by Plant).
Line 101: Line 99:
 
|-
 
|-
 
| data-sheets-value="{" | "Invalid parameter(s) that returned from SFDC!"
 
| data-sheets-value="{" | "Invalid parameter(s) that returned from SFDC!"
−
| data-sheets-value="{" | Cirrus apk 1.12
+
| data-sheets-value="{" | 42Q apk 1.12
 
| data-sheets-value="{" | Missing to upgrade MES portal with "mes15_sfdc-webservice-1.11.8.160309-1 or higher version"
 
| data-sheets-value="{" | Missing to upgrade MES portal with "mes15_sfdc-webservice-1.11.8.160309-1 or higher version"
 
| &nbsp;
 
| &nbsp;
Line 110: Line 108:
 
| data-sheets-value="{" | 2 or more request before the PC responds / slow connection or network
 
| data-sheets-value="{" | 2 or more request before the PC responds / slow connection or network
 
| &nbsp;
 
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| style="background:yellow" | 42Q APK - PCB Related
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
|-
 +
| data-sheets-value="{" | Invalid Work Order! Try again please!
 +
| data-sheets-value="{" | No work order information from MDS
 +
| data-sheets-value="{" | Check Shop Order status under Shop Order Control (by Plant).
 +
| data-sheets-value="{" | Raise SR to release Work Order
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| data-sheets-value="{" | Invalid&nbsp;!!2 Command Mode! Try again please!
 +
| data-sheets-value="{" | No command from MDS
 +
| data-sheets-value="{" | Check&nbsp;!!2 Command (by Plant).
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| data-sheets-value="{" | Error: The system cannot find the Work Order specified.
 +
| data-sheets-value="{" | No work order information from MDS
 +
| data-sheets-value="{" | Check Shop Order status under Shop Order Control (by Plant).
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| data-sheets-value="{" | The system cannot find the PCB instruction specified.
 +
| data-sheets-value="{" | Travler XML retrieving failed
 +
| data-sheets-value="{" | Check Travaler Status for the Shop Order (by Plant).
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| data-sheets-value="{" | Invalid parameter(s) that returned from InPlan Traveler XML!
 +
| data-sheets-value="{" | Travler XML does not return valid information
 +
| data-sheets-value="{" | Check Travaler Status for the Shop Order (by Plant).
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| data-sheets-value="{" | No route equivalence found for work order
 +
| data-sheets-value="{" | No assigned route from MDS side
 +
| data-sheets-value="{" | Inplan RTGEQUIVID number is different between Oracle Work order and MES, it needs to be re-reported from Inplan system
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
APK display error&nbsp;: "No traveler found compatible with route equivalence: "396515" "
 +
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
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)
 +
 +
| data-sheets-value="{" | 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.<br/> Note. For further troubleshoot details please review this document&nbsp;:
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
x
 +
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
x
 +
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
x
 +
 +
|-
 +
| data-sheets-formula="=HYPERLINK(" data-sheets-value="{" | PCB troubleshoot error not printing traveler
 +
|-
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| style="background:yellow" | MES AUTO process
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
|-
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
Auto-Print label, print label and APK display error&nbsp;:&nbsp;: "No traveler found compatible with route equivalence: "396515" "
 +
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
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)
 +
 +
| data-sheets-value="{" | 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.<br/> Note. For further troubleshoot details please review this document&nbsp;:
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
x
 +
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
x
 +
 +
| colspan="1" data-sheets-value="{" rowspan="2" |
 +
x
 +
 +
|-
 +
| data-sheets-formula="=HYPERLINK(" data-sheets-value="{" | PCB troubleshoot error not printing traveler
 +
|-
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|-
 +
| style="background:yellow" | Appgarden (Air-Deployment) Related
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
| style="background:yellow" | &nbsp;
 +
|-
 +
| data-sheets-value="{" | Parse Error: There was a problem parsing the package.
 +
| data-sheets-value="{" | Installation packages download stops by accident
 +
| data-sheets-value="{" | Cancel the Task at portlet to stop the error message<br/> Go to AppGarden by clicking the icon<br/> Click button Delete Installation files.<br/> Reschedule the air-deployment task.
 
| &nbsp;
 
| &nbsp;
 
| &nbsp;
 
| &nbsp;
 
| &nbsp;
 
| &nbsp;
 
|}
 
|}
−
 
−
&nbsp;
 

Latest revision as of 20:54, 14 October 2021

42Q Home > Tools > PCB Troubleshooting Guide
 

 

 

 

Tools
PCB Troubleshooting
Version MES15.3.3 Portal 1.0
 
 

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:
OPTIONS URL_WEB_SERVICE NAME=EMANUAL_URL_INTERNAL VALUE=

     
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. 		     
Retrieved from "https://42qrpt1.42-q.com/mes_wiki/index.php?title=SOP-42Q_PCB_Troubleshooting_Guide&oldid=40098"