Priority B Errors. In the event of a Priority B Error, Selectron shall, within six (6) hours of receiving Licensee’s report, commence verification of the Error. Upon verification, Selectron shall use commercially reasonable efforts to resolve the Error with an Error Correction. Selectron shall use commercially reasonable efforts to provide a workaround for the Error within forty-eight (48) hours of receiving Licensee’s report of such Error, and an Error Correction within six (6) business days of receiving Licensee’s report. Selectron shall provide Licensee with periodic reports (no less frequently than once every twelve (12) hours) on the status of the Error Correction.
Priority B Errors. Infospace shall exercise reasonable commercial efforts to include the Fix for the Error in the next Software release.
Priority B Errors. Affymetrix shall exercise commercially reasonable efforts to include the Fix for the Error in the next regular SOFTWARE maintenance release.
Priority B Errors. In the event of a Priority B Error, Q5id will, within six (6) hours of receiving Licensee’s report, commence verification of the Error. Upon verification, Q5id will use commercially reasonable efforts to resolve the Error with an Error Correction; to provide a workaround for the Error within forty- eight (48) hours of receiving Licensee’s report of such Error, and an Error Correction within six (6) business days of receiving Licensee’s report. Q5id will provide Licensee with periodic reports (no less frequently than once every twelve (12) hours) on the status of the Error Correction.
Priority B Errors. Within two (2) business days of receipt of notice from Customer of a Priority B Error, Nitorco shall assign appropriate personnel to correct the Error; provide Customer with periodic reports on the status of the corrections; and initiate work to provide Customer with a Workaround or fix. Nitorco shall undertake efforts to provide Customer with a temporary solution. Nitorco shall use commercially reasonable efforts to include the fix for the Error in the next regular maintenance release for the Services.
Priority B Errors. Within five (5) calendar days of receipt of notice from Licensee of a Priority B Error, M-Group shall assign M-Group engineers to correct the Error; provide Licensee with periodic reports on the status of the corrections; and initiate work to provide Licensee with a Workaround or Fix. M-Group shall provide Licensee with such Workaround or Fix within thirty (30) calendar days, and M-Group shall use commercially reasonable efforts to include the Fix for the Error in the next regular maintenance release for the Licensed Software.
Priority B Errors. Within forty eight (48) hours of learning of a Priority B Error, @pos.com shall assign @pos.com engineers to correct the Error; provide Xxxxxsee with perixxxx xeports on the status of the corrections; and initiate work to provide Licensee with a Workaround or Fix. @pos.com shall provide Licensee with such Workaround or Fix within sevxx (0) business days, and @pos.com shall use commercially reasonable efforts to include the Fxx xxx the Error in the next regular maintenance release within ninety (90) calendar days. 2.1.3
Priority B Errors. Within 3 business days of learning of a Priority B Error, AbsInt shall assign AbsInt engineers to correct the Error; provide LICENSEE with periodic reports on the status of the corrections; and initiate work to provide LICENSEE with a Workaround or Fix. AbsInt shall try to provide LICENSEE with such Workaround or Fix within thirty (30) business days.
Priority B Errors. (1) Minneapolis assigns a specialist to commence correction of Error and (2) Provide escalation procedures as reasonably determined by Minneapolis support staff. Minneapolis exercises all commercially reasonable efforts to include the Fix for the Error in the next Software maintenance release. Priority C Errors: Minneapolis may include the Fix for the Error in the next major Software release.
