Error convert to PDF - The remote name could not be resolved.

[Reason]

Problem in converting Word to PDF with One Drive Businnes.

Flow first fills the Word file with two variables, saves it, converts it to PDF, and finally sends it in a message.

I get the following error.

The remote name could not be resolved: 'mediagfx365-my.sharepoint.com'

{
  "status": 400,
  "message": "The remote name could not be resolved: 'mediagfx365-my.sharepoint.com'",
  "source": "api.connectorp.svc.ms"
}

{
  "Cache-Control": "no-cache",
  "Pragma": "no-cache",
  "Transfer-Encoding": "chunked",
  "x-ms-request-id": "f4c62603-2a70-4ae8-a754-87ac4404c07b",
  "X-AspNet-Version": "4.0.30319",
  "X-Powered-By": "ASP.NET",
  "Timing-Allow-Origin": "*",
  "x-ms-apihub-cached-response": "true",
  "x-ms-apihub-obo": "true",
  "Date": "Fri, 09 Sep 2022 15:01:13 GMT",
  "Content-Type": "application/json",
  "Expires": "-1"
}

Flow:

Results:

I do not see any rule as to why flow starts once and then does not.

Microsoft's technical support did not even make a notification within three days ...

What other connector should I use instead of OneDrive for Business?

Which will work. Word file has two text boxes to change and background as watermark. I don't know if it matters.

[DamoBird365]

Hi @Reason 

If you are using the premium word connector to populate a document, there is a 2nd action to convert to PDF, therefore you do not need to save to OneDrive.  Take a look at this point in my recent video that shows you how to populate and convert a word template to PDF (including repeating controls)  https://www.youtube.com/watch?v=L67m8wgd4Ak&t=521s

Damien

[hardow]

That's not a solution to @Reasons problem. Me and a few customers are experiencing the same issue since friday.
The Word Online Connector won't work with dynamic content.

Please provide us a clean solution for this, since it's your error...

[Maxiiii_Strobel]

Hi, 

i have the same problem with HTML since Friday. 

[DamoBird365]

Hi all,

I appreciate you all providing evidence of the problem you are experiencing.  I will let the community team @AnnaChu and @kishbuy238 know so that this can be investigated by the product team, and they can advise on the best course of action.

My advice was based on experience as Super User and Business Applications MVP on the Power Automate product and the most efficient method to convert word to PDF when using the Word premium connector.  Hopefully the product team can identify the problem several of you are experiencing with the OneDrive connector and report back.

Damien 

[GlennRabe]

We have the same problem with HTML since Friday 9 sept. 2022

[hardow]

Hey @Reason & @Maxiiii_Strobel,

I've got kind of a "fix". I'm currently trying the Action until it works.
It took my Do Until Loop 38 minutes and 31 tries to finally convert the file.

So basically start with a Do Until Loop.

Set the limits to:
- Count: leave blank

- Timeout: P7D     -    (This means, the loop will loop for 7 days)

In this Loop you'll need to add the Convert action.

After the convert action set a Bool Var, which you need to initialize beforehand.

In my example its called "convertError", rename the set action to: set convertError true.

Set it to true and add the runAfter parameters: timeout and error, remove succeeded
Then add a Delay, I've chosen 30 seconds.

Between the "set convertError true" and convert action, add a parallel branch and copy paste the "set convertError true" action there. Update the Value of the new action to false and rename it to: ""set convertError false"

The Loop should be ready now, if you want to get notified, if the loop times out or fails, add a parallel branch after it. Then select the Send Mail Action or similar and set the run after settings, like "set convertError true". after that, terminate the flow with error.

I'll provide some screenshots for the temporary solution:

[mskrzypczak2]

Hello. We have the same problem (since friday) when trying to convert .docx file to PDF.

[marina601]

I am experiencing the same issue since Friday! The flow fails every time it tries to convert a word document to a pdf file. Looking forward to further updates

[bubakgodx]

Hi guys, 

Same problem from Friday.

[Maxiiii_Strobel]

Hi @hardow ,

your workaround works. Sometimes a flow runs for 45 minutes and sometimes only 3.
Thank you for your help.
Nevertheless, this is not a long-term solution.

Many greetings
Maxiii

[hardow]

Yeah, but we had to do something asap, so this will stay until the action works again 🙂

thx for your response 🙂

have a great day!

[bubakgodx]

I have same problem Our expedition can't print tags without  this action so 250 people need to manual print need quick FIX asap.

[edobaria]

We are facing the same issue, it broke the working flow.

[WilkinsLuke6]

Facing the same issue here and it is stopping the whole process of my flow as it is reliant on sending a PDF document over a .docx. I am able to create the .docx file in my OneDrive but it is simply the conversion creating issues.

Is there any step of sorts that can convert a .docx to PDF without relying on OneDrive? Thanks

[Maxiiii_Strobel]

Hello everyone,

I just reported a problem in the Microsoft Admin Center.
Microsoft has now created a note for this purpose.

Regards
maxiii

[IvakaVT]

I am experiencing the same issue since Friday 09.09.2022 !!!
It works for a while on Saturday/Sunday but now again crashed.
The differents for me is that my workflow use HTML to PDF conversion for OneDrive
and facing same problem as others with Word to PDF conversion. 

This is the error message:

"status": 400,

"message": "The remote name could not be resolved: "BlaBlaBla-my.sharepoint.com'",

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

Best Regards
Ivaylo

[coxy0505]

We are facing the same issue HTML to PDF not worked since Friday 9th of September.

[jcsdias]

Same issue here.

During the weekend the conversion worked well, but today it is like friday.

We need the correction, please.

[Nao_]

Hi ! Could you please link the note ? I can't find it, thanks !