getting OIPI -5 (OpenInsight 32-bit Specific)
At 21 MAY 2003 04:30:34PM Ray Chan wrote:
We are running OI413 and W2K Services.
Periodically we are seeing an OIPI error message of -5 when we are setting the Set_Printer("INIT"….) statement.
We can see that OIPI is running in the TASK Manager. Does anyone have any suggestions as to what we should be looking for.
Don't know if OI413 is causing this, but we never saw this until recently when we upgraded from OI412 to OI413.
Thanks for any comments and/or suggestions,
Ray
At 21 MAY 2003 11:12PM Donald Bakke wrote:
Ray,
Are you using S/List as well as custom OIPI reports?
dbakke@srpcs.com
At 22 MAY 2003 12:57AM Ray Chan wrote:
Are you using S/List as well as custom OIPI reports?
We do use S/List as well as custom OIPI. However, we are seeing this when using just plain ol'OIPI. Again, it's not completely reproducible. As I said it, it occurs periodically. That is, in the same OIPI report it will print fine, then mysteriously, it won't, then it's okay again after we logoff OI and come back in.
We thought we were losing the OIPI.EXE because that's what we thought we saw one time (or didn't see). However, this last time when I looked at the Task Manager OIPI.EXE was there ;-(
I have a strong suspicion that this may be related to OI4.13 since we never saw this until after we upgraded from OI4.12 to OI4.13. My guess only.
Any ideas or suggestions.
Ray
At 22 MAY 2003 01:41AM Donald Bakke wrote:
Ray,
Can't say we've ever seen the OIPI get lost in any version. However, we are experiencing repeatable problems when printing plain old OIPI reports right after running an S/List report. -14 is the most common error but we also get -5 and -999 as well.
Keep in mind that this might be something we are doing wrong. We have spoken with Sprezz about this and they can't reproduce it. We promised to try to recreate this issue in a very simple test environment. However, since you are running in a similar environment that we are then perhaps you inherited the same problem we have.
dbakke@srpcs.com
At 22 MAY 2003 06:29AM Revelation Technical Support wrote:
Ray-
For the 32-bit versions of OI, you should never see OIPI.exe. You should see OIPI32.exe
At 22 MAY 2003 11:10AM Ray Chan wrote:
Mr RTI,
For the 32-bit versions of OI, you should never see OIPI.exe. You should see OIPI32.exe
You got me . I misspoke. I meant OIPI32.exe and not OIPI.exe. I guess I was using my form of shorthand.
Sorry. However, do you see anything?
This problem started since we converted to 4.13. Any ideas?
thanks,
Ray
At 22 MAY 2003 11:18AM Ray Chan wrote:
Don,
However, since you are running in a similar environment that we are then perhaps you inherited the same problem we have.
This may be the case, but an important clue (I believe) is that for us, we never saw this until very recently after we converted from OI 4.12 to 4.13.
It may be that something in our environment is causing this, but if so, whatever the "problem" is, it wasn't affecting the printing. We have looked at this and don't see anything untoward in the app. For the record, there are no Start/Stop32. We've checked.
Therefore, if you find anything, would appreciate an update.
Thanks again,
Ray