Avatar of Michael Miller
Michael Miller
 asked on

ADFS MSIS7065 error

I have recently set up a ADFS server in my 2012R2 domain.  I can browse to the /adfs/ls/idpinitatedservice.aspx page, however, I either have an error on the login page on the right pane or am prompted to input my credentials.  Upon inputting the credentials I am taken to /adfs/ls/wia with a message that the website cannot be found.  In either scenario the ADFS server records the following error:

  Microsoft.IdentityServer.RequestFailedException: MSIS7065: There are no registered protocol handlers on path /adfs/ls/idpinitatedservice.aspx to process the incoming request.

I have modified the SPN on the user account to include the http(s)/adfs.domain.com and ensured that the account has full access to the certificate being used.  I have also tried restarting the ADFS service as well as the server to no avail.  The difference between the two results seems to be IE11 vs Edge/Firefox.  

The server is using the WID on a 64bit Server 2012R2 system.  I am able to browse to the /federationmetadata/2007-06/federationmetadata.xml page; so I know some of this set up is working.  The error message on the web portal is (Edge browser as well as IE11 on the server):

An error occurred
An error occurred. Contact your administrator for more information.
Error details
Activity ID: 00000000-0000-0000-1300-0080000000fb
Error time: Thu, 20 Apr 2017 13:01:57 GMT
Cookie: enabled
User agent string: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
Active Directory* Federated Authentication

Avatar of undefined
Last Comment
Michael Miller

8/22/2022 - Mon

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Michael Miller

K B,

Thank you for the quick response.  That is the guide that I used to set up our ADFS server.  However, I did notice that the guide says to test with .htm and not .aspx.  When I use the .htm site in Edge everything seems to work correctly.  Using IE11 I am still getting the same redirect to /adfs/ls/wia with a page cannot be found message.  In IE the credentials login is a pop out dialogue rather than built into the portal as in Edge.  The error message doesn't appear on the server when using the .htm site for either browser.

Is there a GPO that has modified the default settings of your IE11? have you added the https://adfs.domain.com to intranet zone.  by default intranet zone is out of the box able to handle this.

perhaps try to setup with a user account that does not have the SPN modifications also
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
Michael Miller

I have tried using the intranet sites list, the only GPO we have in place is for trusted sites, and I have also tried removing the SPN information from the service account.

edit: should have added that I am still seeing the same results on both browsers

are you using a proxy like a WAP server?
does the GPO overlap (perhaps a wildcard) with the entry you are making?

go to File->Properties. The properties dialog shows the zone for that page.

is the server fully patched?

Since this is limited to IE that is where I would look.. setup a workstation free of any GPOs .. test with that and let me know

effectively you are seeing what you should.  You are just missing the automatic login.

so make sure your test workstation isnt touched by any gpo prior .. otherwise you will still have to revert whatever it did
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Michael Miller

So, I tried using a freshly loaded PC and still kept getting the error; even before I joined it to the domain.  Started looking at different online threads and found one suggesting that the URL I was using was incorrect.  


as opposed to


Shame I only noticed the .aspx being incorrect and not the whole last file on the URL.  

Anyway, thanks for taking a look at this for me!