It may be a simple permission problem. On my web servers I enable failure
auditing on all local drives. Right click drive, select properties, security,
advanced, auditing. Click add and enter everyone. Click Ok and select all
failures. Apply to all files and folders. In Local Security Policy under
Audit Policy, set "Audit Object Access" for failures. Your security eventlog
will now show failures. You may also want to set this for HKLM\Software to
trace registry access failures.
[quoted text, click to view] "Gilgamesh4Ever" wrote:
> Hi there,
> I've got an asp application which is hosted on IIS, running on W2K server.
> I've got also an ASP page which is trying to create a Microsoft Project file
> by
> creating an instance of object "MSProject.Application" object. Although the
> MS project has already been installed on the web server, IIS throws an error
> when it tries to create the object. After researching the problem, it became
> clear that the problem is with IIS not allowing the MS Project application
> to start as an out-of-process application. Has anybody done something like
> this?
> Here is the error I see in the event log: ActiveX component can't create
> object.
>
> Thanks,
> Gilgamesh
>
>