Dynamics Blogger

This is the last post in this series of Integration Manager error in GP 2010 that started occurring since last week. The culprit was the Microsoft Connect gadget that caused this issue. It seems the slide causing this issue has been removed yesterday and the connect service has been restored which was having issues earlier. For more information, Visit Mariano’s blog who has provided the first hand information about the error. Integration Manager for Microsoft Dynamics GP 2010 hangs when running an integration - Follow up

Well. Someone looking at the title of the post can sense how important this topic seems to be. This is the third post in a row on the same topic. In fact this became a hot topic on community. It is worth to mention here that I’m receiving significant traffic from Google and Bing search specific to this error for the past 2 days. In the other two posts, I have covered generic troubleshooting segments for the error. Some latest information is pouring into the community about this error that this behavior is due to a Microsoft .Net framework  update. IM is now designated as Hot topic by Microsoft which started occurring early last week. Complete information is available on this hot topic following the link here Integration Manager for Microsoft Dynamics GP 2010 is Unresponsive at the Beginning or End of an Integration   The above link requires customer source login. More information is available on Mariano Gomez Blog link here . Thanks to Mariano for providing this infor...

This article is a continuation of another article Integration Manager crashes published in July. I observed that the Integration Manager is hanging specially in GP2010 even in normal GP client. The behavior is such that after running an integration, the Dynamics GP screen fails to open up and dynamics.exe continue to be seen as active under processes in Windows Task Manager. Killing this process serves no good. Possible Resolutions 1. I cannot be specific on the resolution as I have not personally experienced the error so far. 2. When we upgrade GP2010, GP2010 is installed as a separate instance and GP10 instance continue to exist and so is the case with Integration Manager for GP10. 3. In some cases, this IM instance is left installed and the same instance will be used to run the integrations on GP2010. This can lead to errors. Always ensure latest IM is installed with the required service packs. 4. It is recommended to uninstall GP10 and old IM instances from the computer ...

Macro to enter new dimension codes in Analytical accounting module is provided below. TypeTo field aaTrxDimCode , ' CODE '   MoveTo field Inactive  # 'FALSE'   MoveTo field aaTrxDimCodeDescr   TypeTo field aaTrxDimCodeDescr , ' CODE DESCRIPTION1 '   MoveTo field aaTrxDimCodeDescr2   TypeTo field aaTrxDimCodeDescr2 , ' CODE DESCRIPTION2 '   MoveTo field aaNode   MoveTo field 'Lookup Button 3'   ClickHit field 'Lookup Button 3' NewActiveWin dictionary 'Analytical Accounting'  form aaTreeNodeLookup window Main   DblClickHit field '(L) TreeView' item 1  # ' NODE ' 1 NewActiveWin dictionary 'Analytical Accounting'  form aaTrxDimensionCodeMnt window Main ActivateWindow dictionary 'Analytical Accounting'  form aaTrxDimensionCodeMnt window Main   MoveTo field 'Save Button'   ClickHit field 'Save Button' ...

Sometimes we might not be that lucky to get through with our imports through Integration Manager remotely. A remote session will kill the ongoing Integration and leave the Dynamics GP running despite the crash. I’ve made interesting observations that will save your time next time you encounter the same for some reason. 1. Integration Manager crashes while doing the integrations using terminal server or Citrix like environment. Or for that matter applications like Team viewer, LogmeIn so on. 2. It will crash only when we try to do the integrations using Integration Manager standard destination adapter that requires Dynamics GP session to be on. This doesn’t happen for IM eConnect adapter. 3. This happens when the integration tries to open another GP window during the course of Integration. Troubleshooting 1.There is no proven solution to the above problem. 2. However when it happens, the first thing to do is to go to Task Manager and kill Dynamics.exe process that keeps runn...

While importing sales documents in Dynamics GP through Integration Manager or eConnect, We encounter the following error message. Microsoft.Dynamics.GP.eConnect:  Number = 287  Stored Procedure taIVTransactionLineInsert  :  Description = Location ID/Site ID (TRXLOCTN) does not exist in Site/Location Setup - IV40700 When we see this error, Our immediate focus would be on Quantities/Sites window where the Item number should be assigned to the relevant site ID in import. However, In some cases the integration fails despite assigning the site to the item number. Reason for this error would be due to the presence of Kits. If any of the line items contain Kits and we receive this error, We shall go to the Kit components and check if the components are assigned to the respective sites in import. In one of my imports earlier, I’ve struggled for 4 hours struggling to find which item was not assigned to the site. After constant trials, I found the problem lies in the kit...

Importing Kits is another exercise that is difficult to integrate with Integration Manager as there is no such adapter available. What if we have thousands of Kits to be created in GP. In such cases, Using Table import is a wise option to import thousands of kits in split of seconds. Kits Import is a straight import in GP as the Kit Master is the only table tat we should be looking at. Follow the steps below to import the kits. Make sure Kits are defined with the item type Kit and the Kit components as items with Sales Inventory types in Item master as a prerequisite for Kits Import. Prepare the CSV file with the following fields. Make sure to remove the label Headers in the file after preparation of fields. Item Number – Fill this field with Kit parent code. Sequence Number – Fill this field with Sequence number 16384, 32768 so on for each component line item. Component Item Number – Fill this field with the ...

In my earlier post I’ve covered how to import Inventory BOMs. In this post, I’ll publish a couple of FAQs’ which are very critical for the import. 1. I’ve successfully imported the Inventory BOM into both BOM Header as well as Component Tables. When I go and check the BOM Master record in GP, I could only see my Header record but no components are visible? A. Make sure You’ve assigned constant value of 5 for all your components BM Comp state field. Value 5 stands for Saved status. 2. I’ve successfully imported the BOM into the relevant tables. When I go and check the BOM Card in GP, I could see the header as well as components below it. But when I lookup for Bill Number in Bills and Items lookup, I could not see any of Bill numbers imported? A. Make sure you’ve provided the date values in creation date and modified date fields. If these fields are left blank, the BOM will not be visible in Lookups. 3. I’ve successfully imported the BOM into the relevant tables. When I go and ...

Consider this scenario. You are implementing Dynamics GP Fixed Assets in your company. None of the Fixed Assets have been imported yet. You have ensured you did all your setups just perfect. Now, It’s turn to import your assets into Asset General window using Integration Manager. It can be handled using Integration Manager eConnect destination adapter for Fixed Assets.  You have made sure you set your source files, relationships as well as mappings are all proper. Now, It’s time to run your integration so you hit your Run Integration button. For no mistake of yours, the integration fails returning this error below. Microsoft.Dynamics.GP.eConnect: Number = 6625 Stored procedure taCreateAssetID : Description = unable to obtain the next FAINDEX. What’s wrong with the integration? There is nothing wrong that you did during this  process except resorting to this workaround for getting away with this error. Go to your Fixed Assets General window. Enter one Asset...

  Steve comes with a great post detailing his recent experience on econnect integration in Dynamics GP V9.0. Read the article, clicking the below link Dynamics GP Land: Sending XML Files to eConnect