OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Janardhan S (S.JanardhanICN.SIEMENS.DE)
Date: Wed Dec 05 2001 - 08:29:35 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Hello,

    I have logged as Domain administrator under both the machines( client and server ).
    I was told that "if the system ran out of memory to create a new desktop heap for the service being started", this error might occur.
    I was told to follow these instructions to come out of this problem

                             Find the following value in the registry (Figure 3) and double-click on the value to edit it:
                    a) Registry Path: /HKEY_Local_Machine/System/CurrentControlSet/Control/SessionManager/SubSystems
                    b) Value Name: Windows
               5. A "String Editor" Window will appear (Figure 4). Find the entry "SharedSection=1024,3072" on the line and add
               ",1024" after the second number (which should be "3072"). The resulting line should state:
                    a) %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,1024
                    Windows=On SubSystemType=Windows ServerDll=basesrv,1
                    ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
                    MaxRequestThreads=16
                    b) Note: There should be a space between ",1024" and the next word on the line "Windows"
                            source: http://seer.support.veritas.com/docs/232224.htm

    I tried this also but the same error is occuring again.

    The DCOM server is running on WIN NT Terminal Server. Will that make any difference ?

    Thanks
    Jana

    -----Original Message-----
    From: Joakim Karlsson [mailto:joakim.karlssonCELLNETWORK.COM]
    Sent: Mittwoch, 5. Dezember 2001 15:21
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: SV: Re: Access Denied

    Jana,
     
    The error "initialization of dll C:\winnt\system32\kernel32.dll failed"
    usually occurs when a process is attempting to access a window station
    that it doesn't have the correct access rights to.
     
    But I would guess that the interactive user has access rights to
    WinSta0.
     
    Are you logged on as different users on the different machines?
     
    /Joakim Karlsson

            -----Ursprungligt meddelande-----
            Från: Janardhan S
            Skickat: on 2001-12-05 14:44
            Till: DCOMDISCUSS.MICROSOFT.COM
            Kopia:
            Ämne: Re: Access Denied
            
            

            Hello,
            
            These are my observations w.r.t the access denied problem.
            
            If the Server runs as
            
            INTERACTIVE USER: I get the error "initialization of dll
    C:\winnt\system32\kernel32.dll failed".
            The process is terminating abnormally.
            Eventviewer says The server didn't register with DCOM within the
    required timeout.
            
            Server under LAUNCHING USER: I get access denied.
            
            Server under some user: It succeeds.
            
            Any clues to this problem
            
            Thanks
            Jana
            
            
            
            
            
            
            
            -----Original Message-----
            From: BIGLEY,JOHN (HP-Roseville,ex1) [mailto:john_bigleyHP.COM]
            Sent: Dienstag, 4. Dezember 2001 21:21
            To: DCOMDISCUSS.MICROSOFT.COM
            Subject: Re: Access Denied
            
            
            If you want to turn of all DCOM security I would lower the
            RPC_C_IMP_LEVEL_IMPERSONATE to at least
    RPC_C_IMP_LEVEL_IDENTITY. I highly
            recommend Keith Browns FAQ. Hers is a link specifically to the
    section on
            turning off DCOM security.
            
            http://www.develop.com/kbrown/com/secfaq.htm#TurnOffSecurity
            
            John
            
            -----Original Message-----
            From: Janardhan S [mailto:S.JanardhanICN.SIEMENS.DE]
            Sent: Tuesday, December 04, 2001 2:02 AM
            To: DCOMDISCUSS.MICROSOFT.COM
            Subject: Access Denied
            
            
            Hi,
            
            I am facing the problem repeatedly in our NT domain.
            
            Access denied.
            
            we have two machines
            Mac A
            Mac B
            
            If I register the server in Mac A and invoke the server from Mac
    B by
            calling CoCreateInstanceEx it works.
            
            but If I register the server in Mac B and invoke the server from
    Mac A by
            calling CoCreateInstanceEx it doesn't work.
            
            I changed the setting in DCOMCNFG also giving permissions to
    everyone
            whoever is available in that domain FULL ACCESS.
            
            This didn't change anything and I was getting the same Access
    Denied
            problem.
            
            I was told that if we turn off all security by calling
    CoInitializeSecurity,
            it will work.
            
            I tried this also
            COAUTHINFO coinfo = { RPC_C_AUTHN_NONE, RPC_C_AUTHZ_NONE,
            0,RPC_C_AUTHN_LEVEL_NONE, RPC_C_IMP_LEVEL_IMPERSONATE,0,
    EOAC_NONE };
            COSERVERINFO serverInfo = {
    0,LPWSTR(LPCTSTR(m_szMachineName)),&coinfo,0};
            
            This also didn't work.
            
            Can any one tell me how to find out the exact reason for the
    access denied
            problem. Is there any tool ( like Auditing ) and pinpoint the
    problem ?
            
            Thanks
            Jana
            
            ----------------------------------------------------------------
            Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
            contains important info. Save time, search the archives at
            http://discuss.microsoft.com/archives/index.html .
            To unsubscribe,
    mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM
            
            ----------------------------------------------------------------
            Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
            contains important info. Save time, search the archives at
            http://discuss.microsoft.com/archives/index.html .
            To unsubscribe,
    mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM
            
            ----------------------------------------------------------------
            Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
            contains important info. Save time, search the archives at
            http://discuss.microsoft.com/archives/index.html .
            To unsubscribe,
    mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM
            

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM