Share via

2.2.3 CER File Share Folder Structure

  • Article

 The Corporate Error Reporting Version 1.0 Protocol specifies two globally unique file path locations per CER file share, the root-level location of policy.txt (section 2.2.4) and the root-level location of crash.log (section 2.2.2.2).

 Every type of error report also uses individual count.txt (section 2.2.1), hits.log (section 2.2.2.1) and status.txt (section 2.2.5) files. Each specific instance of an error also has a single error report file, whose name is generated by the CER client. In the examples below, the term "<error reporting file>" is substituted for the actual file name. Every error report looks for the count.txt, hits.log (if the tracking feature is enabled), and status.txt files, and writes its error reporting file, using a standard scheme. The scheme uses the concept of the error subpath SMB file server directory path fragment, whose specifics will be discussed under each kind of report.

 The terms below in angle brackets ("<" and ">") are placeholders, not literals. The actual values MUST be made up solely of ASCII characters. They MUST NOT contain prohibited characters in the filesystem environment in which they operate, and the directory names MUST NOT consist of prohibited names in the file system environment in which they operate. <1>

 Once the CER client generates the error signature specific file names (having replaced the placeholders in the error subpath with the proper parameters for the particular error report), it MUST compute the length of these filenames. If any of them are longer than 260 characters, the report MUST be discarded by the CER client.

 If the directory paths required for these files do not exist on the CER file share, the CER client MUST create them.

 The form of the path names MUST be as follows, where the <UNC file share path> represents the path to the CER file share.

Global files

 <UNC file share path>\policy.txt
 <UNC file share path>\crash.log

Error signature-specific files

 <UNC file share path>\cabs\<error subpath>\<error reporting file>
 <UNC file share path>\cabs\<error subpath>\hits.log
 <UNC file share path>\status\<error subpath>\status.txt
 <UNC file share path>\counts\<error subpath>\count.txt