Yet Another Installation Problem

[wbear009]

After successful installation, I got the following messages:

1. The procedure entry point ?OnUnicodeSystem@@YGHXZ could not be located in the dymanic link library MSDART.DLL.

2. After clicking OK (only choice) then I got:
Unable to connect to database 'Provider=Microsoft.Jet.OLEDB.40;User ID=Admin;Data Source=c:\Documents and Settings\(my acct name)\My Documents\NinjaTrader 6\\db\NinjaTrader.mdb':Ojectspace: Connect String is Invalid - The .Net Framework Data Providers require Microsoft Data Access Componebts(MDAC). Please install Microsoft Data Access Components(MDAC) version 2.6 or later.

3. After click OK (again, the only choice), I got a rather length assertion message indicating failure at Db.Globals.Engine1 with the choices of Abort, Retry, and Ignore. None could get me anywhere.

Here's what I did:

1. Read every installation problem thread on this board.
2. Tried the following suggestions:
a) deleting the NinjaTrader.mdb
b) removing the .NET Framework 2.0 and reinstalling it
c) reinstalling MDAC 2.6 SP2, MDAC 2.6.6526.3, MDAC 2.7
d) removing and resintalling NT6
e) various order of the above suggestions

Lots of hours later: no such luck. I'm very frustrated. Please HELP!!!!!

BTW, I'm running Win Xp Pro SP2 on pretty decent hardware. I do have the old Visual Studio 6 SP6 EE installed, but couldn't imagine it would interfere with the .net stuff (or could it?).

The video demos look so cool. If only I can get it to run. Perhaps I'll consider switching to NinjaTrader from ButtonTrader.

ps: I've noticed the double \\ in the error message. Could it be...Nah!

...Source=c:\Documents and Settings\(my acct name)\My Documents\NinjaTrader 6\\db\NinjaTrader.mdb'....

Thanks in advance for your help, guys.

[NinjaTrader_Vincent]

Hi Wbear009,

Thank you for your post.

