The Dragon Medical ERROR Matrix

This ERROR can appear for all Profile Optimizer (PO) Tasks listed in the DM360NE Nuance Management Console (NMC). This ERROR has been linked to DM360NE, versions 2.1 and 2.2, where version 12.51.200.072 of SDK client software for the PO server fails to perform Acoustic and Language Model Optimization (ACO/LMO) of DM360NE users created in DM360NE, version 2.1 and 2.2.

Upgrade DM360NE to version 2.3 which includes an updated SDK client software (v12.51.202.093).

The NMC Data Distribution Tool (DDT) shows this login rights error in primarily XP based workstations.

This error can be resolved by editing a registry entry as described below. Care should taken when editing the registry.

On Windows XP machines that have issues starting DDT, make the following registry change:

1. Close all web browsers.
2. Verify that PresentationHost.exe is not running in Task Manager (end the process if present).
3. Start regedit. (You must be a Windows administrator.)
4. Create a DWORD value under HKLM\Software\Microsoft\.NETFramework\Windows Presentation Foundation\Hosting\RunUnrestricted = 1

No reboot should be necessary.

For a mergeable registry edit file, see iSupport Solution 14115: NMC Distribution Tool (DDT) shows logon rights error

This message can appear when trying to install the Dragon Medical Citrix Audio Patch (Vddnspatch.exe or Vddnspatch.msi) on a workstation with the Citrix ICA Client, regardless of whether the patch is installed by msi or by running the executable.

The version of Dragon Medical Citrix Audio Patch must support the version of Citrix ICA Client installed on the workstation. Reference the Dragon Medical Citrix Administrator Guide for supported versions of Citrix components.  Further, confirm the version of Dragon Citrix Audio Patch is equal to, or higher than, the installed Dragon Medical client on the XenApp server.

• The Audio Setup Wizard was canceled or paused, to be resumed at a later time.
• After completing the Audio Setup Wizard, Dragon Medical is unable to save the microphone settings to the Dragon user profile.
• The previously configured microphone is no longer connected to the computer, or is no longer being detected by the Operating System.

Use these steps to confirm proper microphone setup and configuration in Dragon Medical:

