Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
We've seen a couple of errors recently that we wanted to put out the information on so that everyone can be aware of the issues in case they run into them.
These errors do not occur only when upgrading to the Year-End updates for Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015 and have been seen over a variety of versions customers are coming from and going to.
The first upgrade error we've seen is related to the eConnect_Out_Setup table and the error itself will look something like this, with the name of the stored procedure varying:
ERROR[Microsoft][SQL Server Native Client 10.0][SQL Server]There is already an object name 'taRequesterPurchase_Order_Transaction2' in the database."
Normally, when we see this type of error, we would simply drop the object from the database and continue with the upgrade. However, in this case, the objects are tied to the records within the eConnect_Out_Setup table, so even when we drop the object, we still get the error as it is re-created.
The resolution is to make a backup of the eConnect_Out_Setup table, then delete any records out of the table, continue with the upgrade past this error and then, when the upgrade of the database is completed, the records can be put back into the eConnect_Out_Setup table.
The second error we've seen is related to the wfDeployClrAssemblies stored procedure when upgrading the DYNAMICS or system database.
We'll often see the DYNAMICS/system database fail on the wfDeployClrAssemblies stored procedure, but then the rest of the error message will show something like this:
"ERROR[Microsoft][SQL Server Native Client 11.0][SQL Server] There is insufficient system memory in resource pool 'Default' to run this query."
The resource pool name may be different then 'Default' from error to error as we've also seen resource pool 'Internal' as well.
In this case, the error is a result more of how Microsoft SQL Server manages virtual memory usage within the application and is not directly related to the amount of physical or available RAM you have installed on the SQL server.
To resolve this error, you simply need to close out of Microsoft Dynamics GP Utilities, stop and re-start the SQL Server service, then launch Microsoft Dynamics GP Utilities again and continue with the upgrade of the DYNAMICS/system database.
This error is more common in, but not solely found in, 32-bit versions of Microsoft SQL Server being used with Microsoft Dynamics GP.
**NOTE: Make sure to manually stop and re-start the SQL Server service itself, as we've seen where rebooting the SQL server does not resolve this error message like restarting the service does.
Hope this helps in the off change that you run into either of these errors when performing an upgrade of Microsoft Dynamics GP 2013 and/or Microsoft Dynamics GP 2015.
Thank you all and good luck with the upgrading!!