Server Rejected registration Request: 3
Server Rejected registration Request: 3 (ClientIDManagerStartup.log)
this is what i get in the clientidmanagerstartuo.log after i deployed a image. I have no idea where to start troubleshooting.
thx for any idea
Oliver
April 16th, 2008 3:20am
Update:
after a couple hours the client sucessfully registerd himself. But i have no idea why :-(
Any ideas why this happens ?
thx
Oliver
Here an extract of the logfile:
Already refreshed within the last 10 minutes, Sleeping for the next 9 minutes before reattempt.ClientIDManagerStartup16.04.2008 02:10:351556 (0x0614)GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSEClientIDManagerStartup16.04.2008 02:20:571556 (0x0614)Computed HardwareID=2:EDCF1BB8EFAA082A0733E2B359F7E010E8E4B239Win32_SystemEnclosure.SerialNumber=CZC8050J3DWin32_SystemEnclosure.SMBIOSAssetTag=CZC8050J3DWin32_BaseBoard.SerialNumber=CZC8050J3DWin32_BIOS.SerialNumber=CZC8050J3DWin32_NetworkAdapterConfiguration.MACAddress=00:0F:FE:96B:5CClientIDManagerStartup16.04.2008 02:20:571556 (0x0614)RegTask: Client is not registered. Sending registration request...ClientIDManagerStartup16.04.2008 02:20:571556 (0x0614)RegTask: Server rejected registration request: 3ClientIDManagerStartup16.04.2008 02:20:571556 (0x0614)RegTask: Starting registration, attempt 52.ClientIDManagerStartup16.04.2008 02:20:571556 (0x0614)RegTask: Initial backoff interval: 1 minutesClientIDManagerStartup16.04.2008 02:21:531556 (0x0614)RegTask: Reset backoff interval: 257 minutesClientIDManagerStartup16.04.2008 02:21:531556 (0x0614)Already refreshed within the last 10 minutes, Sleeping for the next 9 minutes before reattempt.ClientIDManagerStartup16.04.2008 02:21:531556 (0x0614)GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSEClientIDManagerStartup16.04.2008 02:31:191556 (0x0614)Computed HardwareID=2:EDCF1BB8EFAA082A0733E2B359F7E010E8E4B239Win32_SystemEnclosure.SerialNumber=CZC8050J3DWin32_SystemEnclosure.SMBIOSAssetTag=CZC8050J3DWin32_BaseBoard.SerialNumber=CZC8050J3DWin32_BIOS.SerialNumber=CZC8050J3DWin32_NetworkAdapterConfiguration.MACAddress=00:0F:FE:96B:5CClientIDManagerStartup16.04.2008 02:31:191556 (0x0614)RegTask: Client is not registered. Sending registration request...ClientIDManagerStartup16.04.2008 02:31:191556 (0x0614)RegTask: Client registration is pending.ClientIDManagerStartup16.04.2008 02:31:191556 (0x0614)RegTask: Client is pending registration. Sending confirmation request...ClientIDManagerStartup16.04.2008 02:31:191556 (0x0614)RegTask: Client is pending registration. Sending confirmation request...ClientIDManagerStartup16.04.2008 02:32:201556 (0x0614)RegTask: Client is registered.ClientIDManagerStartup16.04.2008 02:32:201556 (0x0614)
Free Windows Admin Tool Kit Click here and download it now
April 16th, 2008 5:46am
in the MP_ManagerRegistration.log i found this message:
Certificate issued to 'SMS' has expired.MP_RegistrationManager18.04.2008 10:49:3327952 (0x6D30)MP Reg: Registration request body is invalid.MP_RegistrationManager18.04.2008 10:49:3327952 (0x6D30)MP Reg: Registration failed.MP_RegistrationManager18.04.2008 10:49:3327952 (0x6D30)MP Reg: Processing completed. Completion state = 0MP_RegistrationManager18.04.2008 10:49:3327952 (0x6D30)
maybe this is the problem why my clients do not rgister. I have SCCM SP1 / R2 Beta on this server. Anyway any ideas to solve this problem ?
thx
oliver
April 18th, 2008 5:46am
sorry for not updating this topic but i solved that problem by my self. In this case the certificate from my MP was not valid.
regards
Oliver
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2008 4:26pm
I was trying to install a client on a system that appeared to have an old non-functioning SCCM 2007 client installed. I uninstalled and reinstalled the client and got very few CCM log files and the "RegTask: Server rejected registration request: 3"
error in clientIDManagerStartup.log appeared almost instantly. I figured it may be a GUID issue due to the previous client install and followed the directions here to clean it up:
http://blogs.technet.com/b/csloyan/archive/2010/04/27/system-center-configuration-manager-and-duplicate-guid-s.aspx
In case that site is inaccessible:
1) Identify the systems with a duplicate GUID
2) Delete the c:\windows\smscfg.ini file from the client
3) Run CCMDELCERT on the client (*)
4) Restart the SMS Client agent (SMS Agent Host)
5) A new GUID will be generated
(*)Ccmdelcert.exe wasn't included in the System Center Configuration Manager 2007 Toolkit, but you can still use the version in the SMS2003 Toolkit 2.
You can download that here:
http://technet.microsoft.com/en-us/sms/bb676787.aspx
It took about 30 seconds after restarting the SMS client that all of the log files started to populate and the client registered successfully.
May 22nd, 2012 11:41am