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 :
Microsoft Dynamics GP (Archived)

Problems with Integration Manager

(0) ShareShare
ReportReport
Posted on by 40

We are running MS Great Plains v8 and SQL 2000.  One of our other sites uses some custom program for which they have an in house developer. Last Friday he contacted me stating that the integration was suddenly failing. Now, I am not a SQL guy, nor am I a GP guy. I have had to scratch and claw just to be able to do the basic administration so the last I do is touch them or even look at them unnecessarily. So nothing has changed on my side. The ONLY thing I noticed is that the MSSQLOLAPService crashed on Thursday night. It does this fairly regularly as it hits its upper memory limit. I just restart the service and all is well for another week or two. So I naturally attributed their issues which began on Friday, to the OLAP service crashing on Thursday (and remaining crashed until mid day Friday). Seemed logical. So on Friday night, all of the integration routines ran successfully. I figured problem solved. Well today he is saying that he is still having the problem. So here is where I really need help in a hurry (sorry to be so longwinded):

- The integration is pulling information from the custom program (which is where they enter their orders I believe) into Great Plains.

- When run, the integration fails on every document and the log states "Error: Please check and reenter the date." with a status code of: 0x80040009 (-2147221495). Source is: Ln 1689 Col 2, Update module, Last CBOM field read was root.'Date', Last window field visited was 'Delete Button' of window 'SOP_Entry' of form 'SOP_Entry'

- He insists that all is correct from his perspective. As well, he says that this was all working as recently as Friday morning and that he has made no changes.

I am not sure where to start in trying to resolve this. Could really use some guidance/help.

 

*This post is locked for comments

I have the same question (0)
  • K Day Profile Picture
    7,365 on at

    I see the important part of that message as "Error: Please check and reenter the date"   If you manually entered a date in GP and put a bad date (like 02/30/09) that is the message you get.  I would have him verify the Source of the integration.  It is obviously pulling a date field, so that date is either a bad date (like above) or it is somehow not formatted properly.  What is the Source of the integration?

  • MSalam Profile Picture
    40 on at

     Thanks for responding.  The source of the date is from the custom program they are using.  He seems to believe that the format of the date shouldn't make a difference and that anything will be accepted.  One thing I noticed in my exploration was that the source field had a "size" of 16 while the destination had a size of 8.  I thought this was peculiar but he seemd to think this didn't matter...and of course he keeps saying that it was all working fine until a few days ago and he didn't change anything, and I didn't change anything so...  Of course he convieniently cleared the log files over the weekend so I can't really get any proof of that...he said that he even tried changing the field to string instead of date and it still didn't work...

  • K Day Profile Picture
    7,365 on at

    The Destination adapter that it sounds like you are using is called the Standard GP Adapter.  I think version 8 also had SQL optimized adapters (direct to the tables).  When you run the integration, does it "hide" GP and then do it's thing, then show GP again?  If so, you are using the standard adapter.  That adapter uses the logic of the window for data validation.  It's as if you were manually entering the Sales Order in the Sales Order window, but really quickly.  I really think it is getting passed a bad date.  The format DOES matter - if you tried to enter letters in the date field, it would not let you.  It has to be a date and it has to be a valid date.  My suggestion would be to identify the record that is getting the error (IM tells you which one it is), look at the source data to see what it is trying to push into the date field, and then enter it manually and you shoudl get the same error.

     

     

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 > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans