Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    4
  • Subscribers subscribers
    9
  • Views views
    2408
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Rumba ODBC driver on Windows 10

MigrationDeletedUser

For the last couple years I've been using the Rumba ODBC driver to allow an application I wrote to receive and send data to our AS/400 over an ODBC connection. I recently wiped my computer and did a fresh install of Windows 10 (I was previously on 7) and now I can't get the ODBC connection working.

I get an ODBC error message saying "Driver not capable" when my app attempts to use the connection.

I thought maybe the Rumba version wasn't compatible with Windows 10 so I installed a trial version of Rumba 9.4.1 (I was using 9.2) to see if that solved the problem and the error message changed to 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'

Is there a specific version I need that works with Windows 10? Or is it possible the setup process is different from 9.2 to 9.4.1?

Thanks!

Labels:

Rumba
  • 0  

    Hi,

    generally it should work with your RUMBA version under windows 10.
    Since you are not getting an architecture mismatch between the Driver and your Application I assume your application is a 32bit Application, right ?
    Try to open the Rumba AS/400 Filtransfer and establisch a connection to your AS/400.
    The Rumba Optimized Server ODBC driver is  incorporated in the AS/400 File Transfer subsystem.

    Using the ODBC Administrator should give you more information , turn on tracing and try your application and look at the log file. Your trace will show SQL_ERROR instead of success

    AS400FTX        31c4-4584 EXIT  SQLAllocEnv  with return code 0 (SQL_SUCCESS)

    HENV *              0x00C4E0C4 ( 0x0130EF30)

    AS400FTX        31c4-4584 EXIT  SQLAllocConnect  with return code 0 (SQL_SUCCESS)

    HENV                0x0130EF30

    HDBC *              0x00C4E0C8 ( 0x075F2D58)

  • 0
    When I log into the Rumba AS/400 File Transfer app, it gives me an error that says "Undefined error (1.0). Call your service representative." Even with tracing enabled, nothing is logged.
  • 0  
    I have Rumba 9.5 , ODBC works out of the box.
    But it seems that your version needs a hotfix to resolve the issue.
    Please contact the Micro Focus Supportline and report the problem with "Undefined error" in As/400 File Transfer.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.