• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 37 subscribers
  • Views 333 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PSPICE-FOR-TI: About the installation of PSPICE-FOR-TI

user3685858
Prodigy 20 points
Part Number: PSPICE-FOR-TI


Tool/software:

Dear Support Team,

There was a problem with the previous download of the installation package to reinstall, double click EXE icon does not have any response.

So, I downloaded the latest installer from the official website, and it will prompt

"You have reached the concurrent device access limit.

Too many devices are attempting to connect with the same access key."

Please help to deal with this problem, thank you very much.

My e-mail is hanchongxiu@jcdz.cc

Thank you!

  • +1
    TI__Mastermind 37790 points

    Hi, this is in work.

    -JC

  • 0 in reply to JC Zhu
    TI__Mastermind 37790 points

    Hello,

    This is done. Please try installing again.

    THanks,
    JC

  • 0 in reply to JC Zhu
    Prodigy 20 points

    "PSpice for TI" installation was successful, and the program version is 17.40.9.

    However, double-clicking "PSpice for TI.exe" still yields no response. The company's colleagues have ruled out other possible restrictions, but it still cannot be opened normally. Earlier, an attempt was made with version 23.10, and again, there was no response after double-clicking.

  • 0 in reply to user3685858
    TI__Mastermind 37790 points

    Hello, please install the latest version. You can uninstall 17.4, then reboot the system and install the latest. If it still doesn't work, please generate a debug file to help us troubleshoot:

    1. Create a new environment variable "CDS_LIC_QA_TesT". Set it to something like "C:\Cadence\PSpiceTI\LicLog.txt".
    2. Run PSpice for TI, wait for some time, then check if the file "C:\Cadence\PSpiceTI\LicLog.txt" is created.
    3. share the file LicLog.txt
    4. Delete the environment variable "CDS_LIC_QA_TesT".

    Thanks,

    JC

  • 0 in reply to JC Zhu
    Prodigy 20 points

    1.I tried the measures“Create a new environment variable "CDS_LIC_QA_TesT". Set it to something like "C:\Cadence\PSpiceTI\LicLog.txt".
    Run PSpice for TI, wait for some time, then check if the file "C:\Cadence\PSpiceTI\LicLog.txt" is created.”, but no LicLog.txt was automatically created on the C drive.
    2.To further rule out the possibility, I uninstalled Cadence 17.2, fearing that it might have affected PSPICE FOR TI 2023 (the program installation package corresponding to version 17.4). However, this concern was unnecessary.
    3. I reinstalled PSPICE FOR TI 17.4 to the D drive, but still, when I double-clicked it, there was no response. The *.DSN file was not connected either, and the LicLog.txt file was not created either.
    4.I installed Cadence 17.2 on the C drive. When I opened ORCAD_CIS.EXE at this time, I saw that LicLog.txt had been created. The content indeed contained the startup log, indicating that my environment change should have been successful. However, unfortunately, it was not generated by PSPICE FOR TI.
    5.On the computer in my home,Since Cadence 17.2 was installed on drive D and PSPICE FOR TI 2024 was installed on drive C, both programs are functioning properly. I simply copied all the files from the C drive where PSPICE FOR TI2024 was installed to the USB drive, and then brought it to the company computer. When I double-clicked captur.exe, an error message appeared. At least this indicates that it is functioning.

  • 0 in reply to user3685858
    TI__Mastermind 37790 points

    in step 1, is it a location that you have write permission to?

    in step 3, how did you install PSpice for TI 17.4? The only package available online is 24.1. Please always use the latest installer, not the installer saved before. Version of installer does not affect version of the package being installed but may cause issues if it is older than the package.

  • 0 in reply to JC Zhu
    Prodigy 20 points

    1,environment variable

    2, Run as administrator

    3,The antivirus software has been exited and the firewall has been turned off. When preparing to download from the server, the system crashed.

    Fullscreen 2844.LicLog.txt Download 
    07/22/2025 14:48:16 (pid-7488-196): (vbl) Licensing errors/warnings set in product_key flow
