Dresser MC3 Troubleshooting
- Emma Fullilove (Deactivated)
- ken Halprin
- Adam Haselden
General Troubleshooting
Review the General Troubleshooting page for basic tips and getting help.
Troubleshooting Topics
The following troubleshooting scenarios will continue to expand with each document release.
Scenario #1: Site ID mismatch
Problem: Unable to poll or collect history from device due to invalid Site ID.
Problem - Log Samples
2023/09/07 13:44:07.103,Error,asiDRESSERMC3.2,DRESSERMC3 Protocol1,ValidateDeviceIdentificationTask::ProcessResponse() Site ID mismatch. Expected:HoustonSite , Actual:
2023/09/07 13:44:07.103,Error,asiDRESSERMC3.2,DRESSERMC3 Protocol1,Task ended in error. See previous messages.
2023/09/07 13:44:07.104,Error,asiDRESSERMC3.2,DRESSERMC3 Protocol1,Unable to continue Poll Cycle. Device identification failed.Meaning: The Site ID does not match what the device has assigned.Meaning: The Site ID configured in ACM does not match what the field device has assigned, or ACM is communicating with a different field device.
Corrective Action: Make sure the field device is the correct one you're trying to communicate with. If it is the correct device, correct the Site ID property on the ‘Device' tab. You can find the field device’s Site ID by looking at the 'Actual:' information at the end of the first line of the log. You can also find the Site ID inside the Dresser Fusion Software.
Scenario #2: Serial Number mismatch
Problem: Unable to poll or collect history from the field device due to invalid Serial Number.
Problem - Log Samples
2023/09/07 13:47:32.925,Error,asiDRESSERMC3.2,DRESSERMC3 Protocol1,ValidateDeviceIdentificationTask::ProcessResponse() Serial Number mismatch. Expected:1234abcd , Actual:
2023/09/07 13:47:32.925,Error,asiDRESSERMC3.2,DRESSERMC3 Protocol1,Task ended in error. See previous messages.
2023/09/07 13:47:32.926,Error,asiDRESSERMC3.2,DRESSERMC3 Protocol1,Unable to continue Poll Cycle. Device identification failed.Meaning: The sign-on code used in the sign-on message was rejected by the device.Meaning: The Serial Number configured in ACM does not match what the field device has assigned, or ACM is communicating with a different field device.
Corrective Action: Make sure the field device is the correct one you're trying to communicate with. If it is the correct device, correct the Serial Number property on the 'Device' tab. You can find the correct Serial Number by looking at the 'Actual:' information at the end of the first line of the log. You can also find the Serial Number inside the Dresser Fusion Software.
Scenario #4: No archive object assigned.
Problem: Unable to retrieve history due to no archive object being assigned.
Problem - Log Samples
2023/09/07 13:50:07.679,Error,asiDRESSERMC3.2,DRESSERMC3 Protocol1,Audit log history is enabled, but there is no archive object assigned. Please assign an Archive Limits Object.Meaning: The log that you are trying to retrieve needs to have an Archive Limits object assigned to it in ACM.
Corrective Action: You must create and assign an archive object for each type of history collection. Archive Limit objects can be shared by multiple devices.
Related content
For assistance, please submit a ticket via our Support Portal, email autosol.support@autosoln.com or call 281.286.6017 to speak to a support team member.