Search Tips

Jensen ready to get to work as new North Dakota Supreme Court chief justice Monday, January 6, 2020

Bismarck Tribune

Jon Jensen likes the courtroom.

That's a good trait for the new chief justice of North Dakota's Supreme Court.

Jensen on Wednesday succeeded Chief Justice Gerald VandeWalle, who will remain on the court but stepped back after 27 years as chief due to declining energy. The state's judiciary in December elected Jensen as chief justice to lead the state's high court for the next five years. A ceremony is set this morning to mark the transition.

Jensen said that from his career in private practice in Grand Forks to his years as a judge for the Northeast Central Judicial District, he has admired the quality of the state's court system and the roles he's been able to have as an advocate for clients and as a judge helping find "the solution."

Read more at: https://bismarcktribune.com/news/local/govt-and-politics/jensen-ready-to-get-to-work-as-new-north-dakota/article_246759ae-82a7-5c0a-ab29-7eb2572ea3c2.html

 

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>