Here’s what happens:

• Releases Workflow Licenses – ensuring that all Workflow licenses currently “in use” get released by DocuPhase for future use
• Recreates DocuPhase Progression Database Objects – re-creating all references to DocuPhase database objects (such as tables) within the Progression database
• Reloads DocuPhase Progression Caches – forcing the reload of the Progression cache within DocuPhase without affecting the Progression Studio or Progression Server maintained caches
• Resets DocuPhase Application Triggers, Views, and Full Text — while this same process occurs at the initialization of each DocuPhase session, resetting it here prevents you from having to log out and into DocuPhase as a separate step
• Resets Analytics Views – while this same process occurs at the initialization of each DocuPhase session, resetting it here prevents you from having to log out and into DocuPhase as a separate step
• Reloads the Tools menu definition – resets the downloadable platform components which may help if Applications are not populating correctly

EXPECTED RESULT:

Generally, everything resets as expected, and the confirmation message (shown above) appears. However, on rare occasions, the reset may not correct certain issues; in this case, an error message appears.

If after resetting DocuPhase, your system still does not respond as expected, or if you aren't able to successfully reset DocuPhase, try the following procedures.

• Use Security Manager to Clear Roadblocks (Release Licenses)
• Unlock Documents*
• Manage Checked Out Documents (Revision Control)**
• Use Viewer Console to Monitor Document Cache
• Find Unresolved Events with Progression Console***
• Review Tracelogs to Find Issues
• Contact DocuPhase Technical Support (Submit a Ticket)

*This is only available if your organization is using ScanDox

**This is only available if your organization is using Revision Control.

**This is only available if your organization is using Progression Workflows.

From the Reset DocuPhase screen:

Click to reset the system and effect the actions described above, and display a confirmation message.

NOTE

If the Confirmation message doesn't appear, use the Tracelogs to find issues as described below.

Show me...

Tracelogs are used to track events such as errors within the DocuPhase system. Errors and/or warnings from various DocuPhase services are recorded in these corresponding logs that can be used to find (and sometimes to resolve) issues.

1)  Go to C:/ProgramData/DocuPhase/tracelogs.

IMPORTANT!

If your system has been upgraded to 6.1 or above, a new file path exists for all tracelogs created in previous versions, as well as new ones created by the upgrade. However, tracelogs existing before version 6.1 can still be viewed via their original file path as well as the new one.

2)  Sort the Tracelogs in the folder by Date Modified, so that the most recent logs come to the top of the list of files.

3)  Find and open the file that relates to the platform component having an issue (e.g., Application Server, License Manager, DocuPhase Database, etc.)

In the tracelog txt file you just opened:

4)  Go to Edit Find and search for the word "error" to easily locate any/all errors that appear in the tracelog.

5)  Review the errors and take action as appropriate.

Show me...