How to fix ServiceOperationFailed error in logic apps while trying to mount file share

Question

How to fix ServiceOperationFailed error in logic apps while trying to mount file share

Usha Sundersingh Bisht 0

logic apps standard - The service provider action failed with error code 'ServiceProviderTriggerFailed'

I have a logic apps standard workflow running..

It has a simple http trigger that attempts to use a built-in file system connector to list files at "\xxx file share path\files"

The list files action gives the following error:

{
    "statusCode": "BadGateway",
    "body": {
        "error": {
            "code": "ServiceProviderTriggerFailed",
            "message": "The service provider trigger failed with error code 'ServiceOperationFailed' and error message 'The user name or password is incorrect. : 'C:\\mounts\\FileSystem-2\\WorkforceShare\\MemberBoards''."
        }
    }
}

I have checked the configuration blade in the Azure portal for the logic app. I can confirm that it has a config name of "FileSystem_mountPath" with a value of "C:\mounts\FileSystem-2". I then opened a kudu session / PowerShell console. I could see screen as shown below.

User's image

I'm not sure why the connector is not able to mount.

Could you please suggest the solution .I am stuck because of this issue. Immediate response is highly appreciated .Thanks

Anand Prakash Yadav 7,860 Reputation points Microsoft External Staff

2024-01-15T12:08:00.39+00:00

Usha Sundersingh Bisht, just checking in to see if the below-answer helped. If this answers your query, do click "Accept the answer” for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.
Anand Prakash Yadav 7,860 Reputation points Microsoft External Staff

2024-01-17T12:10:51.4266667+00:00

Usha Sundersingh Bisht, just checking in to see if the below-answer helped. If this answers your query, do click "Accept the answer” for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

2 answers

Your answer

Anand Prakash Yadav 7,860 Reputation points Microsoft External Staff

2024-01-15T12:08:00.39+00:00

Usha Sundersingh Bisht, just checking in to see if the below-answer helped. If this answers your query, do click "Accept the answer” for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.
Anand Prakash Yadav 7,860 Reputation points Microsoft External Staff

2024-01-17T12:10:51.4266667+00:00

Usha Sundersingh Bisht, just checking in to see if the below-answer helped. If this answers your query, do click "Accept the answer” for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

Answer 1

Hello Usha Sundersingh Bisht,

Thank you for posting your query here! It seems like you are facing an issue with the built-in connector File System. In order to create a new connection to use the connector triggers/action, the following parameters are needed.

Connection name: The name of the connection
Root folder: The root folder for the network share. This should be in the format \<FQDN or IP address of the Machine><folder name>. For example, \test-file-serv.internal.cloudapp.net\Myshare. Note that the root folder cannot have nested folder path like \test-file-serv.internal.cloudapp.net\Myshare\folder1.
Username: The username for the file share. It can be a simple workstation username, or with a domain name in the format DOMAIN\user.
Password: The password for the file share.

Once the connection is created, there is config update which happens behind the scenes and hence the logic app would be restarted. You may wait till the app is restarted (less than a minute usually) to save the workflow or add more actions. The ‘Failed to save workflow’ ’error is expected when the workflow is tried to save during the restart.
Further you may want to know that the File System connector uses the App Service BYOS feature to mount the file share to a specific path. So, when a new connection is created, designer updates the config to mount the file share to C:\mounts<connection-id> and the mount path is then written to connections.json.
The Logic Apps runtime only uses this mount path for any of the action/trigger executions.
However please note that a connection created successfully still doesn’t guarantee that the mount was successful. Since the mount path does not exist from the file system through the Kudu console the connection may not work. Due to networking constraints of the file share/logic apps, the file share might still not be accessible from Logic Apps. To resolve this issue, you can try the following steps:

Check if the file path you are trying to access is correct and exists.
Make sure that the account used to run the Logic App has the required permissions to access the file path.
Check if the file path is accessible from the network where the Logic App is running.
If you are using an on-premises data gateway, make sure that it is installed and configured correctly.

Please refer to below articles:
Using File system connector in Logic Apps Standard
Connect to on-premises file systems from workflows in Azure Logic Apps.

Please let us know if further query or issue remains.

Anand Prakash Yadav 7,860 Reputation points Microsoft External Staff

2024-01-22T11:45:30.5366667+00:00

Usha Sundersingh Bisht, just checking in to see if the below-answer helped. If this answers your query, do click "Accept the answer” for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

Answer 2

Error Description

{"code":"ServiceProviderActionFailed","message":"The service provider action failed with error code 'ServiceOperationFailed' and error message 'Call to SAP client library failed with error message 'SAP server communication failed with error code '101' and error message '00024Invalid language key when configuring the text environment.€€€€€€€€€€€€€€€€€€€€€\nRETURN CODE: DEALLOCATED_NORMAL'.'.'.

Facing above issue intermittently when sending multiple records to SAP connector

while sending 5000 records sequentially , this error happened only for 5 records . Any idea , what could be the issue ?

Share via

How to fix ServiceOperationFailed error in logic apps while trying to mount file share

2 answers

Your answer