Forum Discussion

JaviGolden's avatar
JaviGolden
Frequent Visitor
1 year ago
Solved

Lakehouse sql error

Any query I'm trying to run using the lakehouse sql analytics endpoint is returning this error:

 

Value cannot be null. Parameter name: g

 

Any ideas?   They were all working fine a few hours ago.  

  • This was a server side error (per microsoft) that corrected itself.

4 Replies

  • Hello JaviGolden 

     

    The error it self saying value cannot be null.

     

    • Make sure that all valuees in your query are cleaarly set and not empty. this includes any variiables or inputs your query depends on.
    • Occasionally, restaarting the services or tha Fabric lakehouse setup can fix temporary problems.
    • If you recently changed ur lakehouse setup or queries, undu those changes to check if the error still happens.

     

    If need more info pls visit below links. It might helps you

    How to fix the error - "Value cannot be null. Parameter name: format" - Microsoft Q&A

    Solved: Failed to access/connect to Lakehouse SQL Endpoint... - Microsoft Fabric Community

    Solved: Re: Not able to connect to Lakehouse SQL endpoint - Microsoft Fabric Community

     

     

    Thank you!!

  • v-veshwara-msft's avatar
    v-veshwara-msft
    Community Support

    Hi JaviGolden

    Thank you for reaching out.

    This error is typically caused by an internal reference issue within the SQL analytics endpoint  often linked to object metadata (e.g. missing or corrupted table/view references). Based on the nature of the error, this is very likely a service-side issue. We recommend waiting a short while and retrying the query, as such issues are often transient.

    If the issue still persists, please try the following steps in addition to those suggested by suparnababu8.

    1. Run a metadata query to validate object availability:

      SELECT * FROM INFORMATION_SCHEMA.TABLES;

      If this query fails, it may indicate a broader metadata or synchronization issue.

    2. If there were recent deletions or renames of tables/views, reverting them (if possible) may help.

    3. If available, try running a simple query in another Lakehouse to isolate whether this issue is specific.

    If the issue continues, please consider raising a support ticket using the following link: Microsoft Fabric Support and Status | Microsoft Fabric

    Please reach out for further assistance.
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.

    Best regards,

    Vinay

  • JaviGolden's avatar
    JaviGolden
    Frequent Visitor

    This was a server side error (per microsoft) that corrected itself.

    • v-veshwara-msft's avatar
      v-veshwara-msft
      Community Support

      Hi JaviGolden ,
      Thanks for taking time and sharing that its a server side issue and corrected itself.
      Would you mind marking any helpful reply or yours as "Accepted solution" for other members who come across this thread to find the solution quickly.
      Thank you.