This morning VVUS says split is not found in my strategy monitor, so I went to the data and removed it. Then I keep getting this "The given key was not present in the dictionary" message.... I restarted the app and put VVUS back in.. what exactly did I corrupt ?



9/12/2018 4:01:51 AM: Symbols already up to date: AAXN,ABR,ACN,ADBE,ADSK,AIT,ALRM,AMCX,AMZN,ANGO,ARQL,ASH,ATRC,ATVI,AWI,BAC,BCC,BFAM,BNO,BR,BSX,BZQ,CALM,CATM
,CBU,CDNA,CEQP,CHEF,CIEN,CME,COBZ,CP,CRCM,CROX,CSGP,CTAS,CTSO,CVI,DATA,DECK,DIN,DNB,DPZ,DSW,EAT,ECOL,EGL,EMR
,ENS,ERI,ETSY,EXAS,FAST,FCN,FE,FICO,FIVN,FLS,FOXF,FTNT,GBCI,GDOT,GFN,GKOS,GNL,GPRK,GTXI,GWW,HBAN,HEI,HFWA,HLX,H
QY,HSC,HUM,IART,ICL,IDTI,IIN,IMMP,INGN,IQV,IT,JBHT,JWN,KEYS,KLXI,KORS,KSS,LBY,LIVN,LOGI,LPSN,LTXB,MA,MB,MCFT,MED,MEO
H,MNRO,MORL,MPWR,MRTX,MSI,MTDR,NBHC,NDAQ,NEP,NEWT,NIHD,NOA,NOW,NSIT,NTAP,NUS,ODFL,OMCL,OOMA,OSB,PAGP,PAY
C,PED,PGR,PKI,PODD,PRFT,PRO,PTC,QDEL,QTWO,RCII,REIS,RGEN,RHP,RMD,ROL,RP,RUBI,SAM,SCWX,SFNC,SIEN,SIVB,SKYW,SM
TC,SONC,SPSC,SSD,STAA,STRA,TBK,TDOC,TEUM,TIER,TMO,TPNL,TRU,TTEK,TXT,UBSH,ULTA,UNP,USM,V,VG,VMW,VRS,VSI
9/12/2018 4:01:51 AM: Symbols already up to date: AAXN,ABR,ACN,ADBE,ADSK,AIT,ALRM,AMCX,AMZN,ANGO,ARQL,ASH,ATRC,ATVI,AWI,BAC,BCC,BFAM,BNO,BR,BSX,BZQ,CALM,CATM
,CBU,CDNA,CEQP,CHEF,CIEN,CME,COBZ,CP,CRCM,CROX,CSGP,CTAS,CTSO,CVI,DATA,DECK,DIN,DNB,DPZ,DSW,EAT,ECOL,EGL,EMR
,ENS,ERI,ETSY,EXAS,FAST,FCN,FE,FICO,FIVN,FLS,FOXF,FTNT,GBCI,GDOT,GFN,GKOS,GNL,GPRK,GTXI,GWW,HBAN,HEI,HFWA,HLX,H
QY,HSC,HUM,IART,ICL,IDTI,IIN,IMMP,INGN,IQV,IT,JBHT,JWN,KEYS,KLXI,KORS,KSS,LBY,LIVN,LOGI,LPSN,LTXB,MA,MB,MCFT,MED,MEO
H,MNRO,MORL,MPWR,MRTX,MSI,MTDR,NBHC,NDAQ,NEP,NEWT,NIHD,NOA,NOW,NSIT,NTAP,NUS,ODFL,OMCL,OOMA,OSB,PAGP,PAY
C,PED,PGR,PKI,PODD,PRFT,PRO,PTC,QDEL,QTWO,RCII,REIS,RGEN,RHP,RMD,ROL,RP,RUBI,SAM,SCWX,SFNC,SIEN,SIVB,SKYW,SM
TC,SONC,SPSC,SSD,STAA,STRA,TBK,TDOC,TEUM,TIER,TMO,TPNL,TRU,TTEK,TXT,UBSH,ULTA,UNP,USM,V,VG,VMW,VRS,VSI
9/12/2018 4:01:51 AM: Error(3): The given key was not present in the dictionary.
9/12/2018 4:01:51 AM: Leaving Update Thread from catch

The only mention of the error message in the context (SM) I could find is this: Strategy Monitor Trading with Fidelity 1 minute bars, see Cone's post #13. Not sure how relevant it is in your case:

QUOTE:
Re: "The given key not present in the dictionary"
In my case, this error was caused by the symbol JWM not having updated. It failed during a Data Manager update as well. Later, an on-demand chart request cleared the error; a corrupt entry in the binary file? It's still a bit of a mystery of what precisely caused this symbol to fail update because nothing was entered in the error log.

Anyway, when you see this error, perform a Data Manager update and look at which symbol the update terminates abruptly. The next symbol alphabetically is likely the problem - try an on-demand update in a Strategy Window, or refresh it.

VVUS did have a 1:10 reverse split this week and as you might know there's live bug in the Fidelity static / fundamental provider: Open Issues > Fidelity data can not be updated except for X minute. So I'd have your VVUS data fixed first - which might make the SM issue go away.

I restarted WL a few times and the 4 time, it is up without that error.... Let me wait till market opens and see if it runs properly.. strange

Good to know. Just to make it clear: did the error message affect WLP operation or was it innocuous?

problem is back.... trying to restart again and see what happens

killed the app twice and it is fine again.. let me check what i have done before circling back to bother u

oh the error made the strategy monitor stuck... it won't run

This error hardly can make the SM stuck, it's something else. If StrategyMonitorConfiguration.xml got broken to the point of not opening the SM window, try following advice in the Wiki - close SM, delete the file, reopen SM (no need to close WLP):

Strategy Monitor doesn't work

I think it is my fault, I have some code running removing the symbol tree on the fly... did not notice it till now. Sorry

QUOTE:
I think it is my fault, I have some code running removing the symbol tree on the fly... did not notice it till now. Sorry

No problem.

I knew you're a power user. ;) For example, manually editing XML files before and now this. Knowing how creative you can get at times we might need to "discount" your problem reports. ;)