ARM DS-5 v5.27.1 compile and debugger is ok;but ARM DS-5 v5.28.1 Compilation isOK, debugge failsThe FLEXNET license server has been updated to: FlexNet Publisher 220.127.116.11
Hi KevinMy name is Stephen and I work at Arm.Sorry to hear that you are seeing this licensing issue. Have you seen the Arm DS-5 License Management Guide at https://developer.arm.com/documentation/100952/0529 and knowledge article at developer.arm.com/.../latest ?Please can you confirm that both lmgrd _and_ armlmd have been updated?DS-5 is now a legacy product. The most recent version is 5.29.3 that you can download fromdeveloper.arm.com/.../downloadsI suggest you install that newer version, or better still, update to Arm Development Studio, which succeeds DS-5.developer.arm.com/.../arm-development-studioA free 30-day evaluation is available fromdeveloper.arm.com/.../evaluateStephen
Dear Stephen:Thank you for your help lmgrd and armlmd are already the latest versionBecause of project requirements, we need v5.28.1
However, there is an error
Hi KevinThanks for your additional information. Sorry, but I still can't figure out what might be going wrong here.I suggest you open a Support Case using the "Support > Open a Support Case" option at the top of this page, so that the Arm Support and Licensing teams can properly investigate.I still recommend that you update at least to DS-5 v5.29.3 to benefit from the new features and bug fixes that it brings.Stephen
Further to Stephen's replies, I note that you seem to have very many licenses specified. It may be that other tools are picking up other licenses, whereas the debugger is seeking the license server license, so others not failing may be a misnomer.
In Help > Arm license manager > you should be able to minimize this to just the network license (this will at least help you verify is the issue is happening for all tools). You many need to also manually edit ARMLMD_LICENSE_FILE environment variable.Once you are sure that you are exclusively using the network license, it may be that your IT team have made changes to VPN if you are working remotely that blocks port 8224,
Hope this helps a little, sorry, but I have never encountered this specific error before.