Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
NT7 cannot run in virtual machine with networked Documents folder?
Collapse
X
-
-
Originally posted by dolomite View PostIs there a known limitation where NT7 cannot run when the Documents folder sits on a network share or on a non-NTFS filesystem?
However, thanks to Koganam's suggestion, surfing through the Google results found me this link.
That link implies that:
SQL CE 3.5 SP1 supports network shares: No
SQL CE 3.5 SP2 supports network shares: Yes
SQL CE 4.0 supports network shares: No
As it turns out, I actually have SQL CE 3.5 SP2 installed (see attached screenshot) and have had it installed from the very beginning. I specifically installed SQL CE before installing NT7, due to some other issues.
I would suggest you completely uninstall NT7, remove the "Documents/NinjaTrader 7" folder to remove all user settings, then first install SQL CE 3.5 SP2, per instructions here, then install NT7.
In that case, using NT7 specifically with SQL CE 3.5 SP2, I wonder if you'd still have the same issues ...
Comment
-
Originally posted by bltdavid View PostIs that what the OP did?
Comment
-
Originally posted by koganam View Post... the UNC name provided by "Shared Folders" means that it is probably just Samba net sharing under the covers anyway.
I mean, Microsoft invented SMB anyways, so why would a SMB share necessarily be that different than a local NTFS volume?
Answer: they're probably not.
I suspect most differences regarding local vs shared are builtin into the high level app, for other high level reasons. Aka, it's a product design and/or marketing decision.
Case in point: SQL CE seems to have a specific issue, perhaps with memory mapping files located in a SMB share -- but then how could SQL CE 3.5 SP2 ever have worked? I submit the not-working issue really isn't technical one, but an artificial constraint builtin to SQL CE on purpose. (Which is fine, it seems MS wants you to move to SQL Express Edition if this constraint in SQL CE matters to your product.)
[Edit: Yes, I know a product constraint is just as real to users as a technical one. I'm just pointing out the distinction because the approach to a workaround solution varies based upon knowing if it is a product vs technical limitation.]
It's very curious that SQL CE 3.5 SP2 is reported to be a "one-off" from the high-level constraint of network drives not supported by SQL CE. Strange, don't you think?
But, hey, if it works, it might solve the OP's problem.
Comment
-
-
Originally posted by bltdavid View PostExactly!
I mean, Microsoft invented SMB anyways, so why would a SMB share necessarily be that different than a local NTFS volume?
Answer: they're probably not.
I suspect most differences regarding local vs shared are builtin into the high level app, for other high level reasons. Aka, it's a product design and/or marketing decision.
Network drive mapping was only later shoe-horned onto TCP/IP, after Microsoft was dragged kicking and screaming into the standardized wide-area networking world when they finally put it in Windows for Workgroups (I believe as late as version 3.11; it was a separate addon installation in earlier versions.)
There is then a translation layer that handles the packet format and translates it to hard-disk file semantics. So no, they are very different beasts.
Then, of course, there are also security permissions, separate for network access and file access, and ACL and other such arcana.
Comment
-
-
Originally posted by bltdavid View PostI just completed some initial testing.
Conclusion: Using MKLINK with SQL CE 3.5 SP2 is not a solution.
See attached screenshot.
Comment
-
Originally posted by koganam View PostSymLinking the NT data folder does work on local drives. As expected, if fails if you try to do it onto a networked drive.
Specifically, NinjaTrader suffers from the limitation builtin to SQL CE.
My testing tells me:
It is the fault of SQL CE 3.5 SP2 not supporting symlink'ed network shares that makes the access of the db\NinjaTrader.sdf fail. The MKLINK command doesn't hide anything from SQL CE, so it seems.
[But the symlink to the network share itself, in all other respects, seems to work perfectly fine. That is, MKLINK command succeeds, Windows explorer works fine, etc.]Last edited by bltdavid; 06-18-2016, 12:18 AM.
Comment
-
Originally posted by bltdavid View PostYes, but to be clear, the underlying act of symlinking works great with networked drives.
Specifically, NinjaTrader suffers from the limitation builtin to SQL CE.
My testing tells me:
It is the fault of SQL CE 3.5 SP2 not supporting symlink'ed network shares that makes the access of the db\NinjaTrader.sdf fail. The MKLINK command doesn't hide anything from SQL CE, so it seems.
[But the symlink to the network share itself, in all other respects, seems to work perfectly fine. That is, MKLINK command succeeds, Windows explorer works fine, etc.]Last edited by koganam; 06-18-2016, 07:22 AM.
Comment
Latest Posts
Collapse
Topics | Statistics | Last Post | ||
---|---|---|---|---|
Started by cmtjoancolmenero, Yesterday, 03:58 PM
|
6 responses
28 views
0 likes
|
Last Post Today, 08:55 AM | ||
Started by gbourque, Today, 06:39 AM
|
2 responses
14 views
0 likes
|
Last Post
by gbourque
Today, 07:05 AM
|
||
Started by rexsole, Today, 08:39 AM
|
0 responses
4 views
0 likes
|
Last Post
by rexsole
Today, 08:39 AM
|
||
Started by trilliantrader, Yesterday, 03:01 PM
|
3 responses
31 views
0 likes
|
Last Post Today, 08:28 AM | ||
Started by Brevo, Today, 01:45 AM
|
1 response
14 views
0 likes
|
Last Post Today, 08:14 AM |
Comment