Hi
We have this issue with Vault Windows Authentication. this messagebox is shown
with users (Please make sure you are in the same data management server).
It was starting when we upgrade to vault 2014, and we still have this issue when we update to vault 2015 sp1. it is happened nearly every 3 week. and it happened always after weekend.
I think it is something to do with dns, if I change the servername to ip adresse it is working.
I have try to restart iss. But it is still the same. The only thing that is working, is restart server.
I have found this old link.
The suggestion is to set DefaultAppPool regular time to interval to (17400)
My settings is set to (1740) Vault server is Windows server 2008 R2 IIS 7
Can I still using this old link and change 1740 to 17400 and what does this or is there other suggestion ?
René J
For your issue, when this occurs, can the client and the server still resolve the servername by IP? It certainly sounds like a DNS/Name resolution issue.
-Hywell
I fogot something, If I Login as Administrator or another username without using Windows Authentication then ther is no problem.
I think it something to do with IIS and Vault Windows Authentication.
René J
We are having the exact same problem. The only difference is that I get my Windows Auth error on the 4th of every month. As above, i can use the IP address and everything works well. IIS restart doesn't work. We can still ping the server by using the IP address or the server name successfully. Also, logging in without Windows Auth works.
A few other notes that my reseller had me check:
Any solutions at all to this?
Hi
Thanks for sharing info.
I think it is some thing to do with "vault maintenance" we have a schedule that run every saturday 20.00
maybe you can check on your server, when you are running the vault maintenance script.
but I need to confirm that I am right.
I think, I have a server, that will have this problem this weekend.
I think, I will test before the maintenance script is running and after.
René J
Try to change the C:\Windows\System32\drivers\etc\hosts file and add a static DNS record for your server.
I have also experienced some weird situation where the ping-server-name thing seems OK but you just cannot log in, the trick above finally solved the problem for me.
Do you have Windows Authentication enabled on your Default Website?
I'm not sure if it propogates down, but also ensure it's set on the AutodeskDM site:
Then do an IIS reset and see if it helps. If not, then it's likely one of the other IIS settings. Like tmoney I've had this issue previously, but at the time it was one of those cases where you go over every setting changing multiple things until it works, but then you don't know which one did the job!
Apologies just ignore all of that, just re-read the original post and it said when using IP address it works OK. So it probably won't be anything to do with the above.
It looks like Autodesk may have found a solution to this.
I changed the settings on our server today, so let's hope this is the fix!
Hi
doesn't work
But I think I have sloved the issue
in our vault maintenance script
we have a IIsreset before run maintenance
I have changed this to run after instead of.
It seems to work, the error should have been in this weekend, but it doesn't.
Rene J