Thanks Matt,

The logs didn't show anything useful (even turning on debug logging).
However I was able to resolve the issue in the lab by removing and adding
back the MP role from one server at a time.  It's not my favorite solution,
but it works and sometimes that's all that really matters.  Unless it
happens again I'm just going to schedule to do the same for production and
put it to rest.

On Mon, Oct 27, 2014 at 4:52 PM, Atkinson, Matt <
[email protected]> wrote:

>  Hey Josh,
>
>
>
> Can’t say for sure what is causing it, but take a look at C:\Program Files
> x86\Microsoft Configuration Manager\AdminConsole\SMSAdminUI.log and see if
> there is any more information about the crash in there. If nothing there,
> then check SMSProv.log on the site server.
>
>
>
> Hopefully the log file can point you in the right direction. Please back
> with what you find.
>
>
>
> -Matt
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Josh Taylor
> *Sent:* Monday, October 27, 2014 12:32 PM
> *To:* [email protected]
> *Subject:* [mssms] Console crash when accessing MP properties
>
>
>
> In both my lab and production I get a .NET unhandled exception when trying
> to access the properties of the management point role.
>
>
>
> I have two MPs set up on dedicated VMs pretty much according to Kent's MP
> replica doc (minus client notification).
>
>
>
> Production is on 2012 R2 CU2 lab is on 2012 R2 CU3. All servers are 2012
> R2 and SQL has been upgraded to 2014. All of this worked at setup time, CU3
> the hierarchy hasn't changed since it was originally set up just a few
> months ago.
>
>
>
> I get the crash running the console on a production workstation or
> directly on the primary.
>
>
>
> If I choose continue on the unhandled exception window the property page
> comes up but the database tab is missing.
>
>
>
> Anybody have any thoughts?
>
>
>
> Thanks in advance,
>
> Josh
>
>
>
> ------------------------------
>
> This message is intended for the sole use of the addressee, and may
> contain information that is privileged, confidential and exempt from
> disclosure under applicable law. If you are not the addressee you are
> hereby notified that you may not use, copy, disclose, or distribute to
> anyone the message or any information contained in the message. If you have
> received this message in error, please immediately advise the sender by
> reply email and delete this message.
>
>



Reply via email to