This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 49%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGK%3C/text%3E%3C/svg%3E)
Hello,
in windows server 2022 have a running Eflow-Installation.
Want to add shared folders
Add-EflowVmSharedFolder -sharedFoldersJsonPath "D:\Shared\EFLOW-Shared\sharedFolders.json"
gives:
Creating storage sharedfolders under root (D:\Shared\EFLOW-Shared)
set all folder starting with Folder D:\Shared in properties to "shared" and access to "everyone R/W"
Content of json:
[
{
"sharedFolderRoot": "d:\Shared\EFLOW-Shared",
"sharedFolders": [
{
"hostFolderPath": "cronicle",
"readOnly": false,
"targetFolderOnGuest": "/tmp/host-cronicle"
},
{
"hostFolderPath": "RWAccess",
"readOnly": false,
"targetFolderOnGuest": "/tmp/host-rwaccess"
}
]
}
]
could not insert structure folder pic
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 13%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMN%3C/text%3E%3C/svg%3E)
As mentioned on my comments (given the comments from @Gerald Kluge , this feature is not supported on Windows Server.
Hi @Morais, Nelson You can submit a product feedback on this limitation through the following link - Azure IoT Edge feedback forum
Kindly share the feedback request link once it is created so that the community members who come across this issue can upvote it. This will help Product team prioritize the feature requests.
Done, see this link: https://feedback.azure.com/d365community/idea/2dd72de3-747a-ee11-a81c-6045bdb7ea56
Hi @Gerald Kluge Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.
Update
This feature is not currently supported on Windows Server.
If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.
As wrote in the comment:
I also checked with \\ in the json path, same result.
Also checked with Volume C: as you did.
And created the folder in VM with rights 777.
The full error message:
my Eflow Path is on D:
one of the yaml descriptions for the folder is created under D:\EFLOW\yaml\ and it looks like the nodectl.exe creation is failing.
PS C:\Windows\system32> Add-EflowVmSharedFolder -sharedFoldersJsonPath "C:\Shared\EFLOW-Shared\sharedFolders.json" -Debug
- Creating storage sharedfolders under root (C:\Shared\EFLOW-Shared)
- Did not find any matching sharedfolders!
- Did not find any matching sharedfolders!
[07/11/2023 12:03:42] Exception caught!!!
- D:\EFLOW\nodectl.exe storage sharedfolder create --config "D:\EFLOW\\yaml\cloudsf-EflowStorageSharedFolder592d35fe-e750-4cdf-8ed8-153f4f658356.yaml" failed to execute [E0711 12:03:40.644499 12276 wssd.go:55] [SharedFolder] Create failed with error rpc error: code = Unknown desc = Not Supported Error: rpc error: code = Unknown desc = Not Supported] at line 4349
D:\EFLOW\nodectl.exe storage sharedfolder create --config "D:\EFLOW\\yaml\cloudsf-EflowStorageSharedFolder592d35fe-e750-4cdf-8ed8-153f4f658356.yaml" failed to execute [E0711 12:03:40.644499 12276 wssd.go:55] [SharedFolder] Create failed with error rpc error: code = Unknown desc = Not Supported Error: rpc error: code = Unknown desc = Not Supported]
Hi @Gerald Kluge , thank you for your response and sharing additional information on the error message you are seeing.
Please note that you would not have to explicitly create these folders on the VM. The Add-EflowVmSharedFolder command takes care of adding the folders on the VM for your automatically. Also, these folders are created in a container when they get created through the command.
Inspecting the error, I notice that the path to the yaml file seems to be incorrect which could be causing the issue. You may have defined the Eflow base directory as D:\EFLOW\ whereas, it has to defined as D:\EFLOW
You can access the underlying script file of these commands from the script file AzureEflow.psm1. The file can typically be found from the directory C:\Program Files\WindowsPowerShell\Modules\AzureEFLOW. Inspect the AzureEflow.psm1 under this directory and you can find the implementation of Add-EflowVmSharedFolder method. In line 8369 of the file, there is a call made to Add-CloudSharedFolder which access the path to the yaml file. Please find the following line of code (line 8125) where the path for the yaml file is set.
$yamlFile = $($config["eflowBaseDir"]+"\yaml\cloudsf-$name.yaml")
Try setting the eflowBaseDir parameter to D:\EFLOW in line 160 of the file and execute the command again. Please note that the shared root folder in the json file has to include an escape character as follows, "sharedFolderRoot": "D:\\Shared\\EFLOW-Shared"
Please let us know if this helps. If you face any other errors, please do not hesitate to get back to us. We would be happy to help you.
We noticed your feedback that the above answer was not helpful. Thank you for taking time to share your feedback. Kindly let us know what we could have done better to improve the answer and make your engagement experience good. We are here to help you and strive to make your experience better and greatly value your feedback. If you wish, you may consider re-surveying/rating for the engagement you received on the thread. Looking forward to your reply. Much appreciate your feedback!
Hi LeelaRajeshSayana,
i edited the psm1 file and made a restart (as there where no changes to be senn before)
After restart i get:
AzureEFLOW.psm1 is not digitally signed. You cannot run this script on the current system.
How to bypass?
Regards Gerald
set ex policy by:
Set-ExecutionPolicy -ExecutionPolicy Bypass
get now:
PS C:\Program Files\WindowsPowerShell\Modules\AzureEFLOW> Add-EflowVmSharedFolder -sharedFoldersJsonPath "D:\Shared\EFLOW-Shared\sharedFolders.json" -Debug
- Creating storage sharedfolders under root (D:\Shared\EFLOW-Shared)
- Did not find any matching sharedfolders!
- Did not find any matching sharedfolders!
[07/12/2023 12:58:07] Exception caught!!!
- D:\EFLOW\nodectl.exe storage sharedfolder create --config "D:\EFLOW\yaml\cloudsf-EflowStorageSharedFolder0e07f438-55db-4d00-8cd3-cc26824c8d78.yaml" failed to execute [E0712 12:58:05.236777 7332 wssd.go:55] [SharedFolder] Create failed with error rpc error: code = Unknown desc = Not Supported Error: rpc error: code = Unknown desc = Not Supported] at line 4349
D:\EFLOW\nodectl.exe storage sharedfolder create --config "D:\EFLOW\yaml\cloudsf-EflowStorageSharedFolder0e07f438-55db-4d00-8cd3-cc26824c8d78.yaml" failed to execute [E0712 12:58:05.236777 7332 wssd.go:55] [SharedFolder] Create failed with error rpc error: code = Unknown desc = Not Supported Error: rpc error: code = Unknown desc = Not Supported]
sharedFolders.json is:
[
{
"sharedFolderRoot": "D:\\Shared\\EFLOW-Shared",
"sharedFolders": [
{
"hostFolderPath": "cronicle",
"readOnly": false,
"targetFolderOnGuest": "/tmp/host-cronicle"
},
{
"hostFolderPath": "RWAccess",
"readOnly": false,
"targetFolderOnGuest": "/tmp/host-rwaccess"
}
]
}
]
Any kind of other Debugging possible?
Hi @Gerald Kluge For a deeper investigation and immediate assistance on this issue, please file a support request @ https://aka.ms/azsupt? If you do not have access to a support plan, could you please send an email with the below details, so that we can work closely on this matter.
Thread URL: Link to this thread.
Azure Subscription ID:
Email Subject : Attn Leela
Hi,
I'm having the same issue, running on a Windows Server 2022 (10.0.20348).
Where you able to find the issue and a solution for this?
@Nelson: there was no solution by MS in this discussion here.
The last hint was a new installation, but as i did this already before i stopped here.
Later we learnt, that Windows server is not supported by this feature.
I decided to use a samba docker module to connect.
Hi @Gerald Kluge Thanks for the quick reply! That clarifies a lot!
Given your answer then I would say that the correct response from MS should be that this feature is not supported/buggy on Windows Server (which is where I'm running EFLOW).
@LeelaRajeshSayana-MSFT It would be good to know if this topic would be addressed in a future patch of EFLOW.
Hi @Gerald Kluge Thank you for letting me know the conclusion on this issue. I understand that this situation may have caused some inconvenience, and I want to express my gratitude for your efforts and patience in handling it. I will update my response above to reflect these observations so that other community members running into this would know that it is a limitation.