999 code in OIPI (OpenInsight 16-Bit Specific)
At 06 MAR 2002 06:07:07PM Mike O'Neal wrote:
Greetings all:
I'm getting a 999 code in OIPI 4,1 when running a list statment from S/LIST 2.12. Previous posts indicate this is an installation problem with OIPI. I'm on an NT machine running 3.7.5. Tried uninstalling and installing several times, no luck. I also went through the (rather lengthy) manual un-install and re-install procedures, but still have that error. I also now have a mixture of the same .dll files in both my \SYSTEM and SYSTEM32 directories, with different sizes and dates for the same dll.
Any advice at this point would be *greatly* appreciated.
Thanks,
Mike O.
At 07 MAR 2002 02:35AM Tony Splaver wrote:
Hi Mike,
I am amazed that the manual uninstall and manual installation process did not fix this issue. You indicated that you are using OIPI 4.1, which means that you are using the 32-bit Professional version of the OIPI. Does the -999 error also occur when using the 16-bit version of the OIPI (by not calling the START32 message before running an OIPI report)? Does the error occur when running a simple OIPI report (not through S/LIST)? There may be a version conflict with the SET_PRINTER function – here are a few things to try:
1. You should run the latest OIPI 4.01 16-bit Standard installation first. This setup will install the correct version of SET_PRINTER (for both the 16-bit and 32-bit versions of OIPI, and it will also install the latest 16-bit version of the OIPI.
2. Then you should re-run the OIPI 4.1 setup to install the 32-bit version again.
3. If the -999 error still occurs with the 16-bit and 32-bit versions of the OIPI, then we may need to use the debug version of the OIPI to see if there is anything in the OIPI32.EXE that is causing this problem. This is somewhat unlikely, because the -999 error code occurs in the SET_PRINTER function when it cannot send messages to the OIPI32.EXE.
Tony
At 07 MAR 2002 01:48PM Mike O'Neal wrote:
Hi Tony:
Thanks! Re-installing 4.01, then re-installing 4.1 did the trick. The only anomaly was that during the 4.01 installation I would get a GPF if I tried to re-install anywhere other than into the C:\REVSOFT\OINSIGHT directory. I temporarily renamed my folder over to that, ran both setups, renamed the folder back to what I wanted it to be, and all was well.
Thanks again,
Mike O.
Oystein, thanks also for your earlier help on this