From my experience, right off the bat I know this is usually a web.config problem. I was given a clue by the customer that this happened during a time when some of the admins were playing around with the installation of some 3rd party web parts in this environment. My hunch was that something got written to the web.config for this web app because when I looked at Central Admin, I noticed that they had deployed these custom web parts to ALL web applications including My Sites. So the moral of the story is to be selective when deploying web parts and only install them on the web applications that need them.
Since this My Site web application was pretty clean, meaning no customizations were MEANT to have been installed on it, I figured the quickest thing would be to:
- Create a blank dummy web application
- Copy that web.config file from that web application to the My Site web application (of course backup the existing web.config file first)
- default location of web.config file c:\inetpub\wwwroot\wss\virtualDirectories\[name of web application]\web.config
- problem solved
Aaron Pryor vs Alexis Arguello…Pryor just had Alexis number