A1.130 : Login Issue: Primary Key Error when login
Question: When I try to login an account book which was upgraded from 1.9 to 2.0, system prompted “Primary Key Error”. Why?
Possible Reason:
The registry value failed to upgrade properly when upgrading the database.
Solution:
1) Search and open SQL Management Studio from window search.
2) Connect SQL Server Management Studio.
3) Click on the database name that failed to login and Execute the below query:
update Registry set RegValue='2.13' where regid=0x4
Now, you may login to AutoCount.
--Source from AutoCount Wiki --
Related Articles
A1.127 : Login Issue: Login Error - Could not load type 'HQService.IHQService' from assembly
Question: After I updated to version 2.0.28.196 and login AutoCount, system prompted unhandled application error “Could not load type 'HQService.IHQService' from assembly”. When I closed the error, AutoCount will end task. Why? Possible Reason : This ...A1.117 : Prompted Message: Error during upgrade to 2.0-Invalid Data Definition Language Statement, error message is Violation of PRIMARY KEY constraint … The duplicate key value is (CR Default)
Question: When upgrade database from 1.9 to 2.0, error message prompted “Invalid Data Definition Language Statement, error message is Violation of PRMIARY KEY constraint … The duplicate key value is (CR Default). Why? After clicking OK, another ...A1.126 : Login Issue: Login Error – This account book didn’t have any account edition
Question: When I login an account book in AutoCount 2.0, the system prompted error “This account book didn’t have any account edition”. Why? Possible Reason : Your account book is registered under Product ID with POS edition only, does not have ...A1.125 : Login Issue: Login Error – The underlying connection was closed: The connection was closed unexpectedly
Question: When I login to AutoCount Ver 2.0, the system prompts an error message “The underlying connection was closed: The connection was closed unexpectedly”. The AutoCount Server cannot start, error “Time out has expired..”. Why? Possible Reason : ...A1.123 : Login Issue: Login error – There was no endpoint listening at …
Question : When I login to AutoCount Ver 2.0, system prompted error message “There was no enpoint listening at….” Why? Possible Reason : You’ve not yet installed AutoCount Server at your Server or the service did not start. Solution : If the ...