Re: Problem with ASP instancing VB6 DLL under IIS6 - Windows 2003 (Microsoft VBScript runtime error '800a01fb')
- From: "Tony Proctor" <tony_proctor@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 18 Jan 2007 11:11:14 -0000
Changing the isolation mode will not fix an exception in your DLL. It merely
controls whether your application has a worker process of its own, or shares
a pool with other applications, or runs in-process in Inetinfo.
You need to run your DLL in the IDE, and then access your ASP pages. That
should allow you to find the real cause of the exception
Tony Proctor
"Lucas Junqueira" <ljunqueira@xxxxxxxxx> wrote in message
news:1169043257.350466.236700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I had a problem while trying to access some methods of my VB6 DLL's in
IIS6 using ASP.
The errors were always something like "Microsoft VBScript runtime error
'800a01fb' Exception: DoSomething".
While looking for threads that solved the problem I only saw question,
never answers ... :D
I solved my problem this way (i'll try to explain the menus in english,
though my windows 2003 is in portuguese):
- Go to the IIS manager
- Right click the Web sites folder and click properties
- Go to the Service tab
- In the isolation mode, CHECK the IIS 5 WWW isolation mode
- Click OK
- If asked to restart IIS say Yes
That's it ...
.
- References:
- Prev by Date: Re: Converting ISO-charset to Unicode
- Next by Date: Like operator and square brackets
- Previous by thread: Problem with ASP instancing VB6 DLL under IIS6 - Windows 2003 (Microsoft VBScript runtime error '800a01fb')
- Next by thread: Add Edit Delete Options on right click in MSFlexGrid Control VB6
- Index(es):
Relevant Pages
|
