Autocad Network License Not Available Error 0.0.0

[Adele Strecker]

ThanksI'll dive into this this evening. The debug log shows that the server is running with the correct license. The license server is running on the same machine as Inventor is. Trying the License File option returns an error. It's a simple Inventor and Nastran InCad 2018 license. I've tried creating and downing the license a number of times and get the same data in the License File.

No network involved, all components are on a laptop. As an Expert Elite, we are allowed to use software under ADSK's NFR program. The only issue is that they only supply Nastran's InCad as a "multi-user" license requiring a license server for Inventor and Nastran.

I've done the License about 5 times using the Cut/Paste from the LMTOOLS utility. Both the License Server and software reside on the same machine. The MacBook Pro is a laptop that's not connected to any network.

When I start AutoCAD Mechanical 2020, clicking "Multi-User", enter the license server name, it always appears the following error message: "Network License Not Available, Common causes: all licenses are in use, the server is down, or the license has expired. Contact your system administrator or support. Error [-15.570.0]. However my colleagues can start it normally, I'm sure the license server name is entered correctly, I can ping this server normally. I can start it normally several months ago, now I have uninstalled and reinstalled AutoCAD Mechanical 2020 several times, but this issue still exists, how to solve it?

-15 means that you cannot make a connection to the NLM. Give that others can, then it probably isn't the fact that the NLM isn't started or the firewall is blocking the necessary ports. It could still be latency on your end though. A good place to start is by setting the following system environment variables:

You can also verify that your computer has access to the proper ports by using good old fashioned Internet Explorer. Yeah, it's still on your machine likely hidden somewhere, But you can launch good ole version 11 from your run line with iexplore.exe.

Or if none of that work, you can use my license reset tool. That might help fix any underlying issues with your licensing. It also has the built-in options to assist with the system environment variables that I listed above.

I find it interesting that others can get licenses from the NLM but you cannot, even though you say you can PING the server. Are you sure that when you PING the server that it is responding with the correct IP address of that server? If others are getting licenses, then the ports are open. The IE11 test should work for you as it is independent from any other Autodesk settings. That leads me to believe that something else is going on. Is your network connection properties set to PUBLIC instead of PRIVATE or DOMAIN?

Thank you everyone for your kindly help. My issue has been solved by my corporate's technology engineer. It seems a little complex. Generally, first AdsklicensingService was reset, then installing Autodesk Single Sign on Component.

I'm our small-lab IT support/admin trying to get people set up to check out shared licenses over a VPN, and hit a wall. I'm suspecting that the VPN is blocking some traffic on some ports, but our main IT department is overwhelmed so I'm trying to make sure I haven't overlooked anything, or that there aren't troubleshooting steps I've failed to try.

Environment: Single MacOS 10.12 server running flexlm (port 27000), attempting to pull license with MacOS 10.14 client connected to office network via current version of GlobalProtect, attempting to check out a license for AutoCAD Mac 2018.

What happens: Autocad appears to hang when I enter the network address for multi-user license server. After a VERY long delay (tens of minutes), AutoCAD will eventually throw a "Network license not available" error.

I've tried with and without the port, by short network name ("host"), full network name ("host.domain.edu"), and IP address, all behave identically. I had another user test and apparently the behavior is similar on Windows.