1. Confirm that the microphone is connected to the computer.
   
   Note: If the previously configured microphone is no longer available, it may be necessary to create a new Dictation Source for the user profile if the Dictation Source types are different (for example, the original type is was a "USB microphone" while the new type is a "Bluetooth Microphone".
   
   See iSupport solution 16541: Adding an Additional Dictation Source in Dragon Medical.
   
2. Confirm the Windows Operating System has correctly detected the microphone.
   
   See iSupport solution 14252: Resolving USB Device detection issues where Dragon Medical is installed.
   
3. Confirm the microphone is working properly outside of Dragon.
   
   See iSupport solution 13029: Unable to complete the Audio Setup Wizard.
   
4. When Dragon prompts to run the Audio Setup Wizard, complete all of the steps in order to finalize the audio setup.
   
5. Once the Audio Setup is completed, click Profile > Save User Profile to verify the profile is saved.

Please submit a Service Request and provide the dragon.log to Technical Support as this error requires log file analysis, and investigation of the user's environment and workflow on a per-incident occurrence.

This is a general error category.

Please submit a Service Request and provide the dragon.log to Technical Support as this error requires log file analysis, and investigation of the user's environment and workflow on a per-incident occurrence.

Description

Description

This error is usually a secondary notification as a result of another (sometimes more critical) error.

Please submit a Service Request and provide the dragon.log to Technical Support as this error requires log file analysis, and investigation of the user's environment and workflow on a per-incident occurrence.

Reported in conjunction with a "Server unavailable" message where down-version clients are attempting to authenticate to an up-version NMS. LDAP and the /trusted natspeak switch may be involved.

See iSupport solution 16354: DMNE 1.0 /trusted login fails "Server unavailable" after DMNE 2.1 upgrade.

Description

Message can be presented during a new Dragon Medical installation on a 64-bit system.

“Failed to launch 64 Bit Server” error can also occur under this scenario:

1. Natspeak.exe crashes or is killed. DGNUIASVR_X64.EXE remains running.
2. When Natspeak.exe is next run, it tries to start DGNUIASVR_X64.exe, but this fails since it's already running

Also, see step #10 in the WORKAROUND section when Windows 8.1 supgrades are involved.

Also, if “Failed to launch 64 Bit Server” error occurs within XenApp-published Dragon, or Dragon running in VDI, see step #11 in the WORKAROUND section.

"ERROR (VBar): Unable to spawn 64 bit UIA server (0x80070102)"

The error above is resolved for Dragon Medical 360 | Network Edition (DMNE), beginning in version 2.4.1.

For access to the DMNE version 2.4.1 release note and software download, please refer to:

iSupport solution #14274 - Dragon Medical 360 | Network Edition or Enterprise Edition - What's New and Can I download the Current Version?

1. Disable the User Profile Upgrade option during the beginning of the Dragon installation.
2. For Dragon Medical software prior to version 12.50... on 64-bit (x64) clients, try repairing the Visual C++ 9.0 Runtime component:
1. Close all open applications or open windows.
2. Browse the Dragon Medical installation media or installation files for "ISSetupPrerequisites\VCRuntime" folders.
3. Double click "vcruntime_x64.exe".
4. Choose "Repair" and click "Next".
5. Click "Install" and let the repair finish.
6. Reboot the computer.
   
3. Try disabling UAC (User Access Control) completely (Never Notify)
4. Unregister and re-register the dll file: UIAutomationCore.dll from an Administrator command prompt:
   
regsvr32 /u "C:\Windows\System32\UIAutomationCore.dll" to unregister
regsvr32 "C:\Windows\System32\UIAutomationCore.dll" to re-register

AND

regsvr32 /u "C:\Windows\SysWOW64\UIAutomationCore.dll" to unregister
regsvr32 "C:\Windows\SysWOW64\UIAutomationCore.dll" to re-register



5. Verify that there are no permission issues for the Windows user account at the following directory paths. Try granting the user account full access to that location for testing purposes.

   (32 BIT)
   C:\Program Files\Common Files\Nuance\NaturallySpeaking12\dgnuiasvr.exe"
   
   (64 BIT)
   C:\Program Files (x86)\Common Files\Nuance\NaturallySpeaking12\x64\ dgnuiasvr_x64.exe"

6. Unregister and re-register the dll file: dgnuiax.dll from an Administrator command prompt:

   (32 Bit)
   regsvr32 /u "C:\Program Files\Common Files\Nuance\NaturallySpeaking12\dgnuiax.dll" to unregister

   regsvr32 "C:\Program Files\Common Files\Nuance\NaturallySpeaking12\dgnuiax.dll" to re-register

   (64 Bit)
   regsvr32 /u " C:\Program Files (x86)\Common Files\Nuance\NaturallySpeaking12\x64\dgnuiax_x64.dll" to unregister

   regsvr32 " C:\Program Files (x86)\Common Files\Nuance\NaturallySpeaking12\x64\dgnuiax_x64.dll" to re-register

7. Confirm that the Windows user account has full access to all of the locations listed in the above steps.

8. Verify that the Windows user account has full access to the following registry location:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{03C140B2-4039-4AE3-A819-53BD10023E02}

   Confirm the following registry strings at the above registry location:

   (Default)=dgnuiasvr_x64.exe [or exe file in question]
   ROTFlags=1
   ServerPath=[the proper path to the UI server EXE]

   (64 Bit)
   C:\Program Files (x86)\Common Files\Nuance\NaturallySpeaking12\dgnuiasvr.exe
   
   Note: A 32 bit system omits "(x86") from the file path.
   
9. Verify the Windows user account has full access to the following registry locations:

   (64 Bit)
   •HKEY_CLASSES_ROOT\AppID\{03C140B2-4039-4AE3-A819-53BD10023E02}
   •HKEY_CLASSES_ROOT\Wow6432Node\AppID\{03C140B2-4039-4AE3-A819-53BD10023E02}
   •HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{03C140B2-4039-4AE3-A819-53BD10023E02}
   •HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\AppID\{03C140B2-4039-4AE3-A819-53BD10023E02}

   (32 Bit)
   •HKEY_CLASSES_ROOT\AppID\{D72EC95C-C74B-4ABC-874A-3FE9222E9846}
   •HKEY_CLASSES_ROOT\Wow6432Node\AppID\{D72EC95C-C74B-4ABC-874A-3FE9222E9846}
   •HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{D72EC95C-C74B-4ABC-874A-3FE9222E9846}
   •HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\AppID\{D72EC95C-C74B-4ABC-874A-3FE9222E9846}
   

   ---

10. This error can also be caused when the User Account Control (UAC) is turned off during the process of upgrading to Windows 8.1.
    
    Perform the steps below to turn on UAC in Windows 8.1:
    1. Press "Windows Key + X" on your keyboard to display the Tools Menu, and select Control Panel. Or, right-click the lower left corner of your monitor to display the Tools Menu, and select Control Panel.
    2. Type "UAC" in the search field in the upper right corner of the window.
    3. Click Change User Account Control settings in the search results.
    4. To turn UAC on, drag the slider up to the desired level of security, and click OK.
    5. You may be prompted to confirm your selection or enter an administrator password.
    6. Reboot your computer for the change to take effect.
    
    

    ---

