First of all, I would like you to think about the legality of such a thing. Will Adobe let you practically proxy your application online? I see that they have many licenses, so perhaps one of them actually gives you permission to do this (however, there may still be reservations, so I suggest you read about it). Since this is not a question, I will not talk about it anymore, I just wanted to mention it, because it should be important.
Now, for the actual question - if you look at Microsoft Office Interop, Microsoft claims that it is not supported in a server environment. Go to this Microsoft page and read "Server-side Office Automation Issues" in the "More Information" section.
There are several problems if you decide to run a regular client program on the server side, as indicated on the specified page, but one of the most significant problems:
Interaction with the desktop: Office applications assume that they run under the interactive desktop. In some cases, applications may need to make certain automation functions visible to function properly. If an unexpected error occurs or an undefined parameter is required to complete a function, Office is designed to prompt the user with a modal dialog box that asks the user what the user wants to do. A modal dialog box on a non-interactive desktop cannot be rejected. Therefore, this thread stops responding (hangs) indefinitely. While some coding techniques may help reduce the likelihood of this problem, this practice cannot completely prevent the problem. This fact alone makes running Office applications from a server environment dangerous and unsupported.
Although it was written by Microsoft for their product, they are more or less applicable to any regular client application. And even if you decide to go with this approach, as suggested by Neville K, it will be a very resource-intensive task.
Considering the above, I could ask another question in accordance with the fact that "which library or application on the server side is used to perform any actions with images."
source share