Microsoft Dynamics GP v10 Service Pack 3 now available


Microsoft has released (on time) Dynamics GP Service Pack 3. The direct link to the version 10.0 Service Pack 3 page is:

https://mbs.microsoft.com/customersource/downloads/servicepacks/MDGP10_ServicePack3.htm.
If you are upgrading from previous versions of Microsoft Dynamics GP, Business Solutions-Great Plains, or eEnterprise, be sure to check my new post on available upgrade paths. Also, please make sure to visit fellow MVP, Victoria Yudin's blog who is polling her readers on their intent for Service Pack 3.

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC.
http://www.maximumglobalbusiness.com/

Comments

DougFettig said…
downloaded SP3 (V10) KB957743 V10 ENU.msp

Tried to install but get message:

Dex.Dic version 10.0.2630.0 is not compatible with executable version 10.0.320.0

any suggestions?
November 26, 2008 at 11:22 PM
Mariano Gomez said…
Doug,

Try reinstalling the Dexterity Shared Components from the Feature Pack 1 DVD image, found under the CD Root at \Bin\DexCmn.

Best regards,

MG.-
Mariano Gomez, MIS, MVP, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
November 27, 2008 at 9:51 AM
DougFettig said…
Thanks, I will try that.

I one of my 3 terminal servers now that is getting a message at logon:

The PM_Mass_Voucher_Save_Button trigger is not registered.

Any ideas on how to correct this?

my 2 other terminal servers do not get this message.

After getting the above message, I click OK and Dynamics seems to work fine
November 27, 2008 at 11:51 AM
DougFettig said…
I have a 4th terminal server, that seems to be really messed up the update to SP3 will not load at all.

Would this be the best steps?:
1. Add/Remove programs on Dynamics
2. Reload Dynamics from CD
3. Reload sp3 before running utilities.
November 27, 2008 at 12:02 PM
DougFettig said…
How about this error during upgrade on payroll master, payroll year end pension and paryoll year end wage:

Error Code 0
Error: Other Error (135)
The conversion program encountered an error and the temp table did not get removed.

Remove temp table at db level.
November 27, 2008 at 1:04 PM
DougFettig said…
i have updated V10 to SP3, from SP1, and all seems to be fine except if I
try to access the employee master table.

Either from cards>payroll>Employee, or payroll transaction entry. Anytime I
need to do a lookup on an employee id.

Here is the message:

A Get Change operation on table UPR_MSTR failed accessing SQL Data

If I go to the more information or details button:

[Microsoft][SQL Native Client][SQLServer] Invalid column name 'EMPLSUFF'

[Microsoft][SQL Native Client][SQLServer] Invalid column name 'Dex_Row_TS'

any ideas?
November 28, 2008 at 12:10 AM
Mariano Gomez said…
Doug,

Do you have any third-party dictionaries or Dexterity customizations installed? A trigger registration error may come from a third-party dictionary or Dexterity customization that is attempting to perform some action on before the code on the Save button is executed.

On your Terminal Server, try to remove the Dynamics application and reinstall from the Feature Pack 1 DVD, then apply Service Pack 3.

As for your payroll error, it does not seem the table was updated. You can attempt to force an upgrade from the Dynamics Utilities.

MG.-
Mariano Gomez, MVP
http://www.maximumglobalbusiness.com
November 28, 2008 at 3:17 PM
Denuncias Buenos Aires said…
Hello, I have updated to the last version GP 10 (Argentina localization), and I'm getting issues with some XDL tables.

XDL00101 //// XDL_Numeradores_Config: "Failed accessing SQL Data / Number of results columns doesnt match table definition"

XDL10100 //// XDL_Documentos_WORK: "Failed accessing SQL Data / Number of results columns doesnt match table definition"

XDL_Export_Information: table doesn't exist. "Invalid objet name dbo.xdl00120"



All these problems fire up when I want to make an invoice, or eliminate a product from an invoice not saved yet.



My MS partner doesn't know how proceed.



Please help me!

Thanx.

Pablo
September 17, 2010 at 1:40 PM
Mariano Gomez said…
Denuncias,

Parece que los auto procedimientos almacenados correspondientes a las tablas mencionadas en tu comentario estan danadas o no fueron actualizadas durante el upgrade.

En Dynamics GP, ve al menu de MSDGP > Mantenimiento > SQL. Selecciona la compania afectada, y localiza las tablas en la lista para la serie adecuada (presiona SHIFT y selecciona la tabla con el mouse). Luego selecciona las opciones "Borrar Procedimiento Automatico" y "Crear Procedimiento Automatico". Luego haz clic en Procesar.

Mucha suerte,

MG.-
Mariano Gomez, MVP
September 17, 2010 at 4:41 PM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more