Power BI Desktop Argument is not Valid

[ashleyhand1]

I am receiving this error when I try to open my semantic model in Power BI Desktop. Please help !

Feedback Type:
Frown (Error)

Timestamp:
2024-11-21T16:43:32.5677610Z

Local Time:
2024-11-21T10:43:32.5677610-06:00

Session ID:
c8759d64-0480-4b1f-b934-5837f43054a7

Release:
November 2024

Product Version:
2.138.782.0 (24.11) (x64)

Stack Trace:
System.ArgumentException
at Microsoft.Mashup.Host.Models.Verify.Validate(IValidatable value, String argumentName)
at Microsoft.Mashup.Host.Models.Verify.Validate[T](IEnumerable`1 values, String argumentName, Boolean ensureElementsNotNull)
at Microsoft.Mashup.Host.Models.Verify.ValidIfNotNull[T](IEnumerable`1 values, String argumentName, Boolean ensureElementsNotNull)
at Microsoft.Mashup.Host.Document.JsonSerializer.DeserializeArrayOrNull[T](String json)
at Microsoft.Mashup.Host.Document.JsonSerializer.<>c__DisplayClass4_0`1.<DeserializeArray>b__0()
at Microsoft.Mashup.Host.Document.JsonSerializer.HandleDeserializationExceptions[T](Func`1 action, String json, Boolean includeValueInException)
at Microsoft.PowerBI.Client.Windows.Services.FileHistoryManager.Initialize()
at Microsoft.Mashup.Host.Models.HistoryEntryManager`1.AddEntry(T entry)
at Microsoft.PowerBI.Client.CommandLineFileService.TryOpenOrCreateReport(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, Boolean forceCreate)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass7_0.<RunApplicationLegacy>b__0()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.138.782.0","ModuleName":"Microsoft.Mashup.Document.dll","Component":"Microsoft.Mashup.Host.Document.JsonSerializer","Error":"System.ArgumentException","MethodDef":"DeserializeArrayOrNull","ErrorOffset":"29","ErrorCode":""}

InnerException0.Stack Trace:
at Microsoft.Mashup.Host.Models.Verify.NotNull[T](T value, String argumentName)
at Microsoft.Mashup.Host.Models.JsonHistoryEntry.Validate()
at Microsoft.PowerBI.Client.Windows.JsonOdspFileHistoryEntry.Validate()
at Microsoft.Mashup.Host.Models.Verify.Validate(IValidatable value, String argumentName)

OS Version:
Microsoft Windows NT 10.0.19045.0 (x64 en-US)

CLR Version:
4.8 or later [Release Number = 533325]

Peak Virtual Memory:
70.4 GB

Private Memory:
566 MB

Peak Working Set:
729 MB

IE Version:
11.3636.19041.0

User ID:
ccc1c780-f45b-4fba-b563-29fb56475202

Telemetry Enabled:
True

DPI Scale:
100%

Supported Services:
Power BI

[Anonymous]

Hi @ashleyhand1 ,

Whether your problem has been resolved? If yes, could you please mark the helpful post as Answered? It will help the others in the community find the solution easily if they face the same problem as yours. Thank you.

Best Regards

[Anonymous]

Hi @ashleyhand1 ,

Based on your description, it appears you encountered an error message when connecting to the semantic model in Power BI Desktop. Could you please try the following steps?

1. Update Power BI Desktop:

   • Ensure you have the latest version of Power BI Desktop installed.

2. Clear Cache:

   • Clear the cache to remove any potentially corrupted data.
   • 

3. Test with Another Semantic Model:

   • Try opening a different semantic model to see if it works without any error messages.

Additionally, you might find this thread helpful as it discusses a similar issue: Solved: Something Went Wrong

Solved: Something Went Wrong - Argument is not valid - Microsoft Fabric Community

The procedure that worked for me was:

 1) Create a new .pbx file

 2) Save, close and reopen that file.

 3) You will be able to open up your previews .pbx files again.

---

Best Regards

[Anonymous · Accepted solution]

Thank you for this!! I was having the same issue and about to freak out!  Reopening the file from within Power BI desktop from the recent section worked.  phew! 😅

[ashleyhand1]

same! I repoened the file from Power BI desktop and it worked.