Re: Post Windows 2003 Update Errors

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Robin Hearne" <RobinHearne@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EDD4945E-D9FB-45B6-9068-4894FEDD57B6@xxxxxxxxxxxxxxxx
> We've just upgrade the server that runs our SMS Primary (and only) site
from
> Windows NT 4.0 to Windows 2003. The server was a NT 4.0 BDC and is
currently
> a Windows 2003 Active Directory Domain controller (this will be dcpromo'd
> down to a member server later).
>
> Everything appears to be fine following the upgrade except that the SMS
> Executive service is reporting that it is unable to write to the registry
for
> each key under
>
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_EXECUTIVE\Threads\
". The error given is always one of these two:
>
> The operating system reported error 1352: The security account manager
(SAM)
> or local security authority (LSA) server was in the wrong state to perform
> the security operation.
>
> or
>
> The operating system reported error 1723: The RPC server is too busy to
> complete this operation.
>
> An example of the full error is as follows:
>
> Could not write registry key
>
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_EXECUTIVE\Threads\
SMS_NT_LOGON_DISCOVERY_MANAGER"
> on computer ME-SMS. The operating system reported error 1352: The security
> account manager (SAM) or local security authority (LSA) server was in the
> wrong state to perform the security operation.
>
> Has anyone got any ideas on what could be caused this? I've checked the
> registry permissions and everything appears to be fine.

I imagine you are running SMS 2.0 since you upgraded from NT 4.0? If so, you
may want to consider upgrading to SMS 2003. If you are running SMS 2003,
which security mode are you running?

Steve


.

Relevant Pages

  • Re: Setting Site System Connection Account disabled
    ... the sms is installed in advance security mode. ... But i still have the problem with the distribution point on other server. ... VDABDC002$ account on other server), still the sms says access to the remote ...
    (microsoft.public.sms.admin)
  • Re: Inplace Upgrade os SMS2.0 to 2003
    ... > Currently our SMS 2.0 Installation consists of a Central Site Server and one ... On the Central Site server there are roughly 700+ clients, ... > another server that is being used as a SMS Distribution Point. ... Site boundaries should be retained after the upgrade. ...
    (microsoft.public.sms.setup)
  • Re: Client not reporting into SCCM
    ... Therefore you can't upgrade to ConfigMgr until they upgrade first. ... If you don't want to report to them any more then use a new site code. ... If you rebuild SMS 2k3 then you will still need to update the security on the System Management Container. ... SCCM Server on a seperate server SQL ...
    (microsoft.public.sms.misc)
  • Re: IE6 vs IE& vs IE8 on SBS
    ... When an app needs it or when MS updates a component that needs it then I'll upgrade. ... I just don't upgrade for no reason either. ... Please don't read that last line as dismissing the possible issues of using a browser from a server, I am not and do not advocate it. ... If true, this makes me wonder if there isn't some of the aforementioned security problems present in any OS that has IE6 or earlier installed, active or not. ...
    (microsoft.public.windows.server.sbs)
  • Re: Failed upgrade to SCCM
    ... but I've done an SMS restore to new ... I had during the upgrade would prevent the new install / site repair from ... I recently started the upgrade our SMS 2003 SP3 Server to SCCM. ...
    (microsoft.public.sms.setup)