OIPI Error 13 (OpenInsight 32-Bit) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{tag>category:"OpenInsight 32-Bit" author:"Rudhy B" author:"[url=http://www.sprezzatura.com]The Sprezzatura Group[/url] " author:"Sean FitzSimons" author:"Jonathan Bird"}}

[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]


==== OIPI Error 13 (OpenInsight 32-Bit) ====
=== At 23 APR 2009 05:41:55AM Rudhy B wrote: ===
 
 
<QUOTE>
For unknown reason, I get a critical error message "There has been a problem initializing OIPI - Error 13".  I already re-register vsprint.ocx and vspdf.ocx (under Vista admin mode).



I am using OI 8.07.



What is that error message means ?



Rudhy
</QUOTE>
----

=== At 23 APR 2009 06:46AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url]  wrote:  ===

<QUOTE>This error means "There are no printers defined or no default printer is selected"



For all OIPI Error codes please look at the 'Set_Printer Error Codes' in the Online Help.

 

[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]World leaders in all things RevSoft[/i] 

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>

----

=== At 24 APR 2009 09:17AM Sean FitzSimons wrote:  ===

<QUOTE>Rudhy,



Sprezzatura's response is correct on the meaning of the error. In order for OIPI to operate properly a printer is necessary, it does not work in pure preview mode.



Sean

</QUOTE>

----

=== At 26 APR 2009 10:53PM Jonathan Bird wrote:  ===

<QUOTE>Though Sprezz's response is correct, I have fought with an OIPI -13 error at a client site for a long time, and the error was entirely spurious, there WAS a default printer. Turns out that OIPI can also spit out a -13 when the OCXs are not registered properly. In my case, the OCXs were located on a file server, and registered at each workstation. Copying the OCXs to the LOCAL \windows\system32 folder, and re-registering them fixed the problem.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=67FB4EBD4DFF1070852575A1003546C1|View this thread on the Works forum...]]