System errors Sample Clauses

System errors. We shall have no liability to you for damage which you may suffer as a result of transmission errors, technical faults, malfunctions, illegal intervention in network equipment, network overloads, malicious blocking of access by third parties, internet malfunctions, interruptions or other deficiencies on the part of internet service providers. You acknowledge that access to Electronic Services may be limited or unavailable due to such system errors, and that we reserve the right upon notice to suspend access to Electronic Services for this reason.
AutoNDA by SimpleDocs
System errors. JHTSL shall consult with Republic to develop a process for eliminating transmission errors, to the extent practicable.
System errors. A System Error occurs when functionality that is included in the NAVITAIRE product user documentation is currently not working on Customer’s site in the manner that it is described in the documentation that shall be reasonably up to date. Note: The Customer must refer to the documentation that matches the version of software they are running. If Customer wants a feature that is not currently included in their software version, but the feature is included in a later software version, Customer must upgrade their software to that version to be able to take advantage of the new features and functionality. System Errors detected during testing in the Customer’s test environment should also be logged through Remedy with a reference to the test database code. NAVITAIRE will respond to all Emergency IPRs for the test environment within five (5) business days. No failure of any reconfiguration by Customer of a Configurable Template shall be deemed to be or can create a System Error.
System errors. Customer may report a System Error by calling the NAVITAIRE Support Center at the number provided in Section 1 of Exhibit C of the Agreement ***** or by logging it via the Internet based customer support tool (English version only). Time spent by the NAVITAIRE Support Center during the reporting of the System Error is not billable to Customer. Time spent by NAVITAIRE personnel in the resolution of such System Error (including any development efforts to modify software for such resolution into the Production Version) will not be billable to Customer except in the event that the final determination of root cause of a System Error is identified as being due to events caused by third parties or Customer misuse of the Hosted Services System, in which case all time spent by NAVITAIRE personnel in the resolution of such System Error will incur Support Fees at the rate specified in Exhibit K, Section 1.3. When Customer reports a System Error, it will be assigned an urgency by the NAVITAIRE Support Center based on: (i) whether it constitutes an Emergency as provided in the definition by product type within this Exhibit, or (ii) other classification as determined in good faith by NAVITAIRE using the following guidelines:
System errors. APM shall have no liability to the Client for damage which the Client may suffer as a result of transmission errors, technical faults, malfunctions, illegal intervention in network equipment, network overloads, malicious blocking of access by third parties, internet malfunctions, interruptions or other deficiencies on the part of internet service providers. the Client will be responsible for all orders entered on the Client behalf via the Electronic Services and the Client will be fully liable to APM for the settlement of any Transaction arising from them. the Client acknowledge that access to Electronic Services may be limited or unavailable due to such system errors, and that APM reserves the right upon notice to suspend access to Electronic Services for this reason.
System errors. We shall have no liability to you for damages which you may incur as a result of transmission errors, technical faults, malfunctions, illegal intervention in network equipment, network overloads, malicious blocking of access by third parties, internet malfunctions, power cuts, interruptions, other deficiencies on the part of internet service providers, or any factors wholly or partially outside of our reasonable control. You acknowledge that access to Electronic Services may be limited or unavailable due to such system errors or other reasons referred to in this Clause 10.16.1, and that we reserve the right upon notice to suspend access to Electronic Services for this reason.
System errors. The most probable source of system errors for isochronous transfers is underrun or overflow/overrun of the HC’s internal data buffers. An Isochronous TD is allowed to specify a single data packet of up to 1023 bytes. It is not expected that Host Controller implementations will contain sufficient internal buffering for the largest possible isochronous packet. Therefore, there is a possibility that the system will not provide timely access to the system bus to allow the Host Controller to keep up with the USB data rate in all cases. This can cause the HC’s internal buffer to overflow with data from an endpoint or to underrun and have no data to send to an endpoint when it is required. Buffer overrun happens only on IN endpoints and underrun happens only on OUT endpoints. When an underrun occurs, the Host Controller sets the ConditionCode of the data packet’s PacketStatusWord to BUFFERUNDERRUN and the size field is set to zero. Note: This underrun condition is signaled on USB by the Host Controller forcing a bit-stuffing violation with the recommendation that the bit stuff violation last 16 bit times (i.e., 16 bit times without a transition on the bus). When an overrun condition occurs, the Host Controller sets the ConditionCode of the data packet’s PacketStatusWord to BUFFEROVERRUN and writes the size field to indicate the last byte successfully received from the endpoint before the overrun condition occurred. All data received from the endpoint before the overrun condition occurred are stored in system memory. If, after detecting an overrun, the Host Controller detects a transmission error, then the transmission error is recorded in the PacketStatusWord instead of the overrun error.
AutoNDA by SimpleDocs
System errors. The Company shall consult with HSBC to develop a system for eliminating transmission errors, to the extent practicable.
System errors. If the site crashes, PHOTOGRAM tries to fix the situation as soon as possible. The Company is not responsible for any bugs in the information technology tools resulting from operation of equipment, that the User utilized to access the PHOTOGRAM site xxx.xxxxxxxxx0000.xxx, as well as for failures in performance of Internet service providers.
System errors. JHTSI shall consult with SBBT to develop a system for eliminating transmission errors, to the extent practicable.
Time is Money Join Law Insider Premium to draft better contracts faster.