topic Re: Crash when I open job after I closed another in Fabrication CADmep Forum

Crash when I open job after I closed another

Anonymous — Fri, 16 Sep 2016 08:52:50 GMT

We are using CAMduct 2016 at our factory and recently I have been encountering some bugs with this product.

First of all, time to time it crashes right after I click to open new job if I just closed another one before. Also it rashes when I click "Manage Database" on welcome/start screen.

At first I thought this might be because of slow disk or locked files but it can do the same even after I waited for about 5 minutes after closing a job.

I would like to point that it doesn't crash when I "close" the job but it does when I "open" after I closed a job.

Re: Crash when I open job after I closed another

markcalloway — Tue, 20 Sep 2016 15:02:29 GMT

@Anonymous

Hi,

Do you get any error messages when it crashes, if you do can you upload a screenshot as someone might recognize the error and may be able to advise.

Also please check what version of Microsoft .Net Framework you have installed on you computer, Fabrication 2016 requires version .Net 4 and I have seen .Net 4.6 cause issues on other 2016 programs like Autocad.

Re: Crash when I open job after I closed another

Anonymous — Wed, 21 Sep 2016 06:25:37 GMT

I will check .NET. Maybe reinstall and try again. Then will update. Thanks.

Salih AK
Okul Sk. No:33
Doğanlar / Bornova / İzmir
Tel: +90-232-4353875
http://www.baremmetal.com.tr/
Açıklama: baremyatay

Açıklama: qrcode

Re: Crash when I open job after I closed another

markcalloway — Fri, 30 Sep 2016 11:32:14 GMT

Hi @Anonymous

How did you get on with this, let us know if you managed to resolve it.

Regards,

Re: Crash when I open job after I closed another

Anonymous — Fri, 30 Sep 2016 12:37:56 GMT

Ahh sorry I forgot to update here because of work.

Just as I got replied, it seems to be related to .NET runtime..

Recently I installed 4.6 as some programs requested but looks like there are some bugs with it.

I uninstalled .NET 4.6 and reinstalled .NET 4 and 4.5.

Then it started to work fine again.