I want to run some LAN speed tests on Vault 2011 Professional. I am installing Vault Pro Server 2011 on a Windows Server 2008 machine, which has SQL Server 2008 R2 installed. I'm getting stuck at the "firewall test" stage - the install stops with the message "Windows Firewall detected - Please make sure it is configured to allow client access to the default website"
BTW it's not standard Windows Firewall that is installed - it's Windows Firewall with Advanced Security.
I have set up a new rule to allow incoming connections on ports 80 and 443 to no avail.
Any suggestions please?
Tom
Hi Tom,
The firewall message should be a warning - not an error. It should not prevent you from continuing installation. Is the button to continue installation greyed out? If not you should be good to go.
Paul
Yes, I can finish the install, that's not an issue. I can even switch off the firewall if I wish. My problem is that I can't log in to the vault from a client - it says "Failed to acquire a licence"
Have you installed the license manager and a license file?
Hi,
It sounds like you are connecting to vault server fine - but there is some issue either with or connecting to the license server. The wiki does have some information on troubleshooting this error so you may want to check this out:
http://crackingthevault.typepad.com/crackingthevault/2009/07/failed-to-acquire-license.html
If this doesn't help, you might want to post a new thread with the licensing error. That would probably get answers from people more knowledgable about licensing than I am.
Paul
The problem with Vault and licensing on Server 2008 is actually an IPv6 issue. In a sense, it cannot see the NLM because it tries to connect via IPv6, which fails, instead of the classic IPv4 which works. This happens more often with Vault because people will run the NLM and the Vault client on the same machine... which just happens to be Windows Server 2008, Windows Vista, or Windows 7. A simple hosts file entry for a localhost redirect back to the IPv4 loopback of 127.0.0.1 fixes this. Otherwise, if the NLM is on another machine, the hosts entry for that hostname to the IPv4 address works as well. I have written a KB about this.
For more information about Network License Manager connectivity issues and IPv6, please see my discussion post here:
http://forums.autodesk.com/t5/Installation-Licensing/Network-License-Error-1-5-15-and-IPv6/td-p/2982...
We actually blogged about this awhile back and there are technical solutions on this.
You can also edit the licpath.lic file (Not the license file) located in:
C:\Program Files\Autodesk\ADMS *
Change the server name to use 127.0.0.1 instead. So the format for the first line will look like:
SERVER 127.0.0.1 000000000000
That would work to a certain extent unless it is superseded by the ADSKFLEX_LICENSE_FILE or LM_LICENSE_FILE environment variables. And of course, it would not work to do this if the NLM were on a different machine altogether. But it's good to know that editing the LICPATH.LIC file with a localhost IPv4 address will work. Thanks!
I resolved the issue by setting the ADSKFLEX_LICENSE_FILE environment variable to the vaule "@<servername>"