10.1 License Manager Won't Start

Question

Hello, everyone. I'm having trouble getting ArcGIS 10.1 License Manager to run on our new Windows Server 2012 machine.

I've tried turning the server firewall off but that hasn't helped. The network firewall is configured to allow communication over port 27000.

The error from the log file is:
16:07:10 (lmgrd) Since this is an unknown status, license server 
16:07:10 (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon.
16:07:10 (lmgrd) Starting vendor daemon at port 27000
16:07:10 (lmgrd) Using vendor daemon port 27000 specified in license file
16:07:10 (lmgrd) REStarted ARCGIS (pid 7228)
16:07:10 (ARCGIS) FLEXnet Licensing version v11.10.0.0 build 95001 i86_n3
16:07:10 (ARCGIS) Server started on ServerName for: ACT  
16:07:10 (ARCGIS) EXTERNAL FILTERS are OFF
16:07:10 (lmgrd) ARCGIS using TCP-port 0
16:07:10 (ARCGIS) tcp_s is bad!!! Exiting
16:07:10 (ARCGIS) EXITING DUE TO SIGNAL 28 Exit reason 5
16:07:10 (lmgrd) ARCGIS exited with status 28 (Communications error)

I'm totally stumped. Any help would be much appreciated!

Thanks in advance.

V_StuartFoote · Answer

Matthew,

As usual Richard has the right answer!  And likely the lmgrd and ARCGIS vendor daemons are both using TCP IPv4 port 27000, an edit the service.txt file as indicated should correct.

Similar error/resolution for these related threads:

http://forums.arcgis.com/threads/74808-License-Manager-Service-won-t-start
http://forums.arcgis.com/threads/84395-10.1-License-Manager-won-t-start-after-attempting-to-lock-port

Let us know if that does not resolve and we'll investigate.

Stuart

RichardDaniels · Answer

Looks like problem is the "ARCGIS using TCP-port 0" issue.

In your service.txt file located at C:\Program Files (x86)\ArcGIS\License10.1\bin make sure you have a port specified. The top two lines of the file should look something link the following:

SERVER MYSERVERNAME ANY 27000
VENDOR ARCGIS PORT=1234

Most likely you need to lock your vendor daemon to a static port. There is a ESRI troubleshooting document for this that was first written for ArcGIS 9.x which still applies.