This is connection to TestEDD/DataDiscovery server. I am not very familar with its setup but I think it is not configured correctly. Probably you can swithc it off somehow? After that HP should work fine.
Alternatively, look into EDD setup, but I cannot help with it.
Actually, go and try to switch off Windows authentication in the EDD application in IIS.
If I turn it off for the default web site it works, but not through productions EDD or production itself. Isnāt this incredibly insecure since the entire site has authentication disabled?
Well, it is not unauthenticated, it will just not try to use Windows auth, just tokens.
But if it is production, do not change it. I donāt know enough about EDD to recommend that
also, it works in test, prior to making this change, just not in production, I dont know if that could narrow down as to what the issue could be?
Issue is with EDD setup and its user authentication, I donāt know anything more
ok, thank you so much for your help, I will update as I work through it
I had to do a client re-install because I was having other issues --runtime errors in particular. Since I did the re-install Iāve not had the login window pop up; donāt know if that fix will hold or not⦠but for now all is good.
Spoke (typed) too soon! Still getting the login window AND the runtime error!
I have been recommended a few things by Epicor, non of which worked. Using what Olga and Hasokeric had recommended seems to have made it work, though I question security on it. In IIS, select the Default Web site.
On the site, select āWindows Authenticationā and select Disable. Then give it a try.
Thanksā¦Iāll try itā¦but I agree that it doesnāt quite seem like the most secure solutionā¦
I provided that information to Epicor as well, so i will update depending on what they say⦠but i am sure they will not put too much behind it.
Internally, Microsoft is deprecating Active Directory in favor of Azure Active Directory. Active Directly is not web application friendly. To use Windows Auth, the client must have have an NTLM or Kerberos client (which is not a W3C standard). Devices must be on the domain to access the site, which sounds safer until you have remote access and you open up a lot of VPN access.
For more info:
uggg, this hits me 2 ways, as the Admin for epicor and IT manager⦠wow. Thanks for this info.
I am having a remote session with Epicor today so they can see the way I made it work and diagnose with me the issue, potentially a resolution as well. I will report back if/what I learn something new.
Good luck! Iāve still got to have a call with them on the Application Error Iām getting⦠their suggestion of removing all the Epicor files and reinstalling worked for about 1/2 day. Just havenāt had the time to do a webex yet.
what error is it?
I had that issue, when I updated to 10.2.700.10 it fixed it