Skip to main content
Question

Problem with exporting to Excel

lazarlubomir
Contributor
Forum|alt.badge.img+7

Hello, unfortunately I have repeatedly problem with exporting to Excel in Workspace. I checked log, there is following message: 2016-11-24 10:05:57| 67.6| 0.2|ERROR |Excel Writer: Failed to save changes to the spreadsheet 'D:\\XXX\\XXX\\XXX\\new.xlsx'. Check that you have write permission to the file, it has no password protection and is not opened by another application. Error message is 'Permission denied.'

It looks, that there is error on Excel side, right? I just want to create new Excel file...

21 replies

david_r
Evangelist
  • david_rEvangelist
  • November 24, 2016

Does the directory already exist? If not, create it manually.

Does the file exist? If yes, try to delete or rename it.

itay
Supporter
Forum|alt.badge.img+16
  • itaySupporter
  • Supporter
  • November 24, 2016

Another tip, check the task manager to see if the xls process is still running.

lazarlubomir
Contributor
Forum|alt.badge.img+7
  • lazarlubomirContributor
  • Author
  • Contributor
  • November 24, 2016
david_r wrote:

Does the directory already exist? If not, create it manually.

Does the file exist? If yes, try to delete or rename it.

Directory exists, there is not a problem. File doesnt exist. And Log still throws the same message...

 

 

lazarlubomir
Contributor
Forum|alt.badge.img+7
  • lazarlubomirContributor
  • Author
  • Contributor
  • November 24, 2016
itay wrote:

Another tip, check the task manager to see if the xls process is still running.

Unfortunately - XLS process is not running and problem is still there...

 

 

david_r
Evangelist
  • david_rEvangelist
  • November 24, 2016

That is a strange error. Have you tried rebooting?

Obligatory:

itay
Supporter
Forum|alt.badge.img+16
  • itaySupporter
  • Supporter
  • November 24, 2016
david_r wrote:

That is a strange error. Have you tried rebooting?

Obligatory:

Yep sounds like the workspace needs restarting since it's holding on to some old definition

 

 

via GIPHY

 

 

lazarlubomir
Contributor
Forum|alt.badge.img+7
  • lazarlubomirContributor
  • Author
  • Contributor
  • November 24, 2016
david_r wrote:

That is a strange error. Have you tried rebooting?

Obligatory:

Even when I reboot workbench, problem is still there :-( I feel little bit hopeless

 

 

david_r
Evangelist
  • david_rEvangelist
  • November 24, 2016
lazarlubomir wrote:
Even when I reboot workbench, problem is still there :-( I feel little bit hopeless

 

 

Try rebooting your pc as well.

 

 

lazarlubomir
Contributor
Forum|alt.badge.img+7
  • lazarlubomirContributor
  • Author
  • Contributor
  • November 24, 2016
david_r wrote:
Try rebooting your pc as well.

 

 

Still the dame problem, even after rebooting my laptop :-(

 

 

david_r
Evangelist
  • david_rEvangelist
  • November 24, 2016
lazarlubomir wrote:
Still the dame problem, even after rebooting my laptop :-(

 

 

Do you have any weird or accented characters in the path or filename? Can you create the file manually using Excel? How about changing or simplifying the filename, does that work?
lazarlubomir
Contributor
Forum|alt.badge.img+7
  • lazarlubomirContributor
  • Author
  • Contributor
  • November 24, 2016

@david_r path is ok, take a look: D:\\projekty_CS\\AC_SK\\dfsda.xlsx. There is no problem with characters or something else. I can create and save Excel (using MS Excel) without problem.

itay
Supporter
Forum|alt.badge.img+16
  • itaySupporter
  • Supporter
  • November 24, 2016
lazarlubomir wrote:

@david_r path is ok, take a look: D:\\projekty_CS\\AC_SK\\dfsda.xlsx. There is no problem with characters or something else. I can create and save Excel (using MS Excel) without problem.

Sounds like a case for Safe support to me.

 

 

fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • November 24, 2016

I'd also suggest writing to CSV in the same place and make sure that works. Please do send in all the info to support@safe.com -- logs and workspaces -- and then we can examine.

pratap
Contributor
Forum|alt.badge.img+11
  • pratapContributor
  • Contributor
  • November 25, 2016

Hi,

Just try in different path and file name.

mark2atsafe
Safer
Forum|alt.badge.img+43
  • mark2atsafeSafer
  • Safer
  • November 25, 2016
pratap wrote:

Hi,

Just try in different path and file name.

That's what I was thinking. Maybe there is a permissions limitation to stop you writing to that directory. Try a different path and see if the error occurs (or write to CSV to the same folder as Dale suggests).

 

Also, are you running this on FME Server or FME Desktop? I'm guessing it's not Server, but if it was then that's a likely place to check too.

 

gmbutler2
Contributor
Forum|alt.badge.img+10
  • gmbutler2Contributor
  • Contributor
  • November 28, 2016

I have had this issue before as well. I have found that sometimes it won't overwrite the existing file if there is one. Also, I have seen this error pop up if you have excel open (not the specific file you are saving but excel itself). I either do one of the following.

1. You may have the file you are trying to save open. Close it and try again.

2. This sometimes occurs if the Microsoft Excel program is open. Close all instances of Microsoft Excel and try again.

3. If you are trying to overwrite a file and it is not open, try deleting or renaming the original export through windows explorer and try exporting the data again.

lazarlubomir
Contributor
Forum|alt.badge.img+7
  • lazarlubomirContributor
  • Author
  • Contributor
  • November 29, 2016
gmbutler2 wrote:

I have had this issue before as well. I have found that sometimes it won't overwrite the existing file if there is one. Also, I have seen this error pop up if you have excel open (not the specific file you are saving but excel itself). I either do one of the following.

1. You may have the file you are trying to save open. Close it and try again.

2. This sometimes occurs if the Microsoft Excel program is open. Close all instances of Microsoft Excel and try again.

3. If you are trying to overwrite a file and it is not open, try deleting or renaming the original export through windows explorer and try exporting the data again.

@gmbutler2 Thank You for tip! Problem is probably on my OS in laptop... Even if I try use your tricks, it fails... Anyway, I use exporting to CSV file and then I open it in Excel and save in xls.

 

lazarlubomir
Contributor
Forum|alt.badge.img+7
  • lazarlubomirContributor
  • Author
  • Contributor
  • November 29, 2016
fmelizard wrote:

I'd also suggest writing to CSV in the same place and make sure that works. Please do send in all the info to support@safe.com -- logs and workspaces -- and then we can examine.

@daleatsafe I have contacted my supplier of FME and we will try to solve this problem :-)

 

gio
Contributor
Forum|alt.badge.img+15
  • gioContributor
  • Contributor
  • December 1, 2016

not writing tabs with spaces in tabnames? (feature_type) that will cause write-fail.

pmt
Contributor
Forum|alt.badge.img+3
  • pmtContributor
  • Contributor
  • August 23, 2024

If the output network drive is not mapped, or you don’t have access to the output location, you will get that error.

 

pauldeq
Contributor
Forum|alt.badge.img+6
  • pauldeqContributor
  • Contributor
  • December 9, 2024

I don’t know if this will help, but I noticed that my issue was that I was adding “:” to my file name, and that is not a legal character for a file name. Are you sure that the “\\” in your file name “D:\\XXX\\XXX\\XXX\\new.xlsx” is right? I always thought that it was D:\\ and then each sub folder was a “\”? Like maybe the issue is that you are putting “\\” in places that don’t need it? Just a thought. 

Reply


Helpful Members This Week

Community Stats

30,942
Posts
117,252
Replies
38,742
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.