I've tried re-sequencing the application many times, with small variations RE: the optional steps and without the. I've tried to publish the App-V package globally, which works and i receive the package, but the office integrations are still broken (same error).Ĭlient is App-V 5.0 SP3, full server infrastructure minus Reporting server I believe. The sequencer is prepared with locally installed Office 2010 as per our SOE, prior to sequencing (is this required for the integrations to work?). And our target machine's (VDI) have the same version of Office installed locally as well.Īcrobat appears to function just fine by itself.however it's just the "office integrations" that is to say, the plugin in word, that does not work and that is what our users are complaining about.
Instructions: in the "App-V Deployment: Acrobat DC - Enterprise Administration Guide" found here: We have a very minimal amount of customizations applied to the acropro.msi via a transform (.mst) that was generated by the "Adobe Customization Wizard DC" application to disable updates and EULA. there is no "C:\program files\Adobe\Adobe 2015\" as one might expect. What's interesting is the path to the PDFMaker Add-in is simply "\PDFMaker\Office\PDFMOfficeAddin.dll" (without the quotes). A runtime error occurred during the loading of the COM Add-in." We're attempting to, and are so far (after installing the "App-V Kit" provided by Adobe on the target machines that receive this package) the error is:
Has anyone managed to successfully get Office Integration working with Acrobat Pro DC - Classic Track, when the application is being delivered as a (user published) App-V package on App-V 5.0 SP3?
0 kommentar(er)
