Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Problem integrating with COM+

Problem integrating with COM+

Problem integrating with COM+

We are working in Visual FoxPro 6.0, building *.dll(s) that employ COM+.  I am hoping that someone working with VB may have encountered a similar problem 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:

<<<Start Error>>>

Active Server Pages error ‘ASP 0115’

Unexpected error


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

Active Server Pages error ‘ASP 0240’

Script Engine Exception


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

<<<End Error>>>

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.


RE: Problem integrating with COM+

We are having a similar problem with a VB DLL component.
We have not found the solution yet have you? We will post
somthing here when we do.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close