I'm Rob Marshall, a consultant who specialises in the Microsoft System Center Configuration Manager product. I like to share, i do so by blogging and helping out when I can in the MS SMS newsgroups and participating in the ConfigMgr MVP program.
I was awarded and joined the program in 2009. It'd be an understatement to say it has to be one of the best experiences an IT engineer can have, if they really enjoy specialising in a product.
My biggest weapon for troubleshooting is, my formidable knowledge, no, only joking, you, the community. I find if I cannot answer a question, then I can usually find the answer from using Bing\Google, pouring over the documentation, and if that doesn't work, tinkering in mine or someone elses virtual lab.
The blogs pretty much about ConfigMgr, but it is also a platform for me to express my random urges to display something I've stumbled across, and that I imagine would entertain you or what not as equally as it did me.
Seen an interesting issue where the CCMSETUP parameters incorrectly specify MP as SMSMP, resulting in failure and exotic errors appearing in the CLIENT.MSI and CCMSETUP logs:
Just need to fire up CLIENT.MSI in SMSTRACE, find Return value 3 and you'll possibly see the following:
WARNING: The path passed for the TRK file is empty.SMSMP cannot be specified without SMSSITECODE@@ERR:25001MSI (s) (1C!94) [10:10:37:046]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstancesThe error code is 80004005
Error 25001. Setup failed due to unexpected circumstancesThe error code is 80004005MSI (s) (1C:0C) [10:10:37:046]: Machine policy value 'DisableRollback' is 0MSI (s) (1C:0C) [10:10:37:093]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 10:10:37: SmsSetClientConfigInit. Return value 3.MSI (s) (1C:0C) [10:10:37:093]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (1C:0C) [10:10:37:093]: No System Restore sequence number for this installation.MSI (s) (1C:0C) [10:10:37:093]: Unlocking ServerAction ended 10:10:37: INSTALL. Return value 3.
At the tail-end of the CLIENT.MSI log file:
MSI (s) (1C:0C) [10:10:37:328]: Note: 1: 1708 MSI (s) (1C:0C) [10:10:37:328]: Product: Configuration Manager Client -- Installation operation failed.
MSI (s) (1C:0C) [10:10:37:390]: Cleaning up uninstalled install packages, if any existMSI (s) (1C:0C) [10:10:37:390]: MainEngineThread is returning 1603MSI (s) (1C:54) [10:10:37:500]: Destroying RemoteAPI object.MSI (s) (1C:D0) [10:10:37:500]: Custom Action Manager thread ending.=== Logging stopped: 20-08-2008 10:10:37 ===MSI (c) (1C:20) [10:10:37:500]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1MSI (c) (1C:20) [10:10:37:500]: MainEngineThread is returning 1603=== Verbose logging stopped: 20-08-2008 10:10:37 ===
CCMSETUP log file drops out at the following section: SmsSetClientConfigInit
MSI: Action 13:55:32: SmsSetClientConfigInit. Setting SMS configuration ccmsetupMSI: Setup failed due to unexpected circumstancesThe error code is 80004005 ccmsetupInstallation failed with error code 1603 ccmsetup
It's a classic mistake, easily overlooked.
CCMSETUP should be saying "Command line parameters for CCMSETUP incorrectly specified, unknown parameter SMSMP identified", but it doesn't as you can see above