Converting file: Error from Office Service.

[Rapier]

Hi,

I have an old flow, which worked perfectly, but now I get the following error message:

Error from Office Service. Url=https://euc.wordcs.officeapps.live.com/document/export/pdf HttpCode=NotFound cert=subject:;thumbprint: ResponseHeaders=Connection: close
Date: Tue, 23 Apr 2024 06:41:01 GMT
Server: Microsoft-IIS/10.0
X-Powered-By: ASP.NET

I don't understand this issue, why it appears now?

I try to check this issue in other comments, but none of the mentioned solution works for me...

I checked the connections, and the result of create file step, both of these seems to me good.

Do you have any idea, how can I fix it?

[majorfriend]

Mine is also still not working.
I deleted all my connections and recreated, created a new export of the solution from Dev and imported to Prod, and even created an entirely new flow with a new connection. Same error on all of them.

Still waiting to hear back on my ticket with MS

[marechavala]

SOLUTION:

go to "https://make.powerapps.com/environments/Default-12f921d85a/logicflows

from left menu Click on " ...More" / click on "Connections"

Select connection "OneDrive for Business" / and Delete it

from Top Menu click on "+ New Connection"

from list select "OneDrive for Business" and click on the plus sign on the right "+"

from left menu select "Flows" and edit your affected flow. 

Click on the OneDrive for Business flow item that was being affected and expand it. Click "Add new connection" and wait 3 seconds.

Do this for each affected OneDrive for Business flow connections.

Good Lock!  🙂

[majorfriend]

Ya, this is what I tried this morning and it didn't work for me.

[lizbiz520]

This is happening to me as well. Have a flow that is used daily all throughout the day and has randomly thrown this error all of a sudden.

Error from Office Service. Url=https://wordcs.officeapps.live.com/document/export/pdf HttpCode=NotFound cert=subject:;thumbprint: ResponseHeaders=Connection: close

[patttachai]

yes,this is was suggested since yesterday. Many people tried this and work. But when i deleted and created new connection then run the flow, it still gives me 404 not found error.

i wondered if it depends on environment or what. But both personal and production connection of onedrive still not working for me and some others too.

[robb1]

I'm having this issue this morning too when converting .doc to pdf - Error from Office Service. Url=https://euc.wordcs.officeapps.live.com/document/export/pdf HttpCode=NotFound cert=subject:;thumbprint: ResponseHeaders=Connection: close

I have deleted all onedrive connections and created new ones - still get the same error.

[joshke]

Same here, tried to create a new flow with a new connection - same error! 

[siimgorczyca]

might not be the perfect solution to some of you, but it worked for me. you can replace the action with the Word Online for Business connector action called "Convert Word Document to PDF". It is premium, but works without any issue.

[patttachai]

Yes, this worked for me on a flow. But my other flow is to convert excel(online) to PDF so I cannot use word doc to pdf. I need OneDrive->Convert to PDF to works again. Does anyone know the ticket ID for this bug? I will escalate it thru my support.

[paulbeck1]

The work around is to use another connector to do the conversion.  If you are on a standard licencing for your users, then you can use the Encodian connector to convert word to pdf, however you do need an Encodian account and the free version does work for free (limited conversions) using standard licencing.

I raise a support ticket with MS, as this is an error for anyone using the OneDrive for Business Connector to convert word docs into pdf's.  The error is a 404 so the service has change at the Microsoft end.  I got a reply from support last night late.. "We checked internally and it is the outage from the OneDrive team, and we are transferring case to OneDrive team and Concern Engineer will get back to you."

I imagine this will be corrected today or shortly..

[LinWeiXue]

Hello,the problem has not been recovered, when can it be recovered? It's urgent for us to use.Thanks a lot.

Error from Office Service. Url=https://euc.wordcs.officeapps.live.com/document/export/pdf HttpCode=NotFound cert=subject:;thumbprint: ResponseHeaders=Connection: close
Date: Sat, 27 Apr 2024 10:43:31 GMT
Server: Microsoft-IIS/10.0
X-Powered-By: ASP.NET

  "status": 404,

  "message": "Error from Office Service. Url=https://euc.wordcs.officeapps.live.com/document/export/pdf HttpCode=NotFound cert=subject:;thumbprint: ResponseHeaders=Connection: close\r\nDate: Sat, 27 Apr 2024 10:43:31 GMT\r\nServer: Microsoft-IIS/10.0\r\nX-Powered-By: ASP.NET\r\n",

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

}

[LinWeiXue]

Is there any progress?Any feedback from Microsoft?Thanks.

[LinWeiXue]

hi,i try this,same error

[paulbeck1]

Hi @LinWeiXue - I got an msg that MS will call me on Monday afternoon.

At this point, I'd recommend don't create new flows with the OD4B Convert action, for existing flows if your users have premium licences use the Word convert action to replace in existing flows.  If you have too many flows and low priority flows, you'll need to wait for MS to fix the underlying issue. 

[LinWeiXue]

There are many flows and they are used every day in our company.I had to wait.thanks.

[paulbeck1]

Outline 3 min mp4 of the issue: https://youtu.be/bCaaTHSDxtM

[Yungkingdre]

I also have a similar challenge. What is the way out. I have tried all the provided solution but none is working

[LinWeiXue]

Microsoft is too slow to deal with problems

[AlexEncodian]

If you need a temporary fix, the Encodian action is working fine, is available within a Standard connector and has a free tier:

[JamieD]

I've had this issue since mid-last week. Oddly, I found out today that my colleague, who works with different flows, hasn't.

I've spent most of today trying to isolate what the exact issue is. I've removed connectors and readded them, recreated entire flows, created brand new test flows and other things besides.

I've narrowed it down to this: It seems that older Word files (i.e. older than about a week ago) are able to be converted absolutely fine, no problems at all. But any Word files created or uploaded to OneDrive since then fail to convert, and produce the error reported. Interestingly, this includes old files (which work) which are downloaded and then reuploaded without any changes. Even Word files that I create directly in OneDrive fail to convert. However, if I copy an old file from one folder to another, converting it still works.

So for us, it seems to be an issue with the creation of word files somehow being different now, which is causing the Convert flow to fail.

Although my colleague's flows work perfectly fine. Maybe it's just certain OneDrives? Go figure...