Requirements Editor Error Log
In addition to displayng errors and information from processing issues in the Messages window, an error log is generated maintained each time a document is assembled. The error log contains a rolling list of error events and the associated trace record for each error returned by the system.
- File Name: errors.txt
- Path: C:\Users\user.name\AppData\Local\Wolters Kluwer\RequirementsEditor\3.0
1/22/2014 4:38:18 PM -----------------------------------------------------------------
Content reference(s) could not be loaded Couldn't find organization name.
Trace:
at RequirementsEditor.ViewModel.ExternalDocumentCache.DownloadDocument(String orgID, String docID, Boolean reportProgress)
at RequirementsEditor.ViewModel.ExternalDocumentCache.GetDocument(String orgID, String docID)
at RequirementsEditor.ViewModel.ContentReferences.ContentReferencesManager.AutoUpdateContentReferences(Object state)This
error log can be useful in troubleshooting issues and is particularly helpful in communicating
errors to technical support.Requirements Editor stores settings and locally created files to the Windows application data folder for the user account that Requirements Editor was associated with when installed. As we noted earlier, the error log is one such file stored on this location. In addition to the error log, the Wolters Kluwer repository that is referenced by a document during assembly is stored in this folder as well as a settings file. The files are stored as Local application data associated with a machine; they are not stored as Roaming application data files or in the LocalLow folder.
- Repository
- ORG.WoltersKluwerFinancialServices.Root
- Organizations.xml
- Profile.xml
- errors.txt
- organizations.xml
- RequirementsEditor.settings