• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 38 subscribers
  • Views 231 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: USER AUTHENTICATION - The application has encountered an internal error condition. err code (-2008)

PSPICE-FOR-TI: This application has encountered an internal error condition.... (-2008)

Armin Burchardt
Prodigy 10 points
Part Number: PSPICE-FOR-TI

Tool/software:

Hi!

During startup of the application I entered Email and AccessKey for User Authentication. Changing a letter in the Access Key clearly produces an error but with the right one,

$SUBJECT happens.

I am not working with a virtual machine, this is a regular Windows 10 installation.

Is there a way to get PSpice running?


BR,
Armin

Powershell command from the related thread:

C:\Users\armin> Get-WmiObject -Class Win32_Bios | Format-List -Property *


PSComputerName                 : ACEPC
Status                         : OK
Name                           : 5.12
Caption                        : 5.12
SMBIOSPresent                  : True
__GENUS                        : 2
__CLASS                        : Win32_BIOS
__SUPERCLASS                   : CIM_BIOSElement
__DYNASTY                      : CIM_ManagedSystemElement
__RELPATH                      : Win32_BIOS.Name="5.12",SoftwareElementID="5.12",SoftwareElementState=3,TargetOperatingSystem=0,Version="ALASKA - 1072009"
__PROPERTY_COUNT               : 31
__DERIVATION                   : {CIM_BIOSElement, CIM_SoftwareElement, CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER                       : ACEPC
__NAMESPACE                    : root\cimv2
__PATH                         : \\ACEPC\root\cimv2:Win32_BIOS.Name="5.12",SoftwareElementID="5.12",SoftwareElementState=3,TargetOperatingSystem=0,Version="ALASKA -
                                 1072009"
BiosCharacteristics            : {7, 11, 12, 15...}
BIOSVersion                    : {ALASKA - 1072009, 5.12, American Megatrends - 5000C}
BuildNumber                    :
CodeSet                        :
CurrentLanguage                :
Description                    : 5.12
EmbeddedControllerMajorVersion : 255
EmbeddedControllerMinorVersion : 255
IdentificationCode             :
InstallableLanguages           :
InstallDate                    :
LanguageEdition                :
ListOfLanguages                :
Manufacturer                   : American Megatrends Inc.
OtherTargetOS                  :
PrimaryBIOS                    : True
ReleaseDate                    : 20200723000000.000000+000
SerialNumber                   : Default string
SMBIOSBIOSVersion              : 5.12
SMBIOSMajorVersion             : 3
SMBIOSMinorVersion             : 0
SoftwareElementID              : 5.12
SoftwareElementState           : 3
SystemBiosMajorVersion         : 5
SystemBiosMinorVersion         : 12
TargetOperatingSystem          : 0
Version                        : ALASKA - 1072009
Scope                          : System.Management.ManagementScope
Path                           : \\ACEPC\root\cimv2:Win32_BIOS.Name="5.12",SoftwareElementID="5.12",SoftwareElementState=3,TargetOperatingSystem=0,Version="ALASKA -
                                 1072009"
Options                        : System.Management.ObjectGetOptions
ClassPath                      : \\ACEPC\root\cimv2:Win32_BIOS
Properties                     : {BiosCharacteristics, BIOSVersion, BuildNumber, Caption...}
SystemProperties               : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers                     : {dynamic, Locale, provider, UUID}
Site                           :
Container                      :

  • 0
    TI__Mastermind 37630 points

    Hi Armin,

    This is weird, do you know why?

    SerialNumber                   : Default string

    You can create a debug file for troubleshooting this.

    1. Create a new environment variable "CDS_LIC_QA_TesT". Set it to something like "C:\Cadence\PSpiceTI\LicLog.txt".
    2. Run the installer and wait for the error message, then share the file "C:\Cadence\PSpiceTI\LicLog.tx".
    3. Delete the environment variable "CDS_LIC_QA_TesT".
    4. share the file LicLog.txt

    Step 3 is important because otherwise that file will grow to enormous size over time. We don't want to cause them problems down the road.

    Thanks,

    JC