syExcelReports Table & SQL Server Native Client 10.0 – Thanks Aaron Berquist


While upgrading our GP from GP2010 SP3 to GP2013 SP1, DYNAMICS database upgrade stopped unexpectedly with GP crashing without any information for me to debug.

But it stopped exactly at table syExcelReports and crashed. Without spending anymore time, I just went and checked my ODBC DSN setup, as explained by Aaron Berquist on his blog High Dynamics Range. Expectedly, the ODBC DSN driver was not pointing to SQL Server Native Client 10.0.

For some reason, GP fails to process upgrade further if your DSN driver is NOT native client 10.0 or above.

Those who upgrade your GP to latest version, please check DSN before you start database upgrade using GP Utilities.

VAIDY

GP, ODBC DSN & 64 Bit Systems


This post is long pending, since I had worked on the topic around 2 months back.

According to GP Installation Instruction, To set up an ODBC data source, enter the name you assigned to the SQL Server when you installed Microsoft SQL Server. A data source name called Dynamics GP also is created using SQL Native Client. If you don’t want to set up an ODBC data source, mark the Do not create a data source option.

It’s very handy (and recommended too) to create the ODBC DSN thru’ GP Installation, when we install GP on a 64 Bit System. We all know that GP is a 32 Bit Application. When we install GP on 64 Bit System, it gets installed with 32 Bit Compatibility.

Typically, on a 64 Bit System there are two ODBC Data Source Maintenance wizards available. One is for 64 Bit and other for 32 Bit. What you open from Control Panel -> Administrative Tools (or Start -> Run -> ODBCAD32.exe), is nothing but default 64 Bit ODBC DSN Maintenance wizard.

If you manually create a System DSN for GP, GP Application does not recognize this DSN at all. We have to actually create a System DSN for GP in 32 Bit ODBC DSN Maintenance wizard, which is accessible from the following path:

C:\Windows\SysWOW64\odbcad32.exe

We have to explicitly open this application from the above path and create System DSN for GP there.

Trust me, both look exactly the same. Application Name ODBCAD32.EXE is also the same for both. But location & compatibility factor is different.

In case, you are stranded when your ODBC DSN is not listed in GP’s Welcome Screen Server Dropdown, on a 64 Bit System, rest assured that you have not created DSN on the correct DSN Maintenance wizard.

VAIDY

WIN2008, SQL2008 & GP10 – Issue & Resolution


This one may or may not have caught the attention of Consultants. So here you have it.

I was working on a GP 10.0 SP4 installation on the following environment:

1. Windows Server 2008 Standard
2. SQL Server 2008
3. GP 10.0 SP4
4. 64 Bit Environment

I installed SQL Server 2008 first and then installed GP 10.0. When I launched my GP Utilities, the ODBC Data Source to SQL Server was not listed at all. I must admit that I did not search any forums or KB to find out the reason and solution.

But I found this: SQL Server 2008 on Windows Server 2008 R2 must be applied with SP1 mandatorily. This was the reason my ODBC DSN did not get listed in my GP Utilities. I applied SQL2008 SP1 and it worked.

VAIDY