However, for development and debugging I do not require COM+ services, and
it takes a long time for VB to start when the components are in there during
a debug session.
Everything works fine when the components are in COM+/MTS, but if I remove
them I get the following error from global.asa:
Microsoft VBScript runtime (0x800A01AE)
Class doesn't support Automation: 'CreateObject'
It seems that Windows cannot handle createObject on my COM+ components from
global.asa unless they are actually registered in COM+.
I'm running on Windows XP, and this was not a problem on Windows 2000.
If anyone can tell me how I can get the createObject in global.asa to work
without the need to have the component in COM+ I would appreciate it.
--
Paal Berggreen
Trimanet AS
www.trimanet.no
paal.be...@trimanet.no
+47 98 28 55 02
These utilities log file system and registry access for a chosen process
(you can log all access, or filter on one or more processes) and will
identify access denial to registry keys or files that are critical to
instantiating your object. Basically, you run the utility, and then hit
your page to generate the error. You can then stop logging and examine the
log (search on "Denied") for security problems.
Using this information, you can then set permissions accordingly.
Hope this helps!
Steven Bras, MCSD
Microsoft Developer Support/Visual Basic WebData
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
¤ I have a webclass project (VB 6.0) containing a couple of dll's. Whenever a
After you removed them from COM+ did you use Regsvr32 to re-register them?
Paul ~~~ pcle...@ameritech.net
Microsoft MVP (Visual Basic)