Help Desk and PC Inventory Software by Gritware   Gritware Support Forums
Gritware Support Forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
Canadianmade

Member
Registered:
Posts: 65
Reply with quote  #1 
Every hour I'm getting the following application error;

http://servicedesk.mte85.local/Services/WebTracksServices.asmx Web Tracks Windows Service Unexpected Error : The request failed with HTTP status 401: Unauthorized.

And my computer audits are not processing? This seems to have started after the update. I checked for the web.config file in C:\Program Files (x86)\Gritware\Web Tracks\WebRoot\Services to make sure it contained the Authorization * and that the network service has read permission to the file.

Anything else I can try?

thoese

Moderator
Registered:
Posts: 486
Reply with quote  #2 
Hi,

Do you have some sort of batch file that is calling this service to audit your computers every hour using WTAudit.exe?

Can you manually open the following url?

http://servicedesk.mte85.local/Services/WebTracksServices.asmx 


__________________
Todd @ Gritware
Other resources
Gritware.com
Knowledge Base
Web Tracks Help
Canadianmade

Member
Registered:
Posts: 65
Reply with quote  #3 
I can access the URL fine from outside the server (from my workstation) but when logged into the server using the same account as the batch file is using to run I get a HTTP Error 401.2 when trying to access the site.
I only have the computer audit batch files run once a day. At the times they run the error message is slightly different;

http://servicedesk.mte85.local/Services/WebTracksServices.asmx: The request failed with HTTP status 401: Unauthorized.

I do remember having to change some of the authentication in IIS to get the site to work after the update. I have now turned Anonymous Authentication to Enabled and I can access the site from the server now with the 401.2 error. I only had Windows Authentication on before.
I'll let it run tonight and see what happens!

Canadianmade

Member
Registered:
Posts: 65
Reply with quote  #4 
This is fixed, once I enabled anyonomous access in IIS it started working again.
thoese

Moderator
Registered:
Posts: 486
Reply with quote  #5 
I will look into our installer to see if we can enable the anonymous access by default when setting up the IIS site.

Thanks for reporting back the solution :)

Kind Regards,

__________________
Todd @ Gritware
Other resources
Gritware.com
Knowledge Base
Web Tracks Help
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.