CRN DUI Instructor Information

Pennsylvania DUI Association

CRN – FREQUENTLY ASKED QUESTIONS (FAQ)

The CRN website can be used on either Microsoft Edge or Google Chrome.

 

The viewing and printing of the CRN reports requires the use of Adobe Acrobat Reader version 5 or later.

The software is available free from Adobe.

Click here to access the Adobe website to download Adobe Acrobat Reader.

 

For your screen resolution:

For optimum page viewing, the ‘1024 by 768’ setting should be used.

This setting is found under the Control Panel Display icon, Settings tab.

 

For optimum CPF (profile) printing, page setup settings should be: 

  • Orientation must be Landscape
  • All Margins should be set to .75 inches.
  • The Header and Footer text boxes should be cleared out.  With special codes in these text boxes,

information such as URL, page number, date, etc. will be printed.  Using these codes will not affect the

CPF, but the information is unnecessary for the CPF.

 

For the Adobe Acrobat Reader software, no special settings are needed. The defaults should be fine.

In some cases, there are two (or more) records for the same last name/DOB and one of those records has been made inactive.

 CRN will handle inactive records in this way: 

  1. If you attempt to establish a CRN by entering the DL# and it is an inactive number, information will not be returned from DL&C, and you’ll be forwarded to the PennDOT Driver License Search page. In other words, this inactive DL# will be treated as if it no longer exists.
  2. Likewise, searches by SSN and last name/DOB will not return results for inactive DL#s. CRN will treat inactive DL#s as if they don’t exist.
  3. If an existing CRN (created with an active DL#) is pulled up for the purpose of regenerating the CPF and the DL# has become inactive in the interim, then you will see a message that says, “The DL# of this CRN has become inactive. If you need further assistance, contact the PennDOT CRN Unit at 717-787-2235.”

No

The system will check for a match between the county associated with the Evaluator ID and the county associated with the AO code. If the two do not match, a warning message will pop up that says, “AO Code does not match facility code.” Because this is a warning box, you can close it and move on. The system does not REQUIRE that the AO Code match the facility code.

The edits on the AO code are as follows: the first two digits can be anything between 01 and 68. The last three digits can have a value less than 600 or equal to 601, 701, or 801. You will receive an error message if the AO Code entered does not fall within these parameters.

The DL number that is entered on the CRN Key Data page should be the PA DL#. The field will accept only numbers.

 When you enter a number in the PA Driver’s License Number field on the CRN Key Data page and attempt to establish a CRN, CRN tries to match the number you entered with a record number on the PennDOT DL&C System. If there is no match, you will be asked to search for the record by entering data on the PennDOT Driver License Search page. If no match is found after this search, you will be able to establish a “Non-DL&C” CRN, and you can provide the out-of-state license information on the CRN Personal Data page.

A password could change from Jimmy1 to Jimmy2 to Jimmy3, etc. but alternating passwords or using the same password continuously will not be permitted. The list of previous passwords currently retains the last 24 passwords, and they are retained for two years.

Changing your password counts as activity, so if you change your password every 60 days, your user ID will not expire.

Setting a reminder somewhere to go in and change your password might be a good idea. The notification you receive indicating that your password is about to expire is only seen when you log into CRN. You will not receive an email notification of pending expiration.

Because PennDOT’s DL&C system and the CRN application do not communicate regarding expungements, PennDOT will not delete CRNs if records are expunged.

© 2024 PADUI/Designed by:LaunchUX