Stats

  • Locked Locked
  • Replies 8
  • Subscribers 168
  • Views 37691
  • Members are here 0
More Content
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

OrCAD Capture crashes on start up

mwaskett

Hi All,

I'm having trouble with OrCAD capture v16.6 (latest hotfix), in which the program refuses to open without crashing instantly. I'm not getting any error messages, it just freezes when I open it and doesn't respond. It will not close unless I end the task from task manager. This started happening a couple of days ago, but no new programs have been installed recently so it can't be that that's causing it. I've uninstalled any updates that have been installed since it started happening as well.

I'm using Windows 8.1, and I've been able to use the program fine up until a couple of days ago.

Any ideas on why this is happening, and what I can do to fix it?

Thanks 

  • oldmouldy

    Sounds like you have a lock up, rather than a crash, but nonetheless, you probably have a corrupted CaptureWorkSpace in the registry. Close any running Captureprocesses, start Regedit.exe, search for the application, or locate the tile, accept running with elevated rights, locate the key:

    HKEY_CURRENT_USER\Software\OrCAD\CaptureWorkSpace

    by expanding the registry entries, select the key and right-click>Delete, accept delete of this key and all subkeys, close regedit and restart Capture. If Capture still fails to start correctly, Capture.ini may be corrupted, again, close any running Capture sessions, locate this file, default location is %HOME%\cdssetup\OrCAD_Capture\16.6.0 and delete it. (Default for %HOME% is C:\SPB_Data). Then try starting Capture again, you will need to restore any library and preference settings after deleting the Capture.ini file.

  • mwaskett
    Thanks oldmouldy, seems to have fixed the problem! Deleting the registry key was enough to get it working again. Thanks for your help
  • Wild

    I have an open ticket on this since 8/2012

    From Support on 1/7/2013

    "CCR#1050230 associated with SR# 42991072 is still in Planned state, means it was not fixed in current ISR."

    I need to do the registry hack on 4 different boxes about once every 2 - 3 months.

    Note: There are 12 enteries on this ticket number in the support site.

  • Haui

    I´ve a similar Problem.  First of all am a beginner on Orcad. I started with a demoversion 16.0 an have now upgraded to 16.6. Just one start was OK but after a reboot the program hangs. I did the above procedure in the registry and deleted the capture.ini.  Even the reinstallation of the 16.0 version is not working anymore. I got no error message - the program just hangs. Has someone any further idea how to fix the problem?

  • Wild

     

    From: Atish Mukhopadhayay [ACST_mbox@cadence.com]

    Sent: To:

    Cc: Subject:


    Monday, May 14, 2012 2:48 AM

    Update 42911098 Hangs at launch

    Hello Wild

    My name is Atish from SPB Customer Support and I will be working with you on SR 42911098 Hangs at launch.

    Based on the information you provided in the SR, it is my understanding that you are unable to invoke capture. It hangs while getting invoked. Please try the following
    1. Go to task manager and see if any cadence process (capture.exe, cdsMsgServer.exe, cdsNameServer.exe) is running. If so please kill it manually.

     

    1. Now delete the capture workspace from registry. For this
      1. Go to Start > Type regedit. This opens registry editor
        1. Now locate and delete 16.3 or 16.5 (The version that has being installed ) key located at HKEY_CURRENT_USER\Software\OrCAD\CaptureWorkSpace\16.3.0

    NOTE: Be very careful while editing registries. It is recommended to keep a copy of system registries before editing it.

    1. Change your PATH variable as follows,
    2. Right click My Computer > Properties > Advanced. This will open “System Properties” dialogue box.
      1. Locate PATH in system variable and change its name to “PATH_ORG”
      2. Again click on NEW in System variable section and make a new variable of name “PATH” and assign it the value as explained below.
      3. Copy the old PATH variable to notepad and see that it has paths(pointer) to various programs installed on your system. Our target to place the Cadence pointer at beginning. For this you can modify the variable as follows, In this new value Cadence pointer will at beginning which I have placed below. You need copy other pointers(excluding cadence pointers) after the Cadence pointer. Your PATH Variable will be as,

    ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

    %CDSROOT%\tools\bin;%CDSROOT%\tools\libutil\bin;%CDSROOT%\tools\fet\bin;%CDSROOT%\tools\pcb\bin;%CDSROOT%\tools\specctra\bin;%CDSROOT%\tools\PSpice;%CDSROOT%\tools\PSpice\Library;%CDSROOT%\tools\Capture;%CDSROOT%\OpenAc cess\bin\win32\opt;<rest of the path in your old variable>

    ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

    If you face any problem changing PATH, send us the file (env.txt) as explained below. We will change the PATH and send it back to you.

    ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

    Go to Start >> Run >> Type "cmd" >> Type "Set > c:\env.txt". This command will create env.txt file in C drive, send me that file. If you don't have C drive or there is any permission issue then try on other existing drive (D:\,E:\,...)

    ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

    1. Now use Cadence Switch Release to select 16.3 or 16.5. (if you have multiple versions installed)
    2. Now try to invoke capture and see if it helps

    If you consider this issue resolved based on the information I’ve shared, no further communication is required on your part. If I don’t hear from you within a week, I’ll wrap things up but will keep a record of everything in case we need to work on it in the future.

    Thank you for contacting Cadence Support. Regards

    Atish

    On behalf of Capture CIS team

    ----------------------------------------------------------------------------

    Deleting the key as instructed resolves my issue.  This has continued to plague me about 1 - 2 times a month since may of 2012.  I believe that Cadence has not and will not resolve this issue.

    Regards,

    Wildwpe

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.