How Syncing Works
MAS to JOScan:
- The “JOScan Sync Timer” service on the server handles the Pulling of data from MAS into JOScan at regular intervals, as set in JOScan > Settings > Auto-sync Tables > Server Configs.
- If “Interval Type” is set to Hour, it will always sync once every hour. Otherwise, set it to “Time”, then enter the number of minutes in “Interval Option”. We suggest going no less than 15 minutes at first. Leave “Time Between Syncs” at 5.
- Note: After making changes on this screen, the “JOScan Sync Timer” service on the server will need to be restarted before they take effect.
Every 20 minutes:
- If this service isn’t running, data can be manually pulled by opening a JOScan client and clicking the little green icon in bottom right corner.
- Direct Connect clients (in general, desktops) will then see that new data right away.
- Sync Mode clients (Windows Mobile Devices, Apple Devices, and some older desktop clients) then individually sync with the JOScan database. Please note the different ways to sync:
- When you first launch JOScan, it begins an auto-sync behind the scenes. Eventually it will come back with a message saying success or fail.
- After that the auto-sync runs at regular intervals as set in JOScan > Settings > General > Pull Sleep time (format: hh:mm:ss)
- Manual Syncing: big green icon in the center of the screen.
JOScan to MAS:
- Sync mode clients need to push their collected data to the JOScan database. This is performed using the SyncServices web service on the server.
- Direct Connect clients store their data right in the database.
- From here there are different options:
- Data is then ready to be extracted using the Extract Util (older versions).
- Data gets manually reviewed and processed in JOScan, then extracted using the Extract Util.
- Data is auto-processed (using SyncTimer service) then extracted using the Extract Util.
- Note: In newer versions of JOScan, there is not a separate utility for extracting, but happens automatically at time of processing.
- During extraction, a data file is created. If you use the Extract Util, there is a link to set this path at the top of the window. For new versions, this is set at JOScan > Settings > General > Extract.
- Then import data into MAS by running Data Collector.
If you are experiencing issues where data is not syncing properly, determine at what point the problem is occurring using the explanations above. Then follow
- Restart the "SQL Server (JOSCAN)" service - If there are other databases in that instance, make sure it is okay with your IT before restart the database. This step clears up many issues.
- If the service won't start, make sure the Logon info in the service properties is using a valid admin credentials.
- Check Database Services
- "SQL Server (JOSCAN)" – needs to be running
- "SQL Server Browser" – needs to be running
- "SQL Server Agent (JOSCAN)" – does NOT need to be running
- The JOScan client log files are helpful for finding sync issues.
- On desktops they are at C:\JOScan\logs
- On mobiles, they are generally at "\JOScan\logs", but may also be in "Program Files\MobileClient\logs", or on an SD card.
- SyncTimer Service
- Restart the service "JOScan Sync Timer" – Note: normal operations may not resume until the top of the next hour after restarting this service. In the meantime, manual syncing can be used if necessary.
- Log file is at C:\JOScan\SyncTimer\log.txt
- Some older versions don't have this service.
- SyncServices Web Service
- Make sure IIS is still running
- Grab a URL from JOScan > Settings > General and see if it comes up in a web browser. You should get a page that says "you have created a service".
- Log files generally get saved in the C:\JOScan folder, and have SyncServices in the name.
- If you need assistance, please provide us with as much information as possible:
- Please send us relevant log files
- At what point in the sync process is the problem?
- What troubleshooting steps have you taken, and what was the results?
- When exactly did the problem start occurring? What else happened around that time? Server reboot? Network issues?