After performing SQL migration I had this top level list of things I had to think about, so this is just a private list put here of things that you might need to think about when migrating from one SQL server to another. This is for my environment, if you use clustering and other features of SQL server, then you will have some more to add to the list. However hopefully this will help me next time and may provoke some thoughts to others working on a similar project.
In this case reporting services is co-hosted on the server as is eConnect service and some IIS API end points.
They are in random order, there are many interdependencies.
- Linked Servers, Script out any linked SQL servers and re-create on the new server.
- SQL Jobs needs scripting out and re-creating on new server. Any reporting services jobs need removing and let reporting services rebuild the schedules when it the service starts. References to server names needs checking within the scripts.
- Maintenance plans need moving to the new server.
- SQL Logins needs scripting out and moving to the new server.
- TempDB files need creating with appropriate number of data files for the server and run on appropriate disks.
- Replication needs scripting, removing, then rebuilding on the new server. Change server names in replication as has to use the actual server names not aliases.
- The user databases needs need backup from old server and restore to new server.
- Reporting services, if installed needs keys applying and configuring with new host names in .config file, restore the encryption keys from the old server.
- Back up devices needs scripting out and recreating on the new server.
- eConnect Service needs installing on the new server.
- eConnect Config for service needs updating for changes to port numbers and transport protocol used (if not using defaults).
- Any IIS web services needs migrating to new server (if any installed).
- Script out extended events and recreate on new server.
- SSIS packages need exporting and importing to new sever.
- SQL Operators need scripting out and moving to new server.
- After migration switch DNS aliases to point at new server from old (including reporting services and any iis site alias if applicable).
- Check Database Collations as set correctly for new sever vs old.
- Compare side by side new and old SQL server settings pages for all settings.
- Start SQL server Jobs after migration and once old server is out.
- Check virtual machine settings after migration to ensure full resources have been restored to the virtual machine.
- Ensure Full text index is installed (if required).
- Ensure SSIS is installed (if required).
- Ensure Reporting Services installed (if required).
- Install VMWare SCSI drivers for performance reasons.
- Check firewall settings on machine are the same between old and new, including application settings.
- Duplicate any windows file shares on the new server to be the same as the old server, including share and NTFS permissions.
- Double check any local users and user permissions.
- Install Dynamics GP workflow server CLR objects on the server using stored procedure DYNAMICS..wfDeployClrAssemblies
- Migrate mail profiles from old to new server.
Application folder for Dynamics GP moved
The default installation package location moved for the Dynamics GP application to
C:\Program Files (x86)\Microsoft Dynamics\GP
for releases after GP2018. Previously it was in C:\Program Files (x86)\Microsoft Dynamics\GP2018, where the GP2018 was replaced with the version of GP. As the versions are no longer linked to years this was dropped as a folder naming pattern.
Create installation package utility
The Create Installation Package utility, found on the GP installation media main menu, did not get this memo about the folder change, or it introduced a bug to be more accurate. We find it broken since this change was made. After creating an installation package, and then using that installation package to install GP, the folder is not “C:\Program Files (x86)\Microsoft Dynamics\GP”, instead it is “C:\Program Files (x86)\Microsoft Dynamics\GP2018”, as it was in the previous version.
I’ve just tested this with the GP2019 fall release, and that release (V18.4) still will install the application into the “wrong folder”.
When the package is built we are prompted for the folder location:
As can be seen the location is correct (C:\Program Files (x86)\Microsoft Dynamics\GP\).
What makes things worse it reports that if you specify the local location for the dictionary, the resulting launch file (.SET) will then happily mix the file locations, resulting in mixture of folders in the .SET file for GP and GP2018!
I stumbled on a fix or work around on Ian Grieve blog with this comment at the bottom of the hands on guide to using the Create Installation Package utility (which if you are not familiar with this, then that is a good guide to go by:
Hands On with Microsoft Dynamics GP Fall 2021 Release: Create Installation Package
So if we try this by removing that trailing slash as shown below, then indeed the application ends up, correctly in the GP folder rather than the GP2018 folder! I have no idea how whoever it was discovered this but well done!
See how the slash has been removed, it works!
Interesting issue with upgrading Microsoft Dynamics GP.
The upgrade stopped at the above step
Microsoft Dynamics GP Utilities install/upgrade failed
Turns out this was linked to deleting companies from this instance of GP, and the delete leaving orphaned records in the DYNAMICS..SyCompanyImages table.
The syComanyImages table holds the images used by word template reports, that are uploaded using the form below:
Reports>>Template Configuration>>[Images] button
There was an orphaned record from the deleted company in the table that is used to back that form. The extra record was removed using the following script:
DELETE FROM Dynamics.dbo.syCompanyImages
WHERE (RELID/65536) NOT IN
SELECT (CMPANYID) FROM Dynamics.dbo.SY01500 )
Note that I don’t understand how this table works entirely, other than its holding a binary blob of the image, that is referenced back in this bizarre /65536 formula. I would check what records will be deleted before actually running this script.
Note that It is important to have ran ClearCompanys.sql - Script that will clear out all entrys in the DYNAMICS
database referencing databases that no longer exist on the SQL Server, BEFORE running the above script. This is to make sure that SY01500 only has companies that have databases associated with them.
After moving to from Office 13 to 365 the following error appears when users export from Dynamics GP smart lists to Excel.
We found a problem with some content in 202222-1232S9.XISX. Do you want us to try to recover as much as we can? If you trust the source of this workbook, cick yes
Excel was able to open the file by repairing or removing the unreadable content.
Repaired Records Format from /xl/styles.xml part (Styles)
The file generated as a log says pretty much the same thing
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<summary>Errors were detected in file ’C:\Users\***\AppData\Local\Temp\202222-123259.XLSX’</summary>
<repairedRecord>Repaired Records: Format from /xl/styles.xml part (Styles)</repairedRecord>
By adding the following line somewhere in the Dex.Ini file (normally in the Data subfolder of the application folder of GP), resolved the issue in this case.
This ini switch is not compatible with the GP web client if you are using that.
Undocumented DEX.INI switch cuts down SmartList export times to Microsoft Office Excel
Smartlist: Exports slowly to Excel – Part 1