Difference between revisions of "StableBit DrivePool 2.x Error Reports"

From Covecube - Wiki
m
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
StableBit DrivePool has an extensive error reporting infrastructure. All error reports are written to a local folder on the server, ''C:\ProgramData\StableBit\DrivePool\Service\ErrorReports'' and an Application event log entry is generated. Only The latest 20 error reports are kept on the disk.
+
StableBit DrivePool has an extensive error reporting infrastructure. All error reports are written to a local folder on the server, ''C:\ProgramData\StableBit DrivePool\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 2.x 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 2.x Log Collection]]
Line 8: Line 8:
  
 
== Submit error reports ==
 
== Submit error reports ==
# Open Windows Explorer to ''C:\ProgramData\StableBit DrivePool\Service''.
+
# Open Windows Explorer to ''C:\ProgramData\StableBit DrivePool''.
# Right click on ''ErrorReports'' and select ''Send to'' -> ''Compressed (zipped) folder''.
+
# Right click on ''Service'' and select ''Send to'' -> ''Compressed (zipped) folder''.
 
#;[[File:stablebit_drivepool_errorreport_sendto.png]]
 
#;[[File:stablebit_drivepool_errorreport_sendto.png]]
 
# Take the resulting error report file.
 
# Take the resulting error report file.

Latest revision as of 02:22, 12 August 2015

StableBit DrivePool has an extensive error reporting infrastructure. All error reports are written to a local folder on the server, C:\ProgramData\StableBit DrivePool\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 2.x 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.

To perform the steps outlined below, log into the Windows machine locally, or using Remote Desktop Connection.

Submit error reports

  1. Open Windows Explorer to C:\ProgramData\StableBit DrivePool.
  2. Right click on Service 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.
  5. We'll examine your error reports and get back to you.