Thanks for taking the time Jason, much appreciated. I think I will start pushing more to keep IIS off of primary site servers, or at the least express what can sometimes happen if you don't.
In hindsight, the time it took to spin up a VM to offload the MP role was far less than the troubleshooting effort with IIS and the VM can effectively be a throw away. Oh well, live and learn. Thanks again. Jay Marsett On Jul 15, 2017 3:35 PM, "Jason Sandys" <ja...@sandys.us> wrote: > The use the same service and WMI namespace because that’s how they were > designed. It’s quite integral to the way the MP works so you could request > it all that want but that would require a major redesign which won’t be > happening anytime soon. > > > > As for ccmclean, it simply does a handful of things for them that they > could be done manually including deleting the ccm registry key, deleting > the self-generated certs, deleting the namespace, and deleting the folder > (to my knowledge – I’m guessing a bit here because I never use it either). > It’s not publically available because it’s not supported. It’s a bit heavy > handed with what it does so could possibly delete things that it shouldn’t. > > > > This is an example of why many of us highly recommend not installing IIS > on a primary site server at all and always offload the client facing roles > like the MP onto separate site systems as they are easy to swap out if IIS > gets hosed. Simply removing IIS and reinstalling does not reset any > settings so while it seems like a common thing for folks to do when > troubleshooting, it’s pretty useless most of the time. It will reset file > permissions but it won’t actually reset any IIS settings thus it won’t > reset whatever setting (and there are a lot of them in IIS) that got > changed to cause the issue. Usually it’s easier to just spin up a new site > system with a fresh IIS installation. > > > > J > > > > *From: *<listsad...@lists.myitforum.com> on behalf of Jay Marsett < > jmars...@gmail.com> > *Reply-To: *"mssms@lists.myitforum.com" <mssms@lists.myitforum.com> > *Date: *Friday, July 14, 2017 at 2:48 PM > *To: *"mssms@lists.myitforum.com" <mssms@lists.myitforum.com> > *Subject: *Re: [mssms] Management Point error 500 > > > > Can anyone explain to me why the MP and the CCM client need to use the > same Service and WMI namespace? That seems to be the only reason that this > type of issue occurs; is it just too hard to recode that type of change, or > is there more to it then that? Is it worth a feature request? > > > > After 12 hours of premiere support, they still have no resolution. They > must of run CCMClean 20 different times trying to fix this issue all to no > avail. These guys went so far as uninstalling IIS on my primary site and > reinstalling it, along with every IIS integrated role, in an effort to > correct this, end result is still, error 500 in the IIS logs. > > > > Another question, if Premiere and field support still utilize CCMClean to > attempt to correct these types of issues, why isn't it publicly available > any longer? > > > > We went the alternative route of spinning up another host to house the MP > role so that we could move forward. > > > > Would love to have an answer as how to fix this on our Primary so please > get back to me with any thoughts you might have. > > > > Thanks, Jay > > > > > > > > > > > > On Thu, Jul 13, 2017 at 10:06 AM, Jay Marsett <jmars...@gmail.com> wrote: > > I am hoping someone can help me understand an issue I am having with a > Primary site server/management point Post 1511-1702 upgrade process. It is > a standalone Primary with the MP role and it is the only MP. > > > > After the upgrade from 1511-1610 we noticed that the MP started getting > "error 500, internal server error" once the role was reinstalled by the > upgrade. It had been functioning before we started the servicing process. > In addition, in looking at logging, we realized that the CM client had been > installed on the Primary and for whatever reason it was stuck in a > reinstall/repair loop (probably because the MP was down). I was able to > successfully uninstall the client (using ccmsetup /uninstall) and then I > uninstalled the MP role, rebooted and reinstalled the MP role, > unfortunately, with the same result, error 500. This was all done while on > an unpatched 1610 instance. > > > > We made the decision to finish the upgrade to 1702 and the > hotfix, 4019926, but unfortunately saw the same results, error 500. Some > weird behavior we obsered, when the role is being reinstalled, I actually > see the FSP (on the same site server) responding to clients with 200 "ok" > responses in the IIS logs, but then once the MP role comes back online, the > logs roll back to the error 500. (Just seemed odd to me) > > > > I have seen posts from others about similar issues when the client gets > installed on a site server hosting different roles (DP), but I didn't want > to try "blowing away WMI" on this host, as it is the Primary site server, > but I am open to anyone's suggestions, or experiences. > > > > I did open a premiere support ticket, but that process is slower than > molasses in January these days. > > > > Thanks in advance > > > > Jay Marsett > > > > > > > > >
