x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 12 replies
  • Subscribers 119 subscribers
  • Views 815 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
R Eiken

Crystal Reports 2016 error in custom report after Sage 100 2021.6 update

Posted By

First time in 12 years that the report I maintain is getting an error.

Failed to retrieve data from the database.

Details: s0000:[ProvideX][ODBC Driver][PVKIO]Data page header contains invalid record offset information. [Database Vendor Code: 109 ]

Any help is appreciated,

Richard Eiken

  • 0

    only using InvoiceHistoryHeader, InvoiceHistoryDetail, and InventoryMasterFile

  • 0 in reply to R Eiken

    Sometimes doing a "Verify Database" in the report can point at the issue.

    If you have a numeric parameter, there is a known issue related to those...

  • 0 in reply to Kevin M

    Verify Database, just comes back with "The database is up to date" and returns to error above after a couple of minutes.  Using Date fields to select range, What numeric parameter issues? Is there a knowledge base article?

  • 0 in reply to R Eiken

    The numeric parameter issue is related to CR, not Sage 100.  If you remove your parameter and the report runs, that is the test.

    By any chance is the report looking at a SQL View?  You might need to recompile the view, to correct column alignment... (for fields added by the upgrade).

  • 0 in reply to Kevin M

    Started a new report using just the Invoice History Header and Details.  It is tripping on a bad date field in Invoice History Header. I need instructions on DFDM or do I need to call support and have them walk me through it. I made a backup copy of the company files that I can use for testing.

  • 0 in reply to R Eiken

    Sage used to have a utility for fixing bad dates, but I can't seem to find it in the new KB.  Perhaps someone from Sage will post a link.

  • 0

    Interesting, I wrote this response a week ago, but it looks like it never posted. However, I still see it. Guess I will post it now:

    Might this be like the good old "Database Vendor Code: 9", indicating a bad date somewhere in the table?

    We used to jump through hoops to find the date (ALE, DFDM, pull into excel, etc.) but didn't Sage finally come up with a utility?

    Venturing down the rabbit hole that is the "new" KnowledgeBase, here are the hoops to jump through: Solution ID:  222924450019509

    Still looking for the utility, sigh.. The new knowledgebase makes me sad.. Maybe I imagined the utility.

  • 0 in reply to rclowe

    I may have finally found it: Solution ID:  240104231810823

    Where is the CheckDate Utility for Vendor Code 9 errors?

    Created on  | Last modified on 

    Summary

    CheckDate Utility for Vendor Code 9 errors related to Sage 100 KB 87257 "Error: "Unable to view" [name of report, register etc] Database Connector Error: [Database Vendor Code:9]" when printing a report or register with an invalid date" as well as other date errors.

    Resolution

    If you use third-party products that integrate with your Sage product, check with the vendor of your third-party product to ensure their product is fully compatible with this release. If you integrate with other Sage products, check with your business partner or Sage to ensure that these components are compatible.

    Important: The CHECKDATE utility is not included with your Sage 100 download, and must be downloaded and installed from the attached file below.

    • This utility will scan all Sage 100 data files for invalid dates related to KB 87257 and generate a text file with a list of invalid fields. The invalid date fields will need to be manually corrected using Data File Display and Maintenance.

    To execute this program, place the CheckDate program in the "..\MAS90\SOA" folder on the server where Sage 100 is installed.

    1. From file run, type the following SYZCON
    2. From the SYZCON window type RUN "CHECKDATE and press Return

    NOTE: This utility does not work with Sage 100 Premium. Use a SQL query that includes a function like ISDATE() to find the invalid date fields.

  • 0 in reply to rclowe

    Maybe I'm missing it, but I don't see the Checkdate file attached to the Knowledgebase articles.

  • 0 in reply to sued2

    Yes, I noticed that, too. Not sure if it was a casualty of the changeover of the KnoweldgeBase or if that was deliberately purged by Sage??

    Interestingly, I looked through my SOA folders for my demo systems (2017 - 2023) on my laptop and I found one in my 2021 system. 

    As a test I copied it over to my 2022 system and ran it. It seems to run.

*Community Hub is the new name for Sage City