Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NEED HELP !!! - SAM/SID ISSUES

Status
Not open for further replies.

itpro34

MIS
Jan 2, 2003
34
US
Good day all. I recently put a new server on-line following the steps below. I am now getting errors logged in the system event log. My users are complaining that the network seems to be running slower.

Hardware migration path: (Microsoft article ID 324383

1. backup your information store databases.
2. Take the current exchange server offline (and it cannot be brought back onto the network at this point).
3. Install the new server with the same name, IP address and partition configurations.
4. Install exchange using the SETUP.EXE /DISASTERRECOVERY switch.
5. Restore your databases to the new server.

ERRORS:

System Log:

Source = SAM / Event ID = 16650

The account-identifier allocator failed to initialize properly. The record data contains the NT error code that caused the failure. Windows 2000 will retry the initialization until it succeeds; until that time, account creation will be denied on this Domain Controller. Please look for other SAM event logs that may indicate the exact reason for the failure

Application Log:

Source = MSExchangeFBPublish / Event ID = 8213

System Attendant Service failed to create session for virtual machine NP-EXCHANGE. The error number is 0x80090005.


Source = MSExchangeTransport / Event ID = 929

Failed in reading Connector's DS Info Process Id: 1164 Process location: C:\WINNT\System32\inetsrv\inetinfo.exe ConnectorDN: CN=Internet Mail Service (SBS),CN=Connections,CN=SBS,CN=Routing Groups,CN=SBS,CN=Administrative Groups,CN=NOTTINGHAM,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Nottingham-int,DC=com Hr:80040920 Attribute:[]

Source = SceCli / Event ID = 1202

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 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").

I did the "FIND" command and it appears to be an account call "Admin" But I am not sure how to rectify this

I COULD USE ALL THE HELP I CAN GET HERE. MY NETWORK HAS BEEN DEGROGATED DUE TO THIS IMPLIMENTATION.

Thanks ahead of time
 
Did upou reset the computer account in active directory when you retired the old server ?

Paul
 
Thanks for the reply

When I attempted to do that it said it was a Domain Controller and therfsore could not. I guess I shoulds have dcpromo and demoted the original first (lesson learned).

Is there a work around now though?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top