It seems that regardless of how much testing you do, something can still slip through the cracks. Well after v10.00 Service Pack 4 was released, an issue with the SmartList Builder/Excel Report Builder code was identified. A Hot Topic has been posted with a temporary workaround fix.

Here is an excerpt from the Hot Topic:

After installing Service Pack 4 for Microsoft Dynamics GP 10.0, you will receive the error Wrong…

By now you probably read David Musgrave's series on Microsoft Dynamics GP and Illegal Characters and have come to realize that the single quote character is perhaps one of the biggest culprits in the errors you are receiving when running reports such as your age trial balances in both receivables and payables. It's enough for the single quote character to be in your customer ID, vendor ID, or even document numbers to cause some error while running a report or inquiring a transaction.

The following is an actual case reported by a user on the Dynamics GP newsgroup when running the Payables Historical Aged Trial Balance report:

Sometimes using integration manager you may face errors while doing the integration say for example "Not all required fields have been entered. Required fields appear in bold red type." And you have tried and tried finding and setting all fields but can’t locate the field it is referring to. Here is the simple solution to dig into this error

A little while ago I downloaded and installed the RTM (Released to Manufacturing) build of Microsoft Dynamics GP 2010. After installing GP and Dexterity I started on the process of updating my Dexterity projects to use the RTM build of Dynamics.dic (build 11.00.1247) and Dexterity…

Sometimes you finds your self in a very deep technical investigations looking for the cause of a very stupid error message or behavior that does not represents the actual cause of the message, such as situations below:

I've covered the basic resolution for this issue in my earlier post GP Troubleshooting-I. Recently, In a client place, I got to see this error back again in General Entry. I followed whatever troubleshooting steps required to rectify this that turned out to be futile. Finally, I figured out. It is the same issue as to Regional Settings. We must agree on a common ground that this error surfaces mostly due to SQL collation settings conflicting with Windows regional settings on…

Had a client using MSDE and was getting space errors whenever trying to process any transactions. Couldn't post at all, just print reports. We looked at the size of their database and found it was 2 GBs. As you may know there is a 2 GB space limit on MSDE so I suggested updating to SQL Server Express Edition 2005 which has a 4 GB restriction. It is free and would double their storage capacity.

The client thanked me profusely and said they never heard of Microsoft giving anything away for free. I agreed but told them it's not exactly free as I would charge them for my time which ended up being 3 hours when all was said and done.

If you have looked a DEXSQL.LOG file to see the communication between SQL Server and the Microsoft Dynamics GP application, you might have noticed messages with errors 5701 and 5703 being reported. See the example below:

In my previous post, I mentioned that I was assisting a developer with an issue. It turned out that the issue he was having was not the cause of an error, but the result of a previous error that the users had not told him about. Once the original error was fixed, the entire problem was solved.

So, this raised an issue which is probably one of the most frustrating aspects of support a system that support engineers and consultants have to face on a day to day basis. So I will get up on my soapbox again to discuss this subject.