One of the many State Migration Points I have failed the install (due to the above certificate error). Also, as part of the initial role assignment, the wrong drive was specified.
The site role was removed, web cert added as per above, then readded with the correct path. As a result, the role installed successfully. However, I was then receiving messages about the State Migration Point starting, then stopping unexpectedly.
Checking the SMPMGR.LOG file, I found the following lines :
Creating directory "D:\USMT\SMPSTORED_378B856C$" SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)
Cannot create D:\USMT, Win32 Error = 3 SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)
ERROR: Failed to create directory "D:\USMT\SMPSTORED_378B856C$" SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)
HandleSMPRegistryChanges failed. error (0x80004005). SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)
SMPManager failed to start, Error = (0x80004005). SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)
So the SMP was trying to create the folder on the old path, the one specified before I removed and readded the role with the correct part. Damn!
I took a look at the reg key that has the SMP settings (HKLM\Software\Microsoft\SMS\SMP\StateStore) and found TWO subkeys, one for the incorrect path (D:\USMT) and one with the correct path (E:\USMT).
Seems it only reads the first key in here (which makes sense).. Remove the incorrect subkey, and start the SMS_STATE_MIGRATION_POINT component via the service manager.
Check the SMPMGR.LOG file, and bingo! path is created, and component is now ticking along nicely.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment