Posts

Showing posts from August, 2011

"Object Reference Not Set" error when running Integration Manager with eConnect Adapter

Image
I have seen a number of forum posts around this subject and have even received a few calls for help in troubleshooting the issue. In the occassions I have assisted someone, I have noticed that most of the time the developer or consultant was using an event or field script of some kind, which almost always attempts to get some information from Microsoft Dynamics GP. So, in an attempt to reproduce the problem, I have recreated the following VBScript based on a recent case: ' Created by Mariano Gomez, MVP ' This code is licensed under the Creative Commons ' Attribution-NonCommercial-ShareAlike 2.5 Generic license. Dim objConn, objRec, cmd, sJE set objConn = CreateObject("ADODB.Connection") objConn.ConnectionString = "database=" & GPConnection.GPConnInterCompanyID GPConnection.Open(objConn) Set cmd = CreateObject("ADODB.Command") cmd.ActiveConnection = objConn cmdString = "SELECT NJRNLENT FROM GL40000;"

New Article on MSDynamicsWorld: When It’s Time to Upgrade an Outdated, Customized Microsoft Dynamics GP System…Who You Gonna Call?

Image
It's been a couple months since I've written a business-driven column over at MSDynamicsWorld . This time, my new article looks into an all too common issue: upgrades from older, customized versions of Microsoft Dynamics GP systems. By "older", I am not referring to - believe it or not - version 7.0 or 7.5, even though those are very outdated releases. I'm referring to you, still running version C/S+ 3.17, or 4.0 or even GPA. I know you have milked the product as much as you can and you feel it still does what you need it to do, but you are missing out on a unique opportunity to bring your systems up to date and take advantage of the wide array of ISV solutions that will once and for all get you off the development threadmill. Since it's Friday, the article is meant to serve as food for thought. When It’s Time to Upgrade an Outdated, Customized Microsoft Dynamics GP System…Who You Gonna Call? Leave your comments and feel free to discuss with your peer

Default Printer not 'sticking' when running Microsoft Dynamics GP in Terminal Services RemoteApp

Image
A bit of theory... RemoteApp programs are programs that are accessed remotely through Terminal Services and appear as if they are running on the end user's local computer. Users can run RemoteApp programs side by side with their local programs. A user can minimize, maximize, and resize the program window, and can easily start multiple programs at the same time. If a user is running more than one RemoteApp program on the same terminal server, the RemoteApp programs will share the same Terminal Services session. The following Microsoft TechNet article explains in more detail: Terminal Services RemoteApp (TS RemoteApp) Background Microsoft Dynamics GP (versions 10.0 and 2010), is currently supported in a Terminal Server RemoteApp environment, but a number of my clients and forum users have reported in numerous occasions that the Default Printer settings are not 'sticking' or simply saving when loging out of the application (which also closes the RemoteApp session) an

Cannot insert the value NULL into column 'CONTACT' error when clicking on Items List in Navigation Pane

Image
Moving on from my previous article on a similar subject - see Cannot insert the value NULL into column 'BASEUOFM' error when clicking on Items List in Navigation Pane , I recently came across this error,  Cannot insert the value NULL into column 'CONTACT' when clicking on the All Purchasing Transactions list under the Purchasing Navigation Pane option, after performing an upgrade from Microsoft Dynamics GP 9.0 to Microsoft Dynamics GP 2010 R2. All Purchasing Transactions list error - Purchasing Navigation List The name of the global temp table - in this case, tempdb.dbo.##2093338- varies in almost all cases, but the end result of the error is the same. The issue has been identified running Microsoft Dynamics GP 2010 RTM, SP1 or SP2. Upon further review, the issue is due to bad data in the Vendor ID (VENDORID) column in the Purchasing Receipt History table (POP30300). In summary, if you have a purchasing receipt with a blank vendor ID or a vendor ID that doe

Integration Manager for Microsoft Dynamics GP 2010 hangs when running an integration - Follow up

Image
After some additional testing to find the route cause of Integration Manager 2010 hanging, it seems the issue has been narrowed down to a glitch in one of the slides cycled by the Connect gadget on the home page, and not an issue with the Microsoft .NET Framework 3.5 as originally thought. For those of you who follow closely on the community news through the Connect gadget, you may have noticed the service being down since last Friday - around the same time Microsoft Support started receiving reports on the issue. Sources tell me that this was done as part of the standard testing protocol to discart new functionality causing the problem. The slide causing the issue was removed this afternoon and the Connect service has been restored. If you were getting prepared to apply a new hotfix or service pack, you will be glad to know there may be no need to do so. Stay tuned for further updates. Until next post! MG.- Mariano Gomez, MVP IntellPartners, LLC http://www.IntellPartners.

Integration Manager for Microsoft Dynamics GP 2010 hangs when running an integration

Image
The forums are hot with users and partners reporting an issue with Integration Manager for Microsoft Dynamics GP 2010 hanging when running an integration. Everyone seems to agree the issue started sometimes this past Friday, August 5, 2011, with most users reporting a normal behavior and the ability to run trouble free integrations prior to that date. This issue has been written up under the following hot topic article Integration Manager for Microsoft Dynamics GP 2010 is Unresponsive at the Beginning or End of an Integration   [link broken as hot topic has been retired] According to a Microsoft representative with the Escalation Engineering team: Our development team has identified the issue to be the result of a change in .Net Framework 3.5. At this point our development team is working on creating a new Integration Manager build which will then undergo testing to verify the build and that the issue has been resolved. As soon as we have a new IM build that resolves this i

SQL: Assigning Microsoft Dynamics GP Users to SSRS Database Roles

Image
As I begin to wrap up a Microsoft Dynamics GP 2010 R2 production upgrade from Microsoft Dynamics GP 9.0, I ran into a small issue at my client. After deploying the new SSRS reports, and as users were getting ready to try them out, we realized that some 15 logins needed to be assigned to a number of the 24 default database security roles created for the SSRS reports. User Mappings (some information blurred to protect the client's identity) This would be a bit cumbersome giving the share number of clicks required to accomplish this feat. In addition, we had just setup Microsoft Dynamics GP security, and given that the SSRS database roles were similar to those in GP, something needed to be done to automate the assignment of these roles based on Microsoft Dynamics GP security roles. As a result, I created the following script: -- Created by Mariano Gomez, MVP -- This code is licensed under the Creative Commons -- Attribution-NonCommercial-ShareAlike 2.5 Generic license.

Cannot insert the value NULL into column 'BASEUOFM' error when clicking on Items List in Navigation Pane

Image
Just recently a few partners began reporting getting the error Cannot insert the value NULL into column 'BASEUOFM' when clicking on the Items list under the Inventory Navigation Pane option.   Items list error   The name of the global temp table - in this case, tempdb.dbo.##0251007 - varies in almost all cases, but the end result of the error is the same. The issue has been identified running Microsoft Dynamics GP 2010 RTM, SP1 or SP2. Upon further review, the issue is due to bad data in the Unit of Measure Schedule (UOMSCHDL) column in the Item Master table (IV00101). In summary, if you have an item record with a blank Unit of Measure Schedule or a Unit of Measure Schedule that does not exist in the Unit of Schedule Master table (IV40201), it will cause the Items list to fail with the error above. The following query should help in identifying the offending record(s): ' Created by Mariano Gomez, MVP ' This code is licensed under the Creative Comm