The messages listed in this section are the runtime log messages that are either of class ERRORMSG or CONTROLEXITERRORMSG. In VBVLog, these logs appear with a red sign.
You can also send these log errors to the Windows System Logger by setting a level for each error and enabling the Windows System log in VBVConfig. Refer to VBVConfig to learn how to change the VBVoice.ini file.
The following list is ordered alphabetically by error name The error name is important because it is used as a unique ID when generating SNMP traps from the Windows Event Logs.
"Ambiguous control name '<data>': please rename duplicate control"
Each control in a VBVoice system must have a unique name. This error can occur when there are two or more forms containing VBVoice controls with a control on each with the same name. If an attempt is made to reference one of these controls using a property reference such as <%controlname.property>, this error will be generated.
"voice recognition license exceeded"
Voice recognition is enabled, but the license was exceeded. The correct number of lines must be licensed on this computer, and if running in an .exe, the ini settings for licensing must be set.
"Voice recognition is not enabled"
"VB set bad control name (control name)"
VB code attempted to transfer a call to a new control through the GotoControl property or TakeCall method, but the specified control does not exist.
"Bad date specification (date string)"
Generated by phrase processor in System phrase - Say Date.
"Bad digits in phrase (phrase name)"
The system was using SayDigits when it encountered an invalid character in the string for this phrase type.
"VB set bad node (node number)"
VB code attempted to transfer a call to a new control through the GotoNode property, but the specified control name does not exist.
"Bad number (dial string)"
A Dial control attempted to dial a number that does not contain valid characters.
"Bad time spec (string)"
Generated by phrase play function when playing a System phrase of type Say Date, Say Time.
"Cannot create unique file"
Generated by the Record control when it is building a new record filename. It tries 30 times to create a unique filename based on the record file specification in the Record property page, and then gives up and logs this message.
"Cannot open ODBC database '<database name>'"
A DataFind control attempted to open an ODBC database, but the call to ODBC failed. Check the ODBC Connect string.
"Cannot open record file '<data>'"
"Cannot play VB Phrase in design mode"
A System phrase of type VB Phrase was specified in a greeting. VBVoice was unable to play the phrase because VB was is design mode. Put VB into run mode and try again.
"Data control error <code> < description>"
An error occurred while accessing a recordset provided by a Visual Basic data control. The description should give a clue about the problem, if not check the error code against the trappable database error codes in the VB help file, and also the error codes provided at the end of this chapter.
"Conference control not authorized, or mvip bridging is in use"
This message can occur if:
1) the conference control is not authorized. In this case, it is limited to 2 conferees, in bridging mode only. Authorization for full conferencing can be purchased from Pronexus Sales.
2) The conference hardware in use does not support full conferencing, and/or the MVIPBridging INI setting is set to true.
"Couldn't create the inner timer for conference control"
"Control error"
"Control not found (control name)"
A control name was referenced in a property page field for substitution i.e. using %Controlname% syntax, but the control does not exist. If in VB design mode, check that the form containing the control is showing or minimized. The controls are not loaded into the system until the form is loaded.
If VB is in run mode, ensure that the form containing the control is loaded using a Form.Load or a Form.Windowstate statement. This statement should appear in the Load event for the startup form, or in Sub Main, depending on what has been set in Options/Project for the startup form.
See the CALLANS form in the VMDEMO example for an example. Generally you want to display the forms while testing, but have them hidden when creating your .exe. Use a command line option to hide the forms in run environment, but not in the VB environment. You can set command line options in Visual Basic environment using the Options... Project menu. To hide a form without unloading it, use the forms Visible property, or set its position off the screen.
"CustomErrorx %s"
This is a set of ten predefined custom errors starting from CustomError0 to CustomError9.
These errors are generated when the member function AddErrorItem is called on the object VBVLog, which is defined in vbvcom.dll library passing a type between 0 and 9.
The %s is replaced with the message provided with this function call. Assign each error to a class of errors that you are interested in monitoring in your application.
Log these errors into various logs: VBVLog, NLog, Windows System Logs and/or SNMP traps.
"Trappable database error <code> '<description>'"
An error occurred while accessing a recordset provided by code, using the Microsoft DAO interface.
"Data not set in control (controlname)"
This message occurs when an attempt is made to access a default property from a control that does not have one. Since this condition is checked at startup, this message should never happen, except when the system has been started and an attempt is made to access a property that has not been set yet - like a forward reference, or at design time when a property page is used to provide the default property and the Cancel button is pressed. The data provided with the message is the name of the control in question.
"Dialogic event <data>%i in <data>"
The Dialogic driver has reported an unexpected event. Please contact Pronexus Technical Support.
"Dialogic error <errornumber> in <name>"
The Dialogic driver has reported an error. Please contact Pronexus Technical Support.
"Field not found ( <data> )"
"File open error (filename) (error code)"
The specified file could not be opened. Check the path (if supplied) is correct. If no path is supplied, the file must exist in the VBV default directory.
The error code is one of the following: (hex values)
|
ERROR_FILE_NOT_FOUND |
0x2 |
|
ERROR_PATH_NOT_FOUND |
0x3 |
|
ERROR_TOO_MANY_OPEN_FILES |
0x4 |
|
ERROR_ACCESS_DENIED |
0x5 |
|
ERROR_INVALID_ACCESS |
0xC |
|
ERROR_INVALID_DRIVE |
0xD |
|
ERROR_NOT_SAME_DEVICE |
0x11 |
|
ERROR_NO_MORE_FILES |
0x12 |
|
ERROR_WRITE_PROTECT |
0x13 |
|
ERROR_NOT_READY |
0x15 |
|
ERROR_SEEK |
0x19 |
|
ERROR_WRITE_FAULT |
0x1D |
|
ERROR_READ_FAULT |
0x1E |
|
ERROR_GEN_FAILURE |
0x1F |
|
ERROR_SHARING_VIOLATION |
0x20 |
|
ERROR_LOCK_VIOLATION |
0x21 |
|
ERROR_SHARING_BUFFER_EXCEEDED |
0x24 |
|
ERROR_HANDLE_EOF |
0x26 |
|
ERROR_HANDLE_DISK_FULL |
0x23 |
|
ERROR_DISK_FULL |
0x70 |
"Invalid phrase <data>"
"Invalid tapi condition in '<data>'"
"No connection on node (node number, node name)"
An attempt was made to transfer to another control, but the node selected for transfer is not connected, or is connected but VBVoice cannot find the destination control. Since the system is checked for complete connection integrity before system start up, this message should not normally occur except in test mode.
In systems with more than one VBVoice form, you must ensure that all forms are displayed, or loaded and minimized, before starting a test. VBVoice is not able to find controls on forms that have not been opened.
"No data in control (control name)"
This message occurs when an attempt is made to access a default property from a control that does not have one.
In test mode, the system prompts you to enter some data, rather than generating this error message. If you press Cancel, this message is generated.
At runtime, you may get this message when the system has been started and an attempt is made to access a property that has not been set yet - like a forward reference.
The data provided with the message is the string that references the control.
"Database not accessible in design mode"
VB data controls do not allow access to the underlying database when VB is in design mode. To allow access to your data during testing, start VB in run mode using the Run/Start menu command, and then restart your test. Note that if you have multiple forms, they must be explicitly loaded by Visual Basic code in the Form Load event or Sub Main. See Running your application in the User's Guide.
"No active fax server"
In the SendFax or ReceiveFax control, the fax server was not found or was not able to send or receive the fax. This may occur if there is no active call when performing a same-call fax.
"No recordset defined: use SetRecSource method"
A DataFind control was set to open a Recordset using code, however no recordset was assigned using the SetRecSource method.
"Cannot start test in VB break mode"
You can start a test when Visual Basic is in design mode (with some limitations, see User's Guide, chapter on Test Mode), and also in Visual Basic run mode. You cannot start a test when in break mode - either stop Visual Basic and return to design mode, or restart Visual Basic and return to run mode.
"Phrase requires language control event: VB not in run mode"
A phrase was used which has been enabled in a Language control for custom processing. VBVoice was unable to fire the event because VB was not in run mode.
"ODBC error <code> < description>"
An error occurred while accessing a recordset provided by ODBC. The description should give a clue about the problem, if not check the section below for a list of possible error codes.
"Dispatch error <error code> <description>'"
An error occurred while using OLE Automation to access an OLE object.
"Stopped - no connection on exit node"
"stopped - phrase error"
"tapi error '<data>', '<data>'"
"text-to-speech license exceeded"
Text-to-speech is licensed separately and must be enabled. When running in an exe, the ini settings to enable the correct number of TTS lines must be set.
"Text-to-speech is not enabled"
"unexpected event (event name)"
VBVoice encountered an event from the voice driver for which it has no predefined response. Please contact Pronexus Technical Support.
"control error type <type #> data <##>"
An unexpected error occurred. If this message appears without any other explanatory messages, please send us a copy of the log, together with a description of what was occurring at the time.
"<phrasename>: vap phrase id <name> not found"
The VAP file does not contain a phrase of the specified name. Normally this error will be detected on system start, unless phrases are being created buy code, or by using embedded %% control names, or more than one language is in use.
"vap phrase not found, file (filename), phrase (phrasename)"
VBVoice was unable to process the phrase as defined. Normally due to the phrase as named does not exist in the VAP phrase specified.
"Failed to append <Wave> to <File>: <Error>"