PIA
Assumptions
The engineer has a good working knowledge of the PIA solution
General
If you are experiencing problems, tick off the following questions and check as appropriate.
NOTE: PIA is shares many of the same processes as EDD and EDM, so it's a good idea to tick those off as well.
If having satisifed them and you are still having issues, contact the
V1 Support Team with details of the issue.
Have you checked the log files?
The
Administration > Logs (section on PIA) gives you details on all logs and in most circumstances tell you one way or the other what the problem is.
PIA with DbCapture
Does the Sage installation meet the minimum Patch requirements for compatibility?
Although thoroughly tested, V1 cannot guarentee with 100% certainly a Sage X3 patch will be compatible, but given EDM is very 'light touch', it's unlikely you will have issues.
Has the Implement PIA with DbCapture section been followed in full?
Is the X3EDM!ENDPOINTNAME! ClassicPool running?
This is the gateway allowing V1 to access to Sage X3. If it's not running / has stalled / Syracuse has been updated / any changes made to V1 web-services, it will need restarting.
Have the Endpoints been patched for PIA?
The best way to check is to log in to Sage, go to Development > Scripts > Web Services (GESAWS). Filter for those beginning XV1. If you see them, (such as XV1OCRPIH) you've patched.
Are your DbLogin users uppercase, assigned their licences, access and email addresses assigned?
Is the DbArchive.DBA__FILTER_MAP SQL table populated?
Either using the setup program or using the FilterMapMaintenance addon, if this is empty / wrong, no users will be able to use PIA with DbCapture.
Are the settings in \V1\DbCapture\V1_SETTINGS_DBCAPTURE.def correct?
This include file is shared across all OCR activity. If any value is wrong / has been changed since it was originally implemented, it will result in connectivity and accessibility error messages. Any changes made to this file are immediately applied, so no need to restart any services.