CODEWITHSUNDEEP
c#ms-wordcom-interop
the_drow
the_drow

Reputation: 19171

COMException (0x800A13E9) - Word interop services

I am getting this stacktrace: 

System.Runtime.InteropServices.COMException (0x800A13E9): Word ðú÷ì ááòéä.
   at Microsoft.Office.Interop.Word.Documents.Add(Object& Template, Object& NewTemplate, Object& DocumentType, Object& Visible)
   at Crm.DocumentGeneration.Printing.DocumentsPrinter.MergeDocuments(ApplicationClass& wordApp, IEnumerable`1 printDataItems, String tempDirectory, String template) in C:\Work\Danel.Nursing\Crm.DocumentGeneration.Printing\DocumentsPrinter.cs:line 249

After googling a bit it seems that COMException (0x800A13E9) is out of memory exception but there is enough memory on the server to launch a spaceship 8192 spaceships.
Here is the function call: 

Document document = wordApp.Documents.Add(ref defaultTemplate, ref missing, ref missing, ref missing);

Nothing is null or invalid with defaultTemplate, I checked.

Upvotes: 9

Views: 12118

Answers (4)

Andrew Faerber
Andrew Faerber

Reputation: 83

Update Microsoft has fixed the issue with an update.
For all who have the issue with the regional format please update your Office to the Version 1902 (Build 11328.20158).
You might need to change to the monthly update channel to get it.

For Windows 10 1809 users the issue might come from the windows regional format settings. It seems that there is an issue when you use a special regional format like "English (Switzerland)". If you change it to "English (UK)" everything works fine. The information about this I have found here

Hope this helps someone who still face the issue.

Upvotes: 0

the_drow
the_drow

Reputation: 19171

Here's the solution I found:

  1. Put a folder called Desktop on C:\Windows\SysWOW64\config\systemprofile (Yes I know. WTF?)
  2. Open Regedit, Go to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppId and edit the two enteries that have a Guid ending with 46. Delete every key they have and add a new key called RunAs with the value of Interactive User

After that, start praying. It doesn't work if you access through a terminal server. Which is kind of a problem for me hehe.

EDIT: The problem with the terminal server was that only an Administrator is allowed to raise COM objects so what you have to do is impersonate to an Administrator.

Upvotes: 10

Dennis G
Dennis G

Reputation: 21778

Sorry 'bout that 1MB reference... I just had to jump on that one.

When automating Office Applications make sure, that you use a local account on the server with permissions for the Word COM+ object as well as the documents you are trying to work on.
There are several posts relating to your problem pointing at the account issue:

Upvotes: 3

Mehmet Aras
Mehmet Aras

Reputation: 5374

Your scenario is NOT supported by Microsoft according to the KB article Considerations for server-side Automation of Office which states that

Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.

The article then goes over alternatives to server-side automation one of which is Open XML. You might want to check this article out if you haven't already done so.

Upvotes: -3

Related Questions