Printing Problems - Reports Module

<< Click to Display Table of Contents >>

Navigation:  Reports >

Printing Problems - Reports Module

Previous pageReturn to chapter overviewNext page

Q. I get VSprint7.ocx and VSpdf.ocx error

A. You must run ITMS for the first time (step 3) as an administrator (or a user that has administrator privileges) or you will get these OCX errors. Log off the PC and logon as the computer’s administrator and run iTMS again. This also applies to a terminal server installed with iTMS.  Additionally, you should print a document once as the administrator.

Q. Can I print reports when I access iTMS via a remote session (Terminal Server)?

A. Terminal server sessions need to be setup by a qualified systems administrator. There are a number of company specific network file and print options available in Terminal Server that cannot be addressed in this document. Generally, print services can be configured to print documents generated by iTMS. There are limitations on printing from the Reports module remotely.

Q. What is a SYS1000 error in OI Debugger screen?

A. These types of error are most commonly caused by a network (LAN) dropping out or disconnecting the workstation from its “server”. It is paramount that all iTMS workstations are supported on a correctly functioning Network (LAN).

Q. When I print from iTMS it includes a watermark “Evaluation Copy”

A. It means that the shortcut on the windows workstation to iTMS is not set up correctly.

To rectify this, follow steps outlined in step one and three of “Setup iTMS on a workstation” procedure.

 

Q. Init_Error 5: Cannot print an invoice error init_5 reported or unknown printer error

A. Error message init_5 cannot print invoice, two instances of ITMS have been opened.

First close down ITMS, then start the ‘Task Manager’, click on the “Processes” tab and click on the “Image Name” column header to sort file

order. Look for two instances of OIPI32.EXE

 

 

Delete one instance, if the operator says they cannot find the OIP132.EXE, close down computer and restart.

 

Q. Error: ODBC.dll missing. OINSIGHT locked by another.

A. CLT361 is not installed.

 

Q. iTMS locks up when I print

A. Try printing something else – to see if it is an index associated with the data.

A. Try printing the same document when logged in as the same user on another computer – means it is definitely the computer they were using.

A. Try selecting an alternative printer – see if it is the printer driver.

 

Q. I get access violation when printing from reports (OLD VERSIONS OF iTMS)

A.When running old versions of iTMS on Windows XP and above you will get Access violation errors when printing for the first time each day or logon.

Just ignore the error and print again.

The user will also get an error registry of SSUTIL.OCX > this can be ignored.

The program needs to be updated to version 8.

 

 

 

Last Revised: 18/08/2010 SJ