OnBase Client 13.0

Overview

Hyland Software's OnBase is a system for managing documents stored electronically, usually known as a document imaging system. This is currently a Windows client/server application, used in many offices on campus.

Product Details

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

OnBase is sold in modules, of which we have only a few. Here is the manufacturer Web site. The Web site requires an account to login to access support documents, including user manuals.

This software is supported by the EIS group in ITS. It uses a Carleton-based Microsoft SQL Server database, hosted on (as of Friday August 22) onbasedb.ads.carleton.edu.

System Requirements

The OnBase Client hardware requirements are so low that any college-owned computer purchased and setup in the last four years should qualify.

The OnBase Client requires these software components:

• the Microsoft .NET Framework 4 Client Profile (or Full), or a later version;
• the Microsoft Visual C++ 2010 x86 (32- bit) Redistributable (update via Windows Update or WSUS);
• a 32-bit System ODBC DSN (Data Source Name), as created in the 32-bit ODBC Administrator.

Those first component is part of every Carleton build of Windows 7 and later, and there is an installer available in the KBOX user portal . The last two have been added to the KBOX installer for the OnBase Client. There is also an optional Virtual Print Driver component, which we have added to the KBOX installer.

The OnBase database (ODBC) connection works only from Windows computers joined into the ADS domain, and only when the user is 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-joined computers when using an ADS login that is not its.

The OnBase Client is expected to work with Microsoft Office versions 2007, 2010, and later.

Licensing Information

The general OnBase client, and the Virtual Print Driver, are freely distributable on campus. Specific stations will be licensed for indexing and for scanning documents into the system.

Licensing Restrictions

None for OnBase client

Usage Restrictions

None for OnBase client

Home Use

It is not recommend that this client be installed on non-college-owned computers. Later in summer 2012, it will be available from off campus via Citrix XenApp and/or XenDesktop.

Lab and Classroom Availability

This is administrative software not used in labs or classrooms. It is installed on all PCs in the ITS Training Room.

Installation Instructions

College Owned Equipment

The Hyland OnBase Client 11 installer is available from the KBOX user portal for all users.

Step by step instructions for installing Hyland OnBase Client 11:

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 desktop.
8. Launch the OnBase client. It should launch without a login screen, using the context of the current Windows login.
   1. 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.

/wiki/spaces/itskb/pages/26133059 is the ITS restricted installation information.

Labs and Classrooms

To request this software be installed on a refreshing lab/classroom contact xxx

Personal Machines

Not applicable.

Who To Call

For OnBase questions, call the Help Desk at x5999.

Questions, Tips and Tricks

Technical Troubleshooting

During installation of the Virtual Print Driver, if you are asked whether to install this driver, uncheck "Always trust..." then answer Install. As of Wednesday June 13, the KBOX installer was modified and this prompt should no longer appear.

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 11.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 11.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 (Win7) "C:\ProgramData\Hyland Software" or (WinXP) "C:\Documents and Settings\All Users\Application Data\Hyland Software", where all standard users should have full permissions. (This will not be true for Citrix XenApp/XenDesktop environments.)

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:

1. Go into Properties on the shortcut, and remove the "-AL" from the Target string, if it's present.
2. Double-click the OnBase shortcut to bring up the OnBase login screen.
3. On the right-hand side, just above where you type you username, there is a drop-down box for the ODBC connection.  It probably says "ONBASE".  Click the down arrow to bring up the selection list, and choose "Onbase-production".  Continue to log in, using your old OnBase password.
4. Under the User menu, select for "Workstation Options".  (Some users may not have this available to them.  If that happens, we'll have to send someone over to fix things.)
5. In the "Startup" tab of Workstation Options", there is a drop-down for Default Database Source.  Choose "Onbase-production" and click Save.

Go back to the shortcut Properties and add a space and "-AL" to the end of the Target String (see above).

If OnBase launching results in an error message, "(Autologin) No matching usergroups were found–access denied", make sure you are logged into the computer as a user who can run OnBase; the ITS account is not one of these.

Right now, on 64-bit Windows, the OnBase installation is failing at the vcredist step. SNissen is aware of this and is working on a fix.

Miscellaneous Information