Forum Discussion

JohnAG's avatar
JohnAG
Frequent Visitor
1 year ago
Solved

Something went wrong Error

Yesterday my Data warehouse was refreshing and working fine. Today when I refresh the data warehouse I get the message  Something went wrong  Internal error SqlLoginFailureException.  This is...
data warehouse
Warehouse
  • JohnAG's avatar
    JohnAG
    1 year ago

    it was resolved by Microsoft Support it took 3 different calls with MS support, they didnt' give full explanation on the reason, but they said it shouldn't happen again. it might have been a code oversight and they modified it. 

    thank you for reaching out 

     

    John

V-yubandi-msft's avatar
V-yubandi-msft
Community Support
1 year ago

Hi JohnAG ,

 

Sorry for the inconvenience. Re-establishing the connection can often resolve internal authentication issues. Please try disconnecting and reconnecting the data warehouse in Fabric.

  • Ensure you have admin permissions on the workspace, as recent changes to permissions may cause schema visibility issues.

The Premier Access ID is a unique identifier for Microsoft Premier Support customers, used to track support cases and manage accounts. You can find your Premier Access ID by logging into the Microsoft Premier Support portal.

Similarly, the Contract ID is assigned to Microsoft support contracts to track support cases. If you are not a Microsoft Premier Support customer, you can find your Contract ID by logging into the Microsoft Support portal.

 

Below is a related issue concerning the Premier Support ID in Power Platform that might be helpful.

When raising a Support case for Microsoft on the powerplatform I am - Microsoft Community

 

Regards,

Yugandhar.

JohnAG's avatar
JohnAG
Frequent Visitor
1 year ago

I initially suspected this was a UI issue, meaning the underlying objects would still be accessbible. 

However, after running the following query in Microsoft Fabric Warehouse, I received the same error message "Internal error SqlLoginFailureException."

 

SELECT * FROM INFORMATION_SCHEMA.TABLES;

 

Additionally, I attempted to create a new connection via Azure Data Studio (ADS) but couldn't see the database associated with the SQL connection string, (Note that I've had a working connection in ADS before and it was working). 

 

This is why I need to open a ticket with Microsoft Support. However, I encoutered the following issues while following your guidance: 

 

  1. I couldn't find the optiion to disconnect and reconnect the data warehouse in Fabric. I am an admin on the workspace, so I should have access to thiis functionality. Could you provide a screenshot or more specific steps on where to locate this option?
  2. Since I am not a Premier Support customer, I need to Contract ID. I reviewed the forum link you provided, but I was unable to locate it. Additionally, based on the screenshot below, it seems that both the Contract ID and the Premier Access ID are required fields. 

Right now, my priority is to restore our work ( I also tried to use the restore point option which didn't work either), as it appears that everything has been lost. Unfortunately, the process of creating a support ticket seems overly complex, vague or even intentionally difficult to navigate. 

 

I'd appreciate any additional clarification or guidance you can provide. 

 

 



  • V-yubandi-msft's avatar
    V-yubandi-msft
    Community Support
    1 year ago

    Hi JohnAG ,

    Thank you for providing the detailed information and outlining the steps you’ve already taken. I understand the urgency of restoring your data warehouse and the frustration this issue can cause.

    Please consider these steps to resolve the issue.

    1. The authentication errors in Fabric UI and Azure Data Studio might be caused by capacity or SQL endpoint issues. Please try connecting through Azure Synapse if possible. Additionally, check the Admin Portal → Capacity Settings to ensure everything is operating correctly.

    2. For failing queries, use Power BI REST APIs to verify available schemas and recover the staging schema.

    3. If restore points are ineffective, you may need assistance from Microsoft. Cloning could restore hidden objects, and revalidate connections if pipelines reference the staging schema.

    If you’re blocked by the Premier Access ID requirement, try the following.

    1. Submit a support ticket using different credentials (such as another admin account). Different accounts may have different permissions.

    2. Submit a subscription management ticket via Contact Us - Microsoft Support These tickets are available without a Premier contract and can escalate incidents internally.

    3. If your organization has an Azure support plan, it may also cover Fabric-related issues.

     

    Given the consistent authentication errors across multiple tools and the missing schema, this appears to be a backend issue requiring Microsoft’s assistance.

     

    I hope this information is helpful for you. 

     

    Regards,

    Yugandhar.