Can you please uninstall everything from NinjaTrader of your computer. Then download the latest MS Jet Database engine from here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;239114 (http://support.microsoft.com/default.aspx?scid=kb;en-us;239114)

If that doesn't work, please send a note to support at ninjatrader dot com with your phone number and some one will remote assist on Monday.

Please refer to this post.



Vince

[wbear009]

Vince, thanks for your reply.

I tried your link and the patch did not apply because I currently the lastest SP Jet Engine.

I'll try the support route as you suggested. Getting close....

[trader413]

Hi
I am trying to install Ninjatrader on another computer and I am experiencing similar problems. Can I get some assistant please. Thanks

[NinjaTrader_Jason]

Hello trader 413,

Can you please tell me what exactly happens on your end upon trying to start the software. Do you receive an error message? If so, please tell me what the error message exactly states.

Check if the machine meets the minimum requirements listed at the link below.
http://www.ninjatrader.com/webnew/support_installationguide.htm

[trader413]

I am getting these error messages.

[NinjaTrader_Kyle]

Hello trader413,

Thank you for your post.

Please send a note to Support [AT] NinjaTrader [DOT] com with "ATTN:Kyle" in the subject line. If you would include a link to this forum thread, that would be helpful.

[r2kTrader]

Hi all,

I am having the exact same problems as bear. I can't seem to get paste it.

I even bought xplite professional to take out mdac and odbc and reinstall and still no luck. (Because I tried to install Jet Pack redist as suggested before I even surrendered to coming to the forums for help and I too was told I had the latest drivers and the install wouldn't take.)

XP, SP3, all updates. Brand new install clean off a nice slipstreamed XP Pro disk.

If anyone has feedback, it would be appreciated.


Thanks,


r2kTrader

UPDATE:
I completely uninstalled .NET 3.5 and all other .NET frameworks and service packs. I completely uninstalled Ninja and deleted the directories and flushed the registry.

By the way, this is Ninja .9 version, (6.5.9 ?? the latest with the 9 in it, lol).

I then downloaded and installed the .NET framework using the link from the Ninja site and then re-installed Ninja. No luck :-(

From what I can tell, Ninja is using good old fashioned mdb files with access. As a result, my system is being asked to be supporting the technology from the 90's. MSDE? It's free and faster and would be scalable for those who like to keep daily ticks.

With NT 7 have MSDE?

Anyway, more importantly, what needs to happen in order to get live. I am trading live, so any help would be appreciated. I was hoping to be done tonight, but that's how these things go.

[NinjaTrader_RJ]

Hi,

Can you provide your trace and log files as requested in post #7?

[r2kTrader]

Hi,

Can you provide your trace and log files as requested in post #7?

RJ,

I just sent it over to your attention.

Also, I see that .10 is out, I am trying to install that now. This issue was with the .9 version, so maybe it was addressed in .10?

We'll see.


Fingers x'ing,


r2kTrader

-----UPDATE-----
No luck. Install goes through and then when it is "initializing databases"

I get the dreaded "Unable to connect to database 'Provider=Microsoft.Jet.OLEDB.4.0;' etc..... Same errors as prior poster with same screenshots.

-----UPDATE----
Took out link, it's broken. I will have to dig up the right one. So for the additional update.

[r2kTrader]

Sorry to slam this thread, but I just want to feed what I can to anyone else who might be having this issue (or will quite likely run into it)

I am referring to the Jet error on startup. I am starting to think this has to do with the .NET framework, more specifically, something with .NET 3.5 that is messing up Ninja. While I am not 100%, I would be careful about upgrading .NET until this is verified to work with Ninja. (XP PRO with SP3 is my current OS)

Hope this helps someone.

[NinjaTrader_Jason]

Hello r2kTrader,

NinjaTrader works fine on .NET Framework 3.5 SP1 on my end. I do not think your issue is related to .NET 3.5.

Please let us know the outcome of the instructions Bertrand sent you by email.

[r2kTrader]

Hello r2kTrader,

NinjaTrader works fine on .NET Framework 3.5 SP1 on my end. I do not think your issue is related to .NET 3.5.

Please let us know the outcome of the instructions Bertrand sent you by email.

Jason,

Did you upgrade your pc to 3.5 or do a CLEAN brand new install with 3.5 on there and Service pack 3 and THEN try to install NT?

I don't think it is 3.5 per se as much as it is with the mdac drivers getting upgraded and hence not allowing the legacy drivers to install. (or something like that as a "result" of the 3.5 update).

If however you had say, NT on Xp with SP2 and .net 2.0 & .net 2.0 sp1, and then you upgraded to sp3 and 3.5, etc., then NT may still work.

It's not the hardware. I tried this on 2 boxes that were running NT prior to the clean XP reinstall.

XP PRO
Slipstreamed SP3


QUESTION:
In XP, are there specific SERVICES that absolutely have to be running? For example, does NT or ODBC require Alerter? What are the raw requirements for an NT box? Not just hardward and macro specifics, but rather if you trimmed a workstation down to the absolute minimum requirements, what would it require?

Thanks,

[r2kTrader]

Jason,

I posted in another thread about MDAC and testing via the ODBC panel under the Administration panel (under control panel) and adding a DSN manually and getting a 126 error.

http://www.ninjatrader-support2.com/vb/showthread.php?p=93715#post93715

[r2kTrader]

Jason,

Can you provide the exact Jet 4.0 drivers that are being used by NT?

Also, could you provide access to those that you know are working so I can try to drop them in the system32 directory and overwrite the ones that are there now if any.

I think this is a .dll issue. Should be two files if I am not mistaken.

3.5 installs the latest service pack for MDAC and as a result it seems to make it so you can't go backwards. Had you already had the drivers you needed, they would still be there and as such 3.5 would not cause an issue.

just a VERY rough theory, trying to figure this out as I can see by the posts others have had same/like issue. Maybe this will help.

[NinjaTrader_Jason]

Hello r2kTrader,

I believe I upgraded to .NET Framework 3.5 SP1, while NinjaTrader was already installed, but closed. Note, I am on Vista.

Could you please send me your latest trace and log files as an attachment to support[at]ninjatrader[dot]com and put 'Attn Jason' in the subject header. I found a trace file section in the email correspondance with Ray, but I need the actual trace and log files as attachments.

You can find these files at the following locations:

Start Menu--> My Documents--> NinjaTrader 6.5--> Log--> log.20090511 for today. (log.yyyymmdd for any other date)

Start Menu--> My Documents--> NinjaTrader 6.5--> Trace--> trace.20080511 for today. (trace.yyyymmdd for any other date)

Am I correct, the error occurred once your upgraded to XP SP3?

I will need to contact Development regarding Jet drivers, which I will once I have your log and trace files.

[r2kTrader]

Jason & RJ,

I give up. This is not worth it. I am going to do a raw install of XP with Service Pack 2, then Install Ninja and rebuild.

It's 2009 btw, just in case NT was wondering. They have new technology for data access, lol. So frustrating when you deal with legacy applications.

MSDE as an "option" for those who like to stay a bit more current :rolleyes:

Jet 4.0? seriously.... lol.

[r2kTrader]

Hello r2kTrader,

I believe I upgraded to .NET Framework 3.5 SP1, while NinjaTrader was already installed, but closed. Note, I am on Vista.

Could you please send me your latest trace and log files as an attachment to support[at]ninjatrader[dot]com and put 'Attn Jason' in the subject header. I found a trace file section in the email correspondance with Ray, but I need the actual trace and log files as attachments.

You can find these files at the following locations:

Start Menu--> My Documents--> NinjaTrader 6.5--> Log--> log.20090511 for today. (log.yyyymmdd for any other date)

Start Menu--> My Documents--> NinjaTrader 6.5--> Trace--> trace.20080511 for today. (trace.yyyymmdd for any other date)

Am I correct, the error occurred once your upgraded to XP SP3?

I will need to contact Development regarding Jet drivers, which I will once I have your log and trace files.

Jason,

No, it's a brand new fresh clean install of XP Pro (Slipstreamed with SP3). It's an MDAC issue and there is a registration mis-match of somekind with the Jet 4.0 drivers. Can't fix it unless it is all done manually. I don't think I would consider this an NT issue as much as I would a driver mismatch / MDAC issue. In other words, the fact that NT is using legacy drivers is not a good thing, but technically NT should not be blamed. Rather if the drivers were correct, NT would run fine. On the other hand, if NT was able to run on MSDE then I wouldn't be wrestling to get legacy ODBC functionality.

There is only one solution. I need to start from the beginning. Fact is, if I can't install the access DSN from the ODBC manager in the Admin panel of XP, then NT won't run either.

It would be nice if you had a patch that included the necessary Jet 4.0 drivers as well as a script to register them. This would solve the problem and I really wouldn't worry about "breaking" anything because I can't really see many applications needing Jet 4.0, lol.

So if NT can roll a patch, great. If not, I will have to just build an XP Sp2 box, install NT, then upgrade.

Can't blame NT, only for using legacy drivers.

[NinjaTrader_Dierk]

Unfortunately there is nothing we could do at this time. Note: NT7 will come with a different DB technology (MS SQL Server Compact Edition).

[r2kTrader]

Unfortunately there is nothing we could do at this time. Note: NT7 will come with a different DB technology (MS SQL Server Compact Edition).

That's what I needed to know. MSDE is the play. I won't beat up NT for running on Jet 4.0 then ;)

In the meantime, the interim solution is a clean install with SP2, then NT, then upgrade the service packs, etc. AFTER NT has built its DSNs, etc.

This is clearly an MDAC driver issue that NT is a victim of. I would like to know what the original poster of this thread to resolve his issue, but there was no follow up :mad:

I will report back my findings as per my proposed solution.


Thanks

[r2kTrader]

Unfortunately there is nothing we could do at this time. Note: NT7 will come with a different DB technology (MS SQL Server Compact Edition).

Dierk,

Can NT "roll" a driver patch in the meantime? Just provide the needed dll files with a registration script/cmd file.

I would do it and provide it, but I don't know which dll's NT wants exactly.

[r2kTrader]

I just did a re-install of XP PRO sp2. Then dropped in .net 2.0 as per the link on the NT website.

NT is online.

I am going to burn an image from this point, and then begin the upgrade process and see if NT holds up. My guess is that SP3 slipstreamed installs the last MDAC and as such, won't let you pop in the Jet 4.0 drivers manually for the legacy applications.

If I can get to .net 3.5 and SP3 with all updates, etc. and still run NT, then I will have to assume that is the case. I will also double check my nLite setup as I may have clipped legacy drivers on my setup and as such am unable to install them after the fact due to MDAC having more recent updates, etc.

I would like to know what Bear did, does anyone have feedback?

[r2kTrader]

This was the problem for me. I am using nLite, and I must have opted out of Jet option as I couldn't think of anything that uses it anymore :rolleyes:

I have attached a screenshot for anyone else who uses nLite. If you are not familiar with nLite, you should be ;-)

Do a search for nLite in the forums, we have a nice thread going that should be of interest to traders.

I hope this helps someone.

[NinjaTrader_Dierk]

Thanks for feedback. That's the exact reason why I personally NEVER would mess with my Windows configuration/setup with tools like these...

[r2kTrader]

Thanks for feedback. That's the exact reason why I personally NEVER would mess with my Windows configuration/setup with tools like these...

Dierk,

I understand your point. It is not 1-2-3 click. You have to go through a lot of installs to know what is safe and what is not safe to remove. I took out Jet as I couldn't think of anything that could possibly use it, lol.

These boxes are going to only be used for NT, they are working great and EXTREMELY clean. Post install, my total hard drive used for System (C:) was less than 600 Meg. Total services (I let a few extra run for compatibility reasons so as to avoid having to turn them on manually when I need certain things.) Anyway, total services is less than 10 total.

My system screams and is extremely responsive. I mean RESPONSIVE.

Windows out of the box is simply unacceptable. I paid the price to get stable and it was over 3 days of tweaking and burning and installing. But now the next person already knows that he has to KEEP Jet 4.0 in there if he is to run NT.

So your first instinct is completely correct. If you are not going to see the project through, keep a stock system out of the box and avoid pain at the expense of performance. I am not into paying a plumber to cut my grass and I couldn't stand by watching the hour glass when I knew it was all because of crapware running that wasn't needed for this specific purpose.

If NT can make a section for tweaks, I can report back my findings.

By the way, I was able to do XP PRO with SP3 slipstreamed, but I didn't do ANY upgrades until .NET 2.0 (then the 2.0 SP1) was installed followed by Ninja. Then I did the upgrades and each upgrade I double checked that the ODBC was working correctly.

100% now. It should not have been an issue, but you can't take out Jet 4.0, do an up to date install, then put Jet 4.0 in after the fact without doing so manually (which I am not interested in doing ;-)


Thanks and I hope this thread helps others. I know I have benefited from others on the code side.

[NinjaTrader_Dierk]

Thanks for feedback.

>> If NT can make a section for tweaks, I can report back my findings.
I suggest opening up a new thread in this forum section reporting your findings on your endeavor.

[cricket99]

Any solution?

[NinjaTrader_Jason]

Hello cricket99,

Do you receive the same error message after a successful installation as described in post #1?

Can you please check if your PC meets the requirements listed at the link below.
http://www.ninjatrader.com/webnew/support_installationguide.htm

Did the resolution posted by r2kTrader per post #23 not solve the issue for you?