07/22/2025 14:48:16 (pid-7488-196): (vbl) User authentication started
07/22/2025 14:48:16 (pid-7488-196): (vbl) VBL version: (23.02-s005)
07/22/2025 14:48:16 (pid-7488-196): (vbl) Endpoint URL is: https://cdsplicwc.cadence.com/chws/b2c/v2
07/22/2025 14:48:16 (pid-7488-196): (vbl) Sending request to: /authenticateUser/
07/22/2025 14:48:16 (pid-7488-196): (vbl) Request X-Request-ID: 5ebc9105-f40e-44e2-bc6d-2917ff4d305e
07/22/2025 14:48:16 (pid-7488-196): (vbl) Server challenge key: 0212583fadb376e61880930ffb408c8622b54ccdf0947470692e63597652a61f6f
07/22/2025 14:48:17 (pid-7488-920): (vbl) Certificate issued to: cdsplicwc.cadence.com
07/22/2025 14:48:17 (pid-7488-920): (vbl) Response REQUEST_CORRELATION_ID: 5ebc9105-f40e-44e2-bc6d-2917ff4d305e
07/22/2025 14:48:17 (pid-7488-920): (vbl) Response CHALLENGE RESPONSE: 00a946855f4324081378e20859a97da9450bacbf63566e7bce029d64f9bb8e1480d1edc132a5f6f2087e265f5ad80da868cd4a5c5e158859aa558f299db7c6168860bf01749e69a6b1c28f7aaa767e128698ea0303a10c16ba72ec8efef3d19ed2f7a5d044534beea07ced06c1cc012da6a08acab8426b7c5a0b759234c0cfc4966292f84edfe118ae436118d57585fcefc3987aac03f901616012e93f72de76bdd96645b676f1bc41c61f85a70d3bc53b53d650aedc133d3ac6f2b5ee200f9cd769443e7d29d303473397cc6613e2e0b25a485a562b2e8b8d3dea86da937892a40da6a14e3a527308a1d61a6a5a8e31c08ca9953b63f9675712d7a5ba7c7f7343cd499ff4b48984c049d43b048efc134a71e950d6e8489bf77274996829ab0c871567e282c6fba96b0d619586a56a829e3abc112a00633d8e8b365f9e9b82d065d1a552dcb8da3da0a28108e9086b32
07/22/2025 14:48:17 (pid-7488-196): (vbl) Successfully received reply for authenticateUser/
07/22/2025 14:48:17 (pid-7488-196): (vbl) Successfully parsed reply for authenticateUser/
07/22/2025 14:48:17 (pid-7488-196): (vbl) Mapping Chws Error code: (0) to Vbl Internal Error code: (0).
07/22/2025 14:48:17 (pid-7488-196): (vbl) Setting ChwsLastErrCode: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) AuthenticateUser response has returned code: <0> and message: ""
07/22/2025 14:48:17 (pid-7488-196): (vbl) SessionID: Z0FBQUFBQm9melF0d3QwX083d1RTdWhmdDRBWW5BNjloMkRDRmJGTXlxcVZyZzh0YWFGcVhfM3M5TS1JOFh4VG03MHBmcTFrRWtrdzJtTXFTa2RmS3QyUWp1LU83Q3ZPVHhrWW1uTkNCeVIxY3AxQXN6aUF4ZGRPU2JCcDBKWjNvVkswWW9ydVVCYV8=
07/22/2025 14:48:17 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) User authentication finished with 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) Register installation called with bundle name: TI_PSpice_231
07/22/2025 14:48:17 (pid-7488-196): (vbl) Licensing errors/warnings set in product_key flow
07/22/2025 14:48:17 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) Getting LastErrCode: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) Deleting all the values for the key: "Software\Cadence\Client\TI_PSpice_231". Total values to delete: 6
07/22/2025 14:48:17 (pid-7488-196): (vbl) Value <Token> has been deleted successfully.
07/22/2025 14:48:17 (pid-7488-196): (vbl) Value <ChwsUrl> has been deleted successfully.
07/22/2025 14:48:17 (pid-7488-196): (vbl) Value <LicenseFilePath> has been deleted successfully.
07/22/2025 14:48:17 (pid-7488-196): (vbl) Value <Vlt_k> has been deleted successfully.
07/22/2025 14:48:17 (pid-7488-196): (vbl) Value <Vlt> has been deleted successfully.
07/22/2025 14:48:17 (pid-7488-196): (vbl) Value <user_configuration> has been deleted successfully.
07/22/2025 14:48:17 (pid-7488-196): (mfp) MFP version: (22.01-d007)
07/22/2025 14:48:17 (pid-7488-196): (mfp) Get hw addresses called with upOnly=False
07/22/2025 14:48:17 (pid-7488-196): (mfp) HW addresses:
07/22/2025 14:48:17 (pid-7488-196): (mfp) Checking: mac=d8bbc119318b addlen=6 type=6 status=1 len=448 index=14 flags=1c5 connType=1 tunType=0 name={BB4E033A-D9E9-402F-9597-EA1AEF9FA989}
07/22/2025 14:48:17 (pid-7488-196): (mfp) Friendly name: 以太网
07/22/2025 14:48:17 (pid-7488-196): (mfp) Checking: mac=0 addlen=0 type=24 status=1 len=448 index=1 flags=181 connType=1 tunType=0 name={14B86C9F-F5EF-11EC-9CF6-806E6F6E6963}
07/22/2025 14:48:17 (pid-7488-196): (mfp) Skipping as lookup
07/22/2025 14:48:17 (pid-7488-196): (mfp) HW addresses end
07/22/2025 14:48:17 (pid-7488-196): (mfp) No primary adapter was found, setting as first non-skipped one
07/22/2025 14:48:17 (pid-7488-196): (vbl) After get HW Address: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) After hostname: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) Populated hostname: DESKTOP-OKCJK7R
07/22/2025 14:48:17 (pid-7488-196): (mfp) Getting SMBIOS for type 0...
07/22/2025 14:48:17 (pid-7488-196): (mfp) Iterating of SMBIOS headers, total length 6053 bytes...
07/22/2025 14:48:17 (pid-7488-196): (mfp) Checking SMBIOS header at offset 0000000000000000
07/22/2025 14:48:17 (pid-7488-196): (mfp) SMBIOS header type is 0
07/22/2025 14:48:17 (pid-7488-196): (mfp) Checking SMBIOS header at offset 0000000000000053
07/22/2025 14:48:17 (pid-7488-196): (mfp) SMBIOS header type is 1
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populated BIOS uuid: 9BBEA584-4847-190A-ADA4-D8BBC119318B
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populate count of PCI lines - 16
07/22/2025 14:48:17 (pid-7488-196): (mfp) Done iterating over SMBIOS headers, stopped at offset 0000000000000053
07/22/2025 14:48:17 (pid-7488-196): (vbl) After BiosHardDiskInfo: 0
07/22/2025 14:48:17 (pid-7488-196): (mfp) Getting SMBIOS for type 1...
07/22/2025 14:48:17 (pid-7488-196): (mfp) Iterating of SMBIOS headers, total length 6053 bytes...
07/22/2025 14:48:17 (pid-7488-196): (mfp) Checking SMBIOS header at offset 0000000000000000
07/22/2025 14:48:17 (pid-7488-196): (mfp) SMBIOS header type is 0
07/22/2025 14:48:17 (pid-7488-196): (mfp) Checking SMBIOS header at offset 0000000000000053
07/22/2025 14:48:17 (pid-7488-196): (mfp) SMBIOS header type is 1
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populated Manufacturer - "Micro-Star International Co., Ltd."
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populated serial num - "Default string"
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populated product name - "MS-7D11"
07/22/2025 14:48:17 (pid-7488-196): (mfp) Done iterating over SMBIOS headers, stopped at offset 0000000000000053
07/22/2025 14:48:17 (pid-7488-196): (vbl) After hardwareInfo: 0
07/22/2025 14:48:17 (pid-7488-196): (mfp) Reported number of processors: 16
07/22/2025 14:48:17 (pid-7488-196): (mfp) Querying number of physical cores...
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populated number of physical cores - 8
07/22/2025 14:48:17 (pid-7488-196): (mfp) Calculated threads per core: 2
07/22/2025 14:48:17 (pid-7488-196): (vbl) After cpuInfo: 0
07/22/2025 14:48:17 (pid-7488-196): (mfp) Reported processor architecture 9
07/22/2025 14:48:17 (pid-7488-196): (vbl) After OSInfo: 0
07/22/2025 14:48:17 (pid-7488-196): (mfp) Iterating over physical drives...
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populated physical disk "\\.\PhysicalDrive0" serial number: "0000_0000_0100_0000_E4D2_5C6B_40B4_5101."
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populated physical disk "\\.\PhysicalDrive1" serial number: "            WK30E1D2"
07/22/2025 14:48:17 (pid-7488-196): (mfp) Populated physical disk "\\.\PhysicalDrive2" serial number: "201906270000030000"
07/22/2025 14:48:17 (pid-7488-196): (mfp) Done iterating over physical drives
07/22/2025 14:48:17 (pid-7488-196): (vbl) After hard disk info: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:17 (pid-7488-196): (vbl) Endpoint URL is: https://cdsplicwc.cadence.com/chws/b2c/v2
07/22/2025 14:48:17 (pid-7488-196): (vbl) Sending request to: /createToken/
07/22/2025 14:48:17 (pid-7488-196): (vbl) Request X-Request-ID: b17d487f-d3e5-422f-bad6-a7de42614a53
07/22/2025 14:48:17 (pid-7488-196): (vbl) Server challenge key: 020e1b2d66103c98740add3115e890f505eacac3ebd8ce43528ccc4f65de781d57
07/22/2025 14:48:17 (pid-7488-920): (vbl) Certificate issued to: cdsplicwc.cadence.com
07/22/2025 14:48:18 (pid-7488-920): (vbl) Response REQUEST_CORRELATION_ID: b17d487f-d3e5-422f-bad6-a7de42614a53
07/22/2025 14:48:18 (pid-7488-920): (vbl) Response CHALLENGE RESPONSE: 151e20c61fdf94e6d004b5c1e5a7b9068b0acb7b03da086a9b5bf99f091b7c713e1d69a87990b3099f2f5392e029205f6425c6642c3bcd7f351125f4e8cc68d61ca23a3c9f529bf4d85340f8392f04a7f29992ad3b95bb894f8e54fca3c1f9c1eda235c687dc6b9e49c48e9c0b23b97561315680267c00ae30d9fc1e99dbdd61aba405c5d58107b9505fab828ed02d64228d20a7670e5fbd5fb168ebc00677cb3b6c22b36e2e793d9b33ed0c9376f33bbfb7ecfa7e85f7fc106f0091d9ad54cdb16efb27c8f3a4ab755c74a21659384eef7b7f3b3cda1d965238656d16d6a87482255c14ef4244be191d61c7e0c4192a2ad3a85ddc60956d0217367167a217f3d9d5507cddcd4f84d5f296ca43eddf69d14639e428b8c7e362736ec263ffb7b49eb30332bbb2dad6a611470491fd6056c67759ebba31fe01f8115a6594e6b8289008cec89e0938362e6240a39cf82f82
07/22/2025 14:48:18 (pid-7488-196): (vbl) Successfully received reply for createToken/
07/22/2025 14:48:18 (pid-7488-196): (vbl) Successfully parsed reply for createToken/
07/22/2025 14:48:18 (pid-7488-196): (vbl) Create token has returned status code: "0", and message: "Success"
07/22/2025 14:48:18 (pid-7488-196): (vbl) Token: CH10Z0FBQUFBQm9melF1cTVnMEM5YVJvUkFfcnBDZEZjSWhwc1VTRWlvc04wMGFIRG5VYV85RkJaZVZZSXptNlpTZV9mMzVqMUFSejlhOHp5TEQ3a25MWHo2aHVrVHJvUjVuV3FmTzNCRkhRZVNNeXQ3dHZLclU1TzRoSkphZEVIWlprQnFPd0FTVENaVWJPaEE1RlAyaERNSzJac19zVVljMXhfcGZDbFpqRjJsS2YtTWFQem1ncEpHMFhiaFZudk9pdE9hUTBQMnZMaXE2U1VTOS1kOUtxNkpTTlVLN3MwNnZYeGs3QWRnMTFpbEo1SXl4MnlrQWZDejhIOFoyXzJXVGFuMlVLU3duaXB3aEhsNEE2LUlGeDc2cnB6dkVtTVhJR2hISFJDaXE0MFNXWkxxRW15aEZReXB3djFBSmJMdXpZaWpkVktqSVVLclUyY0NIX2J3d09vQjJaaWtFMnRjUlVRY0VUTzZpb3pVV0lWRkFBMjdRWFRLZzlYMm9GRURRRnRxMUVIOTBJUlFJeEZZZkpDRU1PNnNhWktTYm54WE95ZEtpZGk1ZlpaemlEcUxaamc3Wjh2Z0g5aWRmRWFXdE1WZ1pPN0oxWGw0MTdId2ROOWxMaDM3Z2JuUENmOUFkdGVCSk9TUGllSmg0aENveHNEZmYyeEV0TXlRLWhEZHZtNU5XTWJXbE1pTlFrYnQwbE5ZalFfQy1pRXgzOVF1bFU1NTRmTG1XVFItOTZ0dWgzQVFHUHNKT3FVUXZic29zYjktR1ZBdkFGOXhEaHhIYzY4VXNQQ2lhZGdhNzlna2FULWpDdGRWeklEOXRKZTc3R1ZDVWIwRnpzVHU0bEt5azJvTG5ZM1lCOVkxODlFXzNlY1FLN213cU9SUTFudTNDM3I2QUJ5Q0QxS1hvanFDOUJxZ1BlUk1zaW45aV9IVFdSME1vdDM4cjVOV3pKaWFZVG9LYUhQYWVZLUptZnJnZWRSTVlUbUhKV1hWRlJBVHdlX0ltRVVkSVlTNGFBb0xIUm5fR0hHX0VRcTYxQzNoQ0prZHNXZzMtemlNbEVMV3UzSWd5WGtBZTVHV3JLRVVlRzBVeHJ5dTRFa0pzU2xXa3VFaV9hVlp2N2xILXNpa1BUQmdZaEZHclRVZnlUeEl6WDRjWjdYT0tHTi1wNGMyNExsSW0yTWFpWkduSl81UkNkcXFTWS1wbGxlNWE1OUJNcXU0X0xLQlB6UmF2TllJd2ZrRlFEMkkzVDYzMVd0eGVKcWZEYjdDVU1JWTQ2VnU3aXI1akFodnVTcy1X
07/22/2025 14:48:18 (pid-7488-196): (vbl) Error: Getting registry value size for a key has failed. Registry key name: Vlt - error code: 2
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: -2089
07/22/2025 14:48:18 (pid-7488-196): (vbl) User has entitlement types: Commercial
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Register installation finished with 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Request license called with bundle name: TI_PSpice_231
07/22/2025 14:48:18 (pid-7488-196): (vbl) After get token from registry: 0
07/22/2025 14:48:18 (pid-7488-196): (mfp) Get hw addresses called with upOnly=False
07/22/2025 14:48:18 (pid-7488-196): (mfp) HW addresses:
07/22/2025 14:48:18 (pid-7488-196): (mfp) Checking: mac=d8bbc119318b addlen=6 type=6 status=1 len=448 index=14 flags=1c5 connType=1 tunType=0 name={BB4E033A-D9E9-402F-9597-EA1AEF9FA989}
07/22/2025 14:48:18 (pid-7488-196): (mfp) Friendly name: 以太网
07/22/2025 14:48:18 (pid-7488-196): (mfp) Checking: mac=0 addlen=0 type=24 status=1 len=448 index=1 flags=181 connType=1 tunType=0 name={14B86C9F-F5EF-11EC-9CF6-806E6F6E6963}
07/22/2025 14:48:18 (pid-7488-196): (mfp) Skipping as lookup
07/22/2025 14:48:18 (pid-7488-196): (mfp) HW addresses end
07/22/2025 14:48:18 (pid-7488-196): (mfp) No primary adapter was found, setting as first non-skipped one
07/22/2025 14:48:18 (pid-7488-196): (vbl) After get HW Address: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) After hostname: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Populated hostname: DESKTOP-OKCJK7R
07/22/2025 14:48:18 (pid-7488-196): (mfp) Getting SMBIOS for type 0...
07/22/2025 14:48:18 (pid-7488-196): (mfp) Iterating of SMBIOS headers, total length 6053 bytes...
07/22/2025 14:48:18 (pid-7488-196): (mfp) Checking SMBIOS header at offset 0000000000000000
07/22/2025 14:48:18 (pid-7488-196): (mfp) SMBIOS header type is 0
07/22/2025 14:48:18 (pid-7488-196): (mfp) Checking SMBIOS header at offset 0000000000000053
07/22/2025 14:48:18 (pid-7488-196): (mfp) SMBIOS header type is 1
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populated BIOS uuid: 9BBEA584-4847-190A-ADA4-D8BBC119318B
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populate count of PCI lines - 16
07/22/2025 14:48:18 (pid-7488-196): (mfp) Done iterating over SMBIOS headers, stopped at offset 0000000000000053
07/22/2025 14:48:18 (pid-7488-196): (vbl) After BiosHardDiskInfo: 0
07/22/2025 14:48:18 (pid-7488-196): (mfp) Getting SMBIOS for type 1...
07/22/2025 14:48:18 (pid-7488-196): (mfp) Iterating of SMBIOS headers, total length 6053 bytes...
07/22/2025 14:48:18 (pid-7488-196): (mfp) Checking SMBIOS header at offset 0000000000000000
07/22/2025 14:48:18 (pid-7488-196): (mfp) SMBIOS header type is 0
07/22/2025 14:48:18 (pid-7488-196): (mfp) Checking SMBIOS header at offset 0000000000000053
07/22/2025 14:48:18 (pid-7488-196): (mfp) SMBIOS header type is 1
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populated Manufacturer - "Micro-Star International Co., Ltd."
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populated serial num - "Default string"
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populated product name - "MS-7D11"
07/22/2025 14:48:18 (pid-7488-196): (mfp) Done iterating over SMBIOS headers, stopped at offset 0000000000000053
07/22/2025 14:48:18 (pid-7488-196): (vbl) After hardwareInfo: 0
07/22/2025 14:48:18 (pid-7488-196): (mfp) Reported number of processors: 16
07/22/2025 14:48:18 (pid-7488-196): (mfp) Querying number of physical cores...
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populated number of physical cores - 8
07/22/2025 14:48:18 (pid-7488-196): (mfp) Calculated threads per core: 2
07/22/2025 14:48:18 (pid-7488-196): (vbl) After cpuInfo: 0
07/22/2025 14:48:18 (pid-7488-196): (mfp) Reported processor architecture 9
07/22/2025 14:48:18 (pid-7488-196): (vbl) After OSInfo: 0
07/22/2025 14:48:18 (pid-7488-196): (mfp) Iterating over physical drives...
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populated physical disk "\\.\PhysicalDrive0" serial number: "0000_0000_0100_0000_E4D2_5C6B_40B4_5101."
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populated physical disk "\\.\PhysicalDrive1" serial number: "            WK30E1D2"
07/22/2025 14:48:18 (pid-7488-196): (mfp) Populated physical disk "\\.\PhysicalDrive2" serial number: "201906270000030000"
07/22/2025 14:48:18 (pid-7488-196): (mfp) Done iterating over physical drives
07/22/2025 14:48:18 (pid-7488-196): (vbl) After hard disk info: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Error: Getting registry value size for a key has failed. Registry key name: server_configuration - error code: 2
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: -2071
07/22/2025 14:48:18 (pid-7488-196): (vbl) Error: Failed to read storage entry. Entry key is: server_configuration
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: -2054
07/22/2025 14:48:18 (pid-7488-196): (vbl) CHWS URL stored in the registry is https://cdsplicwc.cadence.com/chws/b2c/v2
07/22/2025 14:48:18 (pid-7488-196): (vbl) Endpoint URL is: https://cdsplicwc.cadence.com/chws/b2c/v2
07/22/2025 14:48:18 (pid-7488-196): (vbl) Sending request to: /requestLicense/
07/22/2025 14:48:18 (pid-7488-196): (vbl) Request X-Request-ID: ddbfc38d-ed4f-4771-ad38-04cc22c49c99
07/22/2025 14:48:18 (pid-7488-196): (vbl) Server challenge key: 02946a4c1634dcf7b540de5ab1160443b1f39e13aaa153b9422faf066d1797959a
07/22/2025 14:48:18 (pid-7488-25488): (vbl) Certificate issued to: cdsplicwc.cadence.com
07/22/2025 14:48:18 (pid-7488-920): (vbl) Response REQUEST_CORRELATION_ID: ddbfc38d-ed4f-4771-ad38-04cc22c49c99
07/22/2025 14:48:18 (pid-7488-920): (vbl) Response CHALLENGE RESPONSE: 37858f149afeabd59b8a88a60ae6381ff2d9dfbc2c50dcaf0474f76993ab040f152f3ae54b370d2bd35e1091103b80319bb4a4f2235f3a234c7afef120c7339787f97d2505ad477726f0b681762c18c1261678c34c08ff85cf0a1a72abd48a870ea6f5054d973c23bd739f106694ef8c62d44f09f35d99edcd04b42ba0f97a11e1560f5a514c991233e26747799a5fde03092980d82677e07d03889b52fb63547bc8d2f6d6ad6cd10cc344ac562b2175ee9acecf2670ac2bdc69ea8b95649599f83ac4d747bbe1115fc9177dc923e0d8d40ca920466675d0d4881703208875c25ebfc368f1aac2d51a0b87c7184aab6a76e30730e375d817603e583df5232c8ac9d95ef0db6b2845c6b776525d864434d60bcc3e9fd429ac48545fbc6fa01c24e4626edc831d57e24bd0aa0789ad3b7ad6a7ae6784c3e0bd6303388fac857b3b00d66c90a6c7b9057ecc5cbfd58a0511
07/22/2025 14:48:18 (pid-7488-196): (vbl) Successfully received reply for requestLicense/
07/22/2025 14:48:18 (pid-7488-196): (vbl) Successfully parsed reply for requestLicense/
07/22/2025 14:48:18 (pid-7488-196): (vbl) Mapping Chws Error code: (0) to Vbl Internal Error code: (0).
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting ChwsLastErrCode: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) RequestLicense request has returned response code: <0> and message: ""
07/22/2025 14:48:18 (pid-7488-196): (vbl) Token: <empty>
07/22/2025 14:48:18 (pid-7488-196): (vbl) Setting LastErrCode: 0
07/22/2025 14:48:18 (pid-7488-196): (vbl) Request license finished with 0

  • 0 in reply to user3685858
    TI__Mastermind 37790 points

    Are you installing in a virtual machine?

    -JC

  • 0 in reply to JC Zhu
    Prodigy 20 points

    No, it was installed on my local D drive. But why can 17.4 be downloaded and installed (but it doesn't work properly), while 23.10 cannot be installed? Can any issues be seen in the installation log?

  • 0 in reply to user3685858
    TI__Mastermind 37790 points

    Do you have both PSpice for TI 17.4 and 23.10?

  • 0 in reply to JC Zhu
    Prodigy 20 points

    1. No, every time it is uninstalled and then installed. It's just that I can only install 17.4 on this computer. 23.10 fails at the download stage.
    2. Today I got a new laptop that can install 23.10, but unfortunately it still won't boot properly.
    3. My computer only has cadence 17.2 installed, but I also tried to uninstall it and arrange it again without success. Now I can only suspect that there is something wrong with my computer.
    4. Now I have uninstalled cadence17.2 in my laptop and am trying to install 23.10 for the second time.

  • 0 in reply to user3685858
    TI__Mastermind 37790 points

    Are you referring to the version of "PSpice-For-TI_setup.exe"? If so, that is the installer, not the software itself. The installer downloads the software package from the web and currently the package available is 23.1-2024-S001. Please use the latest version of "PSpice-For-TI_setup.exe" to install.

    What's the error message when you try to launch it?