Dynamics GP 10 Service pack Upgrade Failure

While upgrading from Dynamics GP 10 SP1 to SP4, one of my clients have encountered the error below.

“The stored procedure Synchronize TableData() of form duSQLAccountsynch : 27Pass Through SQL returned the following results: DBMS: 102, Microsoft Dynamics GP: 0.”

This error was surfacing while running utilities and upgrading DYNAMICS database. I’ve not seen this error before. Taking cue from the error message, I thought initially it might be due to non-synchronization of account framework so tried resetting dex.ini file to Synchronize=TRUE, but it didn’t work at all.

To understand the probable cause of this issue, I had to rely on dexsql.log file.  The log showed that there is a possible permission issue, so we tried running the GRANT.SQL and DYNSA DB owner scripts on the databases as these were databases restored from Live instance. The same issue continued.

The dexsql.log showed that the database upgrade of DYNAMICS is getting interrupted with this error when it is reaching SY10800 table specifically.

After verifying SY10800 table, We realized that the index is missing for this table.

Now the upgrade went smoother. One thing which i didn’t understand during this process is that there is another table SY10800_t that got created possibly during the upgrade by the system itself. I assume the utilities upgrade is creating a temp table which should have been deleted otherwise after successful upgrade. However, it wasn’t deleted since the upgrade is failing at this point. I compared the SY10800 and SY10800_t tables to realize both tables are having the same data while index is missing in SY10800 alone. So, to try resolve the issue, I dropped the SY10800 table from the DYNAMICS DB and then renamed the SY10800_t table as well as index to SY10800 and PKSY10800 respectively. If someone knows the exact history behind this so called “_t” tables, it’d be great if they could add their comments here.

Now tried launching the Utilities and Voila ! It worked.

BTW, I found couple of good resources while binging for the solution related to this issue though they couldn’t help much in our case. Here you go

http://www.gergen.us/wordpress/?p=64

http://www.eggheadcafe.com/software/aspnet/29784177/patch-releases-90-headaches.aspx

Popular posts from this blog

Partner Point: A proactive approach MUST

Here we are talking about Dynamics GP in specific, but this is applicable to other products as well. Our job doesn’t end with just installing and deploying the solution out there. In fact, Our job as the most trusted partner would just start from there. We cannot expect the customers to constantly follow up on the latest software updates rolling down for their use because they expect they are in safe hands just like how You’d relax once you hand over your tax documents to your CPA. Microsoft on its part tries to send E-mail updates to the customers but how many of them would pay attention to these updates unless the partner approach them on a rather personalized basis explaining the benefits. I’ll illustrate the above with an example. We know Analytical Accounting has some critical updates pending in earlier versions of GP and these were made available in GP 10 SP4. As a partner, It becomes our obligation to take this update to the customers, whether they take your advice or not is d
Read more

Dynamics GP Fixed Assets GL Posting Batch Missing After Depreciation Run

Image
I got a call from a user who was seemingly worried about her monthly depreciation batch went missing from GL posting routine in the Dynamics GP Fixed Assets. I quickly took her desktop on Teamviewer Quick support and understood the problem she is facing. Let me explain the issue in detail before I tell you the solution. Dynamics GP Fixed Assets GL Posting Issue Issue The user ran the depreciation routine in Dynamics GP for November month through Dynamics GP | Financial | Routines | Depreciate All Assets. Till here, all was good. She then proceeded to FA GL posting routine. Dynamics GP | Financial | Routines | GL Posting. She could not find the batch in GL posting lookup. In other words, the monthly depreciation batch is not accessible for posting. She then ran the depreciation process again and this time when she went to GL posting window and tried processing, the system threw an error message as below There are no transactions matching these restrictions. Modify yo
Read more