Finance | Project Operations, Human Resources, ...

On-premise deployment fails DB synchronization

(0) Share

Report

Posted on by Community Member

Whenever we deploy a new package we get the following error on line tables such Sales line, Purchase line:

Input string was not in correct format

Our developers found a work around. They move the Sandbox DB to Dev machine, sync it and move it back to Sandbox and Sync again using Visual studio. This removes the error.

I there any solution to this issue?

I have the same question (0)

All responses (12)

Answers (0)

Gunjan Bhattachayya 35,423 on at

Like (0)

Report

Hi,

Can you check the .NET version installed on Sandbox? Might be it is a higher version. If you have a Prod environment, you can check the version on that server as well.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

It's 4.5.1 on sandbox.

Was this reply helpful? Yes No
Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi AR01,

Do you have the same regional setting for the environment administrator account in dev and sandbox? I remember there were some issues when the date format causes sync issues if it's not in en-us format.

Was this reply helpful? Yes No
Suggested answer

Luke Sha on at

Like (0)

Report

It's better to attach DB sync log here.

Please noted Only SQL_Latin1_General_CP1_CI_AS is valid for the server and database collation.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Luke Sha,

Database collation is the same as you mentioned. Where can I find the DB sync logs in my environment?

Thanks

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Sergei Minozhenko,

The regional setting in en-us format in both machines. Also this doesn't after "moving DB from sandbox to Dev then back to Sandbox" which solves the issue.

Was this reply helpful? Yes No
Luke Sha on at

Like (0)

Report

Did issue resolved now? you may find DBSync event log in the AOS server -> Event Viewer -> Application and service -> Microsoft -> Dynamics -> AX - DatabaseSynchronize.

And I suggest you to submit a ticket to Microsoft, then our engineer can have a remote session to check issue with you together.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

20200915AOS1_2D00_DBSync_2D00_Log.zip

The issue isn't fixed yet. I am not 100% sure but I don't see any issue in logs(attached).

Thanks for your suggestion, I hope opening a support ticket would help.

Was this reply helpful? Yes No
Luke Sha on at

Like (0)

Report

Thanks for the log. The log show DB sync is completed successfully.

Where did you see the error? Which step? If package is deployed successfully but user met issue when they open the form. We need more logs for troubleshooting.

If issue can be reproduced stably, we definitely will find the root cause.

Was this reply helpful? Yes No
Touqeer460 10 on at

Like (0)

Report
Input_5F00_string.zip

Which logs do you require? I have attached the trace parcer logs.

Issue:

Whenever we deploy a new package we get the following error on line tables such Sales line, Purchase line:

"Input string was not in correct format"

Our developers found a work around. They move the Sandbox DB to Dev machine, sync it and move it back to Sandbox and Sync again using Visual studio after deployment. This removes the error.

Other than that, the following fields needs to be deleted from SQL server AXDB database (Sandbox on-premise environment) for the successful deployment of the package otherwise it fails while updating environment from LCS.

RUNFULLSYNCONTERMINALUPGRADE from RETAILTERMINALTABLE

SplitPayment_W from CUSTPAYMMODETABLE

Steps to reproduce:

Create a sales order.

Add sales line.

Select item, add price, qty etc.

And save.

Error occurs.

Was this reply helpful? Yes No