Check for the following

[1] You check for the login of the win2k server.
[2] The mentioned error may occur even when the user logged in to the 
server is other than the administrator or who don't have the administrator 
privillage.
[3] Check for the identity of the com component manager is for the current 
user, if not change the same to current user.

Regards,
Lingasamy K

You might need to execute dcomcnfg.exe and select your COM component, then 
set the Default Access Permissions and Launch Permissions.

We have to do this for our COM apllication.

Dawson - CADology, UK

> Hi

> Please can you help?

> We have just switched an ASP application onto a new server (Win 2K 
s> tandard server) and are experiencing what look to be permissions 
p> roblems - everything worked fine on the old server (WIN NT 4.0 server).

> The application is comprised of ASP pages that utilise functionality in 
C> OM components. These components were originally created in VB 6.0 using 
t> he Transaction server type library. I have installed them (without 
r> ecompiling using COM+ services type library).

> FYI - I have also tried re-compiling them using COM+ tl but same message.

> When the ASP pages attempt to call the components the following error
o> ccurs:
-> --------------------------------------
S> erver object error 'ASP 0178 : 80070005' 

> Server.CreateObject Access Error 

> /includes/header.inc, line 65 

> The call to Server.CreateObject failed while checking permissions. 
Access 
i> s denied to this object.
-> --------------------------------------
L> ooks like this is happening when the component is being instantiated...

> Any ideas would be most welcome! The dll itself has permissions like - 
e> veryone (read and execute).

> Thanks
M> ichael

Thanks everyone for your suggestions.

The problem was occuring I think due to the application being set as a 
server application. On changing the activation type of the application to 
a library application all worked OK.

I understand the difference between the two different types of activation 
but would be grateful if someone copould give clear cut advice on which 
activation type to use in what situation and the + and - of each.

Many thanks
Michael


> Please can you help?

> We have just switched an ASP application onto a new server (Win 2K 
s> tandard server) and are experiencing what look to be permissions 
p> roblems - everything worked fine on the old server (WIN NT 4.0 server).

> The application is comprised of ASP pages that utilise functionality in 
C> OM components. These components were originally created in VB 6.0 using 
t> he Transaction server type library. I have installed them (without 
r> ecompiling using COM+ services type library).

> FYI - I have also tried re-compiling them using COM+ tl but same message.

> When the ASP pages attempt to call the components the following error
o> ccurs:
-> --------------------------------------
S> erver object error 'ASP 0178 : 80070005' 

> Server.CreateObject Access Error 

> /includes/header.inc, line 65 

> The call to Server.CreateObject failed while checking permissions. 
Access 
i> s denied to this object.
-> --------------------------------------
L> ooks like this is happening when the component is being instantiated...

> Any ideas would be most welcome! The dll itself has permissions like - 
e> veryone (read and execute).

> Thanks
M> ichael