Power BI error on Initilizing model

It was the 64bit version I downloaded from the site yesterday. I also tried 32bit version (similar error below) and 64 bit on different computer (but same account). Looks liek powerbi tries to load some old model and fails.

Feedback Type:
Frown (Error)

Timestamp:
2017-05-22T05:44:36.5731000Z

Local Time:
2017-05-22T01:44:36.5731000-04:00

Product Version:
2.46.4732.721 (PBIDesktop) (x86)

Release:
May 2017

IE Version:
11.1198.14393.0

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

CLR Version:
4.6.2. or later [Release Number = 394802]

Peak Working Set:
157 MB

Private Memory:
124 MB

Peak Virtual Memory:
767 MB

Error Message:
Input string was not in a correct format.

Stack Trace:
System.FormatException: Input string was not in a correct format.
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt64(String value, NumberStyles options, NumberFormatInfo numfmt)
   at Microsoft.AnalysisServices.Tabular.ImpactDataSet..ctor(DataSet data, Dictionary`2 attributes)
   at Microsoft.AnalysisServices.Tabular.ExecuteUtil.RunCommand(String commandText, IEnumerable`1 parameters, Boolean requestImpact, Int64 impactSinceVersion, Server server, ImpactDataSet& impactDataSet)
   at Microsoft.AnalysisServices.Tabular.ExecuteUtil.TryExecuteXmla(String xmlaRequest, Database db, Model model, TxManager txManager, XmlaResultCollection& xmlaResults)
   at Microsoft.AnalysisServices.Tabular.Model.SaveChanges(SaveOptions saveOptions)
   at Microsoft.AnalysisServices.Tabular.Model.SaveChanges(SaveFlags saveFlags)
   at Microsoft.PowerBI.Modeler.DateTableSubsystem.CreateDateTableTemplate(DateTableDefinition definition)
   at Microsoft.PowerBI.Modeler.DateTableSubsystem.SynchronizeLocalDateTables()
   at Microsoft.PowerBI.Modeler.DateTableSubsystem.EnableAutomaticLocalDateTables()
   at Microsoft.PowerBI.Modeler.ModelManager.EnableAutomaticLocalDateTables()
   at Microsoft.PowerBI.Client.Windows.Modeling.SchemaChangeApplier.Visit(SetTimeIntelligenceSchemaChange schemaChange)
   at Microsoft.PowerBI.Client.Windows.Modeling.SetTimeIntelligenceSchemaChange.Accept(ISchemaChangeVisitor visitor)
   at Microsoft.PowerBI.Client.Windows.Modeling.SchemaChangeApplier.Apply(IModelManager modelManager, IEnumerable`1 changes)
   at Microsoft.PowerBI.Client.Windows.Modeling.AsyncModelAuthoringService.ModelAuthoringTransaction.<>c__DisplayClass13.<ExecuteChange>b__12()
   at Microsoft.PowerBI.Client.Windows.Modeling.ModelAuthoringExceptionHandler.AddModelChangeResultToExceptions(Action action, ModelChangeResult modelChangeResult)
   at Microsoft.PowerBI.Client.Windows.Modeling.AsyncModelAuthoringService.ModelAuthoringTransaction.ExecuteChange(ModelChange modelChange)
   at Microsoft.PowerBI.Client.Windows.ReportUpgrader.EnableTimeIntelligenceAndUpdateSchema(IDataModel dataModel, IOutOfBandModelAuthoringTransaction transaction)
   at Microsoft.PowerBI.Client.Windows.ReportUpgrader.Upgrade(Report report)
   at Microsoft.PowerBI.Client.Windows.Report.Upgrade()
   at Microsoft.PowerBI.Client.Windows.Services.FileManager.OpenFile(ILiveConnectionPropertiesValidator validator, String filePathToOpen, ReportUpgradeResult& upgradeResult)
   at Microsoft.PowerBI.Client.Program.TryOpenOrCreateReport(WindowsHost windowsHost, ISplashScreen splashScreen, IFileManager fileManager, IFileHistoryManager fileHistoryManager, IPowerBIStringProvider stringProvider, String filePath, PBIWinLoadPBIAppAction loadEvent, Report& report, String& importFromExcelFilePath, String& templateFilePath, String& autoRecoveredFilePath, ReportUpgradeResult& upgradeResult)
   at Microsoft.PowerBI.Client.Program.<>c__DisplayClassd.<Main>b__0()
   at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

Invocation Stack Trace:
   at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
   at Microsoft.Mashup.Client.ClientShared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace)
   at Microsoft.Mashup.Client.ClientShared.FeedbackErrorInfo..ctor(String message, Nullable`1 errorCode, String requestId, Exception exception)
   at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()
   at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.SendAndMarshalExceptions(SynchronizationContext context, Action callback)
   at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.HandleException(Exception e)
   at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
   at Microsoft.PowerBI.Client.Program.Main(String[] args)


User ID:
ced67481-4cda-4f33-ab53-02c18c0ca522

Session ID:
4eaa62e0-3b82-438c-b1e8-bd0537afeee6

Telemetry Enabled:
True

ModelChangeResult:
{"changes":[{"setTimeIntelligence":{"enabled":true}}]}

ModelChangeResultSerializationErrors:
Error getting value from 'IsSchemaChangeListComplete' on 'Microsoft.PowerBI.Client.Windows.Modeling.ModelChangeResult'.
Error getting value from 'HasQueryImpact' on 'Microsoft.PowerBI.Client.Windows.Modeling.ModelChangeResult'.

DPI Scale:
100%

Supported Services:
Power BI