InvalidPacketLength

InvalidPacketLength Error Message: Invalid packet length Error Message: Invalid packet length This error typically occurs when using an SQL-92 driver (as opposed to an SQL-89 driver) against a Progress DBMS which is not accepting SQL-92 connections.The Progress instance may simply need to be restarted with SQL conenctions enabled on the primary broker, or a secondary SQL-92 Broker may be configured to accept ODBC connections.The latter case can be confirmed by the occurrence of the following error message in the Progress native database log -- Server's received count 1 does not equal client(1)'s send count 16777216. A secondary SQL broker is generally started with a second UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki.pf file, containing at least the following parameters -- <tgroup><thead /><tbody> <row><entry> <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki-db <DatabasePath></span> </entry><entry> Path to database. Same as that in the primary <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki.pf</span> file. </entry></row> <row><entry> <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki-H <Hostname></span> </entry><entry> Hostname. Same as that in the primary <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki.pf</span> file. </entry></row> <row><entry> <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki-S <ServiceName></span> </entry><entry> Service name for this broker. Port must also be assigned in <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki/etc/services</span>. Both name and port must differ from those of the primary broker. </entry></row> <row><entry> <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki-N TCP</span> </entry><entry> Always, TCP. Same as that in the primary <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki.pf</span> file. </entry></row> <row><entry> <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki-Mpb <MaxServers></span> </entry><entry> Sets the maximum number of servers for this broker. </entry></row> <row><entry> <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki-ServerType SQL</span> </entry><entry> Specifies that this broker will handle SQL connections. </entry></row> <row><entry> <span style="color: red"> UNKNOWN tag: http://www.w3.org/1999/xhtml:nowiki-m3</span> </entry><entry> Specifies that this is a secondary broker. </entry></row> </tbody></tgroup></table> <para> Start this broker after the first one, with a command like (your exact command may vary) -- </para><programlisting>proserve -pf /path/to/second.pf </programlisting><para>Any other parameters set in the primary <computeroutput>.pf</computeroutput> file will be inherited.</para><para>One thing you may need to override/change on a secondary SQL broker for OpenEdge 10.1B and higher is the <computeroutput>-Ma</computeroutput> parameter. This is typically set low for an ABL/4GL broker, but high for an SQL broker.</para></section></docbook>