Dont work after update

(0) Share

Report

Posted on by Lars5

I have this there dont work after update to ver. 2.42.317

Why?

Categories:

Power Automate Desktop

All responses (8)

Answers (1)

Sort by

CU16071609-1 6,255 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@Lars5

Are you getting any error?
Lars5 38 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes
Correlation Id: 7b86fbf5-ce9d-4c72-a7eb-fdb72ebacd0e
Could not find a part of the path 'K:\Power automate\log\2024042-log.txt'.: Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.ActionException: Invalid directory specified ('Could not find a part of the path 'K:\Power automate\log\2024042-log.txt'.') ---> System.IO.DirectoryNotFoundException: Could not find a part of the path 'K:\Power automate\log\2024042-log.txt'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding)
at Microsoft.Flow.RPA.Desktop.Modules.File.Actions.WriteTextToFileAction.Execute(ActionContext context)
--- End of inner exception stack trace ---
at Microsoft.Flow.RPA.Desktop.Modules.File.Actions.WriteTextToFileAction.Execute(ActionContext context)
at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)

But i'm sure the path is correct?
Agnius Bartninkas Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Do you have access to the actual directory? It seems to be a network drive - perhaps the mapping of the K: drive got dropped?

Maybe try using the full UNC path instead of the mapped drive name. See here for reference on how to get it: https://stackoverflow.com/questions/21482825/find-unc-path-of-a-network-drive
CU16071609-1 6,255 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@Lars5

As @Agnius mentioned there is issue with your network/local drive.

Seems you are trying to "K:\Power automate\log\2024042-log.txt" file in d drive but its not accessible or its not available. So please correct that it will resolve your issue.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀
Lars5 38 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Deebuji

There are nothing wrong with my netword drev. as you can see i have connect to K:

It works before update.

But it is correct i have no contact to the path. When i do it manuelt

Can I not connect my K: drev. But I can when i use Windows Explorer?
VishnuReddy1997 2,666 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Lars5 ,

Below are the cases that has to be validated:

1) Map the network drive to your system.
2) Check the file access permissions for the network drive (Read, write, edit and delete)
3) Try to re-give the path of Network drive again.

(Note:- if you got your solution you can mark as solution and gives kudos)

Thanks & Regards
Vishnu Reddy
Agnius Bartninkas Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Just try using \\accp-srv01 instead of K:

That should be more stable, and could probably resolve the issue that has come up after the update.

Also, check that the "Log" folder is actually called "Log" with an uppercase L, whereas you're using a lowercase l in your flow. That might also be causing issues.
Verified answer

Lars5 38 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi

The solution was so simple that a restart was required after installing the power automat update

thanks everyone for input