Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database load error ICXLHIS

Status
Not open for further replies.

kk4765

Technical User
May 16, 2015
3
AE
Hi,

We are trying to load database and it fails. Getting the following error while processing ICXLHIS

error = 0
native code = -1677721600

SAGE 300 ERP ACCPAC with PU3
Database MSSQL 2008 R2

Extra info:
collation order: Arabic_CI_AS
Recovery model: Simple
Database Autogrowth for MDF file is: By 1 MB, unrestricted growth

Total records we see in ICXLHIS table when the load fails is 197000 and in the original database total records are 197172. I verified there are no corrupt data in the original database

Initially had the load error on ICUNIT table and fixed the duplicate unit codes due to insensitive data. Then ICUNIT table was passed during the load. Now the error is in ICXLHIS.

Any help and guidance is highly appreciated.
 
Hi ettienne!

Yes changing the collation from Latin1_General_Bin to Arabic_CI_AS. Initially had the load error on ICUNIT table and fixed the duplicate unit codes due to insensitive data. Then ICUNIT table was passed during the load. Now the error is in ICXLHIS.

Total records we see in ICXLHIS table where the load fails is 197000 and in the original database total records are 197172. I verified there are no corrupt data in the original database near 197000.

What else could be wrong?
 
You're repeating yourself.
Check the original ICXLHIS table around records 197000.
Run SQL query analyzer while you load the data, maybe something shows there. Check the SQL query when the load fails.

Sage 300 ERP Certified Consultant
 
Hi ettienne,

Thank you for your prompt reply. I tried to only check the old database table versus whatever was written on the new database table at the time of fail, and couldn't find any corrupted record.

Sorry for my limited knowledge but I am not sure how I run Query Analyzer to investigate. Do you mean to run SQL Server Profiler? Please advise.

Does native code = -1677721600 gives any clue?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top