Home > Net >  .net core. Using Microsoft Office. Interop. Excel error convert PDF COM components.
.net core. Using Microsoft Office. Interop. Excel error convert PDF COM components.

Time:10-07

Development environment
The.net core 2.1

Server environment
Windows 2012 R2
Office 2016 has activated

I in the local development environment using Microsoft Office. Interop. Excel operation Excel when there is no problem,
Release the modified DCom component attributes on the server, works fine,
But the service to run for a period of time after the DCom components will be an error, said user name password is incorrect or file does not exist,
An error after open the DCom properties, click ok to use, in what all need not modify,

Occasionally bridge abutment before and after the upgrade will appear this problem, sometimes not timing error,

CodePudding user response:

Office was not so used, there are a large number of user interface, you can change without interface Aspose components

CodePudding user response:

reference 1st floor assky124 response:
Office was not so used, there are a large number of user interface, you can change without interface Aspose components such as

Aspose for a fee,

CodePudding user response:

Our company also use Aspose,
Tried a lot before, are not very ideal,

CodePudding user response:

With piracy, first you can make money, buy again, or pay to party a

CodePudding user response:

Retrieving the COM class factory for component with clsids {00024500} - 0000-0000 - C000-000000000046 failed due to the following error: 8000401 a because the configuration identifier is not correct, the system can't start the server process, please check the user name and password, (Exception from HRESULT: 0 x8000401a).

CodePudding user response:

You use the DLL should be cannot apply to the website of the signature, there is a way to circumvent, Selfhost this way provides the API interface

CodePudding user response:

Are you using the.net framework for this problem,
  •  Tags:  
  • C#
  • Related