I am running a simple schedule through Jet Reports to basically test the functionality of the program. However I am having a strange issue that is setting me back;
-The input document is listed on our sharepoint drive: \\sharepoint\DavWWWRoot\accounting\Jet Reports\JET041 - Patent Revenue Calculation Jet Report.xlsx
-The output document is also to be uploaded to the sharepoint drive: \\sharepoint\DavWWWRoot\accounting\Jet Reports\Scheduled Reports\JET041 - Patent Revenue Calculation Jet Report.xlsx
-Running the report through server 2008 R2, with Office 2010, latest ver. of Jet installed 12.5.13072.0 (32-bit)
-The output folder is already created on the mapped drive.
-My access times to the sharepoint file server is great.
The Issue:
When I select attach the report to the email I get a "File "\\sharepoint\DavWWWRoot\accounting\Jet Reports\Scheduled Reports\JET041-Patent_Revenue_Calculation_Jet_Report.xlsx" does not exist'" error. But the file is still uploaded and updated to the output directory and the Email does not send due to this. When no report is selected to attach to the email, then the email sends fine.
I have tested the same file locally having the input file on c:\download and the output in c:\download\output with the "attach report to email" selected and everything is working and sending the email fine.
Any Ideas on this?
Date
Votes
2 comments
-
Jet Reports Historic Posts I think you should probably create a support ticket with Jet Reports support. Then someone can look at the problem with you and hopefully identify what is happening. I'm not really sure all of the ramifications of SharePoint folders; it may be that Outlook is having a hard time attaching the file to the email directly from the SharePoint folder. That would be my guess, but it is probably best to create a support ticket so someone can look at the problem more closely with you.
Regards,
Hughes -
Jet Reports Historic Posts Oh I have :) in fact the developers/CSR are going through it as well and the thread is rather long already.
Looking to help them out some by involving the community and checking if anyone has run into the same issue and had it resolved.
Thanks though :)
Please sign in to leave a comment.