11. If this error occurs within XenApp-published Dragon, or Dragon running in VDI:
    
    The server or domain policy, registry settings, and/or third party Windows profile management software can restrict access or intermittently interfere with access to %appdata% directory path, and then "DGNUIASVR_X64.EXE" can fail to start.
    
    The is caused by when "DGNUIASVR_X64.EXE" attempts to write its log messages only to the dragon.log file within %appdata% and this process doesn't read or use the "datalocations.ini" to override that path.
    
    If a customer can't exclude the "Nuance" folder within %appdata% from interference by their Windows profile management software, and they've employed the "datalocations.ini" workaround, then "DGNUIASVR_X64.EXE" will still write its messages to the old, standard "Dragon.log" file location. If some of its log writes fail, "DGNUIASVR_X64.EXE" will fail to start.

See iSupport Solution 12612: "Failed to launch UI automation server / 64 bit server" error when launching Dragon Medical.

Description

Description

This is a general error.

Solution Details...

Please submit a Service Request and provide the dragon.log to Technical Support as this error requires log file analysis, and investigation of the user's environment and workflow on a per-incident occurrence.

This is a general error that typically results from another error condition.

See iSupport Solution 16348: Interim DMNE 2.0 clients crash during DMNE 2.1 upgrade

Otherwise, please submit a Service Request and provide the dragon.log to Technical Support as this error requires log file analysis, and investigation of the user's environment and workflow on a per-incident occurrence.

Description:

Message may be presented even if the ASW has previously been completed for this user on this computer with this dictation source. The profile's audio.ini file may be incomplete.

See internal iSupport Solution 13835: User Continues To Be Prompted To Run Audio Setup Wizard.

Normally, the integrity is in question for the file identified (X) and the source media should be downloaded again or replaced.

Copy the installation media contents to the local hard disk and then perform a local installation. Otherwise, the software media is likely corrupted and should be downloaded again.

Description

Description

Description

An intermittent issue was reported in DMNE, version 12.50.200.055, where a VMware View VDI session was "deadlocking". This resulted in a loss of dictation for the provider. "Deadlocking" occurs when two (2) or more tasks permanently block one another by each task attempting to lock a resource in which the other tasks are also trying to lock. This issue is specific to the VMware View Agent software and its interaction with the Windows guest operating system.

An initial recommendation was to move the dictation devices from the back EHCI (USB 2.0) ports to the front OHCI (USB 1.1) ports.

Another recommendation was made to disable the EHCI function, forcing the device back to OHCI mode. Reducing the occurrence of "USBD_STATUS_XACT_ERROR" errors on the endpoint (client) is a workaround proposed by VMware and Teradici to decrease the likelihood of the problem being triggered in the guest operating system by the VMware View Agent.

Disabling the EHCI function can be accomplished from the Teradici Management Console. A reboot of the Zero Client will result.

Access to the Teredici knowledge Base article below explaining this requires a registered account.
PCoIP TROUBLESHOOTING STEPS: USB peripherals (15134-933)

Please see iSupport Solution 16276: DMNE 2.x VMware View VDI session "deadlocking" with dictation loss

This has been reported when launching a Dragon Medical client on a Windows Vista operating system.

Microsoft released a security update for Windows Vista on July 11, 2011 (KB2533623) that has caused problems with not being able to launch or install certain third party applications.

The current solution is to remove this specific Microsoft update (KB2533623) following these steps:

1. Click "Start > Control Panel > Programs and Features".
2. Click the "View installed updates" link on the left side of the window.
3. Locate the "Update for Windows Vista for x64-based Systems (KB2533623)" update.
4. Select the KB2533623 update and then click the "Uninstall" button.
5. Once the update has been removed, restart the computer.
6. After the computer restarts, confirm that the Nuance Desktop application can now be launched or installed.

Please see iSupport Solution 14540: “Error while unpacking program, Code 2. Please report to author” error when launching or installing a Nuance product

The previous error messages have been reported when installing Dragon Medical clients. The specific cabinet file being referenced may be different from the one shown above [ENUGen~1.cab].

The problem could also be that the file could not be verified because it was signed with a new VeriSign certificate (Root Authority Certificate) that is by default not included in Windows operating system, or the certificate has expired.

Solution #1:

The following will resolve most related errors:

