Search Tips

Notice of Hearing Wednesday, September 19, 2001

IN THE SUPREME COURT

STATE OF NORTH DAKOTA

NOTICE OF HEARING

Supreme Court No. 20010226

Proposed Amendments to North Dakota Supreme Court Administrative Rule 9

On September 19, 2001, the Judicial Conference filed a Petition for Amendment to North Dakota Supreme Court Administrative Rule 9 regarding Jury Selection Procedure which incorporates the Standards Relating to Juror Use and Management as an appendix to the Rule. On September 19, 2001, a Notice of Comment and the proposed amendments were distributed under N.D.R.Proc.R. § 7. Comments were received through Monday, October 22, 2001, and distributed to the Court. The Court considered the matter, and

ORDERED, that a hearing be held on the proposed amendments, Tuesday, December 4, 2001, at 2:45 p.m., in the Ralph J. Erickstad Courtroom of the Supreme Court, at the State Capitol in Bismarck, North Dakota. Time for personal appearances will be limited. Any person wishing to appear must notify Penny Miller, Clerk of the Supreme Court, at least three days prior to the scheduled hearing. Any person wishing to comment on the proposed amendments may continue to do so in writing prior to the hearing. Address written comments to Penny Miller, Clerk of the Supreme Court, 600 E. Boulevard Ave., Dept. 180, Bismarck, ND 58505-0530.

Dated: October 31, 2001.

/s/ Penny Miller
Clerk
North Dakota Supreme Court

 

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>