All I can tell you is this is most likely a IIS issue (verbs & handlers). I was not able to resolve this, so I emailed DMXzone for a refund - which they would not give me. Instead they sent me a link with convoluted information on how to troubleshoot the problem. Since my IIS is "vanilla" - I expected this extension to work out of the box, but it seems there are other users who are having this problem too.
This was my first request for a refund from DMXZone after buying 20+ products from them. Needless to say, I am very disappointed in their response - this extension was a waste of money since I can't use it, and they can't help resolve the problem. Not so sure I will be buying anything from them again.
According to our www.dmxzone.com/72/refund-conditions/ we cannot process your refund request. The extension has been tested and working on IIS with default settings. We have already explained you what causes your issue, and sent you an article on the IIS website, which explains how to fix it - so please just follow it. I understand that you think this is a problem with the extension, but unfortunately this is caused by your server configuration. If it was bug in the extension, this would have happened to the rest of hundred users, who bought the extension.
Hi Teodor - thanks for your reply - no sense going back and forth with this, as I've stated many times my IIS is "default" and I certainly have not changed any settings in it, but yet, the extension still does not work. I can't speak for the other users having the same problem, I can only speak for myself.
But thank you for pointing out the refund conditions, as I will consider this before purchasing anything else from DMXzone.
Hello MX Addict, As long as i remember the issue you were having was only on your local IIS server, and everything was working fine on the remote server? As i explained, our developers are fixing this, and this will be improved in the upcoming update. Your issue is totally different from David's issue. His issue is caused by his server config while yours is indeed an incompatibility with IIS on Win10.
As for the PAU3 issue - this has already been fixed, and i have sent the fix by email to everyone who requested it...