Versions Compared

Old Version 4

changes.mady.by.user Sande Nissen

Saved on

compared with

New Version 5

changes.mady.by.user Sande Nissen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

(under construction...)

Table of Contents

...

The client version on most machines is version 13.0 SP2 [13.0.2.667]. The client version 13.0 KBOX installer includes the necessary Microsoft Visual C++ 2010 redistributable and the Virtual Print Driver (VPD). (See below for detailed requirements.)

...

  1. Log in to the KBOX user portal.
  2. Click on the Software Library tab
  3. Click on the link to Install Hyland OnBase Client
  4. Click Install Now
  5. There will be a cmd.exe window and a series of dialog boxes with progress bars.
    1. If the cmd.exe window goes away relatively quickly, the workstation may need to have the .NET Framework 4 installed first.
    2. The cmd.exe window will say "ignore errors until further notice", and then several errors will pop up as it attempts to uninstall the old client.
    3. It will then say "errors are relevant again", but there will be one error that comes up virtually immediately that is very much like the previous errors. This one error is safe to ignore.
  6. You may or may not be presented with a dialog box about installing the Hyland Virtual Printer Driver. If prompted, install the driver.
  7. When the installation is finished the cmd.exe window will disappear and the OnBase Client shortcut will appear on the desktopPrograms menu.
  8. Launch the OnBase client. It should launch without a login screen, using the context of the current Windows login. If an OnBase login screen is displayed, you probably tried launching it from a shortcut you created previously. That shortcut will need to be re-created, so delete that old shortcut.

Here is the ITS restricted installation information.

...

Technical Troubleshooting

During installation of the Virtual Print Driver, if you are asked whether to install this driver, uncheck "Always trust..." then answer Install.

If you have problems with the OnBase Client installer, first try uninstalling every trace of any previous OnBase or Hyland software, files, registry settings, and ODBC data sources. The KBOX installer runs a batch file called uninst.bat that tries to do this, but it could have missed something.When installing over the previous version 9.2, a few problems have been seen that may not be handled correctly by the KBOX installer. First, this 13.0 installer will not run until the 9.2 client has been uninstalled. Try uninstalling the Hyland OnBase Client from Control Panel->Add or Remove Programs. If the uninstall process stops with an error 1606, something about not being able to find \\apps.its.carleton.edu\apps\Windows\OnBase\Help\ , contact Sande Nissen for a possible fix. If that fix does not work, you can use this Microsoft tool: http://support.microsoft.com/mats/Program_Install_and_Uninstall .

Second, after a successful install of the 13.0 client, some previously existing files may not have been updated. Check that every "OnBase Client" shortcut on the desktop or under the Hyland start menu has a command line that ends in "-PRINTMON -AL". (You may have to add the -AL). In the shared onbase32.ini file (see locations below), make sure that the DefaultDataSource= line says DefaultDataSource=OnBase-production, not DefaultDataSource=ONBASE.

To check the ODBC data source, as a local Windows Administrator run the ODBC Administrator (odbcad32.exe). (On 64-bit Windows, you must run the 32-bit ODBC Administrator from c:\windows\SysWOW64\odbcad32.exe.) Choose the System DSN tab, and look for OnBase-production. If you can see this Data Source Name (DSN), select it and choose Configure. On the second screen at the bottom, the login ID should be VIEWER and you can enter the password of ODBCsetup, then choose Next twice, then Finish. On the final summary screen, use the Test Data Source... button at the bottom left to see if the ODBC connection is working. The ODBC connection appears to work only with Windows computers joined into the ADS domain, and only when logged into such computers with an AD-based login (e.g., ADS\snissen); in addition, the ADS\its account does not seem to work. Therefore, the OnBase Client will only work on ADS computers when using an ADS login that is not its.

Delete any c:\windows\onbase.ini file and make sure that there is only one onbase32.ini, hidden or not, on the computer, in "C:\ProgramData\Hyland Software", where all standard users should have full permissions. (This will not be true for Citrix XenApp environments, where every user's profile will have its own onbase32.ini file.)

The most difficult problem we saw was when Windows 7 tried to virtualize older versions of the OnBase client because this logged-in user did not have full permissions to the shared onbase32.ini file in "C:\ProgramData\Hyland Software". When Windows 7 virtualizes an application, it creates a copy of any files the user cannot access in a hidden directory under their local userprofile (C:\Users\username\AppData\Local\VirtualStore), and then silently redirects any references to the shared file to the copy in the user's profile instead. So you end up with multiple onbase32.ini files, and it's hard to tell which one is in effect. It's important that non-Citrix users do not use virtualized copies of onbase32.ini, but that they use the shared onbase32.ini to which they have full permissions.

If OnBase prompts for a login upon launching after the upgrade, it means your shortcut did not get updated.  Right-click on the shortcut and select Properties.  At the end of the Target string, add a space and "-AL" and then click "OK".  The target string should look like:

"C:\Program Files\Hyland\OnBase\obclnt32.exe" -PRINTMON -AL

If, after the upgrade, OnBase fails to launch with the above ODBC error, follow these steps:

...

Miscellaneous Information

.