Authoring Errors

When an application fails because of an error in coding, the log records this as an Authoring Error event. The Error Type field in the log file contains more specific information that details the cause of the event. The Error Type field can contain one of the following messages:

• File %S not found.
• File %S corrupted.
• Trying to set a read-only property.
• Wrong call type in method.
• Wrong number of parameters in method.
• Wrong format of file %S.
• Scopes in the page are not valid.
• Illegal scopes in the page: tag %S (Index=%d) was closed before tag %S (Index=%d).
• Illegal scopes in the page are not valid.
• Error opening the requested URL.
• Tried to play a voice file on address that lacks audio support.
• Tried to record a voice file on address that lacks audio support.
• Tried to gather DTMF on an address that lacks detection support.
• Failed to load TTS engine.
• Volume control is not supported on the TTS engine.
• Speech control is not supported on the TTS engine.
• Pitch control is not supported on the TTS engine.
• Threshold control is not supported on the SR engine.
• Failed to load SR engine.
• A message box invoked.
• Error 0x%8x encountered.
• Too many menu items.
• Access key is not valid.
• Breaking the menu because of change in cut-through mode.
• Cannot call External after Abandon().
• Cannot call ITBasicCallControl property after drop.
• Illegal value %S set on attribute %S.
• No element with ID %S in table.
• First element with ID %S in table is not a cell.
• The frameset at %S is empty.
• Calling from a wrong thread.
• Ignores delay answering on a handed-off (answered) call.
• Warning: Gathering text input with an empty termination string and no maximum length.
• Warning: Offering multiple selection menu with an empty termination string.
• Unknown property request: %S.
• Script error: %S in %S line %D.
• Could not finish transfer.
• Abandoning the session because a script error occurred while the application was answering a call, or while WTE was processing the application's post-call page.
• Failed to send data.
• Terminal failure occurred.
• Stream failure occurred.
• Failed to process data.
• Binding failure occurred.
• Failed to write data.
• Warning: Frameset as a scriptlet is not supported. Ignoring.
• Trying to open a non-HTML document.
• Protocol %s is not supported.
• Abandoning the session because of a script error in delayed-answering or post-call page mode.
• Grammar compilation failed. %S.
• Grammar load failed.
• Warning: A tag with the name %S appears before the body. Cannot start on this hash, starting from the body.
• Warning: Access key %S on tag %S (Index=%d) will be ignored because the length of the WTEApplication.InitialAutoNumber property is greater then 1.
• Warning: Access key %S on tag %S (Index=%d) is longer then 1 character. Only the first character on the access key is taken into account.
• Grammar file %S is not in UNICODE format.
• Frame is in a different security zone from that of its parent frame.