Error Copying to Excel

anyac · January 30, 2018, 7:18pm

Has anyone experienced an error when copying a grid to Excel as below. A lot of our users started getting this error about a week ago

lgraham · January 30, 2018, 7:45pm

Yes, I have started getting this recently also.

DCorriera · January 30, 2018, 8:24pm

Yes - our users have been receiving this also. Seems to have started last week

ERPSysAdmin · January 30, 2018, 9:05pm

This, thankfully, has not been an issue for us (yet?) but good to know if it does happen, it has been reported and hopefully a fix will be found for it soon. Thanks @aidacra!

aidacra · January 30, 2018, 10:15pm

QUESTIONS:

Are you using Excel 2016 / O365?
If the users close all instances of Excel before trying to Copy to Excel, is it successful?

If yes to both, then it appears related to a problem Support has submitted to development for further research (PRB0191417 Unable to Copy to Excel).

Mark_Wonsil · January 31, 2018, 4:00pm

Just got an update to Excel here and same:

Yes
Yes

Add us to the PRB list if you like…

Mark W.

Chris_Conn · January 31, 2018, 4:18pm

Same issue with a customer here.

hkeric.wci · January 31, 2018, 4:54pm

I am on Windows 7 with Office 365, no issue yet.

hkeric.wci · January 31, 2018, 4:56pm

Thanks Nathan - if they resolved if, please notify us. No Issues here on Win 7 yet. Community appreciates it =)

tkoch · January 31, 2018, 8:32pm

Same issue here, started early this week/late last week.

markdamen · February 6, 2018, 9:42am

@aidacra UK Support are telling me that it will be fixed in 3.2.xx and that a fix for 10.1.600 won’t be made available because the SCR is P3 and they normally only consider P1/P2 issues.

They also couldn’t see the same pattern that we’re seeing here on the forum, whereby it started a week or so ago for multiple Epicor customers. It came across like it was a bug in the software, that has just been identified and will be fixed.

I am still really intrigued by this issue, and the fact that customisations are crashing as soon as I touch a UD field. Again, same pattern whereby it has worked fine since upgrading to 10.1.600.14 on 16th Dec, but broke all by it’s own during January.

Something has changed IMHO, but I cannot pinpoint what.

Anything you can see from support POV? My case refs are CS00000790841 (PRB0188367) for the customisation issues and CS0000803897 (PRB0191417) for Copy to Excel.

Many Thanks
Mark

pmarques · February 6, 2018, 1:38pm

I just had that issue yesterday. It seems like if any excel window is open I get that error. Closing excel down and trying again worked. On windows 10 with Excel 2016 (O365)

Kimberley · February 6, 2018, 2:19pm

What version of Epicor was this seen on? 10.1.xx or 10.2.xxx?? We are starting our upgrade to 10 and most have windows 10 with O365.

Thanks

Mark_Wonsil · February 6, 2018, 2:26pm

At least in this thread, 10.1.600 and 10.2.100, I think only Win10 so far.

Kimberley · February 6, 2018, 4:00pm

Does it work if you use copy (or copy with headers) and then paste in excel?

aidacra · February 6, 2018, 4:43pm

For the Copy to Excel issue: problem PRB0191417 was accepted by Development and an SCR (software change request) for investigation was issued: SCR 211906.

The investigation is fast-tracked due to the overall user impact. The objective of the investigation is to determine if the root cause is something that we can control, or if it needs to be addressed by another party–MS Office, MS Windows, Infragistics, etc.

Anyone who wishes to keep up-to-date on this SCR, please create a case with Support and ask to have it tied to PRB0191417 if you haven’t done so already.

ERPSysAdmin · February 6, 2018, 5:05pm

Hello,

Just FYI, I was just trying to do some testing of this issue because well, it wasn’t an issue for us…until now. I am running E10.1.600.16 and Excel 2016 on my PC. Microsoft Office has been prompting me to update my version for a while now but I’ve been ignoring it just so I could test this issue.

I’ve had no problems using the Copy to Excel feature from the Epicor 10 client until I installed the latest updates to Microsoft Office. I just applied the update and now I am receiving this when I use Copy to Excel:

So from my testing, it seems to me the update to Office broke my Copy to Excel somehow. I know Epicor is working on this but just wanted to report my findings.

Mark_Wonsil · February 6, 2018, 5:26pm

Exactly what we saw here Heather. Like Epicor, Microsoft wants users to be on the most recent version of the software for easier support and better security reasons. It’s quite possible that this fix is security related. We have a process creating an Excel file in a temp folder which is then opened by the user. A malicious process could add macros to this file - disabled but waiting for an unsuspecting user to enable active content. So there may be another way to perform this task in a safer way. Just throwing out a possibility…

Mark W.

ERPSysAdmin · February 6, 2018, 6:10pm

Very good point @Mark_Wonsil!

Oh my goodness! I don’t know how I ran across this, okay I do, but try testing things long enough and you sometimes stumble into something silly that works! LOL

Okay, try this to temporarily fix the issue…

Click on the Copy to Excel feature in Epicor 10 and then immediately hold down the Alt key on the keyboard. This will prompt you with this dialog box:

Click Yes and your Excel document will open without the error and you might even hear the voice of a thousand angels singing…AAAAAAAHHHHH!!! LOL

ERPSysAdmin · February 6, 2018, 6:30pm

Can I reply to myself?

Anyhoo, I stumbled upon this because I was actually just trying to grab a print screen (using the old school Alt+Print Screen) to show the interesting behavior of my, in this example, ittpg0hg.w0s.xlsx file getting created in the Temp folder initially when you click Copy to Excel.

Now you see it:

And then suddenly it disappears.

Now you don’t:

And then you receive the error:

SO yes it was deleted…but not by me silly Excel.