Why at test conection on creation of a Linked service in Azure I got error 11402 when I am providing the correct username and password

Question

I got the error 11402 when i am creating a linked service connected to the File System. The file is shared and the path is well written. I am writing the username and password to access to my computer, but i cannot enter.

I want to know what would be the reason? The subscription as student? Access of my user to do that?

Answer 1

@David Eleazar Solis Segovia - Thanks for the question and using MS Q&A platform.

his error message indicates that the access to the specified file system is denied. There could be several reasons for this error, such as incorrect credentials, incorrect file path, or insufficient permissions. To resolve this issue, you can try the following steps:

1. Check the credentials: Make sure that the credentials you are using to access the file system are correct. You can verify the credentials by trying to access the file system manually using the same credentials.
2. Check the file path: Verify that the file path you are using is correct. Make sure that the file path is in the correct format and that it points to the correct location.
3. Check the permissions: Ensure that the user account you are using has sufficient permissions to access the file system. You can check the permissions by right-clicking on the file system and selecting "Properties". Then, click on the "Security" tab to view the permissions.
4. Check the resolved IP address: Ensure that the resolved IP address is correct. You can check the resolved IP address by running the "nslookup" command in the command prompt.

According to the offical documentation, the latest SHIR has a security fix that has been changed and does not allow access to local files by default.

You must run .\dmgcmd.exe -DisableLocalFolderPathValidation to disable the setting for more details, refer to Set up an existing self-hosted IR via local PowerShell

For more details, refer to Access denied to server in File System Linked Service in Data Factory.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Hello David,

Thank you for reaching out in Microsoft Q&A. Based on the information you've provided, I'd like to offer some additional insights to help you address this challenge.

You're absolutely on the right track in considering your self-hosted integration runtime (IR) and its interaction with your corporate network's firewall. When your IR is within your corporate network, ensuring proper alignment of the firewall configuration is paramount. This alignment is crucial to enable seamless communication between the integration runtime and external services.

In this context, it's important to verify that the firewall settings on your corporate network allow the necessary incoming and outgoing traffic for your integration runtime. Specifically, pay attention to the required ports that facilitate communication between the IR and external endpoints like SFTP servers. If these ports are not properly open or configured, it can lead to connectivity issues and errors, such as the error 11402 you've encountered.

Therefore, I recommend that you revisit and meticulously review the firewall configuration within your corporate network. By aligning these settings correctly, you're taking a significant step towards resolving the error you're facing during linked service creation.

Error 11402 often indicates an issue with authentication or authorization when trying to establish a connection. Since you've mentioned that you are providing the correct username and password, there are a few potential reasons for this error:

1. Permissions and Access: Double-check the permissions on the shared file path and the NTFS permissions. Make sure that the account you're using has appropriate access rights. Refer to the documentation on managing shared folder permissions: Manage shared folder permissions
2. Network and Firewall: Ensure that there are no network or firewall restrictions blocking the connection from Azure Data Factory to your file system. Azure Data Factory uses specific IP ranges for outbound communication. You can find these ranges in the Azure Data Factory documentation: Azure Data Factory IP ranges
3. Credential Format and Encryption: Confirm that you're entering the username and password in the correct format. If you're using any form of encryption or secure storage for your credentials (like Azure Key Vault), ensure that the retrieval and usage processes are correctly configured. Here's information on using Azure Key Vault with Azure Data Factory: Use Azure Key Vault secrets in Azure Data Factory
4. File Path and Format: Double-check the file path you're entering. Typos or incorrect formatting can lead to errors. Ensure that you're using the right conventions for the file system you're connecting to.
5. Azure AD Integration and Service Principal: If you're using Azure AD for authentication, verify that your directory and authentication settings are correctly configured. If a service principal is involved, ensure it has the necessary permissions. Here's a guide on using managed identities and service principals in Azure Data Factory: Use managed identities and service principals in Azure Data Factory

I hope these resources and steps will help you troubleshoot and resolve the error. If you continue to face difficulties, consider checking the specific error message and logs for more information. If you have further questions, feel free to ask for assistance.

If you found this response helpful, please acknowledge it to help others too.

Best of luck