• State Suggested Answer
  • Locked Locked
  • Replies 26 replies
  • Answers 4 answers
  • Subscribers 121 subscribers
  • Views 6136 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Launch of ARM DS 2023.0 hangs at "Checking existing product setup..." in Product Setup dialog

KenC

I have a new installation of ARM Development Studio 2023.0. I haven't gotten to the point of requesting a 30-day evaluation license. Immediately when launching the program, the product hangs with the following dialog:

Any help would be greatly appreciated!!

Parents
  • 0 in reply to Ronan Synnott

    I deleted the 2023.0 folder in C:\Users\<user>\AppData\Roaming\ARM\ along with the workspace folder. I relaunched 2023.0 and obtained the same result (hang). Another .log file was created with the similar entries. It appears that a call to validateAll is being performed with a NULL pointer because no licenses have been set up yet. It should be an easy fix.

Reply
  • 0 in reply to Ronan Synnott

    I deleted the 2023.0 folder in C:\Users\<user>\AppData\Roaming\ARM\ along with the workspace folder. I relaunched 2023.0 and obtained the same result (hang). Another .log file was created with the similar entries. It appears that a call to validateAll is being performed with a NULL pointer because no licenses have been set up yet. It should be an easy fix.

Children
  • 0 Arm Employee Badge in reply to KenC

    Hi again Ken,

    Apologies for the ongoing trouble.

    It may be overkill, but perhaps an uninstall, delete the entire /AppData/Roaming/Arm/ds folder, and reinstalling, may be the quickest solution?

    Regards, Ronan

  • 0 in reply to Ronan Synnott

    I deinstalled both 2022.2 and 2023.0, and deleted the Roaming/Arm folder, which had entries related to those two installs plus an old DS-5 install. I deleted the Development Studio Workspace folder, rebooted and installed 2023.0. Starting 2023.0 still results in a hang.

  • 0 in reply to KenC

    Like many systems, I have an environment variable "LM_LICENSE_FILE" set to "C:\FlexLM\license.dat". On a hunch, I renamed the "license.dat" file to something else and created an empty "license.dat". 2023.0 launched successfully, being rewarded with the expected "Add License" dialog:

     I added one comment line:

    # IMPORTANT

    ...to "license.dat" and received the "Activate product" dialog:

    I removed the comment and substituted the first "feature" in the file, which happened to be for ModelSim:

    INCREMENT msimcompare mgcld 2023.120 30-mar-2024 0 CFC395FD7C6058EB16C8 \
    VENDOR_STRING=CD6B950A HOSTID=FLEXID=9-72c52260 SN=283629548 \
    SIGN2="101F FA0D 8C47 C6FC 46B9 AAD1 6DAB BE9E 9671 B790 17CB 9032 \
    D99A 05CA C53C 1D09 5F30 3424 4F2D 5B59 0431 90F2 C45A B7AB BA48 D0AB \
    B8AC D045 5B42 BC37"

    ...and got the above "Activate product" dialog. Lastly, I put both the comment and the feature in the same file thus:

    # IMPORTANT
INCREMENT msimcompare mgcld 2023.120 30-mar-2024 0 CFC395FD7C6058EB16C8 \
    VENDOR_STRING=CD6B950A HOSTID=FLEXID=9-72c52260 SN=283629548 \
    SIGN2="101F FA0D 8C47 C6FC 46B9 AAD1 6DAB BE9E 9671 B790 17CB 9032 \
    D99A 05CA C53C 1D09 5F30 3424 4F2D 5B59 0431 90F2 C45A B7AB BA48 D0AB \
    B8AC D045 5B42 BC37"

    ...and got the usual hang dialog:

    Hopefully, that will give your development engineers enough to replicate and/or fix the issue.

  • 0 Arm Employee Badge in reply to KenC

    Hi again Ken,

    Thanks for this information - yes, LM_LICENSE_FILE is searched for a license (as is ARMLMD_LICENSE_FILE).

    I suspect the lack of an Arm DS license therein caused this issue.

    I'll update the development team.

    Hope you can now proceed with the tools.

    Regards, Ronan