Explorer and Analyze Error after Upgrade

SOLVED

Getting an error when launching Explorer - 'count' must be non-negative.  Parameter name:  count.  I have rebuilt the view several times and am wondering if anyone has narrowed down what's going on with this error.  I thought it might be bad data but maybe not...  Any suggestions?  Sage suggested rebuilding the view which I've now done several different ways...  I've tried tracing it and it seems like it's not a SQL error.

Thanks John

Parents
  • 0

    I am having the same issue.  I found ID:54188 in the Sage Knowledgebase but I don't have a view in the failing view.  The view was working before the upgrade from MAS 500 ERP 7.40.3.0 to Sage 500 ERP 2013 October 2013 version 7.50.4.0.  The view runs in SQL Manager and the data looks good.

    It would be good to have more information from sage on the cause.

    Rich Garrett

    DSG, Inc.

  • 0 in reply to Rich Garrett
    verified answer

    I found my issue.  I had created a view for a table that a third party developer created for Sage 500.  The table contained a field weight.  Weight is not a reserved word in SQL but it is part of the MS SQL syntax.  I tried a number of different adjustment and have found a work around.

    I cleared Weight from the Permanent Column on the Column Mapping Tab.  Then typed Weight in the Override Caption.  Now it works.

    Rich Garrett

    DSG, Inc.

  • 0 in reply to Rich Garrett

    Rich - That is definitely the answer in some cases.  We found quite a few problems besides that though with views and how they are defined in Maintain Business Insights Views.  However we were able to fix them by either rebuilding the view or changing it in Maintain BI Views.  I'm pretty surprised this hasn't come up before.  This would make a good blog post (hint hint Sage).  Also note that some of the standard views in Maintain BI Views won't save unless you fix the problems in the meta data (Customers is one example).

Reply
  • 0 in reply to Rich Garrett

    Rich - That is definitely the answer in some cases.  We found quite a few problems besides that though with views and how they are defined in Maintain Business Insights Views.  However we were able to fix them by either rebuilding the view or changing it in Maintain BI Views.  I'm pretty surprised this hasn't come up before.  This would make a good blog post (hint hint Sage).  Also note that some of the standard views in Maintain BI Views won't save unless you fix the problems in the meta data (Customers is one example).

Children