Search Tips

RULE 49. EFFECTIVE DATE; STATUTES AND RULES SUPERSEDED

Effective Date: 3/1/2003

(a) Effective Date and Application. Any amendment or addition to these rules is effective on the date ordered by the court. These rules, and any amendment or addition, govern all proceedings and actions brought after their effective date, and all further proceedings in actions pending on their effective date. If the court decides that application of these rules, or any amendment or addition to these rules, in a particular action pending when the rules or any amendment or addition took effect would not be feasible, or would work an injustice, the previous procedure must apply.

(b) Superseded Statutes and Rules. Upon the effective date of these rules, or upon the effective date of any amendment or addition to these rules, all statutes and rules, or portions thereof, in conflict with these rules or any amendment or addition to these rules are superseded.

The North Dakota Rules of Appellate Procedure originally took effect on March 1, 1973.

Rule 49 was amended, effective March 1, 2003. The language and organization of the rule were changed to make the rule more easily understood and to make style and terminology consistent throughout the rules. Also, references to the effective dates of amendments or additions to the rules have been added.

SOURCES:Joint Procedure Committee Minutes of April 25-26, 2002, pages 29-30.

STATUTES AFFECTED:

SUPERSEDED: N.D.C.C. § 28-27-02. 1.

Effective Date Obsolete Date
03/01/2003 View
03/01/1973 03/01/2003 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>