Difference between revisions of "StableBit DrivePool Error Reports"

From Covecube - Wiki
(Created page with "StableBit DrivePool has an extensive error reporting infrastructure, including automatic error report submission (disabled for now). All error reports are written to a local fold...")
 
Line 3: Line 3:
 
Error reports are written by DrivePool when it encounters expected and unexpected problems in the code. Expected errors will not shut the service down, while unexpected errors will force the service to restart. Error reports are '''not written''' for I/O errors. E.g. A problem moving a file will not generate an error report. For such issues see [[StableBit DrivePool Log Collection]]
 
Error reports are written by DrivePool when it encounters expected and unexpected problems in the code. Expected errors will not shut the service down, while unexpected errors will force the service to restart. Error reports are '''not written''' for I/O errors. E.g. A problem moving a file will not generate an error report. For such issues see [[StableBit DrivePool Log Collection]]
  
Each error report contains information about where in the code the problem occurred, including application state and is extremely helpful.
+
Each error report contains information about where in the code the problem occurred, including application state and is extremely helpful for fixing bugs.
  
 
== Submit a error reports ==
 
== Submit a error reports ==

Revision as of 23:40, 17 May 2011

StableBit DrivePool has an extensive error reporting infrastructure, including automatic error report submission (disabled for now). All error reports are written to a local folder on the server, C:\ProgramData\StableBitDrivePool\Service\ErrorReports and an Application event log entry is generated. Only The latest 20 error reports are kept on the disk.

Error reports are written by DrivePool when it encounters expected and unexpected problems in the code. Expected errors will not shut the service down, while unexpected errors will force the service to restart. Error reports are not written for I/O errors. E.g. A problem moving a file will not generate an error report. For such issues see StableBit DrivePool Log Collection

Each error report contains information about where in the code the problem occurred, including application state and is extremely helpful for fixing bugs.

Submit a error reports

  1. Open Windows Explorer to C:\ProgramData\StableBitDrivePool\Service.
  2. Right click on ErrorReports and select Send to -> Compressed (zipped) folder.
    Stablebit drivepool errorreport sendto.png
  3. Take the resulting error report file.
    Stablebit drivepool errorreport.png
  4. Go to http://stablebit.com/contact to open a contact thread and attach the error report file to the message.