Sharepoint 2013 foundation central admin "something went wrong"

Question

I recently installed SP1 (the bad version before it was pulled) on my SharePoint 2013 foundation server. I ran psconfig and made sure my databases were up to date after SP1. I checked central admin after psconfig and everything was working and good to
go. I have little need to access it on a regular basis, so after the install I haven't attempted to access central admin for approximately a month. As the updated SP1 just hit a few days ago I attempted to pop into CA to does some work on the site in preparation,
and I received the sorry something went wrong message. I thought it may be an issue due to the bad version of sp1 that was installed and/or high ram utilization. As this is a standalone box in production I could not reboot easily. I was finally able to do
the install last night, and it appears the problem is still ongoing. The site has been in production for about 6 months now, I have never had any issues hitting CA previously. SharePoint is running as a VM, and we have decked the specs out for it. We are allocating
4 cores and 24gb of ram to the site, and we are not seeing anything close to max resource utilization on the hypervisor or on SharePoint. I checked the correlation ID that SharePoint provides in the ULS logs and the only thing close to an error I get is a
message "cannot find site lookup info for request uri
http://localhost:<port binding>/." this is followed by "Application error when access /, Error=Exception of type 'System.ArgumentException' was thrown.". I'm exporting a copy of the vhd to experiment on in a test environment now, so
I will update this if I get more info. I don't think this was caused by SP1 as I was able to hit the CA page after doing the upgrade, but other than standard users interacting with the site since SP1, there have been no changes from an administration perspective.
I am the only one who touches the site here so I know changes weren't made without my knowledge. Anyone have a clue what could be causing this?

Answer 1

I see, good to know. IT couldn't have been someone visiting the CA page turning it on, as its an IIS only setting. I cant say that no one ever would have changed the settings, but generally I am the administrator for this server and my colleagues don't touch
it.
When I say default content pages I mean my SharePoint site collection pages. The problem I was having when I started this thread was about CA, but I also noticed on my site collection that FBA is turned on as well. When I turn this off a few things
happen, generally I get a message around authorization saying that the site collection admin or farm admin cannot view the page. On the few occasions I am able to login, the page content often renders without any css, so its just plain text on the page, or
it places the text in random locations around the page. Generally when I try to navigate though I just get an access denied message shortly therafter. Keep in mind I have done absolutely no setup at all around FBA, so I'm not sure why turning off an authentication
method that has not been configured at all would not allow me to access my site pages.