Reporting of Errors. The Contractor shall examine and compare the Contract Documents and shall report any errors, inconsistencies, or omissions he may find to the Engineer immediately.
Reporting of Errors. Client acknowledges that it is not possible for Services provided by Bank hereunder to be free of operator, program or equipment error, and that errors in processing and compiling Account data may occasionally occur, requiring adjustments. As such Client agrees to review and verify all results and to maintain adequate controls for insuring both the accuracy of data transmissions and the detection of errors. Unless otherwise required by law Bank’s sole responsibility for reporting errors caused by Bank will be to reprocess information and reports for the applicable period and to submit corrected reports at its own expense to Client.
Reporting of Errors. Subscriber shall document and promptly report to Sectigo any errors or malfunctions in the Certificates or SCM. Upon Sectigo’s reasonable request, Subscriber shall assist Sectigo in rectifying such errors or malfunctions.
Reporting of Errors. You must promptly view all Estatements, and immediately notify Processor in writing of any errors. Your written notice must include: (i) Merchant name and account number; (ii) the dollar amount of the asserted error; (iii) a description of the asserted error; and (iv) an explanation of why you believe an error exists and the cause of it, if known. That written notice must be received by Processor within 30 calendar days after the Estatement containing the asserted error is first made available. Your failure to notify Processor of any error within 30 days constitutes a waiver of any claim relating to that error. You may not make any claim against Processor for any loss or expense relating to any asserted error for 60 calendar days immediately following Processors receipt of your written notice. During that 60 day period, Processor will be entitled to investigate the asserted error and we will notify you of the results of our investigation.
Reporting of Errors. You must promptly view all E-statements, and immediately notify EVO in writing of any errors. Your written notice must include: (i) Merchant name and account number; (ii) the dollar amount of the asserted error; (iii) a description of the asserted error; and (iv) an explanation of why you believe an error exists and the cause of it, if known. That written notice must be received by EVO within 30 calendar days after the E-statement containing the asserted error is first made available. Your failure to notify EVO of any error within 30 days constitutes a waiver of any claim relating to that error. You may not make any claim against EVO for any loss or expense relating to any asserted error for 60 calendar days immediately following EVO’s receipt of your written notice. During that 60 day period, EVO will be entitled to investigate the asserted error and we will notify you of the results of our investigation.
Reporting of Errors. Reseller shall document and promptly report to Comodo any errors or malfunctions associated with the Security Solutions and promptly assist Comodo in rectifying any such errors or malfunctions upon Comodo’s request.
Reporting of Errors. An Error by Customer shall be reported in writing to Varonis by electronic mail. Each Error Report (“ER”) shall state one Error and shall contain the following information: - A suggested Error Severity Level among one of the classes set out below; - A description of the command(s) and procedures that reveal the Error; - A description of the hardware and operating environment; - Specification of Version of the Software in question; - A short description of the Error; - Examples of input; - The resulting output; - The expected output; - Any special circumstances surrounding the discovery of the Error.
Reporting of Errors. If Customer notifies Supplier in writing that such Covered Software does not operate substantially in accordance with its Documentation, Customer shall provide to Supplier such information and materials as Supplier may reasonably request to document and reproduce such problem and to verify whether any proposed solution corrects such problem. Such information may include a written explanation of such problem, a written description of the operating environment, and (if permitted) a copy of any software program used with the Covered Software. Following the receipt of such information and materials, if Supplier determines that such Covered Software does not operate substantially in accordance with the related Documentation, then Supplier will use reasonable commercial efforts to correct or replace the defective Covered Software.
Reporting of Errors. Customer shall report any failure of the Service to function in conformity with the Documentation (an “Error”) as promptly as possible by providing the information necessary for DigitalEd to create a software problem report (“SPR”). A SPR will not be assigned a Support Case Number until all necessary information has been provided by Customer to DigitalEd.
Reporting of Errors. Customer shall report material problems or errors with the Online Classroom to MMX via e-mail at xxxx@xxxxxxxxxxxxxx.xxx and/or by other means that may be specified by MMX from time to time.