Since I've been working with an extension, I can no longer start WL7.
This message comes up:
System.Windows.Markup.XamlParseException: Durch den Aufruf des Konstruktors für Typ "WealthLab7.MainWindow", der den angegebenen Bindungseinschränkungen entspricht, wurde eine Ausnahme ausgelöst.
---> System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at System.Number.ParseInt32(ReadOnlySpan`1 value, NumberStyles styles, NumberFormatInfo info)
at System.Int32.Parse(String s)
at ProducerList.RemoveCandidate(String , ProducerList )
at WealthLab.Core.SettingsManager.Get(String key, Int32 defaultValue)
at
.
(Object , String , Int32 ,
)
at WealthLab.DataExtensions.ScannerSettingsManager.Initialize()
at WealthLab.DataExtensions.ScannerExtension.Initialize()
at WealthLab.WPF.ExtensionsFactory.Initialize(IWLClientHost host)
at WrapperProducer.PatchInterceptor(Object , IWLClientHost , WrapperProducer )
at WealthLab7.MainWindow..ctor()
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
at System.Windows.Application.DoStartup()
at System.Windows.Application.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
What can I do?
This message comes up:
System.Windows.Markup.XamlParseException: Durch den Aufruf des Konstruktors für Typ "WealthLab7.MainWindow", der den angegebenen Bindungseinschränkungen entspricht, wurde eine Ausnahme ausgelöst.
---> System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at System.Number.ParseInt32(ReadOnlySpan`1 value, NumberStyles styles, NumberFormatInfo info)
at System.Int32.Parse(String s)
at ProducerList.RemoveCandidate(String , ProducerList )
at WealthLab.Core.SettingsManager.Get(String key, Int32 defaultValue)
at
.
(Object , String , Int32 ,
)
at WealthLab.DataExtensions.ScannerSettingsManager.Initialize()
at WealthLab.DataExtensions.ScannerExtension.Initialize()
at WealthLab.WPF.ExtensionsFactory.Initialize(IWLClientHost host)
at WrapperProducer.PatchInterceptor(Object , IWLClientHost , WrapperProducer )
at WealthLab7.MainWindow..ctor()
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
at System.Windows.Application.DoStartup()
at System.Windows.Application.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
What can I do?
Rename
Please update the DataExtensions extension and ideally keep extensions up to date. This bug has been fixed since September.
https://www.wealth-lab.com/Discussion/Can-t-start-WL7-ScannerSettingsManager-7110
https://www.wealth-lab.com/Discussion/Can-t-open-WL7-Build-17B-after-a-crash-of-Scanner-dynamic-DataSet-6681
https://www.wealth-lab.com/Discussion/Can-t-start-WL7-exception-after-trying-the-Scanner-dynamic-DataSet-6708
https://www.wealth-lab.com/Discussion/Can-t-start-WL7-ScannerSettingsManager-7110
https://www.wealth-lab.com/Discussion/Can-t-open-WL7-Build-17B-after-a-crash-of-Scanner-dynamic-DataSet-6681
https://www.wealth-lab.com/Discussion/Can-t-start-WL7-exception-after-trying-the-Scanner-dynamic-DataSet-6708
I reinstalled WL7 and installed all extensions frich. Everything's okay until I install DataExtension. As soon as DataExtension is installed, WL7 can no longer be started.
You must have installed the older build of downloaded extension again.
With DataExtension Build 10 it works. WL7 can no longer be started with higher versions.
I don't know what to suggest you, DataExtensions is 12 builds away from B10 now and it works for everybody else. Try to "Open WL User Data Folder" from the WL7 File menu, then close WL7, delete Settings.txt to Recycle Bin, then restart WL7.
Eugene, maybe we can catch that exception in the stock screener and just report it to the log so WL7 can continue loading?
I noticed how topic starter was trying out different builds (including 36 and 37) yesterday without a single crash record while DataExtensions B22 requires minimum B38 of WL7.
Yesterday I was fixing a bug in CBOE provider, testing it with different regional settings including German and WL7 had no trouble starting up despite the Scanner Dynamic DataSet has been activated.
I still suggest that TS follows the procedure in Post #6 first.
Yesterday I was fixing a bug in CBOE provider, testing it with different regional settings including German and WL7 had no trouble starting up despite the Scanner Dynamic DataSet has been activated.
I still suggest that TS follows the procedure in Post #6 first.
I'll add the exception handling code then.
I deleted settings.txt and restarted WL7. Everything is okay now.
Your Response
Post
Edit Post
Login is required