Share
ReportHello,
Just sharing a support experience that may help others. Today I was trying to assist a partner that in the end find the root cause himself. The scenario was "all end users could not export any page to Excel via CTRL+E using Windows Client with the classic COM Excel Add-In. They could do with no errors, but the sheet stayed empty. The scenario was reported for latest CU Dynamics NAV 2018.
Apart from asking for the obvious troubleshooting steps and the great helpful suggestions various public MVP resources like the ones below, the issue was not resolved.
https://community.dynamics.com/nav/f/34/t/222765
https://community.dynamics.com/nav/f/34/t/222765
https://forum.mibuso.com/discussion/64235/nav-exports-blank-excel
The issue was still not resolved. Fiddler did not help either, especially when running Excel locally on the NST box (like I did in our lab to try to break it myself so that I can try to find root cause). The partner in this scenario did mention a missing SPN caused that issue. When running a four tier environment, SPN's are required:
https://docs.microsoft.com/en-us/dynamics-nav/walkthrough--installing-the-microsoft-dynamics-nav-web-server-components-on-three-computers
However, when only running WIndows Client and a local OnPrem installation of Excel, it would not be my first troubleshooting step, so great catch. Apart from the great suggestions that are out there, we can add one: verify SPN's as they may be required when export to Excel via the classic Excel Add-In in a four tier environment.
Thanks.
*This post is locked for comments
All responses (
Answers (
5
