2 Replies Latest reply on Aug 8, 2017 5:10 PM by cjtx

    Run-time error '62' after VX2.2 upgrade


      Hoping to move from VX.1.1 to VX2.2 soon but for some reason 2.2 doesn't like a couple of our very important Visual Basic scripts/utilities.

      All the other scripts work fine.  Both of them showing an error of input past end of file:








      Was wondering if anybody had any similar issues with things breaking on the upgrade?  I'm guessing/shooting in the dark here but speculating that 2.2 uses some newer Library/DLLs/etc.?  Or maybe it interacts with the automation objects different from 1.1,  or?

        • 1. Re: Run-time error '62' after VX2.2 upgrade

          If your application/script will run at all, it's not a dll problem. If they fail on startup, it may be something to do with the dlls. I had to replace all the references in my compiled applications when going to .2.2, as the dlls are all different and the previous ones (from .1.x) are not compatible with the .2.x release.

          1 of 1 people found this helpful
          • 2. Re: Run-time error '62' after VX2.2 upgrade

            Input past end of file error was caused by an empty txt file that the script uses as an input.   The affected scripts use icdb2bom.exe.  I had only XENTPVX.2.2_esdm_win64 package installed when getting the errors. This package didn't have icdb2bom.exe and learned from Mentor it's included with Design Capture release.

            Installing the Design Capture package after  XENTPVX.2.2_esdm_win64  did not work so I uninstalled everything then installed in the following order:






            Everything now works great!