I am running WL 6.9.20.7 on Win 10. I am running the strategy monitor for 3 real-time strategies with streaming data (Fidelity) enabled during the trading day.
Recently the WL program quits without notice. I'm not sure if this coincided with the most recent update, but I never had this problem before. I don't see it happening, I just notice it's no longer running, Typically, it is when I return to my computer after being away for a period of time. During my away time, the PC doesn't sleep, but screens go dark. Restarting WL works OK as if nothing happened.
Are there other reports like this or troubleshooting tipst o point me to? Any way to get WL to send an email alert when it shuts down?
Size:
Color:
Apparently WLP crashes. Are there any records in the Windows Event Log about the WealthLabPro.exe crash?
It won't hurt to enable logging for the SM as per:
Does Strategy Monitor log errors? Note that this step has to be performed every time.
You might also want to enable Wealth-Lab's logging (once, and disabled after producing a useful report):
Accessing Wealth-Lab Error LogHow many Alerts are there in the SM at the moment? WLP is known to become sensitive to a very high number of Alerts.
There are too many unknowns at the moment but my primary suspect would be your Strategy code. Firstly I would back up StrategyMonitorConfiguration.xml (how big is the file?) and start a clean workspace, then add one instance of some canned Strategy like "Moving Average Crossover" to the SM. If it runs fine I'd investigate your Strategy code in the context of the data and settings it's applied to.
Size:
Color:
QUOTE:
Any way to get WL to send an email alert when it shuts down?
WL wouldn't be able to do it since the program is quitting unexpectedly.
In the past we've seen Wealth-Lab quit unexpectedly if left running overnight. But for you, does this occur during the market session?
Size:
Color:
After setting it up, I actually saw this in QA too. We're looking into it!
Size:
Color:
@Cone. Thank you. Yes it happens during the day. (Just happened again a little while ago.) Would the steps that @Eugene suggested in post #2 above still be helpful to your investigation, or should I hold off until I hear from you?
Size:
Color:
@Eugene
QUOTE:
Are there any records in the Windows Event Log about the WealthLabPro.exe crash?
Don't see any errors that call out WL. Logged one .net error in past 7 days, but I had many more crashes than that. I do have a number of DistributedCom errors; not sure if they are relevant to WL.
Size:
Color:
Thank you but don't worry. I think we have a lead on it already.
Size:
Color:
@Cone Have you been able to identify the cause? I am still experiencing the problem.
Size:
Color:
We're actively looking at it, don't think the crash is related to the S. Monitor, but haven't found the smoking gun yet.
Size:
Color:
@Cone Does it appear that this problem was introduced with the latest update? It seems the problem starting happening around the same time. If so, it is possible for me to revert to previous version to eliminate the problem?
Size:
Color:
Size:
Color:
Besides what Eugene pointed, it seems as if the crash that we've seen in development was traced to changes introduced in the build that we're working on now (6.9.21). Once that's fixed we'll be trying to reproduce what's occurring to you.
Size:
Color: