AutoCAD 2016 mc3.dll / mc3d.dllARX Command Error

AutoCAD 2016 mc3.dll / mc3d.dllARX Command Error

Anonymous
Not applicable
25,715 Views
94 Replies
Message 1 of 95

AutoCAD 2016 mc3.dll / mc3d.dllARX Command Error

Anonymous
Not applicable
Upon opening a drawing in AutoCAD Architecture 2016 I get the error Exception in mc3.dll / mc3d.dll ARX Command. Unhandled Exception C0000005 (Access Violation Reading 0x0000) at Address C9C860F4h I am running windows 7 and Autocad is completely up to date. This randomly started happening after windows forced close the application to restart
Accepted solutions (3)
25,716 Views
94 Replies
Replies (94)
Message 61 of 95

Anonymous
Not applicable

Thanks for that solution.  We had the same issue here and that simple check box fixed the problem.  

0 Likes
Message 62 of 95

Victoria.Studley
Autodesk
Autodesk
Accepted solution

Hi @Anonymous,

 

Here is what happened:

 

An XML file for the Desktop Analytics Program (DAP) was updated, and an error in the file causes this crash to occur. The file on our server has now been replaced by a version that will not cause the program to crash. (I tested this myself this afternoon to confirm, before posting here.)

 

The simplest workaround for affected machines in this:

1. Open a Windows Explorer and navigate to the location C:\Users\<USERNAME>\AppData\Roaming\Autodesk\BLDSYS\2016\{5783F2D7-F006-0409-2102-0060B0CE6BBA}\7.8.106.0\MC3

2. Delete the file called WHITELIST.XML.

3. Reboot the affected machine.

4. Launch the affected AutoCAD program.

5. The working version of the WHITELIST.XML file will download to the location listed above, and the program should now function normally.

 

Here is a screenshot of the location for the file in question, for clarityDAP_Whitelist.png:

 


Victoria Studley
Principal Experience Designer - Fusion Configurations
Join us in the Fusion Insider Program
Fusion Learn & Support | Fusion Documentation
Message 63 of 95

Anonymous
Not applicable
The WHITELIST.XML file can be found in multiple folders under C:\Users\<USERNAME>\AppData\Roaming\Autodesk\ , not necessarily just in BLDSYS folder.
0 Likes
Message 64 of 95

Anonymous
Not applicable

Victoria, should we delete all instances of the "whitelist.xml" file? 

0 Likes
Message 65 of 95

zalant
Autodesk Support
Autodesk Support

Only the one in the BLDSYS folder affects AutoCAD MEP and Architecture. That's the one to delete. Also, if you had previously (today) disabled the Desktop Analytics feature, you need to re-enable it for the new XML file to be pulled down. Otherwise, if the feature is still disabled, the new XML file won't be pulled down, but you also won't be crashing.



Zac Travis
Message 66 of 95

dbroad
Mentor
Mentor

Thanks for the fix but I must say that it is unbelievably bad design for a file in an Autodesk server whose sole purpose is to assess user usage patterns to cause widespread crashes like this. Whatever is internal to AutoCAD that makes this kind of devastating fault should be remedied as #1 priority and a hotfix issued ASAP.

 

A potential hacker could exploit this weakness again.

Architect, Registered NC, VA, SC, & GA.
Message 67 of 95

mknx
Advocate
Advocate
I followed the instructions from VStudley in post #64 and as long as the whitelist.xml file was not there everything was working fine. A few minutes ago the file appeared again and AutoCAD 2016 was crashing again. Either the file is still corrupt or just deleting the file alone does not fix the problem. I'm trying now to modify the registry as mentioned in post #54 and i will see if this helps. This is totally frustrating... people should work with AutoCAD, they should not be forced to fix issues by deleting files or edit the registry. There should be a one-time-switch that disables all communications (maybe except for license checking...) and downloads from autodesk without notifying me. BTW: the path for the whitelist file is different for me: C:\Users\< USERNAME >\AppData\Roaming\Autodesk\ARCHDESK\2016\{5783F2D7-F004-0407-2102-0060B0CE6BBA}\7.8.106.0\MC3 On systems without SP1 the version number 7.8.106.0 might be different also.
0 Likes
Message 68 of 95

mknx
Advocate
Advocate
Accepted solution

Looks like we have to remove multiple versions of the xml file and edit the registry... i got this mail from the support:

 

To fix the crash:

 

1. Exit AutoCAD

2. Navigate to the following folder:

C:\Users\<user>\AppData\Roaming\Autodesk\BLDSYS\2016\{5783F2D7-F006-0409-2102-0060B0CE6BBA}\7.8.106.0\MC3

3. Delete the file WHITELIST.XML from this folder.

 

4. Navigate to the following folder:

C:\Users\<user>\AppData\Roaming\Autodesk\BLDSYS\2016\{5783F2D7-F006-0409-2102-0060B0CE6BBA}\7.8.44.0\MC3

5.Delete the file WHITELIST.XML from this folder.

 

Restart the computer.

 

 

If the issue does not resolve, then please try the procedure outlined in the article below:

 

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Error-...

 

 

0 Likes
Message 69 of 95

TSKSoftware
Participant
Participant
Accepted solution

The following batch file will automate the process for 2016 users.

calling from a domain logon script &/or Run as administrator is the most effective method for rapid deployment.

There are a variety of potential folders for the whitelist.xml so I have added just those I know about.

As you will see its easy to add other locations.

 

M

 

