CADORS - SCRQEAC

System Profile

System Full Name

Civil Aviation Daily Occurrence Reporting System

System Full Name (French)

Système de compte rendu quotidien des événements de l'Aviation civile

Division

Aviation Safety Policy and Intelligence

NTARS Code

C108

Source Code Location (Archived)

http://tfsprod:8080/tfs/CivAv/CADORS-SCREAQ

Source Code Location - CADORS Internal

https://dev.azure.com/transport-canada/DSD-CIVAV Support/_git/CADORS-SCREAQ Internal

Source Code Location - CADORS External

https://dev.azure.com/transport-canada/DSD-CIVAV Support/_git/CADORS-SCREAQ External

Source Code Location - CADORS AOR Processor (NAV Canada EMail Processor)

https://dev.azure.com/transport-canada/DSD-CIVAV Support/_git/CADORS-SCREAQ-NAVCanadaEmailProcessor

Source Code Location - CADORS Self Subscription Emailer (SelfSubscriptionEmailer)

https://dev.azure.com/transport-canada/DSD-CIVAV%20Support/_git/CADORS-SCREAQ%20SelfSubscriptionEmailer

Technology Assessment

Platform Type

Web (Internal/External)

Database Platform and Version

Oracle 18C

Development Language and Framework

ASP.NET + VB.NET

Operating System and Version

Windows Server 2016

Additional Dependencies

 

Authentication

Windows/AD

IT Developer

 

System Overview

Transport Canada collects aviation occurrence information through CADORS. The purpose of the system is to provide initial information on occurrences involving any Canadian-registered aircraft as well as events which occur at Canadian airports, in Canadian sovereign airspace, or international airspace for which Canada has accepted responsibility that includes events involving foreign registered aircraft.

CADORS feeds industry airlines and maintenance organizations, including the Aircraft Services group, as to any related issues or impacts resulting from incidents or occurrences reporting from aviation industry.

Environment Access Information

ENV

UNC

WWWFILES

URL

DB

External

DEV

\\ncrws499\cawwwappsx\saf-sec-sur\2\CADORS-SCREAQ

 

http://cawwwappsx/Saf-Sec-Sur/2/CADORS-SCREAQ

CADORSD

ACC

\\tctestmaster\wwwappsroot\saf-sec-sur\2\CADORS-SCREAQ

 

http://wwwappstest.tc.gc.ca/Saf-Sec-Sur/2/CADORS-SCREAQ/

CADORSA

PROD

 

 

https://wwwapps.tc.gc.ca/Saf-Sec-Sur/2/CADORS-SCREAQ/

CADORSP

Internal

DEV

\\ncrws499\catcappsx\Saf-Sec-Sur\2\CADORS-SCREAQ-2

 

http://catcappsx/saf-sec-sur/2/CADORS-SCREAQ-2

CADORSD

PREACC

 

 

http://catcpreaccpx/Saf-Sec-Sur/2/CADORS-SCREAQ-2/

 

ACC

\\tctestmaster\tcappsroot\Saf-Sec-Sur\2\CADORS-SCREAQ

 

http://tcappstest/saf-sec-sur/2/CADORS-SCREAQ

CADORSA

PROD

 

 

http://tcapps/Saf-Sec-Sur/2/CADORS-SCREAQ

CADORSP

NAV Canada Emailer

 

 

\\NCRWS514\Scripts\CivAv\CADORS\CADORSAOREMAILER\NAVCanadaEmailProcessor.exe

CADORSA

Self Subscription Emailer

 

 

\\NCRWS514\Scripts\CivAv\CADORS\CADORSSELFEMAILER\SelfSubscriptionEmailer.exe

CADORSA

NAV Canada Emailer

 

 

\\ncrws548\scripts\CivAv\CADORS\CADORSAOREMAILER

CADORSP

Self Subscription Emailer

 

 

\\ncrws548\scripts\CivAv\CADORS\CADORSSELFEMAILER

CADORSP

Admin

Access database

 

 

\\ncrdb321\access_db\AARQ\CADORS\NEW CADORS.accdb

CADORSP

 

Application

Purpose

NAV Canada Emailer

(CADORS External - script)

Process AOR (Aviation Occurrence Report) emails that come from NavCanada. Adds the data from emails to CADORSP for review and processing by admin users.

