I am trying to run a ASP page on Windows 2003 Enterprise Edition Server.

The ASP page creates a object using "CreateObject" method and gives following error:

Microsoft VBScript runtime error '800a0046'

Permission denied: 'CreateObject'


However, when I run the same ASP page on Windows 2000 Server, it works.

Can someone help?

Thanks in advance.

Hello,

Can you verify that the server has the component installed or that it is typed correctly in the CreateObject statement? I've had this error before, and I believe these were the causes...

Brian

Hi,

Everything works fine on Windows 2000 Server.

So I don't see any issues with the component or the CreateObject statement.

Thanks

I think it would help to post some code that shows the object you're trying to create.
The fact that it works on 2000 doesn't say very much. Not everything was taken over to 2003, 2003 is locked down by default on a clean install, you may have a custom component that you didn't install on 2003 or indeed restricted security settings prevent you from creating the object.....

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: The Message (feat Mary J. Blige And Rell) by Dr. Dre (From the album: Chronic 2001) What's This?

I am trying to create a new object of a object in an ActiveX DLL.
Code looks something like this:

Set obj = CreateObject("AA.BB")

I have installed the DLL on 2003 server.

How did you install the component? Did you regsvr32 to install it? Can you find the component in the registry?

Also, is the process that calls the DLL allowed to access it?

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: 01 - Ambulance by Blur (From the album: Think Tank) What's This?

I used regsvr32 to install the component and there are registry entries for the same.

How to check whether the callee process has access to the DLL?

I think you should take a look at the folder the DLL resides in, and see if the process can access that folder.

Alternatively, you can host your DLL inside a COM+ package that you can configure to run under a specific account....

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: miDijunkies by Atari Teenage Riot (Track 6 from the album: Delete Yourself) What's This?

Sorry to but in with something that doesn’t relate to this post

Imar
I have just checked out your 'What's This' link. A seemingly impossible interestingly innovative piece of techo brilliance, nice!


Wind is your friend
Matt

Hi Matt,

And it's also a true chindogu, an unuseless invention, don't you think?? ;)

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.