<Data>.NET Runtime version 4.0.30319.0 - There was a failure initializing profiling API attach infrastructure. This process will not allow a profiler to attach. RESULT: 0x80004005. Process ID (decimal): 3640. Message ID: [0x2509].</Data>
</EventData>
</Event>
Of course I tried to repair the .Net Framework installation but nothing helps.
Another piece of information, it only happens when I use a roaming account, never on a local account.
I tried to disable all security, firewall, anti-virus, ... always in vain.
And to complicate things, I only have one PC that has the problem: if I use the same user account on another PC, no problem.
Have any of you ever encountered a problem like this?
Be careful, the size of the memory is not everything, there is also the processor.
I suggest you look at the difference in processors between the two machines, laptops are most of the time not able to run SW since the 2014 version as soon as you have a somewhat large number of parts in an assembly.
In addition, solidworks manages the central memory very badly (at all times), or does not manage it at all. This means that if you do a lot of cinematics, for example, it quickly saturates the memory and causes crashes.
I set an independent sound alert from SW and every hour when it is important I close the file as well as SW. Then turn it back on, I am thus quiet for a minimum of an hour.
This does not happen on large assemblies when they are fully static.
I work on an individual microphone that is not connected to a network.
Which version of Windows are you on? If on Windows 10, have you activated the .Net Framework 3.5?
How did you install Solidworks 2017, by migrating from your previous version or by completely uninstalling the old version and then installing the 2017 version? The 0x80004005 error often comes from a problem in the registry following an incomplete uninstall or obsolete keys...
Hello and sorry for the lack of answer, New Year's Eve obliges.
So already best wishes to you and thank you for your answers.
So in order:
The station is not necessarily very recent but it is equipped with 12GB of ddr3 ram, an intel xeon that still runs very well and an ati firepro card. For me it doesn't come from the hardware because when I use a local profile I don't have a crash. And above all the problem appears even when I have just started the pc, without anything else open.
Regarding the installation, unfortunately I was not there when the version was changed but after seeing this problem I uninstalled completely and reinstalled but I still have the problem. I disabled and then reactivated .NET framework, I updated it and everything but nothing helps. Here again, what intrigues me the most is that with a local profile no problem, but with a roaming profile it doesn't work. However, these itinerant profiles work well on other positions...
