Article ID: 186273 - Last Review: March 3, 2005 - Revision: 3.1 BUG: AV Running VB-Built Component in Multi-Threaded EnvironmentThis article was previously published under Q186273 On This PageSYMPTOMS
When running an apartment model ActiveX DLL that is created in Visual Basic in a multithreaded environment such as Microsoft Internet Information
Server (IIS) or Microsoft Transaction Server (MTS), COM+, Internet Explorer, ActiveX EXEs, and so on, the DLL fails
periodically with an access violation (AV).
RESOLUTION
The following steps may be used to change the DLL to avoid the problem.
This may not resolve the issue in all cases.
Step-by-Step Example
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. REFERENCESFor additional information on errors when using an ActiveX DLL created in Visual Basic 5.0 that contains a For... Each loop that iterates through a Visual Basic collection, click the article number below
to view the article in the Microsoft Knowledge Base:
183164
(http://support.microsoft.com/kb/183164/EN-US/
)
FIX: For..Each Loop in ActiveX Component Causes Errors
For additional information on threading issues with DLLs created in Visual Basic 6.0, click the article number below
to view the article in the Microsoft Knowledge Base:
264957
(http://support.microsoft.com/kb/264957/EN-US/
)
PRB: Visual Basic DLL Has Memory Leaks and Crashes in COM+ If 'Retain In Memory' Is Not Set
APPLIES TO
| Article Translations
|

Back to the top