@echo off
SET _T=Adjusting AutoCad Dial Home issues to prevent Fatal Errors.
echo %_T%
Title %_T%
echo .
SET _TF=whitelist.xml
SET _TD=%userprofile%\AppData\Roaming\Autodesk\ARCHDESK\2016\{5783F2D7-F004-0409-2102-0060B0CE6BBA}\7.8.44.0\MC3\
If Exist "%_TD%%_TF%" del /F "%_TD%%_TF%" & Echo DELETE %_TF% & SET _RB=1
If NOT Exist "%_TD%%_TF%" echo OK %_TF% Not Present
If Exist "%_TD%%_TF%" explorer "%_TD%" & PAUSE
SET _TD=%userprofile%\AppData\Roaming\Autodesk\ARCHDESK\2016\{5783F2D7-F004-0409-2002-0060B0CE6BBA}\7.8.44.0\MC3\
If Exist "%_TD%%_TF%" del /F "%_TD%%_TF%" & Echo DELETE %_TF% & SET _RB=1
If NOT Exist "%_TD%%_TF%" echo OK %_TF% Not Present
If Exist "%_TD%%_TF%" explorer "%_TD%" & PAUSE
SET _TD=%userprofile%\AppData\Roaming\Autodesk\ARCHDESK\2016\{5783F2D7-F004-0409-2002-0060B0CE6BBA}\7.8.106.0\MC3\
If Exist "%_TD%%_TF%" del /F "%_TD%%_TF%" & Echo DELETE %_TF% & SET _RB=1
If NOT Exist "%_TD%%_TF%" echo OK %_TF% Not Present
If Exist "%_TD%%_TF%" explorer "%_TD%" & PAUSE
echo .
SET RKEY=HKEY_CURRENT_USER\Software\Autodesk\MC3
SET RKOC=ADAOptIn
FOR /F "TOKENS=1-3 DELIMS= " %%A IN ('REG QUERY %RKEY% /v %RKOC%') DO (
 SET RVAL=%%C
)
If '%RVAL% == '0x0 goto :OK
If '%RVAL% == ' goto :OK
reg add  %RKEY% /v %RKOC% /t  REG_DWORD /d 0 /f 2>&1 >NUL
FOR /F "TOKENS=1-3 DELIMS= " %%A IN ('REG QUERY %RKEY% /v %RKOC%') DO (
 SET RVAL=%%C
)
If '%RVAL% == '0x0 echo %RKEY% %RKOC% DWORD=%RVAL% & goto :OK
echo You need to Manually edit %RKEY% %RKOC% to DWORD 0
regedit
PAUSE
:OK
echo .
REM if NOT deployed using Logon Script, include the following.
If NOT '%_RB% == '1 echo DONE & ping /n 5 localhost >nul  & exit
echo PC Will now Re-Start, Close all applicaions before pressing a key to proceed !
pause >nul
shutdown -r -t 10
Message 70 of 95

MWALKOWSKI
Participant
Participant

I don't have that string. But what I did do is search for all MC3.dll and renamed ALL OF THEM with .old. Reboot. And all seems to be OK. I'll keep you posted.

0 Likes
Message 71 of 95

MWALKOWSKI
Participant
Participant
It happened to both on our office.
0 Likes
Message 72 of 95

mknx
Advocate
Advocate
Same here. The issue started yesterday on all machines using AutoCAD Architecture 2016, those using ACA2015 had no issues (yet). The string from the support mail (see Post #68) does also not match for me, maybe this depends on the AutoCAD version (Architecture, MEP...) Since i fixed the registry key from post #54 everything seem to be fine. This was also mentioned by the support (follow the link in post #68).
0 Likes
Message 73 of 95

TSKSoftware
Participant
Participant

I noted that even LT uses the registry key for dial home but does not have the .xml file. Turning off WEB content is generally advisable on so many levels. I would not go deleting any .dll files until sure they will be replaced automatically without a further glitch. You should confirm post re-boot and cad start that the .dll files are returned !

M

0 Likes
Message 74 of 95

Anonymous
Not applicable

Those who made a mc3.dll.bak file

I delete all the Whitelist.xml files from BLDSYS folder and deleted my temporary mc3.dll.

renamed the mc3.dll.bak back to mc3.dll in the main program folder.

Loaded Autocad MEP, unchecked (Yes, I would like to contribute to this program.) from desktop analytics. ok.

and Rechecked back on. ok.

 

Everything on my end is working back to normal.

Thanks everyone!

0 Likes
Message 75 of 95

Anonymous
Not applicable

Autodesk this issue is NOT FULLY RESOLVED.

 

I did the fix yesterday and was relieved that everything went back to normal. 

Logged off last night and bam.... Same problem this morning.

 

Deleting the whielist worked but I hope I dont need to do this every time I log off my computer.

0 Likes
Message 76 of 95

drafting242
Explorer
Explorer

type desktopanalytics in the command line, select and then deselect yes. 

0 Likes
Message 77 of 95

p_pacetti
Observer
Observer
 I'm a teacher and this morning in Italy , in my lab all PCs given these problems . How should we do to solve the problem ?
HELP ME THANKS
0 Likes
Message 78 of 95

garret
Contributor
Contributor

The hotifx does not work. This needs to be addressed by Autodesk immediately. We are completely dead in the water production wise.

 

Yes, the XML files were deleted.

Yes, the computers were rebooted.

Yes, DESKTOPANALYTICS was set to No.

Yes, CUSTOMERINVOLVEMENTPROGRAM was set to No.

Yes, the regkey ADAOptIn is set to 0.

 

Yes, my inbox is full of Autodesk CER's for hotfixes that don't work.

Message 79 of 95

jimmydee
Enthusiast
Enthusiast

Followed the instructions and it appears to work - a first glance...

 

...but then AutoCAD crashes within 5 minutes, with the same error message.

 

Ridiculous!

 

Jim Dee

0 Likes
Message 80 of 95

Anonymous
Not applicable

this did not fix the problem!

0 Likes