(401) Unauthorized

[VAD_Support]

What version of 3CX and VAD are you using?
Did you enable remote access to the configuration in 3CX, as described in the users manual?

[SWSDEV]

Yes, I enabled remote access as described.

The current version of 3cx is 8.0.9941.549

The current version of the VAD is 2.0.3549.0



I have set EVERYONE permissions on the /ivr website on IIS. Even though deployment is successful I still get 401 unauthorized when selecting PLAY to debug.

I find no security errors though in the windows log. My Application pool is running under localsystem.

[VAD_Support]

Can you try launching the following URL manually with IE and post here what you get?
http://3CXServer:5484/VAD_GetDebugInfoF ... UILDNUMBER

You mentioned that no files have been copied to the server. Can you manually create the folder YOURPROJECTNAME_Debug_BUILDNUMBER under "%ALLUSERSPROFILE%\Application Data\3CX\Data\Http\Interface\ivr"? And manually copy every file from your VAD machine from ProjectFolder\Output\Debug to the 3CX server in that new folder? Then try launching again the above URL.

Let me know about the progress...

Thanks.

[SWSDEV]

The url doesn't work because the files don't exist.

I'll try the manual copy and get back to you on that.

Thanks

[SWSDEV]

Here's the diagnosis and solution.

Pretty simple after all.

First when I copied the files over the ivr still didn't work.

Next I tried going in to IIS and I removed Integrated Authentication and put Anonymous on. This helped with one part... When I did the actua deploy then I actually saw the files copy over.

So using anonymous authentication worked. However I had previously set up Full access to the Everyone group, so I don't know why that was an issue. Somehow the integrated authentication was passing credentials through that didn't even fit in to the everyone group. I'm sure it was from the remote machine deploying the project.

So now it works, but do you guys have a specific security setting in IIS that you intended?

[SWSDEV]

If the VAD confirmed the existence of all the files after deployment or at least was able to discover the security discrepency that would be great to avoid the false sense of successful deployment.

[VAD_Support]

Thanks for the information. We'll investigate this, now with the information provided I think this is much easier to reproduce.

Is the Windows 2003 server running in a domain? Everything has been tested in machines belonging to the same domain, so maybe if your machines are not running in the same domain, you get those permissions problems...

[SWSDEV]

They are not part of a domain. They should be part of the same WorkGroup though.

[VAD_Support]

OK, thanks for the information. We'll try to reproduce it here in a similar scenario.