none
Update Windows 1703 RRS feed

  • Question

  • <style type="text/css"><!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } --> </style>

    We have an application developed in .NET 1.1 with Crystal Reports 10 for reporting. This application works well on all Microsoft operating systems, from Windows XP to Windows 10 even if for the later, the .NET 1.1 applications are not longer supported.

    After the last automatic update (“Windows Creators”, 1703) our application reporting does not works anymore. Every time when we try to preview even the simplest report, the application crash and close with a generic error “Setup error - Failed to load resources from resource file. Please check your Setup”. If we dig more, we find out it is a CLR error “violation access” revealed by WinDbg.

    It looks like we have to let the customers operate with the current application version and not to force them to switch to any other new framework, operating system or application.

    Considering that our application is installed on more than 1000 workstations on the clients sites, and that our next upgrade at .NET Framework 4.5 will not be available soon because of the lack of resources, what could be the solution?

    There is not any Vulnerability Assessment Tool installed, we managed to reproduce this on our test machines.

    Thursday, July 6, 2017 11:33 AM

All replies

  • Hi gdragu,

    Thank you for posting here.

    According to your question is more related to Crystal Reports, you could post a  new thread in 

    Crystal Reports forum for suitable support.

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions. 

    Best Regards,

    Wendy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, July 7, 2017 6:54 AM