x Want to participate? Join the group to interact
Options
  • Replies 5 replies
  • Subscribers 42 subscribers
  • Views 3149 views
  • Users 0 members are here
Browse Forums
Announcements
68
topics
93
replies
Customization and Integration
262
topics
822
replies
Financials, Projects, and Administration
382
topics
843
replies
General Discussion
327
topics
836
replies
Installation and Technical Issues
335
topics
1k
replies
Manufacturing, Distribution, and Applications
341
topics
696
replies
Reporting and Analytics
123
topics
480
replies
KLou

Failed Upgrade: 7.40.10.0 (Jan 2014) + 2015 1099 to 2016 (7.70)

Posted By

Can somebody confirm this for me?

I'm working through test upgrades from 7.4.10 to the newly-released 2016 version.  Our DB (before applying the 7.4 2015 1099 Update) upgrades successfully, but if the 1099 update is applied will fail during the 7.6->7.7 portion. 

I then created a blank 7.4 DB and was able to replicate the issue on both sides:  Successful w/o 1099, unsuccessful with 1099.

The DBERROR.LOG looks something like this (for the blank DB):

<snip>

Loading C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.40\all_app.lst to mas500Blank_app ...
START TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.50 : 1/14/2016 4:05:08 PM

<snip>

END TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.50 : 1/14/2016 5:01:31 PM
START TIME FOR CLEANING DATABASE: mas500Blank_app : 1/14/2016 5:01:31 PM
END TIME FOR CLEANING DATABASE: mas500Blank_app : 1/14/2016 5:01:31 PM
Loading dbmupd.sql to mas500Blank_app...
Loading dbmcomp.sql to mas500Blank_app...
BCPing pre-processed database information...
B Start bcp of tdmTableColInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.50\ColInfo.bcp
B Finish bcp of tdmTableColInfoP
C Start bcp of tdmTableIdxInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.50\IdxInfo.bcp
C Finish bcp of tdmTableIdxInfoP
D Start bcp of tdmTableColInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\ColInfo.bcp
D Finish bcp of tdmTableColInfoP
E Start bcp of tdmTableIdxInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\IdxInfo.bcp
E Finish bcp of tdmTableIdxInfoP
Loading C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.50\all_app.lst to mas500Blank_app ...
START TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.60 : 1/14/2016 5:01:34 PM

<snip>

END TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.60 : 1/14/2016 5:56:38 PM
START TIME FOR CLEANING DATABASE: mas500Blank_app : 1/14/2016 5:56:38 PM
END TIME FOR CLEANING DATABASE: mas500Blank_app : 1/14/2016 5:56:38 PM
Loading dbmupd.sql to mas500Blank_app...
Loading dbmcomp.sql to mas500Blank_app...
BCPing pre-processed database information...
B Start bcp of tdmTableColInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\ColInfo.bcp
B Finish bcp of tdmTableColInfoP
C Start bcp of tdmTableIdxInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\IdxInfo.bcp
C Finish bcp of tdmTableIdxInfoP
D Start bcp of tdmTableColInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.70\ColInfo.bcp
D Finish bcp of tdmTableColInfoP
E Start bcp of tdmTableIdxInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.70\IdxInfo.bcp
E Finish bcp of tdmTableIdxInfoP
Loading C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\all_app.lst to mas500Blank_app ...
START TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.70 : 1/14/2016 5:56:41 PM

<snip>

Upgrading tapV1099Box: -- Script for tapV1099Box: APP,Load Script Asynchronously - OK; 6:50:58 PM
Upgrading CM Multiple Offset Accounts Enhancement: -- Script for CM Multiple Offset Accounts Enhancement: cmzda001 (Enter Bank Transactions)Load Script Asynchronously - OK; 6:50:59 PM
Upgrading customization metadata: -- Script for customization metadata: APPLoad Script Asynchronously - OK; 6:51:00 PM
------>Upgrading Tax Year (TY) 2015 1099 User Data(PSC): -- Script for Tax Year (TY) 2015 1099 User Data(PSC): APP
Microsoft SQL Server Native Client 11.0 Error 3604:
Error occured while moving TY 2015 1099 User Data, PSC.
------>Upgrading Tax Year (TY) 2015 1099 User Data(PSC): -- Script for Tax Year (TY) 2015 1099 User Data(PSC): APP
Microsoft SQL Server Native Client 11.0 Error 3604:
Error occured while moving TY 2015 1099 User Data, PSC.Load Script Asynchronously - OK; 6:51:01 PM
------>Upgrading Tax Year (TY) 2015 1099 System Data(PSC): -- Script for Tax Year (TY) 2015 1099 System Data(PSC): APPLoad Script Asynchronously - OK; 6:51:02 PM
END TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.70 : 1/14/2016 6:51:02 PM

  • Just curious if you (or your partner) have any customization around 1099 processing?  It looks like the processing is capturing data, but having a problem when trying to put that captured data back into the updated database.  Also, did you (or your partner) use the default script for upgrading, or a customized version of the Sage supplied script?

    The reason I ask is because the 7.4 -> 7.7 upgrade process was tested.

  • in reply to Ramon M.
    Hi Ramon,

    We don't have any customizations around 1099's. And this is using the default script.

    I did some digging, and found that I missed some DBERRORS toward the top of the 7.6->7.7 upgrade:

    Upgrading CM Multiple Offset Accounts Enhancement: -- Script for CM Multiple Offset Accounts Enhancement: cmzda001 (Enter Bank Transactions)Load Script Asynchronously - OK; 10:03:31 AM
    Upgrading Tax Year (TY) 2015 1099 tapVendor (BSC): -- Script for Tax Year (TY) 2015 1099 tapVendor (BSC): APP
    Microsoft SQL Server Native Client 11.0 Error 3604:
    Procedure expects parameter '@statement' of type 'ntext/nchar/nvarchar'.
    Upgrading Tax Year (TY) 2015 1099 tapVendor (BSC): -- Script for Tax Year (TY) 2015 1099 tapVendor (BSC): APP
    Microsoft SQL Server Native Client 11.0 Error 3604:
    Procedure expects parameter '@statement' of type 'ntext/nchar/nvarchar'.Load Script Asynchronously - OK; 10:03:31 AM
    Upgrading Tax Year (TY) 2015 1099 tapVend1099Submit (BSC): -- Script for Tax Year (TY) 2015 1099 tapVend1099Submit (BSC): APP
    Microsoft SQL Server Native Client 11.0 Error 3604:
    Procedure expects parameter '@statement' of type 'ntext/nchar/nvarchar'.
    Upgrading Tax Year (TY) 2015 1099 tapVend1099Submit (BSC): -- Script for Tax Year (TY) 2015 1099 tapVend1099Submit (BSC): APP
    Microsoft SQL Server Native Client 11.0 Error 3604:
    Procedure expects parameter '@statement' of type 'ntext/nchar/nvarchar'.Load Script Asynchronously - OK; 10:03:32 AM
    Upgrading Tax Year (TY) 2015 1099 tapVend1099Wrk (BSC): -- Script for Tax Year (TY) 2015 1099 tapVend1099Wrk (BSC): APP
    Microsoft SQL Server Native Client 11.0 Error 3604:
    Procedure expects parameter '@statement' of type 'ntext/nchar/nvarchar'.
    Upgrading Tax Year (TY) 2015 1099 tapVend1099Wrk (BSC): -- Script for Tax Year (TY) 2015 1099 tapVend1099Wrk (BSC): APP
    Microsoft SQL Server Native Client 11.0 Error 3604:
    Procedure expects parameter '@statement' of type 'ntext/nchar/nvarchar'.Load Script Asynchronously - OK; 10:03:32 AM
    Upgrading frl_acct_code: -- Script for frl_acct_code: APP, No Change,Load Script Asynchronously - OK; 10:03:34 AM

    Digging further, I see your name on the scripts. Based on above, I think that it's choking on the sp_executesql calls (which then obviously affect the original errors in the top post). I'm testing with some modifications to the upgrade script (usc_app.sql?).

    The 1099 tapVendor data is currently empty, but unfortunately, I expect to have some data in there (V1099FATCA) by the time I can push the upgrade.
  • in reply to KLou

    A problem has recently been discovered in the upgrade script. There are three lines that perform a

    exec sp_executesql '1099 related command text ...'

    command, which should be

    exec sp_executesql N'1099 related command text ...'

    The missing N to type the command text needs to be added. The default script SC_App.sql file in the 7.70 tree of the database upgrade utility can be modified by adding the N.  Similarly, the BSC_App.sql file could be modified if an installation was using a customized version of the upgrade utility.

    As usual, Sage cannot support user modifications (even if they are relatively simple).

     I suspect this will be addressed shortly.

  • I suggest you download the 2016 Database Upgrade utility again from the download site. It has been updated, and should address this issue.

  • in reply to Ramon M.
    Fabulous. Thanks to you and Tony for the help on pushing this change out.

*Community Hub is the new name for Sage City