FlexNet Licensing error: -96,491

[Anonymous]

Clients with MoldFlow 2017 installed can't start Moldflow because they get FlexNet Licensing error: -96,491 when launching it.

I built a new server to replace the old license server and I used the same license manager installer and license that the old sever had. The new server has the same name, MAC address, and IP address as the old server so that there would be no disruption to our clients. The license server is installed and configured, the service running, and the licenses and feature usage info show 25 seats available when running a status inquiry. 

The clients are able to communicate with the server, both TCP port 27001 and TCP 2080 are open to the client and I can verify communication on those ports is working. 

From the client I've run lmstat.exe -a and I can confirm that the client sees 25 seats available. However they get the FlexNet Licensing error: -96,491 when launching MoldFlow 2017. I tried a clean install of MoldFlow 2017 on a test machine running Windows 10 and got the same error. 

Why are the licenses not checking out?

Thanks!

[Otto]

Hello FariborzParsi5892 and welcome to the Autodesk community!

It looks like you are experiencing issues with your product on Windows 10 or want to know which Autodesk products are supported on Windows 10. Community members with similar questions found the following article(s) useful:

Windows 10 support for Autodesk products

Other threads about Windows 10 support

Change your mind about Windows 10? Here's how you can roll back

Please consider bookmarking these pages and checking back often; we'll update with new information as our testing continues.

If this information was helpful, please consider marking it as an Accepted Solution by clicking on the "Accept as Solution" link, below. Taking a moment to do this will help others with similar questions find useful answers. Thank you!

Kudos (click on the link or the "thumbs-up!" icon), are also gratefully received! (Even a bot likes praise.)

If this answer missed the mark, please let us know so that other community members can lend a hand. Any additional details might help, too: consider including relevant screenshots, log files, error messages, or system specs.

[Anonymous]

Thanks but I don't think it's a Windows 10 issue. The product supports Windows 10 and the installation works fine (https://knowledge.autodesk.com/support/moldflow-insight/troubleshooting/caas/sfdcarticles/sfdcarticl...).

It's just the licensing that doesn't work.

[Mark.Lancaster]

@Anonymous

That error code usually means the license server is down.  Can you provide the debug log as defined under the LMTOOLS/Config Service tab.

[Anonymous]

Here's the debug log attached. (server name and domain changed for privacy)

[TravisNave]

Mark is right.  -96 is a connection error.  It generally means it can connect to the server but not fully.  Just because you claim the ports are open, doesn't mean that they are.  You have to test to verify. 

Open IE and type this:

http://servername:2080

 -and-

http://servername:27000

Obviously change servername to the hostname of your server.  Had you not edited it out, I would have put it in for you. 

Both of those should give you a jargon result of:

Wê-60Wê-60Wê-60Wê-60Wê-60

If you get an error, then that particular port is blocked.  It's usually the adskflex vendor port of 2080.  Anti-virus and internet protection programs can do it too, not just firewall. 

Also PING the server from a command prompt and make sure you get the correct IPv4 address of the server. 

Let us know the results.

Good Luck!

[Anonymous]

Thanks for your response. I got the Wê-60Wê-60Wê-60Wê-60Wê-60 response when browsing to http://servername:27001 and http://servername:2080.

I did some additional troubleshooting on the client. Here is a screenshot of the MoldflowLicErr.log, the error message box that I receive when opening the program, and lastly the results of running lmstat.exe -a. You'll see that the server is up and showing licenses available. However the Feature string on the error message box doesn't match any of features the server shows as running. Does this indicate a mismatch between the license I installed the client with and what the server is hosting?

[TravisNave]

---

@Anonymous wrote:

Does this indicate a mismatch between the license I installed the client with and what the server is hosting?

---

Yes.  In fact, that is exactly what it is indicating.  The license you have on the server does not match the client software.  Once you fix the client with the right flavor of the software, you should be good to go.

Good Luck!

[Anonymous]

I have 25 license keys available. Which license key am I suppose to use on my lab machine image when installing MoldFlow Synergy to ensure that it works with the network license loaded on the license server?

[TravisNave · Accepted solution]

Your license appears to me for Autodesk Moldflow Insight Ultimate 2017 which is product code 86753MFIA_2017_0F.  You appear to have Moldflow Standard (86751MFIB_2017_0F) installed.  You should be able to get the correct version from your Autodesk Accounts page.  Though technically, I am not sure why the standard product is not cascading to the Ultimate license, since that is the normal progression of the software. 

[Anonymous]

Thanks for clarifying that for me. I'll make sure I download and install the Ultimate version instead of Standard. Thanks again!

[TravisNave]

Sounds good.  If for some reason you still have issues, just post new log files. 

Good Luck!

[Anonymous · Accepted solution]

I finally got to the bottom of the issue and found the final solution. I was still getting the -96,491 error even after installing the correct software version on the client, and regenerating the network license to be sure I had to correct license.

The solution was to add an environment variable name "ADSKFLEX_LICENSE_FILE" and the value as "27001@SERVERNAME" as suggested here: http://forums.autodesk.com/t5/installation-licensing/firewall-issue-with-windows-2012-license-server... on the client machines.

For Windows administrators that would like to set the environment variable with PowerShell use this command(Just make sure to change the port number to the port your server is using):  [Environment]::SetEnvironmentVariable("ADSKFLEX_LICENSE_FILE", "27001@SERVERNAME", "Machine") 

Thanks for everyone's help!

[TravisNave]

Sometimes even the experts overlook the most simple solutions. 

Glad you are fixed and up and running!