Month: November 2021

I did an upgrade for a client recently which encountered a problem in one company and crashed; when resuming the upgrade, the Upgrade these companies? step showed a lock against the company which had encountered the problem:

It’s a while since I encountered this and I had to look up how to remove the lock; it’s quite simple to do with a small SQL script. To remove the lock, run the below in SSMS against the system database (typically named DYNAMICS):

DELETE FROM duLCK

We been doing a lot of work with a client recently to split their US and UK based systems. The original scope involved implementing Microsoft Dynamics GP for a new company based in the UK; the databases were originally created on the US system and then split off by copying the company database and the system database onto a UK based SQL Server.

Along with the client, we did some tidying up of the system, such as removing US users and also ran the clear company script to remove all references to the databases which weren’t being brought across.

A few months later after the new company had gone live, we needed to migrate the other UK databases across to the UK server. We did this by creating new companies, entering the company settings (which are stored in the system database) and restoring the databases from the US server over the top of the blank ones.

When logging into Dynamics GP and selecting one of the companies being migrated over, the following error was produced:

The issue lay with the System Database Name (SY00100) table which has two key columns; DBNAME which stores the name of the system database and is usually the cause of problems with this table when someone runs an old copy of the live to test copy script and the CMPANYID column which stores the id of the company; this is a sequential number unique to each company and assigned when it is created.

We had deleted the original references to the companies on the new server and created new ones, which meant a new CMPANYID had been assigned in the SY001500 table. Once SY00100 was updated, we were able to log in and use the company without further problem.

I did some work recently to assist a client to upgrade Microsoft Dynamics GP to the latest version on an isolated test system. They had previously had the Reporting Services and refreshable Excel reports deployed, but weren’t sure if they were being used.

When we did the upgrade we did not deploy the new versions of the reports while we awaited a decision from the end users as to whether any of the reports were used and therefore needed to be deployed.

While we were waiting users progressed with the user acceptance testing. We had an error raised when a user tried to purchase a requisition and create a purchase order:

The issue here is that when purchasing a requisition, there is a prompt displayed (which can be turned off) which allows the user to see a navigation list showing the new purchase order. In this instance, the user had clicked Yes which opened the navigation list which is when the error appeared.

The error is because the isolated test system cannot see the live SSRS server at which it was still pointing; the 404 error can be avoided by either setting the SSRS reports as not deployed or changing the server and deploying to the test system.

I helped a client create a bank transaction integration in Integration Manager the other day. It’s been a while since I created an integration like this, so we created it as I would a general ledger integration with a header and distribution file with two distributions for each transaction. However, when we ran the integration, we received this error message:

I had forgotten that bank transactions can only have one of the distributions can be mapped (this is covered in a knowledge base article from Microsoft.

This integration was only for creating increase adjustment transactions, so we amended the integration so that only the Debit Amount destination field was mapped. After making this change, the integration ran successfully.

A client reported an issue recently whereby they could not post bank trasactions. This had previously been working, but had recently become a probkem. When trying to post, they received this error message:

Continue reading ““You do not have authorization to post bank transactions” Error in Microsoft Dynamics GP”

We’ve been implementing Microsoft Dynamics GP for a client recently. After creating some new user accounts, I was sending details to the users, when I realised that I couldn’t remember the password structure (I’d been distracted onto another project between creating the accounts and sending the email).

I went back into the User Setup window (Administration area page » Setup » System » User) and changed the password; however, when clicking Save:

I’ve reset passwords before which I have just set, so the error was somewhat puzzling. It took only a few minutes before realising that the problem was the Enforce Password Policy and Change Password Next Login checkboxes were marked.

I had a final stab at the password structure for these accounts and fortunately got it right, so I was able to email the users. The alternative would have been to delete and recreate the user accounts (which would have also required access and security roles to be assigned).