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 message prompted.
Possible Reason:
This is due to the “CR Default” (document format name) is used in version 1.9, and in AutoCount 2.0 there is a new document called Consignment Return which is also using “CR Default” as its document numbering format name. When upgrade to 2.0, the system is unable to generate the document format for Consignment Return as the format name exists (and being used) in the system.
Solution:
1) Login to AutoCount 1.9, change the CR Default name. Go to General Maintenance > Document Numbering Format Maintenance, look for the CR Default format, edit and change to CR Default 1.
2) Should you see error message during the change of document format name, it is because the document format has been assign to voucher format of some of the Payment Methods.
Go to General Maintenance > Payment Method Maintenance, temporary change all Document Numbering Format that assigned with “CR Default” to any other Document Numbering Format.
Go back to the Document Numbering Format Maintenance, now you should be able to edit the document numbering format to CR Default 1.
Go back to Payment Method Maintenance and edit the document format to CR Default 1.
3) Now, you may login to AutoCount Accounting 2.0 again and proceed with database upgrade.
--Source from AutoCount Wiki --
Related Articles
A1.113 : Prompted Message: Error during upgrade to 2-Invalid Data Definition Language Statement and ALTER TABLE dbo.ADVQT…Guid
Question: When upgrade database from 1.9 to version 2.0, error message prompted “Invalid Data Definition Language Statement, error message is Column already has a DEFAULT bound to it”. After click OK, another message prompted “ALTER TABLE ...A1.112 : Prompted Message: Error during upgrade to 2.0-The object ‘DF TMCS IPho Recei XXXXXXXX’ is dependent on column ‘ReceiptHeader’
Question: When upgrade AutoCount Version 1.9 to Version 2.0 for user who use iAutoCount, error prompted “Invalid Data Defination Language Statement… The object ‘DF_TMCS_IPho_Recei_XXXXXXXX’ is dependent on column ‘ReceiptHeader’. Why? Possible ...A1.96 : Prompted Message: Error upgrade to 2.0-Unknow Sql Exception… Invalid object name ‘Settings’
Question : When upgrade database from 1.9 to version 2.0, error message prompted: ‘Unkonw Sql Exception (Number=208, Message=Invalid object name ‘Setting’.) Inner Exception Message: Invalid object name ‘Settings’. Why? Possible Reason : This is a ...A1.116 : Prompted Message: Change Item UOM rate error – Invalid object name ‘Sync’
Question: When I change item uom rate, system prompted an error: “Unknown Sql Exception (Number = 208, Message = Invalid object name ‘Sync’.). Why? Possible Reason: The registry value failed to upgrade properly when upgrading the database. Solution: ...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 ...