It is a good practice to routinely (every 30 days for example) reboot the DPN server to clean up stuck or stale processes and assure the continued reliability of DPN.  Timing the reboot process can be the challenge.  Your DPN server works overtime – well after you have left for the day, DPN continues to work behind the scenes.  You will want to assure that none of the following automatic processes are running before rebooting the server:

• Nightly backup and verify process
• If you are downloading listings, the MLS Download
• If you have SQL, coordinate the reboot of DPN with the reboot of SQL to assure continued connectivity. 
• Confirm SQL syncing is caught up
• Each night the SQL syncing stops and a record count is performed on every file to assure the DPN data counts match the SQL data counts – do not reboot during this process

These processes and others can often take the entire night to complete and may still be "catching up" in the morning when you arrive for work.  This is especially true of the SQL syncing process particularly if you download listings or immediately following the DPN month end close process.  If you are using Financial Analyst for daily reporting, be sure to confirm that the SQL syncing is caught up before running the Analyst Scheduler and working on your reports.   

For assistance with identifying scheduled automatic processes or questions on timing your reboot procedure, please contact anyone in DPN Customer Support.