I upgraded from 4.4.1302.0 to 4.4.1749.0 in a Test environment (Windows Server 2012R2, SharePoint Foundation 2013).
Now any screen which should show a filter builder instead shows the error page "Unable to process your request". So this happens if I click on "Advanced Search" from anywhere, and also if I try to open the "Criteria-based Members" tab on any Set, and the "Members" tab on any criteria group.
I ran the same upgrade in Dev a couple of months ago and have had no such problems there. I did also migrate a bunch of new config into Test on the same day as patching, but I have compared config between Dev and Test and don't think it is config related.
The only error in the event log is a Warning from Microsoft.ResourceManagement.PortalhealthSource:
"The portal was unable to complete a request and showed a user the default error page.
An unhandled exception was caught.
Check the product diagnostic log file and then check the SharePoint log file."
I have looked through the SharePoint logs but all I see is when it shows the Error page - it doesn't say why. I've done a comparison between Dev and Test and the logs look identical up to that point.
I've re-installed the MIM Portal update and confirmed in the install log that there were no errors. I have rebooted all servers.
One thing I have noticed is that Windows patching is much more up-to-date in Test - they routinely patch Test at this customer, but not Dev. So I guess it's possible some combination of Windows patching and the MIM Portal patch has broken it - it would just be really helpful to get an error message from SOMEWHERE!
I have also figured out that the method for diagnostic logging has now changed. I generated a trace log but there are no errors at all, which does seem to indicate an error in the SharePoint layer, not reaching the MIM Service. There used to be a way of commenting out the "ILMErrors" line in the web.config to get more useful messages. but doing this now completely breaks the Portal - is there a new way to do that? (CustomErrors is set to Off but it's still showing the useless error page)
Final observation: the issue happens both when accessing the MIM Portal through its full address, and using localhost on the server.
http://www.wapshere.com/missmiis