Permission Denied When Accessing COM+ Component as Plain Domain User on 2003

From: segedunum (segedunum.1rsupz_at_)
Date: 07/07/05 

Date: Thu, 7 Jul 2005 13:31:50 +0100

Hi All,

I've got a problem running COM+ components on Windows 2003 that I
haven't seen perviously.

If I log into the client workstation as a domain administrator, I can
access the COM+ component absolutely fine. However, if I access it
logged in as an ordinary domain user I get a permission denied 70
error. Otherwise, users can get access to the server fine and use
shares on it. I've been through all the motions for this.

- The workstations and the server are a part of an Active Directory set
up and authenticate against it.
- I've created roles for domain users against my COM+ components to
ensure declarative security for them.

In the event log I've got authentication sucesses for the domain users
from the workstations I'm using, so no failures there and nothing that
would indicate any kind of other failure. None of my COM+ components
implement programmatic security, or even have an Initialize routine.
They're very, very simple components.

I've been through everything I can think of. The only remaining thing I
can think of is if a setting in AD is stopping access, but I have
absolutely no idea what that might be because it could be just about
anything. I think I've exhausted everything in Component Services, but
if anyone has any other ideas that would be great because I can't
believe I'm the only one to see an error 70 like this.

Thanks a lot. 

-- 
segedunumPosted from http://www.pcreview.co.uk/ newsgroup access

Relevant Pages

  • Re: Problem after removed "domain users" from "local administrator"s g
    ... We finally decided to remove the "domain users" group from the "local administrators" group on the workstations and since doing that we have a strange problem happening. ... Some programs simply cannot be used without administrator privileges, ever, which is an excellent reason to switch to software written by competent people. ... The right answer, in hindsight, was to add Domain Users to the Local Users group. ...
    (microsoft.public.windows.server.sbs)
  • Group membership and rights
    ... workstations. ... Login scripts are of the .vbs type, ... when I place my users in the Domain Users ... What local group should the local user ...
    (microsoft.public.win2000.active_directory)
  • Re: Time and date lock
    ... configured the workstations placed the Domain Users in the Local Users ... variable is concerned on any of the machines. ... > get placed into the Local Administrators Group and the Domain Users gets ...
    (microsoft.public.security)
  • Domain Users group does not retain the Log on Locally right
    ... I've got some workstations here in the office that appear were not joined to ... were not able to log onto any machine in the office because "Domain Users" ... My issues are that when I do this I go to check the local policy on the ... workstations and it does add Domain Users to the Lo on Locally policy. ...
    (microsoft.public.windows.server.sbs)
  • Re: Restrict Client PC Date & Time Changes
    ... Just take the domain users out of the local administrators group on the ... You are syncing the workstations with the server, ... > all the client PC are XP Pro. ...
    (microsoft.public.windows.server.sbs)