TIP: Click on subject to list as thread! ANSI
echo: nthelp
to: All
from: Scott
date: 2005-04-25 14:56:58
subject: bexec SID can`t be seen but it`s THERE!

From: Scott 

I have an issue I need assistance on.

My 2003 standard server was giving me an error of 1202 (see below hyphened
line to see full text).

I can see the culprit, it's backup exec, "bexec". Problem is, I
can only access Group Policy Object EDITOR, not the GPO snapin. My mind has
skipped a groove and I don't remember where to find it (it's not in the
usualy snap-in root).

Help please :)

Scott Franklin

------------------------------------------------------------------------
Security policies were propagated with warning. 0x534 : No mapping between
account names and security IDs was done.

Advanced help for this problem is available on
http://support.microsoft.com. Query for "troubleshooting 1202
events".

Error 0x534 occurs when 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 or 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.      Use RSoP to identify the specific User Rights, Restricted Groups, and
Source GPOs that contain the problem accounts:

a.      Start -> Run -> RSoP.msc
b.      Review the results for Computer Configuration\Windows
Settings\Security Settings\Local Policies\User Rights Assignment and
Computer Configuration\Windows Settings\Security Settings\Local
Policies\Restricted Groups for any errors flagged with a red X. c.      For
any User Right or Restricted Group marked with a red X, the
corresponding GPO that contains the problem policy setting is listed under
the column entitled "Source GPO". Note the specific User Rights,
Restricted Groups and containing Source GPOs that are generating errors.

3.      Remove unresolved accounts from Group Policy

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.      For each source GPO identified in step 2, correct the specific User
Rights or Restricted Groups that were flagged with a red X in step 2. These
User Rights or Restricted Groups can be corrected by removing or correcting
any references to the problem accounts that were identified in step 1.

For more information, see Help and Support Center at

--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
SEEN-BY: 633/267 270 5030/786
@PATH: 379/45 1 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.