Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
<solved> Sending Mails via Outlook and Excel-Export don't work
FragenFrager
Member Posts: 63
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.
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.
0
Answers
Anything in the windows Logs?
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.
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.
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/
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.
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.