Reporting an Error Sample Clauses

Reporting an Error. 3.2.1 Upon discovery of an Error, Licensee should report the incident via the Micro Focus SupportLine internet or contact the Micro Focus SupportLine Help Desk and provide the following information: i) Serial number of Maintained Software (if initial contact) or incident number (if subsequent call to a Reported Error). A new incident number will be assigned at the time the incident is reported and provided to the Licensee for future related calls/inquiries; ii) Licensee information, as needed (name, organization, location, phone number, fax, email); iii) Full product name and version number of Maintained Software; iv) Any third party or other environmental information necessary to understand the problem; v) Description of the problem and steps necessary to recreate the problem, including sample programs, files, etc. as necessary; and vi) Where appropriate a minimal length of source code program that demonstrates the Reported Error. 3.2.2 Upon receipt of an Error report and the information listed in Clause 3.2.1 above, Micro Focus will attempt to reproduce the Reported Error within a commercially reasonable timeframe. If the Reported Error is confirmed, the Reported Error shall become a Confirmed Error and Micro Focus will use reasonable efforts to provide a Correction. All Errors must be demonstrable on the Reference Environment and Support Services will be provided for the Reference Environment(s) only. If Micro Focus develops, or has previously developed, a Correction for a Confirmed Error and includes, or has included, that Correction within an Update, Micro Focus may, at its option, provide Licensee with only the Update instead of providing the specific Correction. When provided under this Agreement, such Correction or Update will be provided to Licensee without additional charge. Should the situation arise where Micro Focus reasonably determines that for technical reasons a Correction cannot be achieved by Micro Focus using commercially reasonable efforts and/or within a reasonable time, then Micro Focus will notify Licensee of this fact and will work with Licensee to agree on the course of action to be taken. 3.2.3 In the event that Micro Focus is unable to take a Reported Error and reproduce it at Micro Focus’ premises for diagnostic purposes, Licensee may provide Micro Focus with direct access to Licensee's system on which the Reported Error has occurred for the purposes of remote diagnostic efforts to determine the cause. The parties will ensure t...
AutoNDA by SimpleDocs
Reporting an Error. Customer agrees to: (i) provide Memcyco with reasonable detail of the nature of and circumstances surrounding the Error, (ii) provide a contact person with knowledge of the Error and availability to troubleshoot. Customer must first open a support ticket on Memcyco’s website. For Critical Errors Customer must then contact the Memcyco Technical Support by phone at the number indicated below. Please see below for the contact information for Customer Support.
Reporting an Error. The Honoree undertakes to immediately inform the Executor of any error. For this purpose, the Client sends the Contractor an "Error Report", which states: a) Name of the Customer and technical information about the Customer (phone number, e- mail address, working hours; b) each available serial number from the defective part of the Services; c) within reasonable limits, a detailed description of the Error, as well as any information that, in the opinion of the Customer's engineers, will help the Contractor in performing diagnostics ( including, for example, when the problem first appeared, damaged systems, error message, etc.) and d) the date of the Error Report sent to the Performer. The Customer can contact the Contractor with the aim of submitting an Error Report during the following business hours (hereinafter: Business Hours): 09:00-18:00 Data of the performer: E-mail: xxxxxxx@xxxxxx.xx For the purpose of interpretation of the Services provided under this Agreement, Availability is calculated according to the formula presented below: The period of violation is calculated from the moment of submission of the "Error Report", from the moment the Customer reaches the Contractor's e-mail address, which informs about non-compliance with the quality of the above-mentioned Services, in confirmation, presenting the errors to the Contractor until correction. The next presented period is not considered as the period of the Violation. • Non-compliance of the Services with the quality of the services provided due to the exceptional reasons listed in the Agreement, which can be studied at the following link; • The time spent by the Contractor for the removal of errors not mentioned in the Communication by the Contractor.
Reporting an Error. Customer agrees to test and verify, on an isolated development environment, any suspected Errors in the Software. Customer will report suspected Errors with the Software via ClearBlade’s web‐based ticketing system at xxx.xxxxxxx.xxxxxxxxxx.xxx.
Reporting an Error. 3.2.1 Upon discovery of an Error, Licensee should report the incident via the Micro Focus SupportLine internet or contact the Micro Focus SupportLine Help Desk and provide the following information: i) Serial number of Maintained Software (if initial contact) or incident number (if subsequent call to a Reported Error). A new incident number will be assigned at the time the incident is reported and provided to the Licensee for future related calls/inquiries; ii) Licensee information, as needed (name, organization, location, phone number, fax, email); iii) Full product name and version number of Maintained Software; iv) Any third party or other environmental information necessary to understand the problem;

Related to Reporting an Error

  • CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11164 et seq. and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Child Abuse Reporting Requirement Grantee will: a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements. c. use the System Agency Child Abuse Reporting Form located at xxxxx://xxx.xxxx.xxxxx.xx.xx/Contact Us/report abuse.asp as required by the System Agency. d. retain reporting documentation on site and make it available for inspection by the System Agency.

  • Notification of Error The Trust will notify USBFS of any discrepancy between USBFS and the Trust, including, but not limited to, failing to account for a security position in the Fund’s portfolio, upon the later to occur of: (i) three business days after receipt of any reports rendered by USBFS to the Trust; (ii) three business days after discovery of any error or omission not covered in the balancing or control procedure; or (iii) three business days after receiving notice from any shareholder regarding any such discrepancy.

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • Log and Load Reporting Service This contract may at the States discretion, require the services of a State approved third party log and load reporting service. Purchaser shall ensure log volume measurement, weight, or scale and weight data for each load is received by the log and load reporting service within 1 business day of logs being measured or weighed. If during the term of this contract, the State discontinues use of the Log and Load Reporting Service, the State will notify the Purchaser in writing, and will approve an alternative log and load reporting process. Determination of volume and grade of any forest products shall be conducted by a state approved third party scaling organization and in accordance with the Westside log scaling and grading rules and Xxxxxxxx Volume Table, revised July 1, 1972, contained in the Northwest Log Rules Eastside and Westside Log Scaling Handbook (developed and produced by the Northwest Log Rules Advisory Group) and in effect on the date of confirmation of this contract. Special scaling specifications shall be noted on the State’s Brand Designation form which is hereby incorporated to this contract by reference. Forest Product measurement and weighing facilities required by this contract must be approved by the State. Forest products sold under the contract which require log scaling shall be scaled, measured, or counted by a State approved third party log scaling organization. Forest products sold under the contract which require weighing shall be weighed at a location that meets Washington State Department of Agriculture approval. Prior to forest products being hauled, the Contract Administrator must authorize in writing the use of State approved measurement and/or weighing facilities that are at or en-route to final destinations. Forest products from this sale shall be measured or weighed at facilities, which are currently approved for use by the State and are currently authorized for this sale. The State reserves the right to verify load volume and weights with State employees or contractors at the State's own expense. The State reserves the right to revoke the authorization of previously approved measurement locations.

  • Information for Regulatory Compliance Each of the Company and the Depositary shall provide to the other, as promptly as practicable, information from its records or otherwise available to it that is reasonably requested by the other to permit the other to comply with applicable law or requirements of governmental or regulatory authorities.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.

  • DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with XXX. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A. b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and XXX, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915. c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!