TorreyLauer
Sun Jun 13 14:50:01 CDT 2004
I'm also getting these error messages now in the Event Viewer:
Event Type: Warning
Event Source: Perflib
Event Category: None
Event ID: 2003
Date: 6/13/2004
Time: 2:04:19 PM
User: N/A
Computer: SBSERVER
Description:
The configuration information of the performance library "C:\WINNT\system32\aspperf.dll" for the "ASP" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
I've checked KB 226494 and found under the Event ID 2003 section that I have to re-install this, bu I don't know how. Any suggestions?
There are a few more error messages just like the one above. I'd assume that the fix for them is to re-install them as well.
I am also getting some error messages like this:
Event Type: Warning
Event Source: SceCli
Event Category: None
Event ID: 1202
Date: 6/13/2004
Time: 2:08:37 PM
User: N/A
Computer: SBSERVER
Description:
Security policies are propagated with warning. 0x534 : No mapping between account names and security IDs was done.
For best results in resolving this event, log on with a non-administrative account and search
http://support.microsoft.com for "troubleshooting 1202 events".
A user account in one or more Group policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped nor deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions:
1.Identify accounts that could not be resolved to a SID: From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%\Security\Logs\winlogon.log
The string following "Cannot find" in the FIND output identifies the problem account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").
2.Identify the GPOs that contain the unresolvable account name:
From the command prompt type FIND /I "JohnDough" %SYSTEMROOT%\Security\templates\policies\gpt*.*
The output of the FIND command will resemble the following:
---------- GPT00000.DOM
---------- GPT00001.DOM
SeRemoteShutdownPrivilege=JohnDough
This indicates that of all the GPOâ??s being applied to this machine, the unresolvable account exists only in one GPO. Specifically, the cached GPO named GPT00001.DOM.
Now we need to determine the friendly name of this GPO in the next step.
3. Locate the friendly names of each of the GPOs that contain an unresolvable account name. These GPOs were identified in the previous step.
From the command prompt, type: FIND /I "[Mapping]" %SYSTEMROOT%\Security\Logs\winlogon.log
The string following "[Mapping] gpt0000?.dom =" in the FIND output identifies the friendly names for all GPOâ??s being applied to this machine.
Example: [Mapping] gpt00001.dom = User Rights Policy
In this case, the GPO that contains the unresolvable account (gpt00001.dom) has a friendly name of "User Rights Policy".
4. Remove unresolved accounts from each GPO that contains an unresolvable account.
a. Start -> Run -> MMC.EXE
b. From the File menu select "Add/Remove Snap-inâ?¦"
c. From the "Add/Remove Snap-in" dialog box select "Addâ?¦"
d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add"
e. In the "Select Group Policy Object" dialog box click the "Browse" button.
f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab
g. Right click on the first policy identified in step 3 and choose edit
h. Review each setting under Computer Configuration/ Windows Settings/ Security Settings/ Local Policies/ User Rights
Assignment or Computer Configuration/ Windows Settings/ SecuritySettings/ Restricted Groups for accounts identified in step 1.
i. Repeat steps 3g and 3h for all subsequent GPOs identified in step 3.
I've followed the steps of this one, and it displays as the Default Domain Policy and Default Domain Controller Policy.
There seems to be a LOT of things wrong here. Am I able to do a re-install over the the top of this without having to completely re-setup everything in order to see if that might fix these problems?
What do you suggest I do?
"Marina Roos [SBS-MVP]" wrote:
> Check your cabling of the SCSI drives and termination:
>
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;315266 (it says XP,
> but I would think you can use this for SBS too)
>
> --
> Regards,
>
> Marina
> Microsoft SBS-MVP
>
> "Torrey Lauer" <TorreyLauer@discussions.microsoft.com> schreef in bericht
> news:23C76EAC-7816-4458-82A0-1204F316B6E6@microsoft.com...
> > Marina,
> >
> > The STOP error on the blue screen of death is the following:
> >
> > ***STOP: 0X00000077, 0XC000009D, 0XC000009D, 0X00000000, 0X034CC000)
> >
> > KERNEL_STACK_INPAGE_ERROR
> >
> > Thanks for helping!!! I greatly appreciate it (I missed my flight to
> Hawaii because this darn server started crashing!! ugggh)
> >
> >
> >
> > "Marina Roos [SBS-MVP]" wrote:
> >
> > > Hi Torrey,
> > >
> > > Most of those services don't sound familiar to me at all (except the
> IPSEC).
> > > Do you have the STOP-error?
> > >
> > > --
> > > Regards,
> > >
> > > Marina
> > > Microsoft SBS-MVP
> > >
> > > "Torrey Lauer" <TorreyLauer@discussions.microsoft.com> schreef in
> bericht
> > > news:193CA9B1-AF47-4B6B-9027-1AB1C8A225AD@microsoft.com...
> > > > Our server started crashing last night with the blue screen of death.
> I
> > > don't really understand why. The server hasn't had any changes to it
> with
> > > software or hardware, and has been running flawlessly before this.
> > > >
> > > > When I reboot the server after it crashes, the server is not finding
> he
> > > harddrives. I have a RAID card that the harddrives are connected to.
> No
> > > matter how many times I reboot the server, it doesn't find them. I've
> found
> > > that I have to shut the server off, and then turn it back on in order
> for it
> > > to find the drives.
> > > >
> > > > Could it be a problem with the hardware RAID card?
> > > >
> > > > The only other odd thing that I've seen in the event log are some
> errors.
> > > Here are some of them:
> > > >
> > > > The Closed Caption Decoder service failed to start due to the
> following
> > > error:
> > > > The service cannot be started, either because it is disabled or
> because it
> > > has no enabled devices associated with it.
> > > >
> > > > The previous system shutdown at 4:08:55 AM on 6/13/2004 was
> unexpected.
> > > >
> > > > Then, when the server comes back up, it has these errors:
> > > >
> > > > The IPSEC driver service failed to start due to the following error:
> > > > Insufficient system resources exist to complete the requested service.
> > > >
> > > > The BDA MPE Filter service failed to start due to the following error:
> > > > The service cannot be started, either because it is disabled or
> because it
> > > has no enabled devices associated with it.
> > > >
> > > > The Microsoft Streaming Tee/Sink-to-Sink Converter service failed to
> start
> > > due to the following error:
> > > > The service cannot be started, either because it is disabled or
> because it
> > > has no enabled devices associated with it.
> > > >
> > > > The NABTS/FEC VBI Codec service failed to start due to the following
> > > error:
> > > > The service cannot be started, either because it is disabled or
> because it
> > > has no enabled devices associated with it.
> > > >
> > > > The BDA Slip De-Framer service failed to start due to the following
> error:
> > > > The service cannot be started, either because it is disabled or
> because it
> > > has no enabled devices associated with it.
> > > >
> > > > The BDA IPSink service failed to start due to the following error:
> > > > The service cannot be started, either because it is disabled or
> because it
> > > has no enabled devices associated with it.
> > > >
> > > > The World Standard Teletext Codec service failed to start due to the
> > > following error:
> > > > The service cannot be started, either because it is disabled or
> because it
> > > has no enabled devices associated with it.
> > > >
> > > > Any ideas?
> > > >
> > > >
> > > >
> > >
> > >
> > >
>
>
>