I'm getting an error when opening a document saying that it can't find the jetreports.xlam file i've confirmed that it's in the correct directory and it's looking in the right one. i've gone to the directory and tried to run it manually. I'm then prompted for a smart card, as we don't use smart cards i've dismissed the prompt and thats when the below messages are created in the eventlog. I'm then prompted to enable macros and then given the document without the jet addon active.
I've enabled logging and no errors seem to be getting logged, i've also tried disabling and re-enabling the addon and this hasn't resolved the issue.
Nothing on the system has changed.
Anyone any ideas?
Application: JetFrontServer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
Stack:
at at.a(System.String[])
Faulting application name: JetFrontServer.exe, version: 11.0.11242.0, time stamp: 0x4e5d7648
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18869, time stamp: 0x556363bc
Exception code: 0xe0434352
Fault offset: 0x0000c42d
Faulting process id: 0x1810
Faulting application start time: 0x01d0caba9b756e0e
Faulting application path: C:\Program Files (x86)\JetReports\JetFrontServer.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: d97cf9ce-36ad-11e5-b507-c0cb38ff8612
Date
Votes
1 comment
-
Jet Reports Historic Posts Hello krismatto,
Does this issue only occur for one specific report?
If so, the quickest resolution may be to simply recreate this report in a new workbook.
If you are opening this report from a network location I would suggest copying the workbook down to a local directory and then opening it from that location.
Re-save the file from the local directory back to the network directory from within Microsoft Excel.
Something else to check in the report is to ensure there are no #REFs in the Excel Formulas ribbon > Name Manager.
Named Ranges that point to other, external workbooks, can sometimes cause this to occur.
You cannot run the "JetReports.xlam" file as it will try to open the file in the Visual Basic for Application Editor.
The coding behind the "JetReports.xlam" is proprietary so it requires a password (or in your case, smart card) to unlock the project.
Communications between NAV and Jet are handled through NAV's C/Front DLL. Typically, the C/Front dll file would reside within Excel's process space to make communications as fast and efficient as possible. With 64-bit Excel, however, C/Front cannot reside inside Excel because C/Front is 32-bit. For this reason, we have to run C/Front in an external process (JetFrontServer).
JetFrontServer and Excel then communicate via a specific channel that is part of Microsoft's .NET Framework.
The additional overhead can slow things down a bit, is subject to the same limitations as any other 32-bit application, and it is possible to exceed the capabilities of the .NET communications channel.
It is for these reasons that (just like Microsoft –> https://technet.microsoft.com/en-us/lib … 81792.aspx) we recommend the 32-bit version of Office for our customers needing to maintain compatibility with 32-bit applications.
If you utilize 32bit Excel/Jet Express and have the appropriate CFRONT.DLL installed (which matches your currently installed NAV executables) via the NAV SDK then JetFrontServer.exe will not be called/utilized.
Best regards,
MWilson
Please sign in to leave a comment.