5
For Dynamics GP 2016, I have a user that's getting the error:
After clicking More Info, this is what is prompted:
After clicking OK, the first error will prompt multiple more times until around the 5th time.
This is the only user that's getting this error when doing PO's for this company and would appreciate some insight!
Perfect, that is what it does. I lost my notes on this and have been using it for so long I had forgotten why it was there I simply remembered to add those lines.
The tool allows you to invoice a drop-shipped Sales Order that is linked to a Purchase Order, before you complete the Enter / Match invoice step in GP.
I assume the lines added to the DEX.ini are to not have to have the user pull up the Shipment Notification window and specifically pick the PO and mark it as shipped. If you assume all drop-ships will be Enter / Matched and you want to invoice the end-customer as soon as possible, this is the way to go...
Brian
Wow, I have been using this tool for over 20 years. I did know what these used for in the beginning but now I do not. I remember there were changes made to the PO process when it came to shipping and receiving. This tool undoes those changes and these lines are needed in the dex.ini file to make it function properly.
Put these lines in your DEX.INI file.
taShipmentNotificationAlwaysTransfer = true
taShipmentNotificationAlwaysPost = true
taShipmentNotificationAllowVoids = true
Hi bphill2220,
I reinstalled GP from the workstation without ShipNoti.cnk and I can confirm that the error no longer popped up. However, I do need the Shipment Notification Tool for its purpose so I'd like to keep the module.
After confirming that this is the issue, do you or anyone have a suggestion on how to correct this issue with ShipNoti installed?
The new GP directory will be re-created as the original name you had, for example, if you have a directory:
C:\Program Files (x86)\Microsoft Dynamics\GP2016\
......and you rename it to be this:
C:\Program Files (x86)\Microsoft Dynamics\GP2016_OLD\
You then go into Control Panel > Programs > Programs and Features, right-click on your Microsoft Dynamics GP instance, choose 'Change'.
An options window will open, choose the 'Repair' option and verify it goes through successfully.
If it does, there will be a new GP directory at the original name and path, i.e.
C:\Program Files (x86)\Microsoft Dynamics\GP2016\
We would want to use this 'new' GP directory to launch Dynamics GP from and test.
Let us know if you have any questions.
Thanks
Hi Derek,
To be honest, I have no idea what this all means. Let's say I rename the GP directory so I can run a repair against it. Where would the GP directory be found? Are you referring to its install on the C: drive?
And how would I run a repair?
If you've verified that multiple users have the same error on one workstation, but these same users can go to other workstations with Dynamics GP installed and not see the issue, then the issue would appear to be specific to the workstation, which would only really leave the following to rule out:
1. The Dynamics GP code/directory itself
2. ODBC DSN being used to connect SQL and GP
3. Forms and Reports dictionary files, if not using the same as other Dynamics GP instances on other machines.
4. The user's Windows profile
>For the ODBC, make sure it is setup as per KB 870416
>For the GP directory, look at the Dynamics.set file for this workstation's Dynamics GP instance, and compare it to other workstations. Does this workstation have anything installed that the other workstations do not, or vice versa?
As well, you can try renaming the GP directory on this one workstation, then run a Repair against it, which will re-create the entire GP directory, folders and files. Login to this 'new' GP directory and attempt to re-create the error.
The above is all on the assumption that the testing you've done is on the exact same company database, on all the machines you tested, with all the different users.
Thanks
Hi Bill,
This error happens when transferring an order to an invoice. I had another user who has no problem doing transfers on their own workstation try to duplicate the error on the workstation affected and the same get/change taShipmentNotification shows up.
Not sure if this is important to note but the user who originally received the error has POWERUSER as the role ID.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (