LOADING STORED PROCEDURES - Create_Requester_Procs_cursor

Technorati Tags: gp 2013,upgrade,cursor error

Recently I did an upgrade from GP2010 to GP 2013 R2 (build 1745) and ran into a variety of problems.

I thought I’d share them here, in the event someone else is faced with the same issues.

Some background on the upgrade, we switched about everything you could:

 

1. Switched SQL Server physical machines.
2. Moved from a physical machine to a virtual server.
3. The names of the servers, and the SQL server changed.
4. Moved from Server 2008 to Server 2012.
5. Moved from SQL 2008 R2 to SQL 2014.
6. Moved from GP 2010 to GP 2013.
7. Moved an eConnect web commerce application.
8. Moved AVALARA’s web service.
9. Several 3rd party products were involved.

After several attempts to do things that did not solve the problem, the following DID solve the problem. My thanks goes out to fellow MVP Richard Wheeler who gave me the tip to shrink the transaction log.

1. Restore the databases to the new server
2. Execute the Upgrade scripts suggested by Microsoft
1. Account_Framework_Validation.sql
2. Check_Workflow_Status.sql
3. eConnect_Out_Setup.sql (this is really not necessary)
4. Invalid_Records_POTables.sql
5. Payroll_Work_Tables.sql
3. Truncate the eConnect_Out_Setup table
4. Shrink the transaction log of the target databases:
1. DBCC SHRINKFILE ('DB_Log.ldf', 1), etc;
5. Install Dynamics 2013 on the new Server
6. Update the tables using DynUtils
7. Import the eConnect_Out_Setup table records that were previously removed in step 3.

You most likely do not have to complete all of the above steps. But it worked for me, so I stopped.

I had done several upgrades before this one and never had a problem. I guess I just got lucky this time .

Until next time,

Leslie