1. Confirm Windows Local Administrator rights are used on the workstation where Dragon Medical is being installed.
2. The cabinet file may not be read properly when the system is accessing the DVD or installation media. Use a flat-file installation method to install Dragon Medical from the local hard drive by copying the contents of the Dragon Medical software media (DVD) to the local hard drive of the workstation, and execute the setup.exe file from that location.
3. During the Dragon Medical Install_Shield, use the Custom install as the Setup Type and select the "This feature will be installed when required" for the Speech Files icon.
4. Temporarily disable any antivirus / malware / spyware software, especially any real-time / endpoint protection.
5. Uninstall the Windows Update KB978601 if present. This can be reinstalled after Dragon Medical is successfully installed.
6. Reboot the computer and close all non-essential applications.
7. Uninstall any previous version of Dragon Medical software using a Dragon software remover tool. See iSupport Solution 14760: How to completely uninstall Dragon - Remover Tool
8. If the cabinet error occurs when installing from a download, the downloaded files may be corrupt. Try downloading Dragon Medical media again and install from the new download.

Solution #2:

If Solution 1 does not allow a successful installation, there may be problem with Windows WinTrust on the system. The Dragon installer uses Windows WinTrust to verify that the cabinet file's digital signature is valid. In some cases there may be a problem with WinTrust detecting the file's valid digital signature.

1. Open Internet Explorer by right-clicking the icon or menu item and selecting the "Run as administrator" option.
2. Select Tools > Internet Options > Content.
3. In the Certificates group, click the Certificates button.
4. Select Trusted Root Certification Authorities tab.
5. Select Global Sign Root CA from the list. You may need to scroll down.
6. In Certificate intended purposes group, click the View button.
7. Select the Details tab.
8. Click the Edit Properties... button.
9. Under the Enable only the following purposes radio button, check the box for Code Signing.
10. Click OK > OK > Close > OK to save changes and exit.

Solution #3:

Finally, the problem may be that the installation cabinet file could not be verified because it was signed with a new VeriSign certificate (Root Authority Certificate) that is either not included in the currently installed operating system, or that the certificate has expired. If the Trusted Root Certificate Authorities' certificate has expired or is non-existent, the following problems can occur:

• Inability to access the NMC Console
• Inability to deploy Dragon Medical client via SCCM

Normally Windows updates its list of Root Certificates automatically. However, this may not have been accomplished if blocked by security features.

Confirm that the “Update Root Certificates” component is enabled within Windows as follows:

1. Click Start > Control Panel > Add or Remove Programs > Add/Remove Windows Components > Update Root Certificates.
2. Otherwise, download the certificates update file manually from: "http://download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/rootsupd.exe"

Apply the latest root certificate update from Microsoft as described in KB931125: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3867

Otherwise, see the following iSupport Solutions:

14540: “Error while unpacking program, Code 2. Please report to author” error when launching or installing a Nuance product

13013: "Error 1330" may appear when installing Dragon NaturallySpeaking 10

14575: WinTrust Error 1330

When attempting to create and save an Acoustic and Language Model Optimizer Scheduler task in the Dragon Medical Enterprise Edition (DMEE) product, the above error messages can occur.

Please see iSupport Solution 14612: DMEE Optimizer Scheduler errors and Windows Scheduled Tasks log

Dragon Medical introduced a new feature in client version 11 and higher where the user can select, correct, or format multiple recognized text matches, such as repeating words or phrases. Dragon labels each instance of repetitive text with superscript numbering allowing the user to simply say the number corresponding to the desired instance. This feature uses the formfiller.exe process. Error has been reported when DMPE (version 11.00.300.312) is disconnected from a Roaming profile location (working off the locally cached profile) and the dictator selects a word appearing multiple times in the dictation. Dragon hangs and presents the error.

Refer to DragonBar Help Topics (Help > Help Topics) and search on “Formatting or correcting multiple text matches” for additional operational information.

This issue has been fixed in the version 12 client software.

If this issue persists, disable the formfiller process:

1. Exit Dragon Medical and open the nssystem.ini file.

(Windows XP) C:\Documents and Settings\All Users\Application Data\Nuance\NaturallySpeakingXX

(Windows 7) C:\ProgramData\Nuance\NaturallySpeakingXX

2. Under [Settings] add the following line:

   Show disambiguation numbers=0

3. Launch Dragon Medical.

Disabling the formfiller feature via the above nssystem.ini modification will remove the superscript numbering feature as well as the aforementioned error/symptoms. The user will be able to select a word that was dictated multiple times where Dragon highlights only the last instance of the repetitive word selected. The user can then speak “select previous” and “select next” commands to navigate between redundant instances of the selected word if needed.

See iSupport Solution 14713: Workaround for DMPE "COM" and "1726" errors caused by formfiller.exe for additional dragon.log content.

