<solved> Sending Mails via Outlook and Excel-Export don't work

FragenFrager
FragenFrager Member Posts: 69
edited 2025-07-07 in NAV Three Tier
Hello,
one of our customers is currently experiencing a problem where data cannot be exported to Excel using a specially customized report. Furthermore, emailing via Outlook isn't working. The Excel-Error is attached.
Both Outlook and Excel are part of an Office 365 installation.
When exporting to Excel, the attached error message appears; when sending an email, a message appears stating that Microsoft Outlook is unavailable.

The Microsoft.Office.Interop.Excel.dll and the Microsoft.Office.Interop.Outlook.dll are located in the directory
C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client
I couldn't determine whether they are disabled/blocked/not allowed.

On one of the affected workstations, an online repair of Office 365 helped; on the other computer, neither this nor a reinstallation of the Navision client helped.

Unfortunately, I can't check on the affected computer whether the corresponding DotNet assembly is found because no development environment is installed there.

Anyone else have any ideas? Otherwise, the only option I can think of is the premium package, which would require a complete reinstallation of the affected computer.

Answers

  • joostheger
    joostheger Member Posts: 12
    I think the problem isn;t BC/NAV. Maybe you can proof this by installing another tool that uses the same entry. Which probable wont work either. That way, you can dump the problem with the system administrators.
    Anything in the windows Logs?
  • FragenFrager
    FragenFrager Member Posts: 69
    Hello joostheger,
    thank you for your reply. What do you mean with another tool that uses the same entry? Have you got an example?
    I watched the Eventlog. Unfortunately, no message is written to it immediately after the crash when using excel or outlook from BC.
  • RockWithNAV
    RockWithNAV Member Posts: 1,172
    As per the error message it seems that some excel components system wanted to use and failed.
    A case .net interop, the easiest solution is to install either excel or the outlook family, missing dll components will be taken care by itself.
    Thanks

    Blog - rockwithnav.wordpress.com/
    Twitter - https://twitter.com/RockwithNav
    Facebook - https://facebook.com/rockwithnav/
  • FragenFrager
    FragenFrager Member Posts: 69
    I reinstalled Office, but the problem still exists. :/
  • joostheger
    joostheger Member Posts: 12
    @FragenFrager Hi, what I meant is, that I think Excel might be the problem. To test this, it would be usefull if you would have another application, that uses the same Excel-dll / the saw method of communication with Excel. And I dont have such an application as an example, unfortunately
    However I do not know the solution, I agree with RockWithNav that the problem seems to be in the installation of Excel or at least not in BC.
  • FragenFrager
    FragenFrager Member Posts: 69
    Thanks. Well, as mentioned, I reinstalled the whole Office on the affected PC, but the problem still exists. However I see that I did not mention that the Navision-Version is 2016. Maybe, it ist not compatible with newer versions of Outlook/Excel?
  • joostheger
    joostheger Member Posts: 12
    on the pc's that are working, do they have an older version of Office, then?
  • FragenFrager
    FragenFrager Member Posts: 69
    Hello joostheger,
    the affected PC was now changed to one where classical outlook could be installed, so it works.
    I'm not sure what will happen if an update into the new outlook will be forced again. The customer claims that he had no chance to prevent the update to the new outlook on the PC where it did not work.
  • joostheger
    joostheger Member Posts: 12
    Glad you fixed it! Preventing an application from auto updating is typically something to discuss with an application manager or system manager. Good luck with it.

Categories