POS Sync Common Issue

Home » POS » POS Sync Common Issue
POS No Comments

Issue

Application Error 1: “Outlet xxx does not have DB Sync. Return value is null. Please insert POS dongle USB Key first”.

possync1

Solution: Check at workstation computer (branch) whether got plugged in the dongle and make sure got DB sync module.

 

Application Error 2: “Failed to get valid DB Sync license. Please register your POS license”.

possync2

Solution: Make sure the account book at server side are registered.

 

Application Error 3: “The process cannot access the file C:\WINDOWS\TEMP\xxx.dll’ because it is being used by another process”.

syncerror1

Starting from Date 30/9/2014, seems that Avast Antivirus Program had updated their system and attempt to block AutoCount POS Sync. Error might prompt out such as above screenshot.

syncerror2

Solution: In order to avoid this, need to add the exception for the specific folder from being scanned by Avast, follow these steps.

  1. Open the Avast user interface and go to ‘Settings‘ » ‘General
  2. Find the tab ‘EXCLUSIONS‘ and add specific folder.

 

Application Error 4: “Load Module License fails. (Result = RemoteUSBKeyNotFoundError)”.

possync3

possync4

Solution: Go to Tools–>Program Control–>License Control–>Controlled by USB Key–>Put the server hamachi IP address at Remote USB Key.

 

Application Error 5: “HQ POS Sync version number 3.0.x is not match with sync client version number 3.0.x at terminal xx”.

possync5

Solution: Make sure the program version (major number, minor number and build number) are same between server and outlet.
Example: Server version=3.0.10.81, Outlet version=3.0.9.78 (Sync are not allowed)
Server version=3.0.10.81, Outlet version=3.0.10.80 (Sync are allowed)

 

Application Error 6: “Check outlet to HQ connection failed. Unable direct sql server connection from outlet xxx to HQ”.

possync7

possync8

Solution: Make sure server IP is put hamachi IP address instead of local IP address.

 

Application Error 7: “There is an error in XML document”.

possync10
Possible Causes:

  1. Carriage Return “\r”
  2. Line Feed “\n”
  3. Invalid Character “hexadecimal value 0x1E” possync12
possync11

Solution: Go to Backend AutoCount POS Sync–>DB Sync–>SQL Query–>Select table (You need see the error message stop at which table)–>Press Check XML Error.

 

Application Error 8: “Please make sure current Port No ’19318′ is not using by others program / other sync profile and Auto Sync is turn off”.

possync16

possync17

Solution: Make sure HQ Remoting Port is different in each sync profile. (Can use 19318, 19317, 19316 and below or 19320, 19321, 19322 and above)

 

Application Error 9: “SqlException: Internal Query Processor Error: The query processor encountered an unexpected error during execution”.

Solution: Run DBCC Repair

 

Resetting Winsock Catalog and Solving Network Problem

netsh winsock reset is useful command that you can use in Microsoft Windows to reset winsock catalog back to default setting or clean state. You can try this if you are having following Internet access or networking problems but still failing to resolve the problem after trying all other suggestions.

  1. Internet or network problem after removing the adware, spyware, virus, worm, trojan horse, etc.
  2. Loss network connection after installing/uninstalling adware, spyware, antispam, vpn, firewall or other networking programs.
  3. Unable to access any webpage or can only access some webpages.
  4. Pop-up error window with network related problem description.
  5. No network connectivity due to registry errors.
  6. DNS lookup problem.
  7. Fail to renew the network adapter’s IP address or other DHCP errors.
  8. Network connectivity issue with limited or no connections message.
  9. Other networking problems.

Solution: Here is the way you can launch command prompt after logging in as administrator.

  1. Go to Start -> All Programs -> Accessories
  2. Right-click on Command Prompt and click Run as administrator
  3. possync13

  4. Type netsh winsock reset in command prompt and hit ENTER button
  5. possync14

  6. Restart the computer in order to complete the reset, after that test to access your network or Internet again.

 

How To Repair A Suspect Database In MS SQL

Possible Causes:

  1. The database could have become corrupted.
  2. There is not enough space available for the SQL Server to recover the database during startup.
  3. The database cannot be opened due to inaccessible files or insufficient memory or disk space.
  4. The database files are being held by operating system, third party backup software etc.
  5. There was an unexpected SQL Server Shutdown, power failure or a hardware failure.

Solution: These steps require you to have Microsoft SQL Server Management Studio installed on your computer.

  1. Open Microsoft SQL Server Management Studio and connect to your database
  2. Click the New Query button
  3. Paste the following SQL script into your New Query page replacing [YourDatabase] with the name of your database.
  4. possync15

  5. Click Execute