Recovery Checklist for Dawn Clinical Framework version 7.xx
Here is a list of potential issues and suggestions as to how to recover from them. This
document has been written for IT professionals supporting the application.
Page Not Found/ Internet Explorer cannot display the webpage
All client PC’s
Check the server hosting the Dawn application web site (i.e. the server running IIS) has
Check the server hosting the Dawn application web site is still connected to / accessible
over the network
Check IIS is running on the server hosting the Dawn application web site and permits
Active Server Pages.
Single client PC
Check the PC can access the network. If not:
Check the network cable is attached and is not damaged.
Reboot the PC
Dawn log in screen appears but you cannot log in
Check the Dawn database server (i.e the machine running SQL Server) has not crashed.
Check the Dawn database server is still connected to / accessible over the network
Check that SQL Server is running on the Dawn database server
Check the password for the SQL server Login the Dawn Application uses to connect to
the database is still valid (see Appendix 1 below on how to check and amend the
If the database connection has been lost, you MUST unload the Dawn application before
logging back into the application once the database connection has been restored. To unload
In your browser open the UnloadNow.asp page under the Dawn site/directory e.g.
http://DawnServer/DawnAC/UnloadNow.asp. Repeat until the Application Unloaded page is
displayed (if the unload script times out you may get a Page Not Found or Remote Procedure
call failed error on the first one or two attempts).
Version 4.00 Page 1 of 11 25/07/2008
Within Dawn perform the following steps to check the users account:
Press F5 to display the System menu.
Choose Normal Tables/HCProfessional from the menu.
Search for the user experiencing the problem. Choose the Edit icon to display their
details and select their Account Info tab.
Set their Failed login count to zero and ensure the Locked checkbox is unchecked.
Reset their password and ensure they create a new password that matches the strong
password criteria (hover your mouse over the login screen’s info icon to check the
Dawn hangs / exhibits unexpected behaviour
Unload application by running the UnloadNow.asp from the Dawn site/directory e.g.
http://DawnServer/DawnAC/UnloadNow.asp. Repeat until the Application Unloaded page
is displayed (if the unload script times out you may get a Page Not Found or Remote
Procedure call failed error on the first one or two attempts).
On the Dawn application Web site server open the IIS management console and perform and
try the following:
Recycle the Dawn Application Pool (Windows 2003 only)
Stop and Start web site and (if Windows 2003) recycle the Dawn Application pool.
Check you are not running a virus checker with an option to intercept the Windows
Scripting Host (e.g. ScriptScan in MacAfee). If so disable this option on the Dawn Server.
Ensure your virus checker is not running a Scan on the server during work hours.
For Load balanced / clustered servers repeat on all in cluster.
On the SQL server open your SQL Server Management utility (e.g. Management Studio,
Enterprise Manager, DbaMgr2K) and check the following:
Right click on the Dawn database and choose Properties. Choose Files and check the
size of the transaction log. If this is very big (i.e. several gigabytes in size) your
transaction log backups may not be working. Truncate your transaction log then shrink
the file. (If you do not know how to do this using the tools provided in your Management
Utility, see Appendix 2 below on how to do this using two simple SQL queries).
Right Click on your Dawn database and choose Properties. On the General tab check
how much free space is available within the database. If this shows 0 Mb, the database
may be trying to Autogrow itself (allocated itself more disk space). If you have a large
database, the Autogrow may timeout and should do this manually. Choose the Files
option in the database properties window and manually increase the initial size setting for
the Primary Data file, DawnAC_Data. By default SQL server attempts to grow the
database by about 10% at a time (so if your database is 3Gb it would allocate approx
300Mb more). However, if your database is large it may pay to be pro-active and allocate
substantially more disk space for it to grow into.
Version 4.00 Page 2 of 11 25/07/2008
Messages stop printing / emailing / faxing automatically in response to
Check statistics on front page (7.3 onwards) – if pending counts (other than outbound
interface) are increasing, DawnMailer may not be processing.
Ask the user to check the Messages List View/Pending Messages filter (if available) to
see if there is a long list of pending messages.
If this is running as an application on a PC simply press Stop (if necessary) then Start.
If it is running as a service, stop and restart the service.
If DawnMailer is running as a service under FireDaemon, it appears as FireDaemon:
DawnMailer under Services & Applications/Services in the Microsoft Management
If the problem persists:
Stop DawnMailer as a service and restart as an application to check if any error is
displayed. If run on the server, DawnMailer.exe is installed in the Polar Studio/Webroot or
Polar Studio/Bin folder – if it is in both use the Webroot copy.
If DawnMailer keeps switching itself to Stopped. Clear out pending messages (using the
Messages List View in Dawn) and restart DawnMailer.
Any messages, you delete or mark as undeliverable/discarded in this way will not be sent.
You will need to generate new messages for these patients / HC Professionals.
If DawnMailer is running but nothing is printing:
Check the printer is working.
Check the Dawn server / DawnMailer machine can still connect to the printer over the
network. (Stop DawnMailer, run as an application and choose the Test Mail option)
Email Messages are marked as Undeliverable
Check the SMTP setting in DawnMailer is correct (check the DawnMailer.ini file or run
DawnMailer as an application and check the dialog - if run on the server, DawnMailer.exe
and .ini files are installed in the Polar Studio/Webroot or Polar Studio/Bin folder – if copies
exist in both use the Webroot versions).
Check the SMTP server is running
Check the email address of each recipient is correct
Check that Firewall / virus software is not blocking the SMTP port (25) on the server
Check the Sender address configured in Dawn is recognised/permitted by the SMTP
server (some SMTP servers do not permit fake sender addresses e.g.
Version 4.00 Page 3 of 11 25/07/2008
Check the Dawn Server is permitted to use the SMTP server to relay emails.
INR results, Patient Demographic Updates or Admission /Discharge
updates are not being processed by the interface
Check with the team who support the Laboratory or Patient Administration System that
sends the messages to Dawn to ensure their system is receiving acknowlegements
messages from the JResultNet (The Dawn Interface HL7 Listening component). If not,
restart the DTI JResultNet Service on the Dawn server.
Check the Dawn IE application is running on the Dawn Interface server (if it is running as
a Service restart the service).
If Dawn IE is running as a service under FireDaemon, it appears as FireDaemon: Dawn
IE under Services & Applications/Services in the Microsoft Management console.
Check the HoldMonitor to see if all messages are being put on hold and if so, why.
Dawn Interface Stops Updating Dawn or You Get an “Unrecognized
database format” Message When Attempting To Log Into Dawn.
This error DOES NOT mean the Dawn database has corrupted. The full message is
“Unrecognized database format 'C:\Program Files\Polar Studio\Project\Dawn_MF_Dyn.bpd’ ”.
This indicates the Dawn application dynamic file (Dawn_MF_Dyn.bpd), which contains the
application error log, is damaged and should be replaced.
Under normal running this error should not occur. However, if a server is severely
bottlenecked on resources it is possible that, on a rare occasion, it could fail to lock the
dynamic file correctly causing it to corrupt. The dynamic file is cached in memory on the
server for the main application. As such, it is likely that the Dawn Interface Engine (Dawn IE),
which runs as a separate process, will hit this problem while the main Dawn application (using
the cached copy of this file) continues to function correctly. In this case, if possible do not
Unload the main Dawn application until you are ready to apply the fix described below.
How to recognise this problem if the interface alone is exhibiting it:
The Dawn Interface Engine (Dawn IE) continues to import files but fails to update the main
Dawn database so the updates never appear in Dawn.
These messages are not lost – they remain in the Dawn IE intermediate tables and will be
applied automatically once the problem is resolved.
Check whether files are building up in the Dawn Interface Engine Input Files folders, e.g.:
Dawn Interface\DAWN IE\Applications\Dawn AC Version 7\Input Files\PatientUpdate Demographics and ADT
Dawn Interface\DAWN IE\Applications\Dawn AC Version 7\Input Files\TestResult INR and Test Results
interface v7.8 and above
Dawn Interface\DAWN IE\Applications\Dawn AC Version 7\Input Files\INR INR result interfaces pre
If files are building up in these folders, a corrupt dynamic files is NOT the problem. Try
Version 4.00 Page 4 of 11 25/07/2008
restarting Dawn IE.
If files are disappearing from these folders (as they should when Dawn IE imports them), but
no updates are appearing in Dawn, check the Dawn IE log.
1. If Dawn IE runs invisibly under FireDaemon, first stop Dawn IE in the FireDaemon
Services Manager (using the desktop shortcut), then run Dawn IE as an application by
double clicking the Dawn Interface\Dawn IE\DawnIE.exe file. The Dawn IE – View
Reports dialog appears.
2. Choose the View Report button to display the log. If the dynamic file is corrupt the log
will show multiple instances of the following error message:
HIS1, Map files, Error Occurred. Class: cDawnUpdate, Function:
LogOn Description: Failed to logon to Polar Studio - check dll
version numbers - Unrecognized database format 'C:\Program
Files\Polar Studio\Project\Dawn_MF_Dyn.bpd'., Failure
To Replace a corrupt dynamic file
Download a new copy of the dynamic file from the following ftp site:
Your browser will attempt to log you in with anonymous access which is not permitted so you
will initially receive an error message.
1. If you are using Internet Explorer 7 or above choose Page/View this ftp site using
2. Choose File / Login As from the Windows Explorer menu bar and enter the following
3. Open the BPD Dynamic File folder and download the Dawn_MF_Dyn.bpd
4. Stop Dawn IE.
5. Unload the Dawn Application by running http://Dawnserver/DawnAC/unloadnow.asp
(where Dawnserver/DawnAC is the address of your Dawn system)
6. Open the Polar Studio\Project folder in Windows Explorer and rename your existing
Dawn_MF_Dyn.bpd file to “Corrupt Dawn_MF_Dyn.bpd”. Please note if you are running
an early version of Dawn the name of the dynamic file might be slightly different in which
case look for the file ending _dyn.bpd and note down its original name (e.g.
Dawn_AC7_dyn.bpd) before renaming it.
7. Copy in the new dynamic file you downloaded. (If your original file was named differently,
rename the new dynamic file to match the original file name).
8. Restart Dawn (either by clicking the restart hyperlink or by opening Dawn in the normal
way) and check you can log in without error.
9. Restart Dawn IE (under FireDaemon if that is how it normally runs) and check updates
are now coming into Dawn.
Version 4.00 Page 5 of 11 25/07/2008
Data is missing or a recurrent error occurs where it did not occur
previously for more than one patient
Some settings are cached – including the database connection. If some data is not being
displayed it may be that connection or system settings have been lost or unloaded from
the cache. Unload and reload the application (see section “Dawn hangs…” above) to
reload the application from disk.
If the problem persists:
Make a backup of your database to a different location (i.e. do not overwrite any previous
Restore your last good backup and check if this resolves the problem
Our Contact Details
If the above steps do not resolve the issue, please call or email. If we are closed for business,
please leave a message and your contact details and we will investigate the problem and call
you back at the start of your business day.
Tel no: + 44 (0)15395 63091
Fax no: +44 (0)15395 62475
Version 4.00 Page 6 of 11 25/07/2008
Appendix 1 – Checking and Amending the Dawn Connection Properties
1. Unload the application using your browser by running the UnloadNow.asp from the Dawn
site/directory e.g. http://DawnServer/DawnAC/UnloadNow.asp. Repeat until the
Application Unloaded page is displayed (if the unload script times out you may get a Page
Not Found or Remote Procedure call failed error on the first one or two attempts).
2. Using Windows Explorer, locate the Dawn_MF_Project.bpp file in your
Polar Studio\project folder on the server (this is normally located within your
program files folder).
If you are running Dawn version 7.1 or earlier, locate the Dawn_AC_7_Project.bpp file
3. Double click on the project file. You are prompted for a password.
4. Enter sydney1 in the password field (leave the New Password and Confirm fields blank).
5. Press OK to login. You may be prompted to convert the project to the latest version, in
this case press Yes (this option does not affect your application, it simply lets you open
the project file in the Polar Studio editor).
6. Choose Applications/ DawnAC/ Application-
settings from the menu tree on the left to
display the application settings.
7. Select the Connection tab.
Version 4.00 Page 7 of 11 25/07/2008
8. Edit the connection properties as shown below:
Press the Open file
icon to load the current
from the project ini file
Press OK to load the
Version 4.00 Page 8 of 11 25/07/2008
Press the Browse button
beside the database field to
read the list of databases
hosted by the SQL Server
If the list of databases is displayed,
the connection properties are
In this case press Cancel and close
Polar Studio without making any
However, if you receive the
following error either the user
name or password has changed.
Version 4.00 Page 9 of 11 25/07/2008
… then press
the Save icon
to update the
settings in the
If you receive the following error the Server property is incorrect.
If this is set to:
…it is a looking for a default (unnamed) instance of SQL server on the same server as the
project file. If your SQL server instance resides on another machine or has been given a
specific name, enter the correct server name in the Server property field.
Version 4.00 Page 10 of 11 25/07/2008
Appendix 2 – How to Truncate and Shrink a Transaction Log using SQL
All insertions, updates and deletions are to the database are written first to the transaction
log. The “transactions” are then applied to the database in the background. Once a
transaction has been written to the database, its status is updated in the log.
When you run a transaction log backup, it removes all written transactions from the log.
However, if do not run transaction log backups or your transaction log backups have not been
working, the log may grow very large.
To remove written transactions from the log either:
Make a transaction log backup
Truncate the transaction log (a backup option which removes the unwritten transactions
without backing up the log).
If your transaction log has grown very big, it may not be practical (or even possible with the
free disk space available) to backup the transaction log so truncating the log may be
When you remove the written transactions from the log, SQL Server does not automatically
recover the disk space used. The log file remains the same size; it simply comprises
predominantly free space as opposed to predominantly used space. If you are making
regular transaction log backups this is desirable as reserving this space for use by the
transaction log as it grows again avoids potential file fragmentation. However, if the log has
grown very large, you may need to recover the space.
Recover the space by Shrinking the transaction log.
Your database management utility (e.g. Management Studio, Enterprise Manager,
DbaMgr2K) should provide an option to do truncate the log and to shrink the log. (It is
preferable to shrink just the log file rather than shrinking the database as a whole. Most
Management utilities have a Shrink Files option where you pick which file you want to shrink,
in addition to a general Shrink Database option).
If you are not sure how to truncate and shrink the log using your Management Utility, you can
perform these tasks using the following commands.
1. Open the option in your Management Utility that allows you to run a Query (Tools/Query
Optimizer in Enterprise Manager; File/New/Query with Current Connection in
management studio; Activity/Query in DbaMgr2K).
2. Enter the following command and press the execute button (often depicted using ! or )
– substitute your own database name for DawnAC if different)
BACKUP LOG DawnAC WITH TRUNCATE_ONLY
SQL Server truncates the database (this query does not return anything)
3. To recover the space freed (if necessary), enter the following command and press the
DBCC SHRINKFILE (DawnAC_Log, 1)
Version 4.00 Page 11 of 11 25/07/2008