This error has been reported when installing:

• Dragon Medical vSync MiniTracker on Citrix servers
• Dragon Medical client

For errors installing MiniTracker, see iSupport Solution 14843: DM360NE Error 1722 during installation of vSync MiniTracker component

For errors installing Dragon Medical clients, use the following steps to disable Data Execution Prevention (DEP):

1. Click on the Windows Start Menu, then open the Control Panel.
2. Click Classic View.
3. Double-click System
   Note: For Windows Vista and higher, click Advanced System Settings in the System window.
4. On the System Properties dialog box, click on the Advanced tab.
5. Click the Settings button in the Performance section.
6. Click the Data Execution Prevention tab.
7. Click Turn on DEP for essential Windows programs and services only.
8. Click OK and OK to apply the changes
9. Reboot the client.
10. Install Dragon Medical.

This message occurs when attempting to launch Dragon Medical using Windows User Account Control (UAC) and "Run as Administrator" is selected for "natspeak.exe". "Run as Administrator" is not active by default, requiring the user to turn on this setting. However, this elevated privilege level is not needed to run Dragon NaturallySpeaking.

Clicking the "Close" button on the dialog box will close the error, but Dragon will not launch.

This message can also appear when logged in as the local Administrator account on the system.

Please use the following steps to turn off the "Run as Administrator" setting:

1. Click Start > Computer.
2. Double-click the Local Disk C: drive.
3. Browse to \Program Files(x86)\Nuance\NaturallySpeakingXX\Program folder.
4. Right-click natspeak.exe.
5. Select Properties.
6. Click the Compatibility tab.
7. Clear the checkbox for Run as Administrator.
8. Click OK.

Note: It is not possible to run Dragon Medical when logged in as the Local Administrator account on Windows Vista, or higher. We recommend creating a new user account on the system that is part of the Administrators group and running Dragon under this new user.

See iSupport Solution 12630: “Dragon NaturallySpeaking should not be run in elevated mode” error message

This DMNE messages can be presented when the NMS (Nuance Management Server) software install shield is running just after the Database Server and Service Logon windows were completed and Next is clicked.

The NMS installation log reveals the following lines (C:\Users\[Windows Acct.]\AppData\Local\Temp\1\NMSCInstallation.log):

1: Reading the SQL script data from ISSQL Connection table...
1: ISSQLRequirement table does not exist...

Installing a service through an install shield like DMNE NMS, where it prompts to enter a network domain\username and password, may return a "Server not found" error, acting as if it cannot find the user login specified.

This may happen more often with workgroups. It can also occur when using any of the Browse buttons in that install shield, resulting in a message, "The list is empty."

For browsing anything like groups or users, the ISNetApi needs the server name. For the server name to be verified or browsed, the computer's ComputerBrowser service is required. The ComputerBrowser service can be disabled on some Windows operating systems by default (like Windows Server 2008).

To resolve this issue, the ComputerBrowser service should be enabled under Windows services. The Printer and File Sharing from within Control Panel > Network And Sharing Center (Windows 2008) may also need to be enabled.

See iSupport Solution 14488: Did you know how to resolve a "Server Not Found" message during a DMENE NMS installation?

Description

This error is presented from the NMC Profile Optimizer Status window. This is typically caused when the Profile Optimizer Server service is not running.

1. Confirm the Profile Optimizer Server service is running.
2. Verify that the First, Second, and Subsequent Failure settings under the Recovery tab on the service's Properties window are set for Restart the Service.

Monitoring of the DMNE services is important and can help to eliminate downtime causes. Nuance recommends that the following services be monitored:

• Nuance Management Service > Nuance.NAS.Server.exe 8731 8051
• Profile Optimizer Server > POService.exe 8001
• Profile Optimizer Speech Node > POSpeechNode.exe 8000
• Microsoft SQL > NuanceMC & NuancePODB 1433
• Microsoft IIS > Nuance Management Console http://nms_server/nmc/client.xbap 80

This error is presented within your browser window (IE) when attempting to access the NMC.

This error can be solved by:

• Adding the URL for the NMS website to your browser's (IE) Trusted Site list under the Security tab.
• Using the built-in navigational arrows and tabs when navigating within NMC, instead of using the browser Back button.

DMNE client dragon.log excerpt:

[NMS] [NMS] WebException:
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 172.31.xxx.xx:8051

This error is generally caused when the Nuance Management Server service is stopped on the DMNE NMS server. To resolve this issue, start the Nuance Management Server service.

Resovled issue by removing and reinstalling Dragon.

First tried to repair Dragon Medical installation and run /fixguids, but same result