Navigate
Wasp Helpdesk
  • Register

  • or
  • Login
    Need a password reminder?
or
Contact Us
  • Get in touch

    Send us an email

  • Start a chat session

  • Knowledgebase Read help articles
  • News News & updates
  • Contact Us We are here to help
  • Training View our options
  • Product Sunsets Non-Supported Products
Barcode System Consult
Barcode Printer Consult
Barcode Label Consult
  • Portal
  • Knowledgebase
  • Discontinued Products
  • InventoryControl
  • Version 7
  • InventoryControl: The Inventory Activity Report gives a "Failed to open a rowset" error
Subscribe Download PDF

InventoryControl: The Inventory Activity Report gives a "Failed to open a rowset" error

Jason Whitmer
2025-01-07
in Version 7

Symptom: When trying to open the Inventory Activity Report, I get a "Failed to open a rowset" error. Other reports open properly.

icv7-inventory-activity-rowset-error.PNG

Crystal Report Windows Forms Viewer

Failed to open a rowset.
Details: ADO Error Code:0x
Source: Microsoft SQL Server Native Client 11.0
Description: Incorrect syntax near the keyword 'CONVERT'.
SQL State: 42000
Native Error:
Failed to open a rowset.
Error in File C:\Users\[user]\AppData\Local\Temp\Inventory Activity Report {6B1B697F-EA2D-4D59-8525-16A6442939E1}.rpt:
Failed to open a rowset.

Resolution: Please first make sure you are on version 7.3 or newer by checking Help > About. If you need to download the current version, the installer is here:
https://dl.waspbarcode.com/wasp/InventoryControl7.exe

Once you are on the current version, please download and extract this file on the database server machine:
https://dl.waspbarcode.com/wasp/supportfiles/InventoryActivityReport.zip

If you are running the Enterprise edition, you may need to edit UpdateInventoryActivity.wql with Notepad or a similar text editor to enter the correct SQL instance and account information.

Run UpdateDB.bat to execute the database script. Then copy Inventory Activity Report.rpt to C:\Program Files (x86)\Wasp Technologies\InventoryControl\Reports on all machines where the client program is installed, overwriting the original report file there.

If this does not correct the issue, ensure that the files were extracted from the downloaded zip file, rather than running from within the compressed folder. If the error still persists, please contact support and send us the wql.log file created in the directory where you ran UpdateDB.bat so we can determine why the script failed.

Rate the quality of this page

This page was helpful :) :( This page was not helpful

3 of 12 people found this page helpful


Quick Jump
  • Wasp Helpdesk
  • Knowledgebase
  • News
  • Contact Us
Top
Helpdesk software provided by Deskpro