v8.0.27 Removes Workspace Indicators

[Lancer]

Installed v8.0.27 to the new Program Files location, rebooted, opened Control Center, connected data, then opened a workspace. On charts, no indicator panels or indicators now exist that were there previously prior to v8.0.27. Only the price panel remains on charts. At Chart > Indicators > Configured, only some price panel indicators remain listed, and no indicator panel indicators.

Looking at the Indicators > Available list, only standard NT system indicators exist. None of my previously listed custom indicators are even listed now as available. Tried two other workspaces, and same result. Also tried applying a pre-v8.0.27 chart template to a newly created chart, and same result - all custom indicators are gone.

So, v8.0.27.0 has stripped all custom indicators from every workspace, including removing them from the Indicators > Available list. Seeing this problem, I did not save the workspace when closing, and looking in the workspace .xml file, I see that the indicator names and properties are all still there. I have backups, and will be rolling back to v8.0.26.

So, v8.0.27 gets a NO vote from me. It was a 7 month wait for this v8.0.27 update, and it fails in both value of feature improvements and quality.

Edit: Looking at the log file, after the "Restoring workspace <workspace name>" line, there are a string of "Failed to restore Indicator" lines. For example: "<Date, Time> |3|16|Failed to restore Indicator 'NinjaTrader.NinjaScript.Indicators.<indicator name>. Most likely (a) the implementation changed or (b) one or more properties have been renamed or removed or (c) the custom assembly which implements this Indicator no longer is there." Looking at the trace file, the same lines print, same text, but with "ERROR:" designation.

The process producing the Failed to restore indicator messages repeats continuously, filling the log and trace files with messages that cycle through all indicators that failed to restore, again and again. This continuous cycle apparently puts NinjaTrader in a frequently Not Responding state per Task Manager, and requires an End Task action if NinjaTrader cannot be closed normally.

Any quick solution ideas before I roll this mess back to v8.0.26?


v8.0.26 Install location: C:\Program Files (x86)\Securities\NinjaTrader 8
v8.0.26 Folders/Files location: C:\Users\<UserName>\Documents\NinjaTrader 8

v8.0.27 Install location: C:\Program Files\Securities\NinjaTrader 8
v8.0.27 Folders/Files location: C:\Users\<UserName>\Documents\NinjaTrader 8

[brucerobinson]

still on r26.0
Ninjagarbage
#Fightback
#Zerotolerance

[Lancer]

Fix ideas, anyone?

[brucerobinson]

#Lancer - I may be wrong on this - but if it sounds like may be in the ballpark....
Someone had their Documents folder in a non-default location (on their OneDrive, but not Default) and couldn't find the path to it so I chimed in to identify path.
That might not specifically be your issue (as in, you may know where your Documents Folder resides) but I think the gist is the new 64bit Installer now located in \Program Folder will be looking for your 'customs' in the Default Documents\Ninjatrader 8 installer location, and if that is not where yours were with 26.1 it will come up empty-handed. So either move them from where they were with 26.1 to where 27.0 is looking for them, of tell 27.0 to look for where you like to keep them when you install it.

Sounds like something like that, anyhow., would fit with the error messages
Can't help on specifics of doing that as I'm a SimpleHuman who can only cope with Defaults.

Best,

[Lancer]

That was my thought, that v8.0.27 failed to pick up the existing paths to indicators. And who knows what else it missed. I'm not sure where to check it, and we users should not have to be doing this anyway.

Edit: Checked in Config.xml, and nothing indicative in there.

[brucerobinson]

hmmm, curiouser and curiouser.
Indeed, reminds me why I'm a vXX.1 kinda guy hehehe
Sorry couldn't help
A further thought - and I'm running blind 'cos haven't touched 27 yet - and you've probably had it anyhow but you did ask....
So you're saying (from paths above) 64bit only is the same as 32 insofar as where it puts User and non-core platform program files i.e. Docs\Ninja folder?
I don't know that is not the case, I'm just throwing out ideas in the absence of any response from Support who should have better insight (although I can't actually recall the last time I didn't have to fix my own (or rather I should say NT's) problem :-)) and don't know what you've already tried.
Are you certain 64 is using that folder, or does it just 'look like it' because it is still there from before and could be a new one elsewhere you haven't spotted?
Regardless, I wonder if it might be worth removing your 'old' Docs\Ninja folder altogether and forcing the new Install to create its own new one (thus seeing that it does and it is in that location), and then putting your custom indies into it etc after seeing it created but before launching Ninja for the first time? Then, you would know it is looking in there and finding its own indies and workspaces, but not finding yours

Don't mean to offend if you've tried all this sort of stuff, just ideas

[Lancer]

v8.0.27 is using the same Documents folders as existed with v8.0.26, with no other new set elsewhere. Some changes of course, for example, some new files and new file dates, and the NinjaTrader 8\cache folder was cleaned out, now empty. But all the preexisting custom indicator .cs files appear to still be there at bin\Custom\Indicators. Preexisting custom Ninjascript .zip files are all there in the NinjaScript folder. So, really no reorganizational change at all in the Documents folder. Still, something has changed or failed significantly because when v8.0.27 opens a workspace, it just completely fails to restore the custom indicators, and who knows what else is not right.

I continue to wonder what troubleshooting advice NT support staff might have to contribute here.

[DTSSTS]

Lancer please keep us updated here, I am a Vendor and have not installed .27 either, fearing something similar

[hedgeplay]

Still, something has changed or failed significantly because when v8.0.27 opens a workspace, it just completely fails to restore the custom indicators, and who knows what else is not right.

Hi Lancer,

Just an FYI. The loss of indicators happened to me on the last major upgrade.

TLDR: Check your log and trace files for compile errors.

We need the NT team to keep the underlying platform rolling forward to newer Microsoft standards and dependent Dlls so NT8 will remain viable on our microsoft clients. That caused some breaking changes within the 0.27 release.


Likely either:
1) you just need to recompile. Compile, exit and restart..

2) your indicators need to redesigned to become compatible with the breaking changes in the 0.27 release (check the release notes)

3) your indicators (including third party indicators) need to redesigned to become compatible with changes to the NT8 internal platform dependent dlls or compile settings.

Hedge

[Lancer]

Pre v8.0.27 custom Indicators, BarsTypes, etc. are on the list in v8.0.27 NinjaScript Editor, so at least v8.0.27 is aware of them. However, recompile attempts fail with these same errors for every file selected to recompile:

NinjaScript File: <none>

Error:
Metadata file "C:\Program Files (x86)\Securities\NinjaTrader 8\bin64\InfragisticsWPF4.DataPresenter.v15.1.dll" could not be found.
Metadata file "C:\Program Files (x86)\Securities\NinjaTrader 8\bin64\Infralution.Localization.Wpf.dll" could not be found.
Metadata file "C:\Program Files (x86)\Securities\NinjaTrader 8\bin64\NinjaTrader.Core.dll" could not be found.
Metadata file "C:\Program Files (x86)\Securities\NinjaTrader 8\bin64\NinjaTrader.Gui.dll" could not be found.
Metadata file "C:\Program Files (x86)\Securities\NinjaTrader 8\bin64\SharpDX.dll" could not be found.
Metadata file "C:\Program Files (x86)\Securities\NinjaTrader 8\bin64\SharpDX.Direct2D1.dll" could not be found.

Code: CS0006

Line: 0

Column: 0

In Errors above, the paths are to locations where v8.0.26 was previously installed in Program Files (x86) prior to installation of v8.0.27 in Program Files.

[brucerobinson]

So combining Hedge & Lancer feedback it appears there are ‘code-breaking’ changes in the shift to SQLite.

“We need the NT team to keep the underlying platform rolling forward to newer Microsoft standards and dependent Dlls so NT8 will remain viable on our microsoft clients. That caused some breaking changes within the 0.27 release.”

I would of course agree with sentiment - but it is how you go about that. Not being a vendor or developer I’m not familiar with the communications that go on between NT and their vendor partners with such releases, but very bitter experience has shown me when I see NT embarking on such it will in all likelihood be poorly executed. As soon as I read in the Release Notes it’s a case of ‘here we go, buckle your seatbelts…’

As a User, there is no advisory in the Release Notes to warn this release may break third party indicators, check with vendors, may have to recompile etc.

Even with my limited knowledge I could surmise something was likely still pointing to an _86 directory. Whichever way you look at it this is simply poor forethought and rollout planning, especially when the product/business model relies on third-party add-ons to be anything like fit-for-purpose.

Just chuck it out there and let the carnage ensue….

And not a word from ‘Support’

Still on 26.0

#Fightback
#Zerotolerance

[hedgeplay]

Pre v8.0.27 custom Indicators, BarsTypes, etc. are on the list in v8.0.27 NinjaScript Editor, so at least v8.0.27 is aware of them. However, recompile attempts fail with these same errors for every file selected to recompile:

Error:
Metadata file "C:\Program Files (x86)\Securities\NinjaTrader 8\bin64\InfragisticsWPF4.DataPresenter.v15.1.dll" could not be found.


In Errors above, the paths are to locations where v8.0.26 was previously installed in Program Files (x86) prior to installation of v8.0.27 in Program Files.

Right.. In the Release Notes (have a look) breaking changes "C:\Program Files (x86)" moved to C:\Program Files ..


So in the NT8 NinjaScript code editor right click and tap "References." Delete all references to C:\Program Files (x86)\ and replace them with the same files under C:\Program Files. IF you actually need to add references for the default NT8 libs.

Press F5 in the Ninjascript Editor to recompile. Exit NT8 and come back in again and look to see if any error messages remain in the log.. rinse and repeat until done.

Hedge

[Lancer]

Hedge, that was the problem. The v8.0.27 installer did not remove those six references to the old v8.0.26 Program Files (x86) location, although it did remove all the actual files. The installer did create new references to the same files installed at the new Program Files location, but it also kept the old references as well. So, after I manually deleted the six old x86 file references, compiled only once, exited, restarted, and opened a workspace, all appears to be working normally at this point, with all custom indicators restored. So, it turns out to be an easy fix, but the v8.0.27 installer should have done those deletions. NT Support staff, if you ever get around to reading this thread, there is a bug fix to include in v8.0.27.1.

Thanks brucerobinson, DTSSTS, and hedgeplay for the replies and assistance!

[timko]

Time and again, it confirms to me, we are indeed the UAT team or Quality Assurance team of Ninja.
To be honest, I feel sick of it.....

[FMtrader]

Think I will simply wait for 27.1 and hopefully avoid this rubbish. The novelty of spending hours sorting this type of stuff out is also wearing very thin on me.