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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Cash Reciepts Error - ...
Microsoft Dynamics GP (Archived)

Cash Reciepts Error - Get Change on table doSetup

(0) ShareShare
ReportReport
Posted on by Bill Campbell 12

There are a number of postings that talk about Credit Card Authorization and Online Services but I found a good posting at 

https://community.dynamics.com/gp/b/gprosesolutions/archive/2011/03/29/docreditcardauthorizationactivity-error.aspx

However, there is one major piece that I did not find here and it was related to the solution as posted.

If all you do is goto Microsoft Dynamics GP > Tools > Customization > Customization Maintenance you will be frustrated as you really need to got to Microsoft Dynamics GP > Tools > Customization > Customization Status


However, if you only do this, it will not work.  You have to complete the removal of the Online Services completely from the system.

Remove lines in the Dynamics.set and DynUtil.set related to the 6449 Dictionary, both above the Windows line, and the 3 lines below, and remember to set the counter at the top of the file to Number-1.

Next, you have to remove the .dll files from the GP folder.  The critical one is from the Addins folder - and is the GP Online Services dll

Found that if I did everything else, but not this last step, nothing mattered.

*This post is locked for comments

I have the same question (0)
  • Bill Campbell Profile Picture
    Bill Campbell 12 on at

    So this was posted more of a response to a blog - not sure if it is in the right place - but I think others encountering this message need some additional information.

  • Derek Albaugh Profile Picture
    Derek Albaugh on at

    Hello Bill,

    I wanted to respond to this to mention that we actually do not want to remove Dynamics Online Services (6499) as it is a core module/feature that gets installed anytime you install Dynamics GP 10.0 SP5 or later and there are actually other processes, such as Sales Order Processing, that will look at DO tables for this feature during the processing. If those tables are not there or not updated to the correct structure, it can cause other issues.

    If you don't have this feature in the DynUtils.set file, it won't get upgraded to a higher version or build and that can cause other issues as well.

    Regarding the blog you mentioned, while the author does mention disabling this feature, later in the blog he mentions they used SQL Maintenance to recreate the tables and stored procedures for Dynamics Online Services, which would be what you'd want to do if you don't actually use this feature and there isn't any data in the DO tables.

    Thanks

  • Bill Campbell Profile Picture
    Bill Campbell 12 on at

    Ok Derek, I understand that I was responding to the content of the Blog and may have missed the recreate section - but I have a problem with this module when it causes these types of errors - is that related to 'as you pointed out - not properly updated' tables.

  • Verified answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at

    From our experience, that is usually what we run into. Customers don't use Dynamics Online Services so they will remove it from the Dynamics.set, DynUtils.set files so it's not loaded when the Dynamics GP application is loaded, which is the equivalent of putting a Band-Aid on the issue instead of fixing it.

    What we find is that it is mainly a table not having been updated or dexterity procedure, etc. that is causing the issue.

    What we usually do is put Dynamics Online Services back into the .set files as well as the dictionary files and AddIns, then run the following scripts to re-initialize this module to the new or current version, which normally resolves the issues, as all objects get dropped and re-created at the new/current version:

    To re-initialize Dynamics Online Services for the all Dynamics GP databases, use the following scripts:

    1. Update DYNAMICS..DB_Upgrade set db_verOldMajor=0, db_verOldBuild=0, db_status = 0 where PRODID = 6499

    2. Delete DYNAMICS..DU000020 where PRODID = 6499

    3. Delete DYNAMICS..DU000030 where PRODID = 6499

    >>Run this script against each and every company database that shows in the DYNAMICS..SY01500 table:

        DROP TABLE DO03100

    >>Run this script against the DYNAMICS system database as well:

        DROP TABLE DO40100

    Re-initializing Dynamics Online Services feature for a database or all databases will completely drop and re-create all objects, meaning that all tables will lose any data in them, so we want to make sure that this feature has never been used in the companies, or that we don't need the data contained within these objects, before we run these scripts to re-initialize.

    Thanks

  • Verified answer
    Bill Campbell Profile Picture
    Bill Campbell 12 on at

    Derek, as a follow up to this matter.

    I just encountered this on a client that has never used the Dynamics Online Services, never used Credit Card and has never put any data into these tables.

    He was opening the Cash Receipts table for a recently updated - Service Pack appliction - of GP2010 and encountered this error message.

    Before calling me he went into Maintenance >> SQL >> Selected Dynamics Online Services and DROP / RECREATE the DO Setup and then in his operational company selected Dynamics Online (for series) and did the same DROP / CREATE for all the tables.  In addition he RECREATED the Stored Procs.

    He reports now that all is well.

  • Derek Albaugh Profile Picture
    Derek Albaugh on at

    SQL Maintenance would re-initialize the SQL objects for Dynamics Online Services \ 6499 as mentioned, so it makes sense it resolved the issue.

    Thanks

  • Bill Campbell Profile Picture
    Bill Campbell 12 on at

    Yep, but the scary thing here was, different version discussed and the solution was that clear that he had no fear to proceed.

    I should note, that client and I have been together for 20 something years and we discuss a great deal of technical information back and forth.  I would not have every shared this with a client with whom I did not have complete trust and know that prior to doing this he made a full backup of his data.

    Talk to you soon.

  • Derek Albaugh Profile Picture
    Derek Albaugh on at

    Yes, normally we do not recommend using SQL Maintenance to re-create tables unless we're sure that there is no data in that module/feature, as the tables are not re-created with data..........we do use it frequently to re-create the dexterity stored procedures.

    Sounds like your client may've ran into this before or had done something like it. At least he made backups. :)

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans