Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Problem interfacing with COM+
Message
 
 
To
All
General information
Forum:
Visual Basic
Category:
ActiveX controls
Title:
Problem interfacing with COM+
Miscellaneous
Thread ID:
00461250
Message ID:
00461250
Views:
45
We are building *.dll(s) in Visual FoxPro 6.0 and employing COM+ with them. I am hoping that someone working with VB may have seen this problem at some time and have a potential solution. Here is some more information...

We are developing a system that employs a three tier architecture with COM+ in the middle tier. We are currently experiencing problems with some of our objects… if anyone has an idea as to what it could be based off the information below, we would very much appreciate some advice.

We are employing a 3-tier architecture as follows:

Environment - Win 2000 Advanced Server / IIS 5.0

1. Data – SQL Server 7.0; SP3

2. Business Object – *.dll(s) multi-user, multi-threaded – Visual FoxPro 6.0 SP 4 (multi-user)

3. Front End – ASP 3.0

Our Business Object works perfectly when run in VFP 6.0. However, from ASP Pages, if we create the instance it is very unpredictable. Sometimes it works fine and produces the same results as when run directly through VFP 6.0, but a good deal of the time it gives the following error:

<<>>

Active Server Pages error ‘ASP 0115’

Unexpected error

/authorize/return.asp

A trappable error (C0000005) occurred in an external object. The script cannot continue running.

Active Server Pages error ‘ASP 0240’

Script Engine Exception

/authorize/return.asp

A ScriptEngine threw exception ‘C0000005’ in ‘IactiveScript::Close()’ from ‘CactiveScriptEngine::FinalRelease()’

<<>>

Whenever this error is returned it does not even try to create an instance of the object.

We have hypothesized that Windows 2000 Advanced Server loses the reference to the *.dll, causing us to have to restart the “Out of Process Pooled Applications” in the COM+ Explorer. Once we stop the process and start it again, the application will start working. Even though it starts working again the unpredictable behavior will return and the above stopping and starting of the service will again be necessary.

This problem occurs frequently, roughly 33 – 50% of the times that the object is called.

If anyone has experienced this problem or if anyone has any suggestions as to a solution, it would be much appreciated.

Thanks.
Next
Reply
Map
View

Click here to load this message in the networking platform