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?

[aarongil]

I just did the same test and received the same results, older files convert but not newer ones. This is really strange behavior. This needs to get fixed soon.

Has anyone heard anything on a fix?

[jbprsn]

I am one of the lucky few where deleting the connection and establishing a new connection as worked.  For me, there is no distinction between old and new files.  It works with both, for me.  That really only muddies the waters of troubleshooting but I am hoping they get this resolved asap for each of you!

[majorfriend]

Mine randomly started working again.
We tried deleting the connector and readding and even rebuilding the flow and it still failed. It failed with new and old files.

Then on Friday it started working again, no idea why.

I was in the middle of trying the Word Online convert to PDF action, when it started working again.

[Justin-GOV]

This issue started affecting us Sunday evening and I opened a ticket with Microsoft. They indicated they were aware of the issue and are working on a fix - possibly rolling it out iteratively.

I also tried the recommendations listed in this thread. Replacing the connection and replacing the card/action did not work.

When I used the Word online - covert to PDF, it did work, but that isn't what we need for the flow.

[LinWeiXue]

Hello,Is there any feedback?Can you provide the tracking number of the problem? I will also urge Microsoft throughmy comany ,thanks.

[paulbeck1]

I can see different error messages so i assume MS are working on the issue.  I have got an update on my ticket raised on Thursday last night, that they are still looking into it.  So no reason given, expected correction date given.  Hopefully we get more info today when the fix is expected.

[paulbeck1]

@Yungkingdre Encodian have a connector, you need to register with Encodian, not they have a free version with fairly low numbers so depending on your need, that is a good option.  To use encodian, ensure your company governance allows it, most of my clients I need to get approval.  @AlexEncodian 's reply has more detail on using encodian. Encodian is excellent and has a lot more features so imo worth getting it setup.

The other option is to use the Word (Convert to pdf) action, note the action behaves differently to the ODfB convert action, so ensure you check your change.

[paulbeck1]

The endpoint used by the connector is not working.  There are 3 easy choices:

1. Wait for MS to fix it (assuming you have too many to change)
2. If you have premium user licencing, replace the ODfB convert action witht he Word convert action (pls note you may need to change the logic as the 2 actions work differently)

3. Use Encodian (Standard licence connector, there is a free tier, and use replace the OD4B Convert flow action with  Encodians equivalent convert word to pdf action.

[JamieD]

I raised it with our IT Dept a couple of days ago. They've now replied, including the following:

"We have raised this with Microsoft who are currently looking at it, they've told us that they have managed to recreate the error on their end so progress is being made on their end."

Fingers crossed!

[AmandaSJC]

Tal vez alguien ya encontró alguna solución?

[paulbeck1]

No more news from MS support on the open ticket as of 30 April evening 19:45 London time. If there is no more info to me from support by tomorrow afternoon, I will escalate the support ticket. 

[Justin-GOV]

The updated information I received from my support ticket April 30, 2024, 3:00 pm Eastern US time was: "We are still adding more and more tenants to the list of people who are having this issue, ... it looks to be quite a widespread issue. Regardless we still don’t have an answer and we are still delving into a solution."

[JT-1964]

paulbeck1, I just got a 90 day premium license while waiting for this fix (I have the same problem described). Can you recommend logic change required? Here are the 3 steps I need to replace with:

Thanks!

[paulbeck1]

@JT-1964 It does depend on your flow, but I've tried to copy your logic, this should be your fix with a single Action replacement 

 

[paulbeck1]

No more news from MS support on the open ticket as of 1 May evening 19:00 London time.

[hamidomar000m]

Hi @paulbeck1 
is there any update regarding your ticket?

[JT-1964]

Worked perfect. Thanks. Hopefully, the OneDrive issue gets fixed before my free trial is up!!

[paulbeck1]

Sent to my support ticket 15:10 on 2 May 2024, requesting an update on the OD4B Convert to pdf action connector issue:

I am not receiving any feedback or calls.  Please i need an update for my client.

The community is also eagerly awaiting an update onto if and when this will get fixed.

Please call or email and let me know what the issue is, and when it is likely to be resolved.  Or if MS does not intend to resolve the issue.  We can't be left in limbo with this issue."

My original ticket was sent 24/04/2024, 15:36:11 8 days ago...

[Justin-GOV]

Microsoft has officially published the issue in their service health portal as OD789650. For those of us with access to Microsoft service health, at least we can now monitor the progress.

Description

Impact is specific to the 'Convert file' and 'Convert file using path' options within the OneDrive for Business connector.

Scope of impact

Any users of the OneDrive for Business connecter attempting to convert files in Power Automate may be impacted.

May 3, 2024, 1:15 AM EDT

We're finalizing the process of implementing additional service logging that we anticipate will help us isolate the underlying source of impact and determine our options for remediation accordingly.

Next update by:

May 3, 2024, 4:30 PM EDT

[Parth1706]

Any one received update from Microsoft? Their deadline is up.