I have done a fresh install of SQL Express 2014 and also Jet Professional 18.4.18186.3 on a Server 2008 R2
everything seems to be fine until i try to upload reports where i get the above error
I have done a fresh install of SQL Express 2014 and also Jet Professional 18.4.18186.3 on a Server 2008 R2
everything seems to be fine until i try to upload reports where i get the above error
Hello Bschaathun,
Please note that an issue was recently identified that is a result of one of the Windows Updates that Microsoft pushed out on July 10th-13th.
Users may receive an error stating that “The type initializer for ‘Jet.Data.JetDataSourceFactory’ threw an exception” when attempting to use a data source from the Web Portal, in any way. This includes running reports, scheduled tasks, and uploading reports from Excel.
This issue affects Windows 10 and Windows Server 2012 environments that host the Jet Service Tier, where the updates have been installed. The applicable updates are:
Windows 10:
KB4338819 (https://support.microsoft.com/en-us/help/4338819/windows-10-update-kb4338819)
Windows Server 2012:
KB4338419 (https://support.microsoft.com/en-us/help/4338419/description-of-the-security-and-quality-rollup-updates-for-net-framewo)
KB4338424 (https://support.microsoft.com/en-us/help/4338424/description-of-the-security-and-quality-rollup-for-net-framework-3-5-s)
We have confirmed, in both cases, that uninstalling these updates fixes the issue, which is the current workaround. We’re currently identifying the cause and working with Microsoft to ensure the problem is resolved as quickly as possible.
Thanks for your patience, and we will keep you updated as we work towards a resolution.
Best regards.
Apologies, meant to say of course I have created a couple of data sources as well connecting to a remote SQL server
Thank you for this question and answer. I have the same problem. I'm looking forward for this issue to be fixed.
Thank you!
Hello all,
The solution currently is to remove the installed Windows Updates.
Cheers,
Hi,
The only solution which worked for me on my Server 2008 R2 environment was to uninstall Jet and Server elements, uninstall .Net 4.7.2
Reinstall Jet Server elements and let it install .Net 4.5
In the process now of setting everything back up (my own fault - i forgot to back up the SQL backend)
P.S. before doing all this i removed any patches and updates applied in the last week which did not fix the issue - the last element of that was .Net 4.7.2
Hello Bschaathun,
I was unsure at which side I needed to remove the updates. Eventually removing the updates on the machine where the Jet Server was installed helped, as Cynthia suggested. For me, the recommended solution/workaround worked. Sure, this has to be fixed, but for now it works for us.
Have you tried to only remove the mentioned updates? Anyway, I guess it works now for you :-)
Is there an estimated date that this issue will be fixed before I start removing updates to the server?
Hello all,
We are working to ensure the problem is resolved as quickly as possible. Currently, there is no ETA on this as of yet. We apologize for any inconvenience.
Cheers,
Just checking to see if a solution has been found for this problem. removing the updates on the server Jet is installed on is not really a viable option for us since it houses other applications. Thanks!
Hi Cynthia,
Do you have the Windows updates KB numbers for Windows Server 2016 ?
Kind regards,
Cristian
Cara -
Microsoft has released a manually-installable update to resolve the issues caused by the July 10th Microsoft Security and Microsoft .NET updates. More information is available in the Jet Online Knowledgebase.
Hello Cristian,
In the linked KB above, you would find the below information. I have highlighted the Windows 2012 Updates.
Cheers,
Hi Cynthia,
As I have Windows Server 2016, I downloaded the corresponding update from the website. When installing it, the install failed.
However I managed to solve the issue by simply adding NETWORK SERVICE to the Administrator Group on the "Local users and Groups" setup! Of course this might not work for everyone, but I'm on a test environment...
I'm installing the latest Windows Updates right now and will let you know if that fixed July Updates bugs!
Kind regards,
Cristian
Applying the patch on my Windows 2016 server fixed the problem on that. It did take an extraordinary amount of time though so patience is required.
As i am in the process of decommissioning the 2008 Server I will leave that alone as it is currently working having reinstalled as per my comments above.
I can confirm as well the August Windows Updates fixed this issue for Win Server 2016.
Thanks for all your help,
Cristian