I cannot export a report straight to Excel when I use Output Type: Export to Excel. It keeps failing saying that "A file with the name XXXX already exists and can't be deleted". There are no files in that folder so I don't understand what the problem is. I can run that same report but set it to open in the viewer, then export it to Excel to the same folder mentioned above and it exports with no problems! Anyone has a answer for this?
Thanks
*This post is locked for comments
Re: Failure to export to Excel. You can browse to the network letter for your mapped drives and select a folder which will then show as say N:\reports. You can save to this folder without a problem but it will not export. To Export to Excel be sure to use the UNC pathname (\\servername\sharename) - do not use hidden shares (have a $ appended to the end).
The process service account needs to have access to the location where the file is being written. Verify in the event viewer on the server, that no errors related to permissions on the folder exist.
The export process from the Report Viewer doesn't use the process service account, which is why it's exporting from the Report Viewer.
Jill
I would also like to third this issue! Same errors, running on MR FP1 through Citrix.
I would also like to second this issue. I get the same message on every client machine other than the server (also has Report Designer installed up there).
I have tested and gotten this error on Win7x86 and Win7x64, where I have also tried installing the x86 version of the reporter client on Win7x64 with no difference. I have also run with administrator option, and have tried XP SP3 compatability mode under execute options. I have also tested this under Windows XP native and XP Mode in Win7 with the same error. Exporting as 'XBRL Instance Document' also fails with no details, but an 'Exporting failed' error same as anything else I guess.
In all cases, the report successfully refreshes the online report in the Library, which I can verify via the Report Viewer. There are no errors in the report definition. It's just when saving a copy to a path that the error occurs. Shortening the path to something like 'C:\MgmtRptF' does nothing, produces same error as any other local path.
On the machines raising errors, I have even used SysInternals Process Monitor to watch what the ReportDesigner.exe process is doing. Looks like it gets to the point where it successfully confirms that it can open a handle to the local directory (my desktop) with read/write access, but then after that doesn't interact with the desktop folder at all. Temp files are not created on the client machine, either in the destination directory or under any directory, so ProcMon says.
Using a UNC path instead (one that I have admin rights to), I get the following error (names omitted for security reasons):
"There was a problem opening the file '\\server\share\subfolder\report.xlsx'. It can't be accessed because you don't have permission to this file path."
Any help would be appreciated. Considering this last post is only about a month old, I'd say this is a bug, or at the very least some installation bullet point that is not very clear and I've missed it.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156