I'm trying to create an excel sheet and send it as an inbox/email attachment from an SAP background process using the xml method. I'm following the code/method described here. I'm able to receive the inbox with an excel attachment but upon trying to open the attachment I get the following error message:
Problems came up in the following areas during load:
Workbook Setting
This file cannot be opened because of errors. Errors are listed in:
C:\Users\user\AppData\Local\Microsoft\Windows\Temporary Internet files\Content.MSO\36F0E91E.log.
However, no log file actually exists at that location.
EDIT. I've found I can view the error log file by opening the path in a web browser. The error message given reads:
XML PARSE ERROR: Null or missing attribute value
Error occurs at or below this element stack:
<ss:Workbook>
Late reply, but have you considered the excellent library abap2xlsx that can be found on SDN code exchange? I believe that example 3 (ZDEMO_EXCEL3) in that package includes sending to email recipient.
Related
I downloaded a excel file (.xlsx) of size>110MB using API (http request) and tried to read the file using workboook read range and Excel application scope read range activity in Uipath. but I get error that 'file has corrupted data'. I tried a custom activity from marketplace as well. I am unable to open the file even manually. Can someone help
I'm trying to post an envelope but it keeps failing for non-pdf file with the following failure:
<errorCode>UNABLE_TO_LOAD_DOCUMENT</errorCode>
<message>Unable to load the document. Unable to load Document(1;Parking Application). Error: the document is corrupt, rebuilding failed </message>
I know that I can trying sending the document as multi-part request but I'm wondering what is the issue in this request:
https://drive.google.com/file/d/0B4IcppTb9svVSFhXYkdFa0gtbms/view
it contains a word document.
It doesn't seem to be an issue with the base64 encoded string because the string can be decoded back to the file just fine e.g. using http://www.motobit.com/util/base64-decoder-encoder.asp
You forgot to include the
<fileExtension>docx</fileExtension>
node in your XML adjacent to the documentBase64 node.
(The snippet above assumes you're sending a docx file. Change it to whatever the filetype is.)
In other words, if your document is not a pdf, you need to tell the platform what the format of your documents are. It assumes pdf.
I have some queries in my Access database which pull data from Excel files that appear in the database as linked tables. They have worked just fine, until suddenly and inexplicably I was getting the error "External table is not in the expected format," when trying to access them.
I thought it might have to do with the fact that I was using a macro-enabled workbook, but it was fine before. I do have a mail merge set up in Word which is linked to the database, and using one of the aforementioned queries.
It turns out that the issue was due to the mail merge document. Once I saved and closed the mail merge file in Word and tried accessing the queries and tables again in Access, the error was no longer appearing.
It seems that if a Word mail merge is connected to the database, this error may appear. I am not sure as to why a more appropriate error is not appearing; after testing it seems to happen regardless of whether the linked file is a macro-enabled workbook or not.
In short, as Olivier put it, the file was locked by Word. A simple issue, but not exactly clear given the error message (unless you follow Andre's logic that the expected format is a non-locked file, hahah).
I hope this helps someone else!
My form is hooked to a query. The "not in expected format" message happens when the query is set up as a "snapshot". When I changed to "dynaset", the form started to work as expected.
I am having issues creating a good data flow from Excel Source to SQL DB in BIDS 2010. I'm using 32-bit runtime, i have windows authentication on the SQL Server. I'm trying to send the data to a table that has no relationships or constraints at all. My excel file is .xls and I've tried doing this to SS2012 and SS2008R2 databases, getting the same errors back.
Here's my Package Validation Error:
Error at Data Flow Component [SSIS.Pipeline]: "component "Source for Excel Connection Manager" (1)" failed validation and returned validation status "VS_ISBROKEN".
Error at Data Flow Component [SSIS.Pipeline]: One or more component failed validation.
Error at Data Flow Component: There were errors during task validation.
(Microsoft.DataTransformationServices.VsIntegration)
Please check at this URL, I have commented earlier today.
BIDS Package Error's on Truncate while EXPORTING to flat file
Some suggestion as well:
1) Check the Data type in excel source. If the Source data type is different Convert or cast them as it is in Database.
2) Map the column correctly. Check if there are not null field in the destination.
3) Make sure you change the Project properties to RUN64bits to FALSE
This may not relate, but I was getting a very similar error while trying to write data to Excel from global tables. Turned out to be an issue with the Connection Manager for the database. I had to set "RetainSameConnection" to True and it started working right away. Again, this may be unrelated to your issue, and this is several months later, but it could be a solution for someone else that runs into the problem.
Again this may not be the case always but for me the excel was corrupted.
I followed these steps after wasting 3 hours:
tried to open the source excel file, it didn't open and prompted the file is corrupted.
recreated the excel file from the source, saved as excel (.xlsx) file
recreated the connection manager and edited excel source
and everything works fine.
I have been trying to Programmatially open a Infopath (2013) from from a SharePoint list (2013) in order to call the print to PDF functionality of the infopath client application.
When trying to open the Infopath file I am receiving the following error:
InfoPath cannot open the following file: {sharepoint filename}.xml. Not enough storage is available to complete this operation.
My C# code looks something like this:
string fileName = string.Format(#"{0}/{1}", application.Web.Url, application.Url);
Microsoft.Office.Interop.InfoPath.Application infoPathApp = new Microsoft.Office.Interop.InfoPath.Application();
XDocument InfXDoc = infoPathApp.XDocuments.Open(fileName, (int)XdDocumentVersionMode.xdCanOpenInReadOnlyMode);
Any ideas what would be causing this error?
thanks!
We had this issue and believe we have found the cause. Check your IE browser settings and verify that "Do Not Save Encrypted Files to Disk" is not checked. If it is checked it will trigger this error message.