"Status 415 Unsupported media type" when using Convert Word Document to PDF

[Femke1]

Hi everyone,

Hope someone is able to help me. I'm using a flow which converts a Word document to a PDF at some point in the flow. This worked fine for quite a while now.

Suddenly, without any change that I know of, it gives me an error (status 415 - unsupported media type). When I look at the raw outputs, it says: 

"Content-Type": "application/json"

In an earlier flow, where it all worked well, it said:

"Content-Type": "application/pdf"

I ran a test flow and it gave me the same output if I tried to convert to PDF with the same document. When I made a new document in the same folder on Sharepoint, it worked fine.

But before I have to remake all the Word-documents (it's a lot of work, because I have a lot of processes with this problem), I want to find out WHY this happens - maybe there is another solution?

I've been thinking that it might have to do with changes on our company server... maybe? I really do not have a clue where this is coming from... The only thing I changed in this flow recently, was that I removed questions from a Forms form, and therefor in this flow I removed the answers out of the action 'Update item' (to write them to a SP List). That's all.

Can anybody help me understand this? Your help is much appreciated! Thanks in advance 🙏

Femke

[Sesch]

I've encountered the same problem. The flow has worked fine until now. I get the same error message as you.

[JSchalleyCegeka]

Exactly the same issue here! It all worked perfectly fine for 6 months, until a couple of weeks ago... Now it's throwing the error related to that "Content-Type": "application/json" for me as well.

The full error message is this for me:

{

  "status": 415,

  "message": "Unsupported media type.\r\nclientRequestId: 5854cf05-406d-4262-867a-638daeb507da",

  "error": {

    "message": "Unsupported media type."

  },

  "source": "wordonlinebusiness-we.azconn-we-003.p.azurewebsites.net"

}

Fun fact: when I use the OneDrive-connector to convert the same files to PDF, I also get a very similar error message there... (this also used to work perfectly fine for the past 6 months, until a couple of weeks ago)

Full error message:

{

  "status": 406,

  "message": "Conversion of this file to PDF is not supported. (cannotOpenFile / Error from Office Service. Url=https://euc.wordcs.officeapps.live.com/document/export/pdf HttpCode=UnsupportedMediaType cert=subject:;thumbprint: ResponseHeaders=X-ErrorCode: WordAccessViolation)",

  "source": "api.connectorp.svc.ms"

}

Literally nothing has changed in the flows or in the files that have to be converted. So it has to be something that was changed on the Connector side of things I assume?

I think I have done all the testing and debugging I can, just to come to the conclusion that "it doesn't work like it used to any more"... so I really hope this gets resolved soon since our client's process is now kinda stuck because they need the PDF's to be created automatically. 

[Sesch]

I used the Adobe connector instead, that worked perfect!

[JSchalleyCegeka]

Yeah but that requires a license on the Adobe side I think, right?

[Sesch]

I suppose so...

[JSchalleyCegeka]

That's not an option for my client then. Appreciate the input though 👌

The main fact is that this has all worked perfectly fine until recently, so it's probably something that can work again when/if it gets fixed. 

[JSchalleyCegeka]

I just did a new test without changing anything and it seems to work again now! 😎👌

[Femke1]

Good that it's working again, nice! For me I have replaced all Word documents and from now on I will never work with a Word document that I receive again. I have decided that I will only work with new documents that I will remake from scratch, just to be sure 😉

But thanks for your update!

[faisalkhawaja]

I have this problem!  Was there never a solution from MS or the community??

[JSchalleyCegeka]

Not really, or at least I have never found anything useful on it no. Back when I had the issue, after a while it just started to work again, without me changing anything. 🙄

[Femke1]

No, not that I know of, unfortunately... I replaced all of my Word documents. Now it runs smooth again.

[poweruser2024]

Hi to all,

I got the same problem and found that in my case the error was raised by the connector trying to convert an empty Word file (since I was doing some test in my dev environment) into PDF. As soon as the Word file has content the conversion should worked (at least in my case).

Not sure if this could help you.