Windows: Unable to find SAPI error on google - c++

I am using SAPI to make a voice speak text.
The error code returned is
-2147024888
The method "Speak" for 'ISpeechVoice' failed
However I was unable to find this error code on Google.
I am not sure why.
Does anybody have any ideas? I expected Microsoft to list all possible error codes for SAPI.
On the page http://msdn.microsoft.com/en-us/library/ms717306%28v=vs.85%29.aspx this error code is not there.
Thank you for any help!

The SAPI error code listings are for the error codes specific to SAPI. Other errors could be returned.
-2147024888 is equivalent to 0x80070008, which is a Win32 HRESULT (E_OUTOFMEMORY); the call is failing because something (either inside the TTS engine or in SAPI) is not able to allocate enough memory.

Related

Error message from VS2022: appmodul.cpp not found

While trying to debug a C++ windows application in Visual Studio 2022, I get the message:
You need to find appmodul.cpp to view the source for the current call stack frame
I really have no idea what the message mean, and the added comments do not help.
Any help would be appreciated.
Thanks
Al

Using node-ffi with Electron not working (cannot find message text for message number 0x%1...)

I'm actually trying to use a dll with electron but I've got an error when it reaches the line:
const ffi = require("ffi");
Error
Translation : The system cannot find message text for message number
0x%1 in the message file for %2
Using Electron 1.8.2
newbie here. After some research it might be because you're trying to laod a 32-bit DLL in a 64-bit environment.
Check this post for more info.

Invalid PE File x64dbg

I am trying to open a simple Hello World program written in c++ in x64dbg and I get an error "Invalid PE File". The file loads fine in IDA. What might be the problem ?
Author of x64dbg here, the error you're experiencing is misleading and has nothing to do with the validity of the PE file. It simply means that CreateProcess failed for your file. This can have various reasons, once of which is the validity of the PE file. Get the latest version from here for a better error message.
Validate the process starts correctly outside of the debugger and make sure it is not blocked by for example your anti virus software.

Error: not.exe has stopped working - When trying to build LLVM

I am trying to build LLVM on windows, and everytime I do so I get to a certain point and then recieve an error that says "not.exe has stopped working" It pops up on the desktop about 15 times.
I am not sure what is going on, but when I check the error in Visual Studio I receive this:
Error 4 error : Couldn't execute program 'C:/Users/Cyborg/Documents/Developer'The process cannot access the file because it is being used by another process. C:\Users\Joe\Documents\Dev\llvm\test\CUSTOMBUILD check-llvm
I receive this error 5-7 times depending on how fast I click the error that pops up on the desktop. So clearly this issue is happening because of that.
The fault module is: MSVCR100.dll
Does anyone know why this is happening?
I don't know why you're getting the error since I don't build or use LLVM on Windows. Since no one else has chimed in, I'll try to give a hint or two.
"not.exe" (or "not" under Linux) is a little LLVM helper program used when running the lit based regressions tests. It is used to execute a program and return a good exit status if the program fails and a bad exit status if the program doesn't fail.
I'm guessing that "CUSTOMBUILD check-llvm" (what ever that is) is attempting to run the regression tests and your getting your mysterious error as a result whenevr "not" is used.
I hope that helps.

Visual Studio 2012 error: Assertion Failed

I am using Vc++(2012) with allegro 5.0.7. and following this link for tutorials.
I get assertion Failed error when I compiled the code present at the above given link. Here is a snapshot of my error.
You are trying to use a null bitmap. The most common reason is you are running your program from a directory that you are not expecting, causing your relative paths to fail.
Read and follow the advice of this article to solve the issue.