Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Yet Another Installation Problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Yet Another Installation Problem

    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.

    #2
    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:
    [FONT='Arial','sans-serif']http://support.microsoft.com/default.aspx?scid=kb;en-us;239114[/FONT]

    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
    Last edited by NinjaTrader_VinceB; 10-27-2007, 08:11 AM.
    Vince B.NinjaTrader Customer Service

    Comment


      #3
      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....

      Comment


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

        Comment


          #5
          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.

          Comment


            #6
            I am getting these error messages.
            Attached Files

            Comment


              #7
              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.
              KyleNinjaTrader Customer Service

              Comment


                #8
                ODBC Jet Problems during fresh install

                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.
                Last edited by r2kTrader; 05-10-2009, 06:31 PM.

                Comment


                  #9
                  Hi,

                  Can you provide your trace and log files as requested in post #7?
                  Ray S.NinjaTrader Customer Service

                  Comment


                    #10
                    Originally posted by NinjaTrader_RJStein View Post
                    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.
                    Last edited by r2kTrader; 05-10-2009, 10:07 PM. Reason: Updating - Tried additional things.

                    Comment


                      #11
                      Jet 4.0 Error on Startup

                      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.

                      Comment


                        #12
                        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.

                        Comment


                          #13
                          Originally posted by NinjaTrader_Jason View Post
                          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,

                          Comment


                            #14
                            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.

                            Comment


                              #15
                              Jet 4.0 Drivers

                              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.

                              Comment

                              Latest Posts

                              Collapse

                              Topics Statistics Last Post
                              Started by argusthome, 03-08-2026, 10:06 AM
                              0 responses
                              106 views
                              0 likes
                              Last Post argusthome  
                              Started by NabilKhattabi, 03-06-2026, 11:18 AM
                              0 responses
                              54 views
                              0 likes
                              Last Post NabilKhattabi  
                              Started by Deep42, 03-06-2026, 12:28 AM
                              0 responses
                              36 views
                              0 likes
                              Last Post Deep42
                              by Deep42
                               
                              Started by TheRealMorford, 03-05-2026, 06:15 PM
                              0 responses
                              38 views
                              0 likes
                              Last Post TheRealMorford  
                              Started by Mindset, 02-28-2026, 06:16 AM
                              0 responses
                              74 views
                              0 likes
                              Last Post Mindset
                              by Mindset
                               
                              Working...
                              X