Stage signals error
Author: Gamba
Creation Date: 4/8/2013 2:13 AM
profile picture

Gamba

#1
I created a system in my private sandbox and wanted to stage a signal. I get the message: "TradingSystem "" not found".

Setup and username are correct, I can see my system and uploaded the backtest-results.

Hint: First I created the assignment to the system on another pc. This morning I tried to upload signals
from my main pc (physically another computer). I guess this causes the error. Is the system assignment based on a special pc? Sometimes I want to upload signals from pca 1 sometimes from pc2. It depends of my current working location.
profile picture

Eugene

#2
No, assignment is not tied to PC - but a) WSP's configuration files and b) Strategy's XML file must be identical for the trick to work on both PCs.

Reopen the Strategy window and try again. Did it help? If not, make sure that:

1. The 2nd PC contains the files WealthSignalsConfig.xml in WealthSignalsLinkedAccounts.xml copied from your first PC in Wealth-Lab's AppData folder (see the Wealth-Lab User Guide > Data > “Where data are stored?” for the exact placement), and
2. The copy is fully identical with the source
3. Your strategy file has the same GUID on 2nd PC. This requirement means that the strategy's XML file must be copied in its entirety and w/o modification. (The WealthSignals Publisher looks up a Wealth-Lab Strategy's unique identifier in its XML file on disk and uses it for linking to a WealthSignals Trading System account).
profile picture

Gamba

#3
I copied the xml-Files, but I cannot stage the current signals because market time is after 9:25 EST.
I will try it the next days, whith new signals.
profile picture

Eugene

#4
You can still try it out today w/o risk. OK through the time warning, if you get a different response from server (like Failed), then probably your system could be "found" this time.
profile picture

Eugene

#5
I can suddenly reproduce the error. Presumably something has broke on our end. If it is, we'll fix ASAP.
profile picture

Gamba

#6
Ok, Eugene. Today there are no new signals for the system. I'm not able to stage something. Maybe tomorrow.
profile picture

Eugene

#7
It's recommended that you post NST status in the WSP today. If it works, the problem is gone.
profile picture

Eugene

#8
Looks like you were able to claim NST successfully.

For me, the "Not found" error was also gone for good after having restarted Wealth-Lab. Go figure.
profile picture

Gamba

#9
No, I tried it yesterday from website directly and it worked for me.
Today there are still no new signals and I tried send the NST state, but the error still occured on my 2nd PC.
Pleas see attached screenshot. I already have copied the XML-Files from the first one.

Ok, after an additional restart of WL it works and it says: "NST status claimed".
Hope that after signals occur the next days it will still work for me :-)
profile picture

Eugene

#10
Right now it's not clear what may be causing this intermittent error for you but thanks for the heads-up. Time will tell.
profile picture

Gamba

#11
Hi Eugene, the error occurs the last two days again and I guess I can reproduce it today.

First of all my Wealth-Lab instance runs the whole week without restarting, normally.
The Strategy Monitor (SM) is open the whole uptime and since this week, in addition, the strategy for WS
is open the whole time. Every morning the SM runs and generates signals for for some strategies,
including the strategy for WS. A couple of hours later I have to run the strategy for WS in backtest-mode
again, to get new signals and the error, posted above, occurs. I am not able to stage signal, because
the system was not found.

First of all a restart of WL works, and after rerunning the strategy for WS I can stage the signals.
This morning I closed the SM not the wohle WL instance and after a new run of the WS strategy
I am able to send the signals. No restart is required, but I have to close the SM. Please try to reproduce it.

That is some additional work every morning, so I hope you are able to reproduce and fix the problem.
profile picture

Cone

#12
It sounds like you're on to something, but it's hard to see the connection. I tried running the SM before sending my test signals today, but still I have never seen the problem
profile picture

Eugene

#13
Basically, Trading System "" is failure to find the GUID of the Strategy.

Performance visualizers are not executed in the SM at all. Closing or starting the SM has no effect on a Strategy. There's no conflict, it's merely a coincidence. Couldn't repro that.

Another factor is that I'm already running a WSP beta version with dozen of fixes so it's comparing apples to oranges. Version 2013.04 will be included in Wealth-Lab Developer 6.4.62 patch build shortly.

For months, I've been running up to a dozen systems for testing purposes every morning, and haven't had this error - until April 9 when I supposedly could've done something in order to reproduce your issue. However, I usually never leave those WS strategies open - there's a saved workspace window to save time and effort.

I think there may be an error in your XML config file e.g. a duplicate entry. Let's reset it:

1. Please close Wealth-Lab,
2. Find your user data folder,
3. Remove the WealthSignalsLinkedAccounts.xml file,
4. Start WL,
5. Open your WS strategy and re-assign it to the "Undertaker" system,
6. click "Save" in Setup,
7. then close the WS strategy
8. and reopen it.

P.S. Does the error appear on your Server 2003 VM (end of life in 2010 according to Microsoft) or on Win7 PC?
profile picture

Gamba

#14
The error appears on Windows 2003 Server, the 2nd PC. I guess the setup process on the other PC
and then staging signals on the Window Server leads to the problem.

I will try to rest the XML config at the weekend and will give feedback on monday, when new signals
or stop-signal for current signals occur.
profile picture

Eugene

#15
No, it can not be caused by that because Strategy assignment one one PC does not affect another PC. They're configured individually. So it's something related to your Server 2003 virtual machine. Attaching the WealthSignalsLinkedAccounts.xml file might help shed some light on it. For example, there can be duplicate assignment within the config file (just a guess).

Before testing, please download and upgrade to Wealth-Lab Developer 6.4.062 (already available) that includes the latest WSP build 2013.04.
profile picture

Eugene

#16
WSP 2013.04 that comes with Wealth-Lab Developer 6.4.062 (already available) won't fix it, and configuration file is not the culprit. As a workaround, you can close and reopen the Strategy window.

Seems like I have a clue as to what might be going wrong when you see this error. Let's see if I'm able to fix it for 2013.05.
profile picture

Gamba

#17
Ok, I did an upgrade of the WealthSignalsLinkedAccounts.xml. I will try it on monday.
BTW: I saw that the GUID on the 2nd PC is another than on the initial one. Hope that reassigning the strategy fix this issue.
The strategy-code has changed on the 2nd PC in one row, so I guess this causes the new GUID.
profile picture

Eugene

#18
Unfortunately, the problem is unlikely to be fixed by reassigning. While waiting for the fix, reopening the Strategy window (or restarting WL at worst) should work though.