Did you look through the application log on the CRM server to see if there are any clues there? I'd hate to send you off on a wild goose chase if there is some indication there of what is really going on.
That said, ADFS is likely installed somewhere else. Are you a Deployment Admin in CRM? If so, you can start (but *do not complete*!!!) the "Configure Claims-Based Authentication" wizard and get the ADFS server from the Federation metada URL. e.g. https://adfsserver.company.com/yada-yada-yada/federationmetadata.xml where adfsserver.company.com resolves to your adfs server. Make sure to cancel the wizard after gathering the information. Again, all of my experience is with CRM 2011 in a simple setup with one CRM server and a separate ADFS 2.0 server. I presume 2013 is very similar, and you may be running a newer version of ADFS which might also be different. On Fri, Jan 17, 2014 at 10:03 AM, John Bonner <[email protected]> wrote: > Soooooooo dumb question here. The CRM server does NOT have the ADFS role > installed....so I can't access the MMC to check the certs as you > suggest...or am I looking for the wrong thing? > The site is IFD as I can access it from the public wire and it does have a > ssl cert installed in IIS...so possibly a disaster waiting to happen? > > JB > > > ------------------------------ > Date: Fri, 17 Jan 2014 09:46:20 -0500 > > Subject: Re: [NTSysADM] CRM 2013 Working fine then suddenly 404 error? > From: [email protected] > To: [email protected] > > I'm running CRM 2011 and ADFS 2.0, so things may be a bit different for > you, but... > > Check for errors in the CRM server's application log. I have seen ID 1309 > in the past when the ADFS server updates its own certificates and the new > ones are not trusted by the CRM server. > > For sanity, you can also check the certs that ADFS is using by opening the > ADFS management console on that server, expanding the Service node, then > clicking on Certificates. Check the dates on all the certs there. If the > token signing and token decrypting certs are new, I would guess that's your > issue. If so, you'll need to import the new certs into the CRM server's > store and restart IIS. > > Don't change anything in ADFS if you haven't set up IFD personally and > know what you are doing. > > I would advise exploration at this point without any modifications. > > > On Fri, Jan 17, 2014 at 9:30 AM, John Bonner <[email protected]> wrote: > > > Boy that sure does fit as a possibility: > > "There are several variations of this – but if you aren’t getting * > *anything** in the logs – start looking at your certificates! More times > than not – it is the SSL certificate and you aren’t even getting to ADFS > which is why there aren’t any error messages to work with. " > > Now I just have to educate myself on how to check to see what the sysadmin > who is unavailable today configured. > > > ------------------------------ > Date: Fri, 17 Jan 2014 09:23:33 -0500 > Subject: Re: [NTSysADM] CRM 2013 Working fine then suddenly 404 error? > From: [email protected] > To: [email protected] > > > IFD install? If so, check the ADFS token signing cert., and other things > with ADFS. > > > On Fri, Jan 17, 2014 at 9:19 AM, John Bonner <[email protected]> wrote: > > As the subject says I had a perfectly good CRM 2013 install on 2012 and > it was being used. Sometime overnight the site went down. Now I get a 404.0 > error. I've disbaled friendly errors...just get a blank page not even a > 404. I've modified the web.config debug=true nothing. Fiddler shows > nothing...well not exactly. Fiddler shows a 404 as well. Event logs on > server show nothing. > > > > I've removed ssl cert and reapplied. Tried accessing the site http nada?? > I looked for any updates that were pushed overnight nothing..(they are > disabled but I checked anyway). > > If I browse to http it redirects me https as it should. It prompts for my > NT credentials as it should. Downloads favicon and decides it has done all > it's going to do. > > > > So I am at a real loss as to even getting a clue as to the problem. If > someone can help me with some further troubleshooting direction it would be > appreciated. > > > > Thank You > > > >
