Search Tips

Registration and training for new appellate e-filing system Thursday, March 14, 2024

The new appellate public access, e-filing, and docket system will include a public portal through which appellate case documents can be accessed and through which documents can be submitted for e-filing.

Registration will not be necessary to view documents on the public portal. 

Registration will be necessary to e-file documents.  All attorneys will be required to e-file and self-represented parties are encouraged to do so.  Registrations must be approved by the Supreme Court Clerk’s office, which is open from 8:00 a.m. to 5:00 p.m.  Outside of these hours, the clerk's office will not approve registrations. The system will be live starting April 8, 2024, and registration is not available before that date.  Therefore, we advise you to be prepared to register if you have filings due the week of April 8.  We also advise others to register well in advance of any filing deadline.  

Training will be provided on March 28, 2024, for anyone wishing to e-file.  The training concentrates on the process and procedures for how to e-file along with a question and answer session.  The training will be offered virtually and is expected to last 1 hour.  The link to register is https://ndcourts-gov.zoom.us/webinar/register/WN_6LVTA6-OSe-gGwMvNnpQPw.  The traning will be recorded both for those who cannot attend and as a reference.

 

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>