Friday 29 January 2016

Error Dex.dic version 11.xxxxx is not compatible with executable version 11.xxx+1

You receive the above error when installing a service pack for your current GP version.

Dex.dic version 11.00.0218.000 is not compatible with executable version 11.00.0364.000


To resolve
  • Go to program files>GP (relevant version)
  • rename the dex.dic to dex_old.dic
  • there will be a dex_us.dic file in there, copy the dex_us.dic
  • rename the copy to dex.dic
  • rerun the service pack

GP 2013 Unable to Save Fixed Asset on General Window

There is a bug with Gp2013 that crashes the system when you click save on the asset card window.
This happens when you have over 150 assets numbered consecutively.

The resolution would be to upgrade.
The workaround is to click on the next record button and let the system prompt you to save the record.

MSI Error 1317: 'An error occurred while attempting to create the directory' during installation

So you are trying to add a sub feature of Dynamics GP and you were able to do so via control panel.
You are now trying to launch GP for the cnk file to load and then you get the above error.
You check permissions and find that you have full admin permissions to the GP folder.
In my instance the issue was the 'SYSTEM' user did not have access. Once i added this user to have access to the folder the install completed.

Wednesday 27 January 2016

Integration Manager Error - Item already exists in collection

You are on GP 2015R2 and try running any integration and get the above error.

You need to install the Hotfix for 2015R2 and this will resolve the error.

Monday 11 January 2016

Invalid Versions! This version of Professional Services Tools is only compatible on GP 2013

So you are on GP 2015.

On signing in to GP you continuously get the message to include new code no matter what you do.

Then you launch PSTL and it says "Invalid Versions! This version of PSTL is only compatible on GP 2013".

You need to remove PSTL from control panel and follow steps from this guy. please note that you cannot just delete the SY07130 table as it will remove all third party applications. So try to delete only those for "Customer Exception"

https://community.dynamics.com/gp/b/dynamicsgpessentials/archive/2015/02/21/dynamics-gp-2015-rtm-pstl-invalid-versions

Wednesday 6 January 2016

Update Include in Lookups on Chart of Accounts

Providing that your include in lookups are laid out like this, the combinations below will apply.
Sales
Inventory
Purchasing
Payroll


Combination SQL Value
NNNN 0X0
XNNN 0X1
NXNN 0X2
XXNN 0X3
NNXN 0X4
XNXN 0X5
NXXN 0X6
XXXN 0X7
NNNX 0X8
XNNX 0X9
NXNX 0XA
XXNX 0XB
NNXX 0XC
XNXX 0XD
NXXX 0XE
XXXX 0XF


Have the combination matched to each account.
Import the chart of accounts to the system.
Extract the chart of accounts after upload including the account index.
Use the following script and update in SQL it must include same spaces and apostrophe as seen below.
update GL00100 Set dsplkups =0x4 where actindx ='1'

Tuesday 5 January 2016

Dynamics GP Upgrading from a version to its R2 version

SCENARIO:
You need to upgrade from GP2015 to GP2015R2 for example.
You have downloaded the media and on running the file you are only allowed to add/remove features or repair.

WHAT TO DO:
Run the file in the Updates folder and this will get you on the new release. Then run utilities as admin so the tables can be updated.

REASON:
You are already on the main version of the software and its just a patch/service pack that needs to be added.

Fiscal Period Setup Error "The date cannot be part of a different fiscal year"

Confirm there are no fiscal years setup with incorrect dates in the same Fiscal Period window.

Then run Reconcile in Admin for Fiscal Periods. (Microsoft Dynamics GP>Tools>Utilities>System>Reconcile, then select Fiscal Period and insert into the list)

The report will tell you where there were errors, go back to the Fiscal Period window and fix the corrupt year, then create the new year.

You will then be required to run a reconcile on GL, AR and AP.

Dynamics SL "Date must be in an open 1099 year, please reenter"

User is unable to print cheques in January although your fiscal year is set to span calendar years.

1099 setup looks at calendar year. Hence, if the years in your 1099 setup window is not the current calendar year you have to purge the oldest year so the current and next years can be updated on the system.

To Purge Go to: Financial> AP> Setup> Processes> 1099 Calendar Year Control. Purge the oldest year and this would update the Current and Next Year values.

You will then be able to print your cheques.