I can't bear the owc of Microsoft. This is the third problem I mentioned yesterday and it has not been solved.

shenmue024

Have you installed the downloaded owc locally? When it is quoted, it is new? The file corresponding to the com in the quote?
In addition, the config file must be copied in the past, because the assembly is written in the config.

六零六

I have done everything
Including re-copying the program, no need to publish

Hey, forget it. If it doesn't work, I can only use my owc10 honestly. It turns out that there is no problem with using owc10, and there is no problem with the server.

shenmue024

If you can use 10, you can use 10 to achieve the function.

zisexiaomao

I am vague to remember where I mentioned that the use of owc requires verification of whether the client has a license or authorization since the certain version.

六零六

The current problem is wrong with owc10 locally, no error on the server
Use owc11 error on the server, owc10 error

What to do, really
A melon problem took me two days, more tired than programming

Does any brother know? ? ?
Solved also convenient for future generations

bastard

To install it.
In addition, if the server is 64-bit, owc can not work, he can only run in a 32-bit process.
Or the reason they said above.

ganglq

Now the problem is wrong with owc10 locally, no error on the server
Use owc11 error on the server, owc10 error
_____________________----
Is there a conflict with the existing on the server, I just make a guess

ganglq

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly'Microsoft.Office.Interop.Owc11, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the specified file.
____________________________________________________________________-
'Microsoft.Office.Interop.Owc11,<---
?

六零六

This problem has not been solved till now, and it caused me to work overtime today

The most annoying thing is the problem of not finding the reason, the time-consuming bottomless hole 　　 :)

德鲁伊

It is recommended to delete it completely, and clean up the information in the registry, restart the machine, and finally copy the DLL to System32 and register it again. Try again in VS...