Stats

Locked Locked
Replies 8
Subscribers 168
Views 37869
Members are here 0

OrCAD Capture crashes on start up

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

Parents

Wild over 10 years ago
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

Go to task manager and see if any cadence process (capture.exe, cdsMsgServer.exe, cdsNameServer.exe) is running. If so please kill it manually.

Now delete the capture workspace from registry. For this

Go to Start > Type regedit. This opens registry editor

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.

Change your PATH variable as follows,

Right click My Computer > Properties > Advanced. This will open “System Properties” dialogue box.

Locate PATH in system variable and change its name to “PATH_ORG”

Again click on NEW in System variable section and make a new variable of name “PATH” and assign it the value as explained below.

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:\,...)

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

Now use Cadence Switch Release to select 16.3 or 16.5. (if you have multiple versions installed)

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
Cancel
Vote Up 0 Vote Down

Cancel

Reply

Wild over 10 years ago
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

Go to task manager and see if any cadence process (capture.exe, cdsMsgServer.exe, cdsNameServer.exe) is running. If so please kill it manually.

Now delete the capture workspace from registry. For this

Go to Start > Type regedit. This opens registry editor

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.

Change your PATH variable as follows,

Right click My Computer > Properties > Advanced. This will open “System Properties” dialogue box.

Locate PATH in system variable and change its name to “PATH_ORG”

Again click on NEW in System variable section and make a new variable of name “PATH” and assign it the value as explained below.

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:\,...)

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

Now use Cadence Switch Release to select 16.3 or 16.5. (if you have multiple versions installed)

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
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

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.