Sage 100

 View Only
Back to discussions
Expand all | Collapse all

Providex\ODBC driver internal error

  • 1.  Providex\ODBC driver internal error

    Posted 01-17-2019 12:38
    Getting this error all of a sudden at a client when trying to refresh a excel report.  He hasn't ran this report since end of Sept (so maybe not all of a sudden) LOL but never had issues before.  3 other tabs work fine and the one tab that is having this issue is the AR invoice history header and detail file of course. I am thinking a date issue but not sure how to find it.
    Any thoughts would be appreciated.

    ------------------------------
    Diane Ruth
    President
    Mooresville NC
    704-360-4363
    ------------------------------


  • 2.  RE: Providex\ODBC driver internal error



  • 3.  RE: Providex\ODBC driver internal error

    Posted 01-17-2019 14:56
    Thanks Wayne but don't have that issue.

    ------------------------------
    Diane Ruth
    President
    Mooresville NC
    704-360-4363
    ------------------------------

    Original Message


  • 4.  RE: Providex\ODBC driver internal error

    Posted 01-17-2019 12:54
    Run a fresh unfiltered query against the tables.  If you get full results, it is not bad data.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst, Munjal-White Consulting
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 5.  RE: Providex\ODBC driver internal error

    Posted 01-17-2019 14:53
    And if it is a date problem, Sage did release the date utilities a while back that you can run.

    ------------------------------
    Jeff Schwenk
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------

    Original Message


  • 6.  RE: Providex\ODBC driver internal error

    Posted 01-17-2019 14:56
    Humm as I said 3 tabs work and update but the history file does not. That is why I was thinking it might be the date but wasn't sure if that was the error I would getting.
    Jeff I will look for the date utility and try it. 
    Thanks all.

    ------------------------------
    Diane Ruth
    President
    Mooresville NC
    704-360-4363
    ------------------------------

    Original Message


  • 7.  RE: Providex\ODBC driver internal error

    Posted 01-22-2019 15:08
    KB 89700 https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=89700&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_DOWNLOAD_1&stateId=26648&cmd=displayKC&dialogID=1243223&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true

    ------------------------------
    ==================
    Rhonda McNamara
    Customer Success Manager
    Stewart Technologies, Inc.
    rsm@stewarttechnologies.com
    ------------------------------

    Original Message


  • 8.  RE: Providex\ODBC driver internal error

    Posted 01-23-2019 08:21
    See if you get anything when you turn on ODBC logging. It might help point you in the right direction.

    ------------------------------
    Todd Martin
    President
    MBA Business Software
    https://www.mbabsi.com
    Atlanta GA
    678-495-5712
    ------------------------------

    Original Message


  • 9.  RE: Providex\ODBC driver internal error

    Posted 09-20-2021 09:21
    Has anyone else had this "[ProvideX][ODBC Driver] Internal Error"?  I am seeing this in 2019v5, but only with 64-Bit Excel and it appears Diana Ruth is no longer active on 90Minds.

    ------------------------------
    Dan Burleson
    Software Consultant
    Connex Software
    Corvallis OR
    541-224-6642
    ------------------------------

    Original Message


  • 10.  RE: Providex\ODBC driver internal error

    Posted 09-20-2021 10:10
    Dan, yes and it is random. Sometimes on simple queries, sometimes on more complex, large result sets, small result sets. There is no consistency in my experience. 

    When it happens, we have them go back to 32 bit Office and no more issues. I think there is an issue in the 64bit ODBC driver.

    ------------------------------
    Eric Lunceford
    First Mate Business Solutions
    Oklahoma City, OK
    877-880-8960
    https://www.firstmatellc.com/
    ------------------------------

    Original Message


  • 11.  RE: Providex\ODBC driver internal error

    Posted 09-20-2021 10:14
    There is a pre-req for the 64-bit driver install.  Did you install it through the launcher, or just use the MSI directly?  (You may have missed something it needs that way).

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 12.  RE: Providex\ODBC driver internal error

    Posted 09-20-2021 16:59
    Diane has retired

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------

    Original Message


  • 13.  RE: Providex\ODBC driver internal error

    Posted 09-20-2021 22:05
    Thanks Kevin and Eric for the suggestions. The 32/64 bit ODBC was installed from the 'Autorun.exe' (and repaired). Diane was responsive even in retirement. Doing an ODBC trace might produce some information, but I don't have ready access to the failing machines and fishing is risky at this point.  Eric's experience will likely lead to my recommendation as well. I'll report back the final solution.

    ------------------------------
    Dan Burleson
    Software Consultant
    Connex Software
    Corvallis OR
    541-224-6642
    ------------------------------

    Original Message


  • 14.  RE: Providex\ODBC driver internal error

    Posted 09-24-2021 04:07
    Edited by Dan Burleson 09-24-2021 04:08
    I did find a work-around for 64-Bit Excel that avoided the "Internal Error" yet retained the performance advantage of the C/S ODBC driver. This is only happening for large tables that have expanded into a 2nd file. You can see my post on the Sage Community here. I found that the behavior wasn't random once I better understood the relationship between the SOTAMAS90 DSN and Excel's connection string. Also, note that the C/S ODBC connection string parameters in the Excel file's Connnection Properties can be active even though C/S ODBC had been disabled for the user.

    ------------------------------
    Dan Burleson
    Software Consultant
    Connex Software
    Corvallis OR
    541-224-6642
    ------------------------------

    Original Message


Related Content