Exceptions while programmatically launching AutoCad2019 on Windows 10 (2024)

When I try to launch the AutoCAD 2019 through console program in Windows 10 through the following codes,

AutoCAD 2019 is failed to start up and reports with the following exceptions.

(.NetFramework : 4.7)

I tried to useacax23enu.tlb andAutodesk.AutoCAD.Interop.dll,

but still, throw the same exception.

Can anyone help me to solve this problem?

Many Thanks.

Code:

try
{ Type acType = Type.GetTypeFromProgID("AutoCAD.Application.23"); acApp = (AcadApplication)Activator.CreateInstance(acType, true);}catch (Exception ex){
// Exception Handling}

Exception Message:

Retrieving the COM class factory for component with CLSID {4AC6DFE1-607B-45B2-B289-D7FBCD44169C} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)).

Report

0Likes

The AcadApplication GUID is the right one for AutoCAD 2019.

There is an interesting article on this error here:https://blogs.msdn.microsoft.com/adioltean/2005/06/24/when-cocreateinstance-returns-0x80080005-co_e_...

I think you have a problem in your AutoCAD installation. A repair or a reinstall can help.

Maxence DELANNOY
Manager
Add-ins development for Autodesk software products
http://wiip.fr

Report

0Likes

Also, read this post:https://forums.autodesk.com/t5/net/error-while-programmatically-launching-autocad/td-p/5555190

Maybe it's linked to the user account running your console program.

Maxence DELANNOY
Manager
Add-ins development for Autodesk software products
http://wiip.fr

Report

0Likes

I have exactly the same problem when I switched my application from Acad2018 to Acad2019.
The problem occurs on Win10 and Win7 systems so I think it's independent from the OS.
Are there any other ideas so solve the issue?

Kind regards,

Jens

Report

0Likes

If your program run as administrator, try to run it with a standard account.

Maxence DELANNOY
Manager
Add-ins development for Autodesk software products
http://wiip.fr

Report

0Likes

the problem is independent from user rights, the problem occurs as administrator and with standard user rights.

Regards,

Jens

Report

0Likes

If you can, try on another computer to check if it is due to a bad configuration on your local machine.

Maxence DELANNOY
Manager
Add-ins development for Autodesk software products
http://wiip.fr

Report

0Likes

Just did a quick verification with one of my computers: Windows 10 Pro, Vanilla AutoCAD 2019. Following simple console app starts AutoCAD successfully:

using System;using Autodesk.AutoCAD.Interop;namespace AutomateAcad2019{ class Program { static void Main(string[] args) { Console.WriteLine("Press R to run AutoCAD, any other key to exit:"); var an = Console.ReadLine(); if (an.ToUpper().StartsWith("R")) { RunAutoCAD(); Console.WriteLine("Press any key to exit:"); Console.ReadLine(); } } private static void RunAutoCAD() { AcadApplication acApp = null; try { Type acType = Type.GetTypeFromProgID("AutoCAD.Application.23"); acApp = (AcadApplication)Activator.CreateInstance(acType, true); acApp.Visible = true; Console.WriteLine("AutoCAD started!"); } catch (Exception ex) { Console.WriteLine("Error" + ex.Message); } } }}

Since the console app is a desktop app, it runs with my login user account, which is local admin. I'd assume if I use a standard user account that was able to run AutoCAD with this computer, the console would also work OK.

So, the problem would not be with the code, rather, the condition under which the EXE app and/or AutoCAD is to run, which, you (and the OP) did not describe at all.

Report

0Likes

Hi Norman,

thank you for the sample code.

With this console app everything works fine.
When I use the same code inside my own application (Autodesk Vault JobProcessor - custom job) I figured out that the line
(AcadApplication)Activator.CreateInstance(acType, true);

starts a non visible DWG TrueView process (dwgviewr.exe) !??

Maybe something is wrong with my Acad2019 Installation, but it's strange, that exactly the same issue occurs on a completely different system.

Kind regards,

Jens

Report

0Likes

Ah OK. This is why the context is important. A custom job for the Vault job processor is executing in a MTA thread (instead of a standard STA thread). This can explain why your call toCreateInstance() is failing.

You can try to replace yourCreateInstance() with a Process.Start() followed by a loop callingMarshal.GetActiveObject(). When AutoCAD will be started,Marshal.GetActiveObject() will return successfully.

In order to use Process.Start(), you need to have the path of acad.exe. You can find it in the registry.

Maxence DELANNOY
Manager
Add-ins development for Autodesk software products
http://wiip.fr

Report

0Likes

With Process.Start() the AutoCAD start works - thank you!
So I have to change the communication with Acad to open a dwg and do some things.

I can't use acApp.Documents.Open and SendCommand(...) any more, I think I have to load a script with Process.Start().

Some work to rebuild the program and I'm still wondering what has changed from Rel. 2018 (Acad+Vault) to Rel.2019.

Kind regards and thanx for your help,

Jens

Report

0Likes

You can, just get the COM server with Marshall.GetActiveObject() (code not tested):

Process process = Process.Start(acadExePath);if (process == null) throw new ApplicationException("AutoCAD can not start.");if (!process.WaitForInputIdle(60 * 1000)) throw new ApplicationException("The AutoCAD process has not finished its initialization in the specified timeout.");AcadApplication acadApp = null;for (int i = 0; i < 60; ++i){
 const uint MK_E_UNAVAILABLE = 0x800401e3; try { acadApp = Marshal.GetActiveObject("AutoCAD.Application"); break; } catch (COMException ex) when ((uint) ex.ErrorCode == MK_E_UNAVAILABLE) { Thread.Sleep(1000); }}// You can use acadApp here

Maxence DELANNOY
Manager
Add-ins development for Autodesk software products
http://wiip.fr

Report

0Likes

Unforunately the line

acadApp = Marshal.GetActiveObject("AutoCAD.Application");

results in an type conversion error?

Report

0Likes

Use "AutoCAD.Application.23" as ProgID to be sure that you're getting the 2019 version.

Maxence DELANNOY
Manager
Add-ins development for Autodesk software products
http://wiip.fr

Report

0Likes

hmm, it's another problem.
The line

acadApp = Marshal.GetActiveObject("AutoCAD.Application.23");

doesn't get compiled because of a type mismatch.

Report

0Likes

C# is strong-typed language. In your code, acadApp is declared as type of "AcadApplication", while Marshal.GetActiveObject() return's type of "object". So, you need to cast the returned object:

// This may raise exception, if the object returned is not AcadApplication

acadApp=(AcadApplication)Marshal.GetActiveObject(...);

or you can

acadApp=Marshal.GetActiveObject(....) as AcadApplication;

if (acadApp!=null)

{

// your are ok to continue...

}

else

{

// Cannot get AcadApplication object...

}

Report

0Likes

OK, thanks for your help.

When I cast the returned object the application gets compiled.

But the result is still the same:
When I run the code from a console app everything works fine.

When I run the code from my Vault job processor extension I can't communicate with AutoCAD

-> Marshal.GetActiveObject(progID) as AutoCAD.AcadApplication; returns null

Report

0Likes