Again we are back at ... Removing KB3115455 will resolve this issue. I thought SalesForce fixed this, but appears Microsoft fixed it as well and both solutions are causing the same issue as KB3115262. Can we get these ducks in a row with either one ...
Asked
Active
Viewed 42 times
1
-
4Is this really a different question than End user cannot open a .xls report exported from Salesforce? – Adrian Larson Aug 15 '16 at 15:12
-
1Not really a different question another issue that came out today. Different Windows Update KB3115262 caused the same behavior as we are seeing in KB3115455. Microsoft patched the issues with this update "KB3115455" but with SalesForce developers fixing the issue on their own, Microsoft fixed it as well and appears to cause a "Corrupted" error pop up. So we are back at square one again. I'm letting everyone know that there is an issue again and what Windows Update is responsible for it. I could not reply to that post because I just created an account so was stuck opening another one. – Josh A Aug 15 '16 at 15:20
-
Can you provide steps to reproduce this issue? – AtulRajguru9 Aug 15 '16 at 16:03
-
Currently we have KB3115262 removed from customers computers and with the new update KB3115455 installed as of 8/9/16 update it is producing a "Corrupted" error when running reports in SalesForce. I removed KB3115455 from the system and was able to successfully run the report and open without errors. – Josh A Aug 15 '16 at 16:14
-
Why is this being marked as duplicate. It is not a duplicate issue. With KB3115455 being released its causing a corrupted error when running a report. It spins off of the issue with KB3115262 as specified in the "So Called" duplicate. But, still this issue is a separate from the previous one. I am trying to make others aware of the patch that is causing the "Corrupt" prompt. KB3115262 did not launch an error from Excel and say the file was Corrupt. It simply just did not open the file and you would sit at a blank Excel screen. – Josh A Aug 17 '16 at 14:25