SDAPI crash
Submitted by Dan Lufkin on Fri, 04/20/2007 - 18:59.
For a couple of days now I've had occasional crashes when I make a correction -- I get an error that "an internal recognizer error has occurred. NS may be in an unstable state, etc.
The log for this event shows:
14:41:58 SDAPI Error 1: Error: [s:\mrec14\10820\sdapi\apist.cpp 287 sdapi\apist 24] SDWord_GetName: SDhVoc 0xffffffff
14:41:58
14:41:58 Expected value 0x80040201.
14:41:58 (c:\work\rh4\vdct\textcorr.cpp,780) : pDgnSRCorrection2->Correct() returned unexpected value E_UNEXPECTED (0x8000ffff).
14:41:58
14:41:58 SDAPI Error 1: Error: [s:\mrec14\10820\sdapi\apist.cpp 287 sdapi\apist 24] SDWord_GetName: SDhVoc 0xffffffff
14:45:58 Warning: detected SDAPI Error in recognition loop
14:45:58 ERROR (EngSink): There was a internal system error which will prevent you from saving your user files. You may be able to continue dictating, but you will not be able to save.
14:45:58 Error dialog overflow - Error was: There was a internal system error which will prevent you from saving your user files. You may be able to continue dictating, but you will not be able to save.
14:45:58 Details:
14:47:10 Warning: querying status for a nonexistent window
14:47:30 LOG (VBar) Begin cleanupAcOptSessionArchive
14:47:30 LOG (VBar) End cleanupAcOptSessionArchive
14:47:30 LOG (VBar): Unloading compatibility modules...
14:47:30 (MyCmds) MyCommands snap-shot deleted
14:47:30 (MyCmds) MyCommands uninitialized for "Dan Lufkin (v9)" speaker
14:47:30 LOG (VBar): Compatibility modules unloaded
14:47:31 Starting Shutdown of S2
and goes downhill from there.
Any ideas? Reinstall?
If I restart DNS, it works OK for a while, makes corrections just fine, then suddenly ...
Grateful for any advice.
Dan
»
- Dan Lufkin's blog
- Login or register to post comments
Dan Lufkin wrote: For a
For a couple of days now I've had occasional crashes when I make a correction -- I get an error that "an internal recognizer error has occurred. NS may be in an unstable state, etc.
The log for this event shows:
14:41:58 SDAPI Error 1: Error: [s:\mrec14\10820\sdapi\apist.cpp 287 sdapi\apist 24] SDWord_GetName: SDhVoc 0xffffffff
14:41:58
14:41:58 Expected value 0x80040201.
14:41:58 (c:\work\rh4\vdct\textcorr.cpp,780) : pDgnSRCorrection2->Correct() returned unexpected value E_UNEXPECTED (0x8000ffff).
14:41:58
14:41:58 SDAPI Error 1: Error: [s:\mrec14\10820\sdapi\apist.cpp 287 sdapi\apist 24] SDWord_GetName: SDhVoc 0xffffffff
14:45:58 Warning: detected SDAPI Error in recognition loop
14:45:58 ERROR (EngSink): There was a internal system error which will prevent you from saving your user files. You may be able to continue dictating, but you will not be able to save.
14:45:58 Error dialog overflow - Error was: There was a internal system error which will prevent you from saving your user files. You may be able to continue dictating, but you will not be able to save.
14:45:58 Details:
14:47:10 Warning: querying status for a nonexistent window
14:47:30 LOG (VBar) Begin cleanupAcOptSessionArchive
14:47:30 LOG (VBar) End cleanupAcOptSessionArchive
14:47:30 LOG (VBar): Unloading compatibility modules...
14:47:30 (MyCmds) MyCommands snap-shot deleted
14:47:30 (MyCmds) MyCommands uninitialized for "Dan Lufkin (v9)" speaker
14:47:30 LOG (VBar): Compatibility modules unloaded
14:47:31 Starting Shutdown of S2
and goes downhill from there.
Any ideas? Reinstall?
If I restart DNS, it works OK for a while, makes corrections just fine, then suddenly ...
Grateful for any advice.
Dan
Dan,
From the looks of your Dragon log it appears that your user is corrupted.
However, in order to check for the problem, use the following procedure, which is listed from simplest (most parsimonious) to most complex.
1. Restore your backup user. Test this user and see if the problem persists.
2. If your backup user produces the same error, try creating a new user, "No Training" if you're using DNS 9, and see if the new user creates the same problem.
3. If neither of the above options works to solve the problem, then it is most likely that DNS requires a reinstall/repair.
4. If the problem still persists, then you likely will have to use the DNS remove utility and completely remove DNS from your system. However, there are some caveats here.
First, be sure that you export your custom vocabulary and custom commands before you do anything. In this manner, you will preserve these. Also, export them to a location away from any of the user folders or DNS program folders. Otherwise, the DNS remove utility will delete them because it deletes all registry entries and folders/files, including any files contained within them.
Second, before you use the DNS remove utility, uninstall DNS using the normal uninstall procedure so that you preserve your activations. However, currently (Sunday April 22, 2007) the activation server is either down or overloaded. If you get the message saying that your activations cannot be updated, don't continue the uninstall. If you do, you will lose and activation. Wait until at least late Monday. Nuance has been notified that their activation server is not functioning at this time. However, they will not correct this until sometime on Monday. Therefore, you'll just have to wait. However, if the deactivation process occurs properly and you are not prompted per above, continue the uninstall.
Third, after you have uninstalled DNS and run the DNS remove utility, reinstall DNS.
My guess is that somewhere between #1 and #3, your problem will be resolved. Regardless, the Dragon log indicates that your user is most likely the source of the problem (i.e., corrupted).
Chuck Runquist
Former Dragon NaturallySpeaking SDK & Senior Technical Solutions PM for DNS
It is not so much my confidence that scientists will get it right as it is my confidence that nonscientists will get it wrong. Isaac Asimov
To which I add my own version, "I am not so confident that technically oriented people will get it right as it is my confidence that non-technically oriented people will get it wrong."
Thanks, Chuck -- I switched
Thanks, Chuck -- I switched over to my backup user right away and so far the SDAPI error hasn't struck again. I must admit that I've subjected my old user to many an indignity and it doesn't surprise me that he's downed tools. My backup user needs some discipline, but I'll soon have him toeing the line.
Could I ask what it was specifically in the log that tipped you off?
Thanks again,
Dan
Dan Lufkin wrote: Thanks,
Thanks, Chuck -- I switched over to my backup user right away and so far the SDAPI error hasn't struck again. I must admit that I've subjected my old user to many an indignity and it doesn't surprise me that he's downed tools. My backup user needs some discipline, but I'll soon have him toeing the line.
Could I ask what it was specifically in the log that tipped you off?
Thanks again,
Dan
Dan,
Overall, it was the entire sequence of errors. Most of which is to technically complex to explain. Simply put, one of the corrections that you made during one of your sessions corrupted one of your correction files which DNS was trying to save in one of the Acoustic and Language Model Optimizer archive files. When attempting to save your files, and information located at one of the addresses in memory was invalid. That is, it returned an incorrect memory address, which did not contain the expected value. When this happens, DNS cannot write the information. As a result, as you note from the log, is that DNS cannot save your files. This is really the indicator that your files are corrupted.
Although the errors tell me what went wrong, they don't provide any details. Even development and/or technical support can only identify the problem, not the cause. Most likely your memory got corrupted during a correction operation and DNS preserves your profiles so that you can continue to dictate, but it can't save your user files and will continue to create the same error. The really is nothing other than the fact that it can't save your files and the type of error noted from which any information can be gleaned. However, the bottom line is that anytime you cannot save your files, your users are corrupted and you should go to the back up immediately.
In addition, this is why I always recommend that users export their user files when they know that they are OK. This provide you with an extra backup in case something happens to your main and your backup users.
If you were looking for an explanation of the error, i.e. won't get into that because he gets far to technical and it would take a book to explain everything in sufficient simplicity anyway.
Chuck Runquist
Former Dragon NaturallySpeaking SDK & Senior Technical Solutions PM for DNS
If you hear the sound of hoofbeats, think horses not zebras.
Law of Parsimony (Occam's razor)
Thanks, Chuck, I get the
Thanks, Chuck, I get the general idea. Because the error message always came when I made a correction (although many corrections went unnoticed), I figured that I'd mangled a correction sometime.
I must admit that I didn't export my old user file to some safe location. As soon as I get the new user perfected, I'll stow it out of harm's way.
Thanks again,
Dan
Dawkins's Law of Difficulty: In any academic subject obfuscation expands to fill the space left by intrinsic simplicity.
I have been getting exactly
I have been getting exactly the same error message for the past week or so:
SDAPI Error 1: Error: [s:\mrec14\10820\sdapi\apist.cpp 287 sdapi\apist 24] SDWord_GetName: SDhVoc 0xffffffff
I had only been using my new user for a few weeks so I deleted it and created a new one, but the song remains the same. Inevitably, after one or two corrections I get the problem when I say "choose" or even if I try clicking the selection I want rather than speaking.
Not looking forward to it all, but seem I have no option but to follow Chuck's advice, uninstall DNS9, remove all traces and reinstall.
Graham
After doing a fresh install
After doing a fresh install I am still getting similar error messages on a fairly regular basis, this is the latest and strangely it occurred whilst the microphone was off and I was not even using DNS:
SDAPI Error 1: Error: [s:\mrec14\10820\mrecutil\realdf.cpp 1593 mrecutil\realdf 30] SDUttFile_Open: C:\Documents and Settings\Graham\Dati applicazioni\Nuance\NaturallySpeaking9\results\uttFile