• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 39 subscribers
  • Views 777 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.

Original question:

PSPICE-FOR-TI: PSPICE-FOR-TI install error.

PSPICE-FOR-TI: Installation issues

Timofey Zakamldin
Prodigy 10 points

Part Number: PSPICE-FOR-TI

I can't install PSPICE-FOR-TI: "An Internal error occurred. Please go to http://e2e.ti.com for further assistance. (-1)"

Logfile:

19:39:52 21 апреля 2021 г. : Initializing
19:39:52 21 апреля 2021 г. : Downloading URLs file from : https://pcb.cadence.com/startPages/PSpiceTI_data/TI_URLs.txt
19:39:52 21 апреля 2021 г. : Response Content length = 1724
19:39:52 21 апреля 2021 г. : C:\Users\timz\AppData\Roaming\Cadence\PspiceTIInstall\TI_URLs.txt bytes downloaded = 1724
19:39:52 21 апреля 2021 г. : Reading Json URL File
19:39:52 21 апреля 2021 г. : setting media download server URL from Json File
19:39:52 21 апреля 2021 г. : Reading Json URL File
19:39:52 21 апреля 2021 г. : setting Dll path from Json File
19:39:52 21 апреля 2021 г. : Chws URL is: https://cdsplicwc.cadence.com/chws/b2c/v1
19:39:52 21 апреля 2021 г. : DownloadServerPath is: https://software-dl.ti.com/pspice/esd/installer
19:39:52 21 апреля 2021 г. : parameter count = 1
19:39:52 21 апреля 2021 г. : -wrapper
19:39:53 21 апреля 2021 г. : ReleaseVersion in XML: 17.40.006 InstalledVersion on system: 
19:42:14 21 апреля 2021 г. : error_code cdsVblRegisterInstallation: VblInternalError
19:42:14 21 апреля 2021 г. : strErrorMsgDesc: An Internal error occurred. Please go to http://e2e.ti.com for further assistance. (-1)

  • 0
    TI__Mastermind 37810 points

    Hi Timofey,

    Would you please run these commands in the Windows command window and share the output with us?

    • nslookup software-dl.ti.com
    • nslookup cdsplicwc.cadence.com

    Thanks,
    JC

  • 0 in reply to JC Zhu
    Prodigy 10 points 

    nslookup software-dl.ti.com
Server:  DC1.ab2b.ru
Address:  192.168.134.64

Non-authoritative answer:
Name:     e2888.dscf.akamaiedge.net
Addresses:  2a02:26f0:e2:496::b48
          2a02:26f0:e2:4a4::b48
          2.17.168.76
Aliases:  software-dl.ti.com
          software-dl.ti.com.edgekey.net

    nslookup cdsplicwc.cadence.com
Server:  DC1.ab2b.ru
Address:  192.168.134.64

