The support tools launcher is a command line and menu selection type utility. It allows users to launch the support tools which are encrypted in a self-extracting zip file.
Severity Major
Description A program exception occurred while processing DSP event or API command.
Impact The channel will be reloaded.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP media drivers. If the problem persists, contact your Nortel support organization.
Severity Minor
Description An unexpected DSP event was received by the LLS and ignored.
Impact Not applicable.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP media drivers. If the problem persists, contact your Nortel support organization.
Severity Minor
Description An unexpected API command was received by the LLS and ignored.
Impact Not applicable.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP media drivers. If the problem persists, contact your Nortel support organization.
Severity Minor
Description An unexpected Windows message was received by the LLS and ignored.
Impact Not applicable.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP media drivers. If the problem persists, contact your Nortel support organization.
Severity Major
Description A media handler returned an error code to the LLS.
Impact The application command in progress will be terminated. The DSP channel may be reloaded.
Recovery Action This could indicate a hardware problem. Diagnostics should be run on the indicated hardware.
Technical Support Action Replace the hardware on which the problem was reported.
Severity Minor
Description The DSP could not execute a command.
Impact The DSP command will not be executed. The application impact will depend in the particular command.
Recovery Action Disable and re-enable the affected DSP channel.
Technical Support Action This could indicate software problem in the DSP media drivers. If the problem persists, contact your Nortel support organization.
Severity Major
Description A an error was returned by the operating system during a system call.
Impact An event will be lost by the board or channel.
Recovery Action Disable and re-enable the affected DSP channel.
Technical Support Action This could indicate software problem in the DSP media drivers. If the problem persists, contact your Nortel support organization.
Severity Major
Description The main DSP task has not replied to an audit command. This may indicate that the DSP is not functioning.
Impact The DSP will be reloaded.
Recovery Action This could indicate a hardware problem. Diagnostics should be run on the indicated hardware.
Technical Support Action Replace the hardware on which the problem was reported.
Severity Information
Description The DS30 clock may lose synchronization during an M1 CPU switchover. When this is detected, the LLS forces the clock to re-synchronize.
Impact Noise will be heard on the active voice channels until the clock is synchronized.
Recovery Action This could indicate a hardware problem on the M1. Determine the reason for the M1 CPU switchover.
Technical Support Action Not applicable.
Severity Major
Description A program exception occurred while performing a DSP recovery operation. A reload operation will be attempted. Check the instance for the DSP and channel number.
Impact The channel will be reloaded.
Recovery Action Run out-of-service diagnostics. Replace any faulty hardware and reboot.
Technical Support Action Re-flash the DSP firmware. Use C52util to determine if all configured DSPs are booting. Replace any DSPs that do not boot.
Severity Minor
Description DSPs require the DS30 clock to correctly process voice data from the PBX. This clock signal was not being received from the DSP hardware.
Impact Voice processing functions on the DSP may not operate correctly.
Recovery Action Run out-of-service diagnostics. Check that the DS30 and SCBUS cables are properly installed. Replace any faulty hardware and reboot.
Technical Support Action Replace any DSPs or carrier boards that exhibit this problem.
Severity Minor
Description Diagnostics are run by the DSP firmware and then the DSP is booted. If these fail, this event is reported.
Impact The DSP may not be functional.
Recovery Action Run out-of-service diagnostics. Replace any faulty hardware and reboot.
Technical Support Action Replace any DSPs or carrier boards that exhibit this problem.
Severity Major
Description A timeout occurs when LLS tries to synch up with TalkListen object on TSP.
Impact Unable to playback or record voice for a particular channel.
Recovery Action Make another call and see if the problem persists. Check the event log for other related operating system events. Reboot the server.
Technical Support Action This could indicate software problem in named pipe or a frozen system.
Severity Major
Description DSP returns an error when LLS tries to set interrupt interval for PCM data.
Impact Unable to playback or record voice for a particular channel.
Recovery Action Make another call and see if the problem persists. Disable and re-enable the affected DSP channel. Check the event log for other related operating system events. Reboot the server.
Technical Support Action This could occur if the DSP is not in healthy state. Check DSPerr to see what actually caused the error.
Severity Major
Description Unable to create a semaphore or event handle which is used to communicate with the Talk/Listen object on the TSP side.
Impact Unable to playback or record voice for a particular channel.
Recovery Action Make another call and see if the problem persists. Check the event log for other related operating system events. Reboot the server.
Technical Support Action This could occur if the OS is not in healthy state. Check Win32_rc to see what actually caused the error.
Severity Major
Description LLS receives a named pipe openclosed notification but cannot find the channel task associated with the pipe.
Impact If the notification is open, then LLS is unable to playback or record voice for a particular channel. If the notification is closed, then there is potentially memory leak.
Recovery Action Make another call and see if the problem persists. Check the event log for other related operating system events. Reboot the server.
Technical Support Action This could occur if there is memory corruption or bug in the code. Reboot the server and see if it helps.
Severity Minor
Description DSP returns an error when LLS tries to initialize the circular buffer in DSP.
Impact May play back or record some glitches in the beginning of the operation.
Recovery Action Make another call and see if the problem persists. Disable and re-enable the affected DSP channel. Check the event log for other related operating system events. Reboot the server.
Technical Support Action This could occur if the DSP is not in healthy state. Check DSPerr to see what actually caused the error.
Severity Major
Description Unable to create a semaphore or event handle which is used to communicate with the Talk/Listen object on the TSP side.
Impact Unable to playback or record voice for a particular channel.
Recovery Action Make another call and see if the problem persists. Check the event log for other related operating system events. Reboot the server.
Technical Support Action This could occur if the system is out of memory or memory corruption. Reboot the server and see if it helps.
Severity Minor
Description LLS is unable to release a semaphore which results in the Talk/Listen object not notified of outgoing PCM voice data.
Impact Unable to playback a portion of the voice message for a particular channel.
Recovery Action Make another call and see if the problem persists. Check the event log for other related operating system events. Reboot the server.
Technical Support Action This could occur if the Talk/Listen is too busy retrieving signals from the semaphore or the OS is not in healthy state. Check Win32_rc to see what actually caused the error.
Severity Minor
Description The ASR resource was unable to retrieve the context data in a command handler or callback function.
Impact The ASR command or callback will be ignored. This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Minor
Description The ASR resource was unable to switch the DSP task for this channel to ASR. The ASR DSP task must be loaded for ASR to be operational.
Impact ASR may not be operational for this channel.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem in the MPC ASR driver. If the problem persists, verify the MPC firmware and reload the firmware if required.
Severity Minor
Description The ASR resource was unable to perform a KVSet operation for this channel to ASR.
Impact ASR may not be operational for this channel.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem in the MPC ASR driver. If the problem persists, verify the MPC firmware and reload the firmware if required.
Severity Minor
Description An error was encountered while executing an ASR API call.
Impact This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Minor
Description The ASR resource was unable to abort an ASR session.
Impact This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Minor
Description The ASR resource was unable to assign a unique transaction ID while executing an ASR command.
Impact This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Minor
Description The RTC Process was not completed.
Impact This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Minor
Description The ASR resource was unable to read the PCM sample buffer when the tokenizer timeout expired.
Impact This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Minor
Description The event was not the right one when double check the event.
Impact This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Minor
Description The timer could not be started.
Impact This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Minor
Description The data was not found in Database.
Impact This ASR channel may not be operational.
Recovery Action Disable and re-enable the MPC channel specified in the event browser.
Technical Support Action This could indicate software problem the CTM component. If the problem persists, reboot the server.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Conference Scheduling Unit. It may have impact on Conference Application or LDAP Server.
Recovery Action None.
Technical Support Action This Event contains all the error information received from the CSU. Note that the appropriate return code was returned to the calling client and therefore can be used to track down what user operation was being performed when the problem occurred.
Severity Minor
Description This event provides information about the conference that could not be started.
Impact There is no impact to the system
Recovery Action Try to reschedule specified conference.
Technical Support Action This event means that MP Card, with conferences scheduled to be on it, was reduced from the system.
Severity Info
Description This is an informational event to indicate that the Audio Conference application has started.
Impact There is no impact to the system.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity Major
Description Audio Conference application can not be started.
Impact No conference can be scheduled. This may signal general memory allocation problems.
Recovery Action Do the following:
Shut down the SLEE service and than re-start it again.
If the problem persists, contact your Nortel representative.
Technical Support Action Reason indicates, wich module of the application has failed to start up. The return code (rc) was returned by the module.
Severity Info
Description This is an informational event to indicate that the Audio Conference application has re-started after the number of channels has been changed.
Impact There is no impact to the system.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity Minor
Description Audio Conference application can not be re-started with the larger number of channels.
Impact Existing conferences will not be affected. New conferences can be scheduled within the old limit of channels.
Recovery Action Do the following:
If you still wish the number of channels for conferencing to be expanded, then shut down the SLEE service and than re-start it again.
Contact your Nortel representative.
Technical Support Action Reason indicates, wich module of the application has failed to start up. The return code (rc) was returned by the module.
Severity Info
Description Indicates that Audio Conference application has stopped.
Impact There is no impact to the system.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity Minor
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates an Audio Conference communication problem. The message may be lost, that may affect application's behaviour.
Recovery Action Do the following:
Stop and re-start the Audio Conference Application.
If the problem persists, contact your Nortel representative.
Technical Support Action This Event contains all the error information received from the application. Session id is equal to Instance.num. Retrieve the AudioCnf.log file.
Severity Minor
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates an Audio Conference communication problem. The message may be lost, that may affect application's behaviour.
Recovery Action Do the following:
Stop and re-start the Audio Conference Application.
f the problem persists, contact your Nortel representative.
Technical Support Action This Event contains all the error information received from the application. Session id is equal to Instance.num. Retrieve the AudioCnf.log file.
Severity Minor
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. Message might be lost, that may affect application's behaviour.
Recovery Action Do the following:
Stop and re-start the Audio Conference Application.
If the problem persists, contact your Nortel representative.
Technical Support Action This Event contains all the error information received from the application. Session id is equal to Instance.num. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference application, while handling either incoming or out-going call.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, the application's id is AppID. The return code (rc) shows the reason for the call to be rejected. Please refer to the "Audio Conference" check list.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information, received from the application. Line id and CardID of both channels are psecified in "Details" field. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information, received from the application. Line id and CardID of both channels are specified in "Details" field. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem happened, while waiting for incoming call. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Note that the return code (rc) in this Event is returned by the middleware. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Retrieve the AudioCnf.log file.
Severity Debug
Description This event provides information wich may be valuable in debugging conference errors. This information should be passed on to your Nortel representative.
Impact This event indicates a problem with Audio Conference applicative state machine. It may also indicate a problem in the middleware, which would affect overall system performance.
Recovery Action Not applicable.
Technical Support Action This Event contains all the error information, received from the application. Line id is equal to Instance.num, is placed on the card with the CardID and participates in the conference associated with the MeetingID. Retrieve the AudioCnf.log file.
Severity Information
Description Name of tool is launching and who launch this tool.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Display control file cannot be opened.
Impact Submenu cannot be selected.
Recovery Action Try again. If problem persistss, contact the Customer Service Representative.
Technical Support Action Shutdown all tools launcher. Remove the directories (tltemp and cptemp). Look for the Operating System problem.
Severity Major
Description Display control file is corrupted.
Impact Submenu cannot be selected.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Re-install the self-extracting zip file (tools2.exe) to \nortel\bin directory
Severity Minor
Description Directory cannot be opened. Only happen when the multiple launchers are launching within a short time intervals (50ms) or the directory is using by another application.
Impact Tools Launcher cannot be launched.
Recovery Action Close all application (explorer or command prompt) using the directory.(tltemp or cptemp) and try again
Technical Support Action Not Applicable
Severity Major
Description Invalid type of record in display control file.
Impact Submenu cannot be selected.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Re-install the self-extracting zip file. (tools2.exe) to \nortel\bin directory
Severity Major
Description Invalid access level of a tool or submenu from a record in display control file.
Impact Submenu cannot be selected.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Re-install the self-extracting zip file. (tools2.exe) to \nortel\bin directory
Severity Major
Description Memory is used up, not enough memory to run the launcher. Launcher will quit immediately except if there is insufficient memory occurs when launching a tool.
Impact Submenu or Tools cannot be selected or launched.
Recovery Action Free up some memories by closing some unnecessary tools.
Technical Support Action Look for memory leak problem by using windows task manager.
Severity Minor
Description This is an unexpected error, pointer is not expected to be NULL. System Problem.
Impact Launcher will quit immediately. Tools and Submenu cannot be launched or selected.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the Operating System Problem.
Severity Minor
Description Unable to rename the tools executable file when the tool is existed already. System Problem
Impact Tool is unable to launch.
Recovery Action Follow these steps:
Check the disk spaces whether is full in the drive where you execute the Tools Launcher.
Shut down all equivalent tools if exist.
Try to launch the tool again. If problem persists, contact the Customer Service Representative.
Technical Support Action Shutdown all tools launcher. Remove the directories (tltemp and cptemp). Look for the Operating System problem.
Severity Minor
Description Problem to get the exit code of the tool when trying to query its status.
Impact The tool may not function properly.
Recovery Action Close the tool if it still exists and re-launch the tool again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on the tool and operating system.
Severity Major
Description Process cannot be launched. System Problem.
Impact Tools launcher may not be launched. Tools and Submenu may not be launched or selected.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on the Operating System
Severity Major
Description Cannot wait the process to finish. System Problem.
Impact Tools launcher may not be launched. Tools and Submenu may not be launched or selected.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on the Operating System.
Severity Major
Description Cannot get the exit code of the process. System Problem.
Impact Tools launcher may not be launched. Tools and Submenu may not be launched or selected.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on the Operating System.
Severity Minor
Description The current Tools Launcher exceeds the maximum number of tools can be launched
Impact Tool is unable to launch.
Recovery Action Close one of the launched tool or use another tools launcher.
Technical Support Action Not Applicable
Severity Major
Description Cannot find the display control file after unzip from a self-extracting zip file.
Impact Submenu cannot be selected.
Recovery Action Follow these steps:
Check the disk spaces whether is full in the drive where you execute the Tools Launcher.
Re-launch the tools launcher and select the submenu.
Technical Support Action To check whether the display control file is in the self-extracting zip file (tools2.exe). If not, re-install the zip file to \nortel\bin directory. Note : the filename of the display control file can be found from the control file (control.men)
Severity Minor
Description Not all accessible tools can allow user to choose. System Problem.
Impact Tools launcher terminates immediately.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on the Operating System
Severity Minor
Description Cannot create a thread to close the tools handle in a time interval
Impact Tool may launch slowly.
Recovery Action Not Applicable
Technical Support Action Look for the problem on the Operating System.
Severity Major
Description Cannot rename the 1st level self-extracting zip file. System Problem.
Impact Tools launcher terminates immediately.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Follow these steps:
1. Check the system return error code.
2. Check the version of the tools self-extracting zip file matches the version of the Tools Launcher by executing the nbsa_btl -vt in the \nortel\bin directory. If not, re-install the self-extracting zip file tools2.exe to \nortel\bin directory.
3. Check the first level self-extracting zip file (tools.exe) is in the tools self-extracting zip file.
4. Check the disk spaces whether is full in the drive where you execute the Tools Launcher.
Severity Major
Description The application executable file cannot be opened. System Problem.
Impact The Application (tool) cannot be launched.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on the Operating System
Severity Major
Description Unable to create thread to launch the tool.
Impact The Application (tool) cannot be launched.
Recovery Action Close some unnecessary tools and try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the memory leak and operating system problems.
Severity Major
Description Self-extracting zip file is missing.
Impact Tools launcher cannot be started.
Recovery Action Ensure the tools self-extracting zip file (tools2.exe) is in \nortel\bin which should also be in the path environment variable with the drive letter where MAS installed. If it is not in the \nortel\bin directory, contact the Customer Service Representative. If the \nortel\bin is not in path environment variable, add it in the variable.
Technical Support Action Re-install the tools self-extracting zip file (tools2.exe) to \nortel\bin directory
Severity Major
Description The application executable file is already existed in the copy or launch directory.
Impact The Application (tool) cannot be launched.
Recovery Action Close all tools launchers and try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Remove the directory tltemp and cptemp in the current directory.
Severity Major
Description The application executable file is missing the self-extracting zip file.
Impact The Application (tool) cannot be launched.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action To check whether the tools executable file is in the self-extracting zip file (tools2.exe). If not, re-install the zip file to \nortel\bin directory. Note : the filename of the tools file can be found from the control file (control.men)
Severity Major
Description Unable to open the renamed first level self-extracting zip file. System Problem.
Impact Tools launcher cannot be started.
Recovery Action Close all tools launchers and try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Remove the directory tltemp and cptemp in the current directory
Severity Minor
Description The renamed filename for the application executable file or for the first level self-extracting zip file is already existed in the launch directory.
Impact Tools Launcher or the application cannot be launched.
Recovery Action Wait one second and try again.
Technical Support Action Not Applicable
Severity Minor
Description Users type the wrong login id or password within 3 times consecutively.
Impact Tools launcher cannot be started.
Recovery Action Try to launch the tools launcher again and enter the correct password. If everyone forgets the password, contact the Customer Service Representative.
Technical Support Action To reset passwords for all users, re-install the file tools.tpd in the \nortel\data directory.
Severity Major
Description Mutex cannot be created. System Problem.
Impact Tools launcher cannot be started.
Recovery Action Close all unnecessary tools and try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on the operating system.
Severity Major
Description Display control file is already existed in the launch directory.
Impact Submenu cannot be selected.
Recovery Action Close all tools launchers and try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Remove the directory tltemp and cptemp in the current directory.
Severity Major
Description Unable to get the current directory. System Problem.
Impact Tools launcher cannot be launched.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on Operating System.
Severity Major
Description Cannot get the mutex. System Problem.
Impact Tools launcher may not be launched. Tools and Submenu may not be able to launch or select.
Recovery Action Try it again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on Operating System.
Severity Major
Description First level self-extracting zip file is already existed in the launch directory.
Impact Tools launcher cannot be started.
Recovery Action Exit all tools launcher if any. Remove the launch directory.
Technical Support Action Not Applicable
Severity Major
Description Invalid password in the display control file.
Impact Submenu cannot be selected.
Recovery Action Try it again. If problem persists, contact the Customer Service Representative.
Technical Support Action To check whether the display control file in the self-extracting zip file (tools2.exe) has the password at the top of the file. If not, re-install the zip file to \nortel\bin directory. Note : the filename of the display control file can be found from the control file (control.men)
Severity Minor
Description Invalid to close an application handle
Impact Tool may not be launched properly.
Recovery Action Try to launch the tool again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the operating system problem.
Severity Information
Description Event or Error is recovered.
Impact No impact on system. However, the tool or submenu may not be launched or selected.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Tool misses at least one DLL
Impact The tool cannot be launched.
Recovery Action Check if the path environment variable has the path \nortel\bin and \dsp with the drive letter where MAS installed. If not, add them in the variable. If problem persists, contact the Customer Service Representative.
Technical Support Action Check all required DLL for that tool is located at \nortel\bin or \dsp directory.
Severity Minor
Description Unable to encrypt the user input password since at least one character in the password is invalid.
Impact Password cannot be changed.
Recovery Action Choose another password.
Technical Support Action Not Applicable
Severity Major
Description Uable to decrypt the password in the password file.
Impact Unable to use the launcher as well as to change the password.
Recovery Action Try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Reinstall the default password file (tools.tpd) to the \nortel\data directory.
Severity Major
Description Unable to write the encrypted password into file.
Impact Unable to change the password.
Recovery Action Close all tools Launchers and try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Follow these steps:
1. Check if the file tools.tpd exists in \nortel\data directory.
2. Look for the problem on Operating System.
Severity Major
Description Unable to open the password file for writing.
Impact Unable to change the password.
Recovery Action Close all tools Launchers and try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Follow these steps:
1. Check if the file tools.tpd exists in \nortel\data directory.
2. Look for the problem on Operating System.
Severity Minor
Description Unable to find the executable file for the launcher.
Impact Unable to use the launcher.
Recovery Action Check if the path \nortel\bin with the drive letter of MAS installed is in the path environment variable. If not, add it in the variable.
Technical Support Action Not Applicable
Severity Major
Description Unable to find the password file in the current directory or in \nortel\data
Impact Unable to use the launcher as well as to change the password.
Recovery Action Contact the Customer Service Representative.
Technical Support Action Re-install the password file (tools.tpd) to the \nortel\data directory.
Severity Major
Description The checksum for the password file is invalid.
Impact Unable to use the launcher as well as to change the password.
Recovery Action Contact the Customer Service Representative.
Technical Support Action Re-install the password file (tools.tpd) to the \nortel\data directory.
Severity Minor
Description Invalid user to change the password.
Impact Unable to change the password. System Error.
Recovery Action Close the launcher and try it again.
Technical Support Action Look for Operating System Problem
Severity Information
Description Report who change the password.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Unable to copy password file.
Impact Unable to change the password.
Recovery Action Close all tools launchers and try it again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for the problem on the operating system.
Severity Minor
Description Process unable to finish within two minutes
Impact Tool may not be able to launch.
Recovery Action Use the advance option /cuw to increase the wait time. Contact the Customer Service Representative.
Technical Support Action The system may be very slow and some processes are using almost 100% CPU.
Severity Major
Description Password file is corrupted.
Impact Unable to use the launcher.
Recovery Action Contact the Customer Service Representative.
Technical Support Action Re-install the password file (tools.tpd) to \nortel\data directory.
Severity Major
Description Unable to open the password file for reading
Impact Unable to use the launcher as well as to change the password.
Recovery Action Close all tools launchers and try again. If problem persists, contact the Customer Service Representative.
Technical Support Action Look for problem on Operating System.
Severity Minor
Description Unable to get the drive handle of the current directory.
Impact Tool Launcher cannot be started.
Recovery Action Start the tool launcher again in the local hard disk with NTFS partition. If problem persists, contact the Customer Service Representative.
Technical Support Action Check the return code and take appropriate action. If problem persists, contact Product Support.
Severity Minor
Description Unable to get the partition information of the current drive.
Impact Tool Launcher cannot be started.
Recovery Action Start the tool launcher again in the local hard disk with NTFS partition. If problem persists, contact the Customer Service Representative.
Technical Support Action Check the return code and take appropriate action. If problem persists, contact Product Support.
Severity Minor
Description The type of partition in the current drive is not NTFS
Impact Tool Launcher cannot be started.
Recovery Action Start the tool launcher again in the local hard disk with NTFS partition. If problem persists, contact the Customer Service Representative.
Technical Support Action Coding Error, contact Product Support.
Severity Minor
Description The zip file is not an executable file.
Impact Tool Launcher cannot be started.
Recovery Action Contact the Customer Service Representative.
Technical Support Action Re-install the self-extracting zip file (tools2.exe or mcetools.exe ) to \nortel\bin directory
Severity Minor
Description Invalid type of the zip file.
Impact Tool Launcher cannot be started.
Recovery Action Contact the Customer Service Representative.
Technical Support Action Re-install the self-extracting zip file (tools2.exe or mcetools.exe ) to \nortel\bin directory