Hi All -
We are trying to upgrade a client from GP10 SP3 (10.0.1328) to GP10 SP5 (10.0.1779). DYNAMICS upgrades smoothly, but the 2 company databases are throwing errors. The first error we encounter is:
The stored procedure smGrantAccessOnAccountMSTR returned the following results: DBMS: 0 Microsoft Dynamics GP:
I tried restoring the databases from the backups we took prior to upgrading the databases. Once we were able to get past this error message, we hit the following trigger error message:
The following SQL statement produced an error:
CREATE TRIGGER [dbo].[zDT_IV00107U] ON [dbo].[IV00107] AFTER UPDATE AS SET NOCOUNT ON BEGIN UPDATE [dbo].[IV00107] SET DEX_ROW_TS = GETUTCDATE() FROM [dbo].[IV00107], INSERTED WHERE [IV00107].[ITEMNMBR] = [INSERTED].[ITEMNMBR] AND [IV00107].[CURNCYID] = [INSERTED].[CURNCYID] AND [IV00107].[PRCLEVEL] = [INSERTED].[PRCLEVEL] AND [IV00107].[UOFM] = [INSERTED].[UOFM] UPDATE [dbo].[IV40800] SET DEX_ROW_TS = GETUTCDATE() FROM [dbo].[IV40800], INSERTED WHERE [IV40800].[PRCLEVEL] = [INSERTED].[PRCLEVEL] END SET NOCOUNT OFF
ERROR [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid column name 'DEX_ROW_TS'.
Here is the full picture of what we had done prior to running Utilities.
We migrated DYNAMICS and 2 company full database backups from a SQL 2005 instance to another server. On the new server we installed a named SQL 2008R2 instance (there was already a default SQL 2005 instance). We went through the entire GP migration process (Captured SQL logins and ran the SQLLOGINS script against new instance of SQL/ran Dex_req against master/ran Grant against DYNAMICS and company databases/ran sp_changedbowner against DYNAMICS and company databases/changed database compatibility level to 100/ran Clear Companies script to remove reference of TWO/Fabrikam which we did not migrate). We created a separate ODBC that points to the new named instance of SQL 2008R2. There was already an instance of GP10 SP3 on the new server, so we applied SP5 to bring the software up to build 10.0.1779. We then mapped the Dynamics.set file to point to the migrated modified forms and reports from the original SQL server. After this we launched Utilities.
Any help you can offer would be greatly appreciated, as this upgrade is in process and needs to be completed in the next couple days. We are looking for fixes for both error messages. Thanks.
Cheers,
James.