Non-authoritative answer:
Name:     cdsplicwc.cadence.com
Address:  64.207.220.106

  • 0 in reply to Timofey Zakamldin
    TI__Mastermind 37810 points

    Hi Timofey,

    Thanks for the reply.

    we need some extra information. Please follow these steps:

    1) Copy both the files ( VblInstallerTest.exe and cdsvbl.dll in the zip file below) onto some directory on the user’s machine.

    2) Open a Command Prompt and go to the directory where files were copied

    3) Set the environment variable:

    set CDS_LIC_QA_TesT=vbl_qa.log

    4) Invoke "VblInstallerTest.exe <user-product-key>" , replacing <user-product-key> with actual one Product-key is same as what user specifies during installation, e.g. 2ca7c99b-1df1-4651-ab7f-5655b8fdb112

    If crash encountered and "VblInstallerTest.exe has stopped working" error box appears, choose "Close the program"

    Wait until previous command exits. ( may take a few minutes).

    5) Collect vbl_qa.log from current folder

    Collect VBL_minidump_<pid>.dmp if was generated in current folder (can be 60+MB in size) 

    Here are the zip file that contains the two files mentioned above:

    cds_VBLfiles.zip

    Thanks,
    JC

  • 0 in reply to JC Zhu
    Prodigy 10 points

    Fullscreen vbl_qa.log Download 
    04/22/2021 16:26:19 (pid-13156-13180): (vbl) Register installation called with: key=<removed> bundle=TI_PSpice_174 url=https://cdsplicwc.cadence.com/chws/b2c/v1
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Get hw addresses called with upOnly=False
04/22/2021 16:26:19 (pid-13156-13180): (mfp) HW addresses:
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Checking: mac=309c23a2d1a7 addlen=6 type=6 status=1 len=448 index=7 flags=1c5 connType=1 tunType=0 name={277E4E05-6093-405D-953A-727DBB9E5168}
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Friendly name: Ethernet
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Setting as primary
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Checking: mac=ff49f8a9e5 addlen=6 type=6 status=2 len=448 index=12 flags=1c5 connType=1 tunType=0 name={49F8A9E5-1490-4BEC-AC4E-C19903F4BD5F}
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Friendly name: Ethernet 2
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Checking: mac=0 addlen=0 type=24 status=1 len=448 index=1 flags=181 connType=1 tunType=0 name={846EE342-7039-11DE-9D20-806E6F6E6963}
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Skipping as lookup
04/22/2021 16:26:19 (pid-13156-13180): (mfp) HW addresses end
04/22/2021 16:26:19 (pid-13156-13180): (vbl) After get HW Address: 0
04/22/2021 16:26:19 (pid-13156-13180): (vbl) After hostname: 0
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Getting SMBIOS for type 0...
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Iterating of SMBIOS headers, total length 4754 bytes...
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Checking SMBIOS header at offset 0000000000000000
04/22/2021 16:26:19 (pid-13156-13180): (mfp) SMBIOS header type is 0
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Checking SMBIOS header at offset 0000000000000044
04/22/2021 16:26:19 (pid-13156-13180): (mfp) SMBIOS header type is 1
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated BIOS uuid: 00000000-0000-0000-0000-309C23A2D1A7
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populate count of PCI lines - 21
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Done iterating over SMBIOS headers, stopped at offset 0000000000000044
04/22/2021 16:26:19 (pid-13156-13180): (vbl) After BiosHardDiskInfo: 0
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Getting SMBIOS for type 1...
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Iterating of SMBIOS headers, total length 4754 bytes...
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Checking SMBIOS header at offset 0000000000000000
04/22/2021 16:26:19 (pid-13156-13180): (mfp) SMBIOS header type is 0
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Checking SMBIOS header at offset 0000000000000044
04/22/2021 16:26:19 (pid-13156-13180): (mfp) SMBIOS header type is 1
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated Manufacturer - "Micro-Star International Co., Ltd."
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated serial num - "Default string"
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated product name - "MS-7B24"
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Done iterating over SMBIOS headers, stopped at offset 0000000000000044
04/22/2021 16:26:19 (pid-13156-13180): (vbl) After hardwareInfo: 0
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Reported number of processors: 6
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Queriyng number of physical cores...
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated number of physical cores - 6
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Calculated threads per core: 1
04/22/2021 16:26:19 (pid-13156-13180): (vbl) After cpuInfo: 0
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Reported processor acrhitecture 9
04/22/2021 16:26:19 (pid-13156-13180): (vbl) After OSInfo: 0
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Iterating over physical drives...
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated physical disk "\\.\PhysicalDrive0" serial number: "182040801471"
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated physical disk "\\.\PhysicalDrive1" serial number: "     WD-WCC6Y3RFKX0C"
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated physical disk "\\.\PhysicalDrive2" serial number: "S3CKNWBHB99208F"
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Populated physical disk "\\.\PhysicalDrive3" serial number: "0025_385A_01B2_B250."
04/22/2021 16:26:19 (pid-13156-13180): (mfp) Done iterating over physical drives
04/22/2021 16:26:19 (pid-13156-13180): (vbl) After hard disk info: 0
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Setting LastErrCode: 0
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Sending request: /createToken/
04/22/2021 16:26:19 (pid-13156-4316): (vbl) Error getting response: (-2146892986) WinHttpSendRequest: 2148074310: Предоставленные клиентские привязки SSPI-канала некорректны. (Client's supplied SSPI channel bindings were incorrect.)


04/22/2021 16:26:19 (pid-13156-13180): (vbl) Send request for createToken/ reported error 500
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Mapping HttpResponseCodes 500 to cdsVbliErrCode -1
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Setting LastErrCode: -1
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Setting LastErrCode: -1
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Register installation finished with -1
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Mapping cdsVbliErrCode -1 to cdsVblErrCode -1
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Request license called with: bundle=TI_PSpice_174
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Error getting registry value size for key T - error 2
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Setting LastErrCode: -54
04/22/2021 16:26:19 (pid-13156-13180): (vbl) After get token from registry: -14
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Setting LastErrCode: -14
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Request license finished with -14
04/22/2021 16:26:19 (pid-13156-13180): (vbl) Mapping cdsVbliErrCode -14 to cdsVblErrCode -1
04/22/2021 16:29:19 (pid-13156-13180): (vbl) Download license called with: bundle=TI_PSpice_174
04/22/2021 16:29:19 (pid-13156-13180): (vbl) Error getting registry value size for key T - error 2
04/22/2021 16:29:19 (pid-13156-13180): (vbl) Setting LastErrCode: -54
04/22/2021 16:29:19 (pid-13156-13180): (vbl) After get token from registry: -14
04/22/2021 16:29:19 (pid-13156-13180): (vbl) Setting LastErrCode: -14
04/22/2021 16:29:19 (pid-13156-13180): (vbl) Download license finished with -14
04/22/2021 16:29:19 (pid-13156-13180): (vbl) Mapping cdsVbliErrCode -14 to cdsVblErrCode -1

  • 0 in reply to Timofey Zakamldin
    TI__Mastermind 37810 points

    Hi Timofey,

    Sorry, did you get the VBL_minidump_<pid>.dmp file (step 5)?

    Thanks,

    JC

  • 0 in reply to JC Zhu
    Prodigy 10 points

    No minidump files were created.

  • 0 in reply to Timofey Zakamldin
    TI__Mastermind 37810 points

    Hi Timofey,

    Thanks. The developers are reviewing the log file and we'll let you know if there's anything else we need.

    Regards,

    JC

  • 0 in reply to JC Zhu
    TI__Mastermind 37810 points

    Hi Timofey,

    Nothing to report yet. This is being reviewed by the developers. We'll ask for an update late this week.

    Thanks,
    JC

  • +1 in reply to JC Zhu
    TI__Mastermind 37810 points

    Hi Timofey,

    Would you mind sharing the email you used for requesting PSpice for TI? you can send it via private message. We need to check the server log. 

    Thanks,
    JC

  • 0 in reply to JC Zhu
    TI__Mastermind 37810 points

    Hi Timofey,

    Per your confirmation, I am marking this as resolved.

    Thanks for choosing PSpice for TI, Happy simulating!

    -JC