All emails incoming from NAV Canada NC-SIS system ncsis@navcanada.ca are sent to Aviation Operations (operations.aviation@tc.gc.ca) mailbox avops@tc.gc.ca. It is extremely critical that the auto forwarding rule in the AVOPS email is in place to send the emails from avops@tc.gc.ca to mail server NCRMXMB04a.tc.gc.ca and mail box AORPROD@tc.gc.ca. New emails for AORs are processed and stored in two tables, XA001_AVIATION_OCC_REPORT and XA002_AVIATION_OCC_REP_AIRCRFT. After processing, emails are moved from Inbox to Processed folder, or to Error folder if it has errors in processing. Outstanding/unprocessed AOR emails in the Inbox will be processed every 15 minutes.

Note: see https://dev.azure.com/transport-canada/DSD-CIVAV%20Support/_workitems/edit/190840 where the emailer was not working properly.

The following is a screenshot is a sample of the folder structure.

 

NAV Canada recommends that for any support issues in the future with NC-SIS to contact nc-sis@navcanada.ca (this email address is monitored by the NC-SIS Business Team - notice there is a dash between nc and sis which differentiates it from the system account).

Self Subscription Emailer (CADORS External - script)

Sends out daily occurrence emails to subscribers.

ImageButtonE10Fix

DLL need to be included in CADORS Internal

Access database

To process translations and interact with the translation group. Links to Oracle tables in CADORSP.

Task scheduler screen shot from production script server (ncrws548)

The are 3 scheduled tasks for the whole NAV Canada Email processing application, 1. NAV Canada Emailer, 2. NAV Canada Emailer DeleteErr, 3. NAV Canada Emailer DeleteProc. The 1st runs every 15 minutes to process emails in the Inbox folder and move them to the Processed folder. The 2nd runs every month to delete the email when processed with an error. The 3rd runs every month to delete all emails already processed by the 1st. These three tasks will execute the same application, NAVCanadaEmailProcessor.exe. The differences are the 1st is scheduled without passing in a parameter, the 2nd is scheduled by passing in parameter called DeleteErrors, and the 3rd is scheduled by passing in a parameter called DeleteProcessed.

NOTE 1: the above scheduled tasks DO NOT need a certificate to run NAVCanadaEmailProcessor.exe in any environments.

NOTE 2: NAV Canada Emailer DeleteErr, and NAV Canada Emailer DeleteProc are disabled, business clients process these emails manually.

NOTE 3: Each email has an attachment, which contain the same information in the body of the email. The attachment is not processed by the email processor, it will be archived with the email itself for auditing purposes.

Good To Know

Info to Open Gov Portal - Civil Aviation Daily Occurrence Report System - Open Government Portal (canada.ca)

Where is the query ???? Verify

BII - Reports in CADORS

How-To and Fixes

CADORS cannot print French regional reports

See bug# 229932

Issue:

When printing French regional Quebec “Printer Friendly” reports for a certain dates. there is an exception: “An unexpected error occured. TC has been notified by email. Erreur inattendue. Transports Canada a été avisé par courriel.”

Solutions:

  1. Reproduce the error on Prod: 

Click on the  CADOR Prod : 

http://tcapps/Saf-Sec-Sur/2/CADORS-SCREAQ/

Go to Regional Report , enter Reporting Date : for ex 2022-11-25 (date which was provided by the client is having the printing error ), choose Quebec Region to Search 

Will see the whole list of record and click on Printer-Friendly  at the right menu 

Error : “An unexpected error occured. TC has been notified by email. Erreur inattendue. Transports Canada a été avisé par courriel”

2. If the error is actually shown on PROD, then definitely this case is legitimate. 

This issue happens because there are invalid characters in French text of a certain CADORS number. To find exactly which CADORS number having this issue, we need to trace in the local host (run CADOR in local host)

3. Clone CADOR source code

Using

CADOR internal : https://dev.azure.com/transport-canada/DSD-CIVAV%20Support/_git/CADORS-SCREAQ%20Internal

Set up so CADOR can run properly, change web.config to point to PROD database, 

Search source code to find 'SNTLoginName' . We can use the sNTLoginName = "BOIVCHR' to run in localhost for PROD for now

Follow the same scenario in step2 . However in the local host, we still can see a CADOR reports even it has invalid characters (i.e it does not thrown an exception as happening in PROD)

Go through each CADORS to search for invalid characters, for example it might look like this 

When finding an invalid character, take note its CADOR number

4. Log in PROD CADOR database, filter Detail table with the just found CADOR number, go to the French text, look at invalid character, back up the text before changing, try to remove the whole invalid characters (those look normal but they are not correct) and retype them again, click commit

5. The error is fixed. Ask the clients to verify if they can print the report now

 

 

 

TFS Test Plans, Suites and Test Cases imported: