Search Tips

RULE 77. DISTRICT COURTS AND CLERKS

Effective Date: 3/1/1999

Obsolete Date: 3/1/2000

(a) District Courts Always Open. The district court is deemed to always be open for the purpose of filing any pleading or other proper paper, of issuing and returning mesne and final process, and of making and directing all interlocutory motions, orders, and rules.

(b) Trials and Hearings Orders in Chambers. All trials upon the merits must be conducted in open court and so far as convenient in a regular court room. All other acts or proceedings may be done or conducted by a judge in chambers, without the attendance of the clerk or other court officials and at any place either within or without the district; but no hearing, other than one ex parte, may be conducted outside the district without the consent of all parties affected thereby.

(c) Clerk's Office and Orders by Clerk. All motions and applications in the clerk's office for issuing mesne process, for issuing final process to enforce and execute judgments, and for other proceedings not requiring allowance by or an order of the court are grantable of course by the clerk; but the court upon cause shown may suspend, alter, or rescind the clerk's action.

(d) Notice of Entry of Judgment Served. Within 10 days after entry of judgment in an action in which an appearance has been made, notice of entry of judgment, together with a copy of the judgment or a general description of the nature and amount of relief and damages granted, must be served by the prevailing party upon the adverse party and filed. Service of notice of entry of judgment is not necessary to begin the time for filing a post-judgment motion or an appeal if the record clearly evidences actual knowledge of entry of judgment through the affirmative action of the moving or appealing party.

Rule 77 was amended, effective March 1, 1990; March 1, 1999; March 1, 2000; March 1, 2002; March 1, 2011.

Subdivision (b) was amended, effective March 1, 2002, to eliminate the phrase addressing judicial acts or proceedings outside the district. See N.D.R.Civ.P. 39.1.

Subdivision (c) was amended, effective March 1, 1990. The amendment is technical in nature and no substantive change is intended.

Subdivision (d) was transferred to Rule 58(b), effective March 1, 2000.

Rule 77 was amended, effective March 1, 2011, in response to the December 1, 2007, revision of the Federal Rules of Civil Procedure. 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.

SOURCES: Joint Procedure Committee Minutes of January 28-29, 2010, page 22; September 28-29, 2000, pages 3-7; September 24-25, 1998, page 16; April 30-May 1, 1998, pages 12-13; April 20, 1989, page 2; December 3, 1987, page 11; January 17-18, 1980, pages 9-10; Fed.R.Civ.P. 77.

STATUTES AFFECTED:

SUPERSEDED: N.D.C.C. § 27-05-07.

CROSS REFERENCE: N.D.R.Civ.P. 39.1 (Change in Location of a Hearing, Proceeding, or Trial; Change of Venue); N.D.R.App.P. 4(Appeal When Taken).

Effective Date Obsolete Date
03/01/2011 View
03/01/2002 03/01/2011 View
03/01/2000 03/01/2002 View
03/01/1999 03/01/2000 View
03/01/1990 03/01/1999 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>