Search Tips

RULE 2.2 FACSIMILE TRANSMISSION

Effective Date: 3/1/2002

Obsolete Date: 3/1/2009

(a) Filing. Papers required to be filed with the clerk of the trial court may be filed by facsimile transmission, if the clerk of court has a bond-paper facsimile receiving machine available in the courthouse. Filing is complete when the facsimile transmission is received by the clerk. A document received by the clerk's office in whole or in part after normal business hours must be processed on the next court day and deemed received at the opening of business on that day. The filed facsimile is the original.

Within 5 days after the clerk of court has received the transmission, the party filing by facsimile transmission shall forward the filing fee, if any, to the clerk of the court.

Upon failure to comply with the requirements of this rule, the court in which the action is pending may make such orders as are just, including but not limited to, an order striking pleadings or parts thereof, staying further proceedings until compliance is complete, or dismissing the action, proceeding, or any part thereof.

(b) Issuance of Orders or Warrants. Facsimile transmissions may be used for the issuance of all orders and warrants and have the same effect as the original. The original order or warrant, along with any other documents, including affidavits, must be delivered promptly to the clerk of the trial court for the county where the request or application for the order or warrant was made.

Effective Date Obsolete Date
03/01/2016 View
03/01/2009 03/01/2016 View
03/01/2002 03/01/2009 View
01/01/1995 03/01/2002 View

 

Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>