No firewalls on either end, just what the VPN is inserting (which I don't have visibility into). Server pings fine, and I can connect to it via other protocols (ssh, screen sharing). Doing a port scan, 2080 and 27000 both show open, as expected; adjacent ports don't.

I'm not very good at reading Wireshark network captures, but as best I can tell it's connecting on 27000, then when it tries to connect on 2080 some of the traffic is getting dropped since I'm seeing re-sent packets.

I'm guessing all of the above is pointing toward the VPN system blocking some traffic on 2080, but does anyone have suggestions of what I might try to either confirm this or rule out other configuration issues?

I did get my problem resolved, and the problem turned out to be what I was starting to suspect--our organization's VPN was blocking outgoing traffic (or at least some kinds of outgoing traffic) on certain unusual ports, which included 2080 that the AutoCAD flexlm license server uses.

I can't tell you exactly what settings were changed on the VPN/firewall, since that's at the org level and above my pay grade, but they did say that they made adjustments and the adjustments they made fixed the problem.

It wasn't obvious initially, because the VPN was letting some traffic through, so when you port-scanned the server through the VPN, the ports would show as open. However, when AutoCAD actually tried to pull a license, I believe what would happen is it would initially connect to the server on 27000 (the specified license server port) andstart the negotiation process, at which point it switched to port 2080 to actually pull the license. (Not sure why flexlm switches ports partway through, but it does.) At that point there was a communication breakdown.

When I did a packet capture, I would see some packets on port 2080 getting re-transmitted, which was (I believe) due to the VPN blocking some outgoing traffic on that port (maybe because the packets were not a recognized protocol?), which caused the license pull to fail.

At least one user is still having on-and-off problems pulling licenses for some other reason (that one is visible on other protocols as well), which I've yet to diagnose but will report on once it's fixed if you haven't figured out your problem, in case it's helpful. A second user was having problems returning licenses, which I am suspecting (haven't yet done enough experimentation to confirm) was due to their not setting the recommended license server timeout variable for VPN use, so it was timing out before successfully checking the license back in.

I can't really interpret the error log you're seeing; it looks superficially like it's the same "can't connect to license server" error, which could be anything. The "ICommunicationCenterConnector.SubAwareServiceUrl" bit is odd, though--that kind of looks like it points to another cause, but it could be a red herring if it's just referring to a URL for an error message or something.

I'm a complete rookie on AutoCAD. So please bear me if this question is silly. I'm trying to create a network surface with the irregular shapes of polylines (as below). And I kept getting Error code 98024 and cannot create a network surface. I check multiple times for the end and intersection points to make sure they connect the plines. Not sure what's going on and I found no information about code 98024. Any suggestions would help?

Thanks for the reply. When I use the network tool, I can choose the edges and the polylines in the center in both directions. I suppose that if I don't have any curves, it won't let me choose those lines. Do have any other suggestions?

Based on your shapes I'm not sure I would use network, as the modeler wants to curve and smooth the surface both ways. I would recommend using loft with successive sections to define your surface. Another option would be to use drape, although I'm not sure if that is available to straight Autocad. See attached cad file.

I have this somewhat intermittent problem with our network license. After changing things on my computer and restarting, the license becomes unavailable. LMTools says it is not in use even after stopping and restarting the LM server. The events that have cause this to happen after a restart have been; updated BIOS, uninstalled old printer and installed new one, and most recently today, I was playing with creating a linetype in AutoCAD.

We are at a loss as to what might be the problem. We've tried a number of things to make it available including the restarting the network server and the license server. Nothing seems to work except waiting for it.

I've got a feeling it's a network issue but I'd like to rule out local and/or Autodesk settings that may be interfering with this before bringing in our IT consultant to trouble shoot because he doesn't know about Autodesk network configurations.

When I left for the day yesterday, the license was available. Today, before making the registry edit, it was not available which is unusual. This normally doesn't happen unless there has been a change to my computer.

Yes a semi-colon is needed. Are you still getting 15.570 error still or something else? Perhaps you will want to share the debug log file as specified on the config services tab of LMTOOLS. However if you don't want to share it on this forum you can private message me and we can go from there.

I use Autocad to work on files I have stored and shared here in Dropbox. My Autocad is set to save every ten minutes. I also manually save very often because I've learned a valuable lesson once when we lost power and my battery backup (UPS) didn't work. Hours of lost work is not fun so I constantly save to avoid losing work. With that being said, I frequently get an error "Unable to save to drawing C:\Users\xxx\Dropbox\thedrawing.dwg. Drawing saved to C:\Users\xxxx\Dropbox\sav###.tmp. This is filling up my Dropbox Folder that I'm working out of with all these *.tmp files. Is anyone else experiencing this problem and what can I do to remedy it? I shouldn't have to monitor my account for these *.tmp files.

3a8082e126