| Invert |
Allan Hansen
05/16/2017 08:37
Sharpshooter 7.3.1 crash/error message
We released the latest version of our software in the first half of March 2017. We are using Sharpshooter Reports.WPF 7.3.1. Suddenly this week we have heard from approximately 10 of our customers that report generation has stopped working. When they preview the reports, they get this error message in the report viewer (in a black bar at the top of the Report Viewer):
Report processing error
". line: 0 column: 0 The type 'System.Attribute' is defined in an assembly that is not referenced. Add a reference to the assembly 'System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
Have you got any idea what has happened? - We have not changed a single line of our software in the meantime. Could it be related to a Microsoft update?
|
Allan Hansen
05/16/2017 08:38
Sharpshooter 7.3.1 crash/error message
Just to add a little more information: The error occurs with any of our reports, but it is not all customers that experience the issue.
|
Alexander Bub
05/17/2017 00:00
Sharpshooter 7.3.1 crash/error message
Hello Allan,
Unfortunately, we haven't heard from our customers about such issue, but at the moment we were able to find the following information in the web
https://support.microsoft.com/en-us/help/2971005/error-message-when-you-compile-applications-to-target-the-.net-framework-4.5.2
Could you please check whether you are able to solve the problem as specified in the article? Also, please check to make sure the required .NET Framework is present on the PCs where error occurs.
Thank you.
Best regards,
Perpetuum Software Support Team
|
Allan Hansen
05/18/2017 03:50
Sharpshooter 7.3.1 crash/error message
Just for your info, or maybe if you want to test that your software behaves correctly:
We have determined that the problem only occurs on Windows 10 machines that have touch screens, and regular (non-touch screen) Win 10 machines with the on-screen keyboard open, and it started occurring when the machine was upgraded to .net 4.6.2. The error that occurs is a script error in the report script, and it is probably in our own code, but I have not finished debugging it yet. I will keep you posted if I find anything related to your code somehow.
|
Allan Hansen
08/18/2017 03:52
Sharpshooter 7.3.1 crash/error message
An update:
It seems that the error is limited to Windows 10 machines with touch screens (without the Creators update (1703)) and Windows 10 machines WITH the Creators update (with or without touch screens).
It looks like it is caused by a Microsoft update of some kind, occurring in May or June 2017.
In the meantime we have upgraded our software to use .net 4.6, and the combination of .net 4.6 and installing these three Microsoft updates seems to solve the issue, at least for us:
KB4025342 (2017/07 – v1703)
https://support.microsoft.com/da-dk/help/4025342/windows-10-update-kb4025342
https://www.catalog.update.microsoft.com/Search.aspx?q=kb4025342
KB4022405 (2017/06 - v1703)
https://support.microsoft.com/da-dk/help/4022405/servicingstackupdateforwindows10version1703june13-2017
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4022405
KB4022725 (2017/06 – v1703)
https://support.microsoft.com/da-dk/help/4022725/windows-10-update-kb4022725
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4022725
|
Alexander Bub
08/21/2017 04:35
Sharpshooter 7.3.1 crash/error message
Hello Allan,
Thank you for your feedback and the solution description. We will surely try to look into this problem thoroughly.
Best regards,
Perpetuum Software Support Team
|
Allan Hansen
08/24/2017 04:20
Sharpshooter 7.3.1 crash/error message
Unfortunately the error still occurs in certain machines so we would like to have a remote desktop session with you so you can see the error and figure out what goes on.
As far as we can see. the error occurs at the point where your code fires up the Just-in-time compiler to compile the report script.
We have a virtual machine where we can get the error to happen consistently, and we will make sure that the machine has .NET Reflector installed so you can see what is going on.
|
Allan Hansen
08/29/2017 10:19
Sharpshooter 7.3.1 crash/error message
I have not heard from you regarding this issue. We would like very much to get this error sorted as soon as possible. We can offer you to remote control one of our virtual machines where the error occurs so you can see and possibly debug what is going on in your code when the error happens.
|
Alexander Bub
08/30/2017 01:10
Sharpshooter 7.3.1 crash/error message
Hello Allan,
Sorry for the delay in response. We tried to reproduce the issue using latest Windows 10 release with touch screen, but all our attempts were to no avail. Could you please provide us with any sample that can reproduce the problem on our side?
Thank you in advance.
Best regards,
Perpetuum Software Support Team
|
Allan Hansen
08/31/2017 07:57
Sharpshooter 7.3.1 crash/error message
We would very much like to book you for a 20 minute Skype session ASAP so we can show you the problem. Preferably no later than tomorrow.
Currently we have 6.000 users experiencing this issue intermittently and a new release going out in less than two weeks. Having a solution to this problem is crucial.
To save you the time and effort, we would like to show and tell you what we have found out so far. Participating in the meeting will be myself and our CTO.
|
Alexander Bub
09/01/2017 05:40
Sharpshooter 7.3.1 crash/error message
Hello Allan,
Our team is available Monday to Friday, 8:00 AM to 5:00 PM GMT +6. The nearest time we can do online through Skype is on Monday, September 4. Please let us know if it suits you.
Unfortunately, the issue does not seem obvious to us at the moment as we are still unable to reproduce it on our side.
You can send us the online meeting details to [email protected]. This will create a ticket in our support system that will allow tracking the problem details more easily than using the forum.
Thank you for understanding.
Best regards,
Perpetuum Software Support Team
|
Allan Hansen
09/01/2017 05:57
Sharpshooter 7.3.1 crash/error message
I will send you an invitation to a Skype for Business meeting. We are at GMT+2, so if I schedule the meeting to 10.00 here, it will be 14.00 at your place. I will send the invitation to [email protected].
|
ibis xin
04/27/2018 13:24
Sharpshooter 7.3.1 crash/error message
Hi,
I have the same issue. Could you resolve yours? If yes, what's your solution?
Regards
Ibis
|
Allan Hansen
04/30/2018 13:56
Sharpshooter 7.3.1 crash/error message
Perpetuumsoft made a fix for us to use so if you ask them politely, they can probably be persuaded to send you that version. It solved our issue 100%.
|
ibis xin
05/15/2018 16:51
Sharpshooter 7.3.1 crash/error message
Hi,
There is a new Report SharpShooter version (7.4.1.76) available for download on the perpetuum website. I politely asked our support contact whether that version contains the fix for this issue and got the answer: It would be good to download and try if it fixes the issue. Unfortunately reproducing the bug is not as easy in my case. So, could you please have a look at the version of your Report SharpShooter assemblies and let me know?
Kind Regards
Ibis
|
Allan Hansen
05/15/2018 19:06
Sharpshooter 7.3.1 crash/error message
The version we have is 7.4.1.79. But it is only some of the files that have that version number.
I do not know if the fix is implemented in the latest version available for download so I think you should ask Perpetuumsoft, just to be sure.
|
ibis xin
05/16/2018 16:53
Sharpshooter 7.3.1 crash/error message
Hi Allan,
could you provide me your bunch of Report SharpShooter assemblies (or the installer) you received from Perpetuum? I need them to convince Perpetuum.
Maybe you can put them somewhere where I can download from?
Best Regards
Ibis
|
Allan Hansen
09/14/2018 20:07
Sharpshooter 7.3.1 crash/error message
I think the fix must be included in the current 7.4.1 release.
|
Andrew Henry
04/09/2020 22:54
Sharpshooter 7.3.1 crash/error message
This was not fixed in version 7.4.1.76. But it was finally included 2 years later in the 2019 version 7.5. So thanks for posting about this issue since I would have had no idea to check version 7.5 for a fix otherwise.
|