Last edited by Pieter van Dieren; 21-Dec-2019 at 10:31 AM.
Regards,
Pieter
thats interesting
i would run fiddler to see which exact calls give you the error
Michael Salzlechner
StarZen Technologies, Inc
http.://www.starzen.com
IT Director at Balloons Everywhere
Development Blog
http://www.salzlechner.com/dev
DataFlex Package Manager (aka Nuget for DataFlex)
http://windowsdeveloper.com/dfPackage
"Interesting" is not exactly how I am calling this right now... ;-)
Afraid so.
I've already tried to create an "empty" login view in which nothing happens; same error.
So it must be something in the WebApp myself.
It has got something to do with the Handler Mappings (in general). My development computer has a lot more mappings.
So I also tried to copy those settings from the applicationHost.config to the webserver (I read that this solved it for someone), but that didn't help either.
No clue so far. And too less knowledge about IIS to deal with this....
Regards,
Pieter
have you tried to run fiddler to see what exact call is giving you the error. Or if not fiddler you could probably do the same with the chrome debugger but i prefer fiddler for issues like this
Michael Salzlechner
StarZen Technologies, Inc
http.://www.starzen.com
IT Director at Balloons Everywhere
Development Blog
http://www.salzlechner.com/dev
DataFlex Package Manager (aka Nuget for DataFlex)
http://windowsdeveloper.com/dfPackage
It seems to clip the error text. Can you look at the browser developer tools under the network tab to see if you can fetch the entire response? Maybe there are details that could help us..
I found the cause yesterday....
This WebApp communicates via WebServices with another WebApp.
It only should communicate after the user has logged in, but it tried to send a certain message too soon. This resulted in this particular error.
Because we never noticed this on our development computer and never saw this error, we didn't think of this before.
Thanks all for your input, sorry for wasting your time...
Regards,
Pieter