Forum Discussion
Lookup activity id undefined
Hi mwsmoley
Thanks for using Microsoft Fabric Community.
The error "Connection failed undefined. Activity ID: undefined." in Microsoft Fabric Lookup activity connecting to an Azure SQL Database indicates an issue with establishing the connection.
I tried to replicate the scenario and didn't face any difficulty in setting up connection. Please find the screenshot for reference.
Here are some troubleshooting steps that might help you.
Connectivity Issues: Check if there are any temporary network issues preventing communication between the Microsoft Fabric service and your Azure SQL Database. You can try refreshing the connection or restarting the workflow.
Verify Connection Details: Double-check the Azure SQL Database server name, username, password, and database name in the Fabric Lookup activity configuration. Ensure there are no typos or incorrect information.
Fabric Lookup Activity Configuration: Check the configuration settings in the Fabric Lookup activity. Ensure the connection information matches the Azure SQL Database details.
I hope this information helps. Please do let us know if you have any further queries.
Thank you.
- mwsmoley2 years agoHelper II
Hello,
Thank you for the reply. I do not believe this is related to a connection issue as this was happening on all connection types and instead of using the lookup I switched to useing scripts to not stop development and script activities are able to connect to the server just fine. Additionally I can connect using SSMS and Azure Data Studio.
- v-cboorla-msft2 years agoMicrosoft Employee
Hi mwsmoley
There might be a chance of an intermittent issue could you please follow the below steps that might help you.
Temporary Glitch: Clearing cookies and caches can sometimes resolve temporary glitches within the application that might be causing the issue.
Hard Refresh: A hard refresh bypasses the cached version of the webpage and forces the browser to download the latest version from the server. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).
If the issue still persists, please do let us know. Glad to help.
I hope this information helps.
Thank you
- v-cboorla-msft2 years agoMicrosoft Employee
Hi mwsmoley
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.Thanks.