web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

I am encountering an issue with the ASIEXP81 table when upgrading to Microsoft Dynamics GP 2013 R2: "The stored procedure SynchronizeTableData() of form duSQLAccountSynch : 27Pass Through SQL returned the following results: DBMS: 515, Microsoft Dynami

(0) ShareShare
ReportReport
Posted on by 10

I am encountering an issue with the ASIEXP81 table when upgrading to Microsoft Dynamics GP 2013 R2:
"The stored procedure SynchronizeTableData() of form duSQLAccountSynch : 27Pass Through SQL returned the following results: DBMS: 515, Microsoft Dynamics GP: 0.6545.Capture.PNG

Categories:
I have the same question (0)
  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Hi Raju,

    Have you checked Microsoft's blog about GP upgrade issues ?

    community.dynamics.com/.../microsoft-dynamics-gp-2018-r2-and-year-end-upgrade-known-upgrade-issues

    And this blog post could likely help you narrow down the problem:

    www.gpug.com/.../upgrade-issues-when-upgrading-to-microsoft-dynamic

  • Raju Jogi12 Profile Picture
    10 on at

    Hi Beat Buche,

    Yes, I tried this but not worked.

    IF you have anything specific to fix this issue lease help.

    Your help really appreciated.

    Thank

  • Suggested answer
    Derek Albaugh Profile Picture
    on at

    We'd actually need to run a dexsql.log to capture this error message to see what exactly is going on.

    DBMS: 515 is a SQL error basically stating that we cannot insert the value NULL into column XXXXX.

    I've seen this type of error occur also if the table is having data populated into it, which the ASIEXP81 would, being it is the SmartList Favorite Master table, thus would have all default SmartList reports and favorites in it, but the table is missing the primary key and/or indexes, things like that.

    The other thing to remember with the ASIEXP81 table is, it is the only table in the GP system database that gets setup with a specific number of columns, to correspond with the account framework maximums settings, as shown in the SY003001 and SY00302 tables.

    Because of this, it wouldn't hurt to set SYNCHRONIZE=TRUE in the Dex.ini file, of the GP directory you're launching GP Utilities from, and then see if this resolves the error or not, by re-synchronizing the dictionary files with the account framework settings.

    Thanks

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 611 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 529 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 285 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans