×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

(OP)
Hi there,

On Windows10, MSSQL2014 I´ve got installed version 56 of SAGE 300 ERP. Trying to convert data from accpac version 55 to 56 and the error below comes up. Note that I Run Data Integrity when found this error for the first time and didn´t work. Any idea on how to sort this out? Below is the full error:

"Bank Transaction Header. Database error (operation=REV-BROWSE, error=0)."

For further details, please find enclosed the ScrnSht of the error.

Regards,
Honorio

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

You'll probably need to turn on rvSpy to capture what's happening during the conversion to cause the error. Can you purge some of your older transaction history before upgrading?

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

(OP)
Hi Djangman,

After running RvSpy discovered two tables that was causing errors (BKTRAND and BKTRANH). Purged the older history as you said and converted the data with no errors. And placed the history back after conversion.

Now, I'm litle doubt about if won't this cause errors in the future?

Please, advise.

REGARDS,
Honório

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

"And placed the history back after conversion." Tell me you didn't copy the purged data back?

Sage 300 Certified Consultant

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

(OP)
Hi Ettienne,

Ecxatly, that's what I did, I copied the purged data back to where is was after conversion.

Regards,
HB
Sage 300 Certified Consultant

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

That's not a good idea, why would you do that?

Sage 300 Certified Consultant

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

(OP)
Of couse it´s not. Any different idea?

Will be too much appreciated

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

Just leave the purged data out. You will most probably run into issues with the next upgrade.
Also in newer versions the bank rec slows down drastically if you do not purge the history.

Sage 300 Certified Consultant

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

(OP)
Hi,

I noted some issues with my W10 OS and decided to reinstal and downgrade MMSQL from 2014 to 2012 according to the information below:

Official reply from Sage: MSSQL2014 is not not officially supported.

"Sage 300 ERP 2012 has not been tested or certified with Microsoft SQL Server 2014. So it is not officially support by Sage. If you would like to use Microsoft SQL Server 2014 with Sage 300 ERP, you will need to upgrade to Sage 300 ERP 2014. Sage 300 ERP 2014 officially supports Microsoft SQL Server 2014"

After that I could upgrade to Sage Version56.

Thanks.

RE: Database error (operation=REV-BROWSE, error=0) when upgrading from SAGE 300 ERP version 55 to 56

Known issue
You don't need to downgrade SQL to 2012. Edit the db and set the compatibility level to SQL Server 2012.
Once you have converted you can bump it back to 2014.

Sage 300 Certified Consultant

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close