OIPI Client re-install (AREV Specific)
At 27 SEP 2010 05:04:53PM James Foulkrod wrote:
My customer has one client PC that is suddenly getting bad results printing OIPI reports that it could always print before. Other PCs print the reports just fine even to the same printer that the troubled PC uses. I'm thinking a re-install of the OIPI client might fix the problem.
Can I simply run the oipisetup.msi to re-install it?
Thanks,
Jim
At 28 SEP 2010 08:16AM Jared Bratu wrote:
Go into the OIPINET subdirectory and install the version that was appropriate to your version of OpenInsight. Generally the file with the highest version number at the end is the most appropriate file. You can run that file to attempt a re-install. If an older version is installed you can remove it using the windows control panel before the re-install.
Does the print preview window display the correct results? What about the print driver version?
There aren't any open issues where OIPI goes bad and starts skewing the output but checking the driver and OIPI is worth a try.
At 28 SEP 2010 08:57AM James Foulkrod wrote:
Hi Jared,
I'll try the re-install as soon as I can access the client's machine. But let me answer your other questions in case it doesn't work. The print preview window does not display the correct results. The problem is the apparent paper size. When letter size Landscape is selected it appears that the paper size is about 3" height and 10" width. Portrait orientation shows an opposit problem.
This PC prints non-OIPI reports correctly and other PCs print OIPI reports correctly on this printer (a Brother MFC-8670DN).
This is a new problem on this machine - OIPI printed correctly on the Brother printer before.
Any suggestions?
Jim
At 28 SEP 2010 09:23AM James Foulkrod wrote:
Jared,
The client machine OIPISETUP folder does not have a msi file, just dll, xml, tlb and manifest files. Should I copy the newest .msi from the server to her machine?
Jim
At 30 SEP 2010 11:01AM James Foulkrod wrote:
Jared,
The client machine OIPISETUP folder does not have a msi file, just dll, xml, tlb and manifest files.
Should I copy the newest .msi from the server to her machine and run it from there?
Jim
At 30 SEP 2010 05:13PM [email protected]'s Don Bakke wrote:
Jim,
What version of OpenInsight is this?
At 01 OCT 2010 03:27PM Jared Bratu wrote:
This doesn't sound like the right folder. It should be called OIPINET, not OIPISETUP. It's in the same directory as the oinsight.exe process. This only applies to OI 9.x
Are you using OIPI (8.0.8 and earlier) or OIPI.NET (9.0 and above)?
At 04 OCT 2010 01:20PM James Foulkrod wrote:
The client Machines don't have an OIPINET folder. The OIPINET folder is on the server. The Client machines have OIPISETUP folder in their Program Files\Revelation Software folders. It contains:
OIPINET.dll
oipinet.dll.manifest
OIPINET.tlb
OIPINET.xml
The Server is running OI 9.1. The Application is Arev32.
When I run an OIPI report from the OI development I get this prompt:
"OIPINET may have been upgraded: your version3.3 and 4.6 found. You may wish to run the client installation process(clientsetup.exe) to install version 4.6 of OIPINet on this workstation."
The file clientsetup.exe is not on this workstation or the production system but it is on the GAAP accounting server.
Any suggestions?
Thanks,
Jim
At 04 OCT 2010 01:23PM James Foulkrod wrote:
The production server is actually running OI 9.0. Sorry.
Jim
At 04 OCT 2010 02:31PM Jared Bratu wrote:
9.0 Had some difficulty re-installing the client setup components. You should add/remove the client side components. This KB article applies to 9.0 through 9.1.1. It lists the 4 client side components that should be removed prior to re-installation.
Once the client side components are removed run clientsetup.exe on the workstation from the server where oinsight.exe is located. If no errors are posted you will have re-installed OIPI.NET and the rest of the client side components.