Error from Office Service. Url=https://wordcs.officeapps.live.com/document/export/pdf HttpCode=BadRequest cert=subject:;thumbprint: ResponseHeaders=X-ErrorCode: WordCantOpenDocument X-ClientCorrelationId: 575c2898-0345-4de2-9c90-847469dd76e3 X-ServiceCorrelationId: 575c2898-0345-4de2-9c90-847469dd76

[Anonymous]

Hi,

I'm getting this error in my flow in the Onedrive connector- converting to PDF.

The flow was working fine before and I added another 'single line of text' field in my sharepoint document library and now I'm getting this error:

Error from Office Service. Url=https://wordcs.officeapps.live.com/document/export/pdf HttpCode=BadRequest cert=subject:;thumbprint: ResponseHeaders=X-ErrorCode: WordCantOpenDocument
X-ClientCorrelationId: 575c2898-0345-4de2-9c90-847469dd76e3
X-ServiceCorrelationId: 575c2898-0345-4de2-9c90-847469dd76e3
X-ErrorCategory: BadRequest
X-IsRetriable: False
X-ConversionTimeInMs: 109.3431
X-FileDownloadTimeInMs: 468.926
Cache-Control: private
Date: Mon, 28 Dec 2020 13:05:52 GMT
Server: Microsoft-IIS/10.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

Please help me.

Thank you.

Daniel

[Anonymous]

Hey,

I have the same Problem now, did you find any solution for this Problem?

Kind regards 

Kai

[Anonymous]

Hi Kai,

Yes I did manage to overcome this but it was a while ago. From memory I think I deleted the OneDrive connector, readded it and remapped the dynamic fields of the filename and the ID.

Let me know if this works please. 

Best of luck.

Regards,

Dan

[Anonymous]

Sorry, I forget to answer, yes it worked, thanks for your help

[PaulD1]

I see this error from time-to-time on a flow we have that is using the OD4B Convert to PDF action. The Flow runs about 10 times per day and we see this error perhaps once every couple of months. Resubmitting the Flow (with the exact parameters/data) results in the Flow completing without error, so it seems this error can just intermittently occur sometimes.

[Newbie_16]

I was able to resolve this as well using the steps provided, I removed all onedrive connector then recreate it and also found out that there were two onedrive connector being used by my flow.  Thank you!

[Nikola2]

Hi all, 

I've just started having issues with this after successfully running this flow for 12 months, and can't seem to fix it.

I have removed and reconnected the connectors in the flow, and have redone the whole flow from the start with no success.
When I manually check the .docx file before converting an error pops up advising content cannot be retrieved, then when I click 'yes' to move forwards it opens the doc, but no filename is attached and it has to be saved again.

Please advise if you see anything I'm missing as I'm not super savvy with this!

Cheers, Nikola

[Anonymous]

Hi @Nikola2 ,

In the create file action, do you have the file extension at the end of the file name?

For example if it's a word doc have- filename.docx

Also, do you have the create file id property mapped into the first convert file property?

Regards,

Daniel

[Nikola2]

Hi @Daniel ,

Thanks for your response 🙂

Yes, I've got the .docx extension at the end of the filename:

This is how I've mapped into the convert file space:

Please let me know if you see anything that may be incorrect.
My next step is going to be trying to break this one flow into a couple of smaller flows, as I've been advised that something a bit of time is needed between creating the .docx and then trying to convert to pdf.

Cheers, your help is very much appreciated 🙂

[Anonymous]

Hi @Nikola2 ,

No problem! 

What is in the value of the 'Outputs' that you're referencing in your Onedrive 'Create file' action in the File Name property?

There shouldn't be any characters that are operators such as +,-,?,# or any others that aren't allowed in naming files.

See more here:

Restrictions and limitations in OneDrive and SharePoint (microsoft.com)

I used the 'Name' property from the SP 'Create file' action to map to 'File Name' of the Onedrive 'Create File' action (since I also had the file extension in the SP name is is not necessary to repeat it in the Ondrive file name after the SP name data point)

Also the 'file content' property in the Ondrive create file action has 'body' as the data point that is mapped there. It should be 'file content' from your get file content sharepoint action. 

Sometime Power Automate changes it to body even when it is file content.

Please can you confirm the above?

Thank you.

Regards,

Daniel

[Nikola2]

Hi Daniel,

Thanks for the advice, I did have incorrect characters in Outputs but have updated them and the mapping you recommended.. Unfortunately still getting the error! I've got screenshots below of nearly the whole flow to see if maybe you're able to take on more look and see if I've messed up somewhere else?

I'm still getting this error at Convert File point:

Error Details:

Error from Office Service. Url=https://wordcs.officeapps.live.com/document/export/pdf HttpCode=BadRequest cert=subject:;thumbprint: ResponseHeaders=X-ErrorCode: WordCantOpenDocument
X-ClientCorrelationId: 6bdf2ce9-e3bd-47d0-b95e-6d0341585a8d
X-ServiceCorrelationId: 6bdf2ce9-e3bd-47d0-b95e-6d0341585a8d
X-ErrorCategory: BadRequest
X-IsRetriable: False
X-ConversionTimeInMs: 343.7485
X-FileDownloadTimeInMs: 390.6131
Cache-Control: private
Date: Sun, 22 May 2022 10:33:04 GMT
Server: Microsoft-IIS/10.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

Thank you for your help so far!

Cheers,

Nikola

[Anonymous]

Hi @Nikola2 ,

It's a pleasure.

The value mapped to the file Identifier column (in the 'get file content 2' action) should be 'Identifier' from the 'update file properties' action like so:

Please try again and let me know.

Regards,

Daniel

[Nikola2]

Hi Daniel,

Thanks, I adjusted this but still had the error.

I have now managed to fix it though, and it seems the issue went back further than the flow - I had to completely recreate the document/template I was using and re-add in the quickparts that were correlating with the Form responses.

It's now run the flow perfectly, so I think that another solution to this issue for anyone else is to recreate the template/doc that needs to be converted in case the erroring one has a bug. I should have tried this sooner, really.

Thank you again for all your help! 🙂

Cheers, Nikola

[Anonymous]

Hi @Nikola2 ,

Well done! I'm happy you managed to identify the problem and that's for posting back to the community so others can benefit.

Good luck and enjoy the rest of your week.

Regards,

Daniel

[Anonymous]

someone please help me on this...

[vgreyes]

I received this same error. Our use case was that we used an initial flow to generate the initial Word document from a template using a handful of quick part fields and then made some manual modifications to the generated Word document before running it through a second flow to convert it to PDF. We have done this plenty of times before and even within the last few days using both of these existing flows.

When attempting to open the Word document that was to be used for conversion to PDF, there was a read error from Word (see attached image). I ended up creating the manual edits again on the generated Word document and can only assume that something with the first set of manual adjustments created some kind of read error related to the quick part fields we were using. Once I made the adjustments to those specific fields and ran the conversion flow again, there were no errors. So, my best suggestion would be to walk backwards through your steps to check your Word document because it may not be the flow that broke, but rather the input file that is causing the issue.

[gabismacedo]

Hello I had the same problem and it worked for me to delete the connection, I did it as follows: connections > delete

in the same connection tab I clicked on "new connection" and created a new one

I went back to my stream and clicked on "add new connection"

this way it worked for me.