- Introduction
- Steps to troubleshoot
- How to verify that Tomcat service in Cisco Unity Connection 9.x
- Error Message: "This User Account Does Not Have a Mailbox and Cannot Sign In to the Cisco Personal Communications Assistant. To Use the Cisco PCA, You Must Have an Account with a Mailbox."
- Error Message: "Sign-In Status - Account Has Been Locked."
- Error Message: "Failed to <Save Message>" While Using PC Microphone in Cisco Unity Connection Administration or Cisco PCA
- Related Links
Introduction
In Unity connection 9.x., text is missing on the Menu bar (Microsoft Windows Only).Menu bar of the Cisco Personal Communications Assistant web tool is missing text and only displays down arrows to signify the menu items.
Steps to troubleshoot
Do the following procedure to troubleshoot
To Re-Register DLLs Required for the Cisco Personal Communications Assistant Menu Bar
Step 1 
On the user workstation, select Start and select Run.
Step 2 In Run window, enter regsvr32 msscript.ocx and select OK.
Step 3 In the dialog box that indicates that the DLL registration succeeded, select OK.
Step 4 Select Start and select Run.
Step 5 In Run window, enter regsvr32 dispex.dll and select OK.
Step 6 In the dialog box that indicates that the DLL registration succeeded, select OK.
Step 7 Select Start and select Run.
Step 8 In Run window, enter regsvr32 vbscript.dll and select OK.
Step 9 In the dialog box that indicates that the DLL registration succeeded, select OK.
How to verify that Tomcat service in Cisco Unity Connection 9.x
Do the following tasks to confirm that the Tomcat service is running and if necessary, to restart the Tomcat service:
1. Using RTMT
Confirm that the Tomcat service is running by using either Real-Time Monitoring Tool (RTMT) or the Command Line Interface (CLI). Do the applicable procedure:-
To Confirm That the Tomcat Service Is Running by Using Real-Time Monitoring Tool (RTMT)
Step 1 Launch Real-Time Monitoring Tool (RTMT).
Step 2 On the System menu, select Server > Critical Services.
Step 3 On the System tab, locate Cisco Tomcat and view its status. The status is indicated by an icon.
2. Using CLI
Confirm That the Tomcat Service Is Running by Using the Command Line Interface (CLI)
Step 1 Use the Command Line Interface (CLI) command utils service list to list all of the services.
Step 2 Scan the CLI output for the Cisco Tomcat service and confirm that its status is Started.
To Restart the Tomcat Service by Using the Command Line Interface (CLI)
Step 1 To restart the Cisco Tomcat service, use the CLI command utils service restart Cisco Tomcat.
Error Message: "This User Account Does Not Have a Mailbox and Cannot Sign In to the Cisco Personal Communications Assistant. To Use the Cisco PCA, You Must Have an Account with a Mailbox."
If a user with valid credentials but who does not have an associated Cisco Unity Connection mailbox attempts to sign in to the Cisco Personal Communications Assistant (PCA), the user receives the error "This user account does not have a mailbox and cannot sign in to the Cisco Personal Communications Assistant. To use the Cisco PCA, you must have an account with a mailbox."
To correct the problem, create an account with a mailbox for the user. As a best practice, we recommend that Cisco Unity Connection administrators do not use the same user account to sign in to Cisco Unity Connection Administration that they use to sign in to the Cisco PCA to manage their own Cisco Unity Connection account.
Error Message: "Sign-In Status - Account Has Been Locked."
When users encounter the error message "Sign-in status - account has been locked," it is possible that the user exceeded the number of failed sign-in attempts that is allowed. (This limit is set on the System Settings > Authentication Rules page in Cisco Unity Connection Administration.) It may also be possible that the user forgot his or her credentials, or an unauthorized user attempted to gain access.
Use the following task list to determine the source of the problem and correct it.
1. To confirm that the account is locked, in Cisco Unity Connection Administration, go to the Users > Edit Password Settings page for the individual user, and select Web Application from the Choose Password menu. Under Web Applications Password Settings, you can verify the status of the user credentials to determine whether the password was locked by an administrator, there were failed sign-in attempts, or the password was locked after an excessive number of failed sign-in attempts.
2. To unlock the user account, in Cisco Unity Connection Administration, go to the Users > Edit Password Settings page for the individual user, and select Web Application from the Choose Password menu. Under Web Applications Password Settings, select Unlock Password.
Error Message: "Failed to <Save Message>" While Using PC Microphone in Cisco Unity Connection Administration or Cisco PCA
While uploading an existing .wav file, or saving a new recorded message as a voice name or greeting using the PC microphone, the user receives an error message for failed operation. For example, if a user is saving a new greeting using PC microphone, the user receives "Failed to Save Greeting" error message. This error message appears if the user is using either the Cisco Unity Connection Administration (CUCA) or the Cisco Personal Communications Assistant (CPCA) web application of Cisco Unity Connection. The following exception also appears in the client side Java Console logs:
Exception in thread "Timeout guard" java.security.AccessControlException: access denied (java.net.SocketPermission 10.93.231.234:8443 connect,resolve)
To send the recorded message successfully, add the below entry in the client side JRE security profile file, that is commonly named as java.policy using the IP address of the Connection server. For a cluster, you may need to add an entry for each of publisher and subscriber.
permission java.net.SocketPermission "10.93.237.101:8443", "connect,resolve";
If you get a permission error while trying to modify the java.policy security profile file, you may need to set the permissions of the file to not inherent permissions from its parent and not be read-only.