My dll is marshalled for a different thread!

[robjg]

We have just implemented an intranet site on a 6-server web farm. The login page uses com+ dll (installed on each server) but from time to time, users are getting an error like this:

"Automation error The application called an interface that was marshalled for a different thread.
/bottom_lo.asp, line 25 "

('line 25' is the first usage of the dll. )
We did alot of testing but this never happened, so i presume its a problem that arises with several users hitting the page. Any ideas what the problem is and how to get around it?
Thanks
Rob

 

[teriviret]

You'll get that error if you create an object in one COM apartment and try to use it from another COM apartment without marshaling its interface.

My guess is it's something to do with the "6-server web farm". Maybe one of the servers created a COM object, and passed the interface to one of the other 5 servers without marshaling the interface?

When one user logs in, is it possible that the handling of that user is passed off from one server to another? You might not see it in testing if the server load is not very high. It might only be happening when a lot of users are trying to get to the servers simultaneously.

 

[robjg]

excuse my ignorance, but I would need something more tangible than that to resolve the problem....I wouldnt even know how to "marshal an interface" ...is it even possible with a VB component?

I've not had much dealing with COM objects, and certainly never experienced this terminology, so i'm still no nearer to solving the problem.
Thanks for replying anyway.

 

[teriviret]

Sorry, I don't know much about VB. In VC++ though you can use the functions I talk about in this thread:

[URL unfurl="true"]http://www.tek-tips.com/viewthread.cfm?SQID=860709&SPID=195&page=1[/url]

I just remember getting the exact same error message you are getting, until I solved it by using these COM functions.