David
Tue Mar 07 00:23:25 CST 2006
There are many reasons why an object cannot be created. Permissions is only
one of many reasons. File not found is another reason.
All else being equal between your 32bit machine and 64bit machine, process
"bitness" issues are the most likely culprit. Maybe:
1. Your 32bit code is trying to write something (or reset ACLs) and getting
it FileSystemRedirected or RegistryRedirected on 64bit machines
2. Your 32bit code insists on loading "in-process" but the process is 64bit.
That fails because process only allows the same bitness.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Abe Simpson" <abe@simpson.com> wrote in message
news:ODiXryVQGHA.6008@TK2MSFTNGP10.phx.gbl...
> Hi all,
>
> Some of my clients are reporting this error on a 64-bit Windows when
> running my COM objects under ASP:
>
> -----
> Microsoft VBScript runtime error '800a01ad'
> ActiveX component can't create object
> -----
>
> This error is very common on 32-bit Windows and can be easily fixed by
> adjusting permissions on the COM DLL. However, it seems that this trick no
> longer works on 64-bit Windows.
>
> Can someone shed some light?
>
> Thanks.
>
> -- Abe
>