Ok Trevor, I posted it right now in the InDesignSDK Forum.
Why? Even though scripting through COM is only used by a minority, it got nothing to do with C++ plugin development.
Have you followed the advice in the other threads on that topic?
Thank you for both links, however sadly our situation did not change.
I tried both links, I registered "Resources for Visual Basic.tlb" successfully (Registration of C:\ProgramData\Adobe\InDesign\Version 10.0\de_DE\Scripting Support\10.1\Resources for Visual Basic.tlb successful)
And I re-Generated the "Resources for Visual Basic.tlb" by launching InDesign as "Run as Administrator":
On our test-computer, we get still the same error message (...CO_E_SERVER_EXEC_FAILURE).
On my local-Computer the situation is also exactly as ever:
- When launching the executable programm, InDesign programmatically opens fine as ever.
- When launching the executable programm as Windows-Service the same error message occurs (...CO_E_SERVER_EXEC_FAILURE). We tried using an Administration-account for the windows-Service, and a local user.
Any new ideas?
There has been another thread about wrong GUIDs being registered by the application.
I think there was one solution to decompile and patch the TLB, but can't find the pointer.
If you search the archives for TLB, DOM, CreateInstance, CLSID and alike there shouldn't be too many hits.
Similar trouble and possible solutions here: