Re: ScriptEngine (VB) sometimes fails a division under Windows Server
- From: "Pavel A." <pavel_a@xxxxxxxxxxxxxxx>
- Date: Sat, 13 Jan 2007 00:27:06 +0200
Probably MS product support is the address for this question.
You should have few support incidents with the MSDN subscription.
--PA
"T G" <tg@xxxxxxxxxxxxxxxxx> wrote in message news:5C652FC7-CEF1-4847-B4FA-261E46079198@xxxxxxxxxxxxxxxx
I'm not sure what section I should put my problem in, so if this is wrong
please point me to the right one.
I have an MFC C++ program which runs a Script Engine on application and
document basis (uses interfaces ActiveScriptSite and ActiveScriptSiteWindow).
It uses VBScript. The following lines of code creates the engine:
CLSID CLSID_VBScript =
{ 0xb54f3741, 0x5b07, 0x11cf, { 0xa4, 0xb0, 0x00, 0xaa, 0x00, 0x4a, 0x55,
0xe8 } };
// create script engine
HRESULT hr = CoCreateInstance(clsidScriptEngine,
NULL, // no aggregation
CLSCTX_INPROC_SERVER,
IID_IActiveScript,
(LPVOID*)&m_pActiveScript);
I have a document in my program that loads a script and runs it. The script
works perfect under Windows XP for example.
But when the script runs under Windows Server 2003 it sometimes seems to
break parts of the engine for some reason. The script can work as expected
for a while, but sometimes it breaks. When this has happened, every line of
code that makes a division fails and I get an error message telling me
"Overflow" when an division is executed. For example this gives me an
overflow message after the engine have stopped working correctly:
Dim test
test = 4 / 2
This does NOT give me an error:
Dim test
test = 4 \ 2
So it seems to be connected to floating points operations.
Once the engine fails to work as intended, the only thing that helps is to
restart the program. It is not enough to open a new document that creates a
new script engine.
My program is built under Visual Studio 2005.
I have an older copy of the program built under Visual Studio .NET 2003 and
it seems like that executable does not break the engine. Are there any
changes in VS 2005 that may cause this error on Win2003 Server? Since the exe
built under VS 2003.NET seems to work.
I have made some research without getting any answers to my problem.
Hopefully someone can give me a hint.
I know my description may be to vague, so feel free to ask for more
information.
Thanks in advance! /TG
.
- Prev by Date: Re: Multi-threaded C++ programs: wrought with peril?
- Next by Date: Re: Multi-threaded C++ programs: wrought with peril?
- Previous by thread: NDIS and Local Loopback
- Next by thread: RE: ScriptEngine (VB) sometimes fails a division under Windows Server
- Index(es):
Relevant Pages
|