You’re offline. This is a read only version of the page.
1,632
Currently have a situation where AX is deployed to RD Web and the users can get to the application and run AX but cannot use the Export to Excel functionality. We have tried a few things and have read a ton of blogs, guides, and articles and cannot find the magic check box that will make this work. Any help would be greatly appreciated:
First issue:
When trying to export to excel, the user is prompted to search for an application to use to open the excel document. After selecting Excel, the following message is received: "The operating system is not presently configured to run this application"
Second issue:
Installed Excel on RD Server...
New error "This copy of Microsoft Office 2016 cannot be used on a computer running Terminal Services. To use Office 2016 on a computer running Terminal Services, you must use a Volume License edition of Office."
In the end, we don't want to run Excel in RD Web, we want it to be run locally to the user, so installing Excel on the RD web server is not really the solution we are looking for.
Following the typical outlined steps to run Excel locally to the client session:
1. Installed the client with "Remote Desktop Services integration" enabled
2. Set "Remote desktop session exports to: "Client""
But we still cannot get Excel to open. Thoughts, questions, directions!?!?!?
*This post is locked for comments
I have the same question (0)
Hi,
this exporting to a local Excel using a virtual channel extension normally works like a charme.
There are some prerequisites beside your described points which should be kept in mind.
- It is possible to disable the use of these non standard virtual channel extensions through some policies (but think this isn't the problem)
- The client side rdp extension should be installed under the user which is running the ax. The extension dll is installed in all cases, but some registry entries are created under the HKCU hive (only valid for the current installing user) Did you try to remove remote Desktop Integration and reinstall it - using a slipstreamed Setup DVD with the identical kernel version (matching CU and/or binary fix) within updates path?
maybe some more hints could be found here
https://community.dynamics.com/ax/f/33/p/176869/433207
and
https://community.dynamics.com/ax/f/33/t/162284
sorry no other idea at the moment
regards
Douglas
Share
Report
All responses (
Answers (
