2810
asked on
Run time error 3633
Hi,
When I want to run a VB6 application on a newly installed machine, I get run-time error 3633. The application runs fine on any other machine and the new machine is properly installed (NT4 ServicePack 6)
I had a look on microsoft support
http://support.microsoft.com/support/kb/articles/Q280/5/13.ASP?LN=NL&SD=gn&FR=0
and I ran as microsoft suggests the MDAC_TYP.exe
but still I get the same error.
Microsoft mentions that if I use MDAC 2.6 or higher, I need to use the Jet redistribution pack, but I have no idea how...
Greetings,
2810
When I want to run a VB6 application on a newly installed machine, I get run-time error 3633. The application runs fine on any other machine and the new machine is properly installed (NT4 ServicePack 6)
I had a look on microsoft support
http://support.microsoft.com/support/kb/articles/Q280/5/13.ASP?LN=NL&SD=gn&FR=0
and I ran as microsoft suggests the MDAC_TYP.exe
but still I get the same error.
Microsoft mentions that if I use MDAC 2.6 or higher, I need to use the Jet redistribution pack, but I have no idea how...
Greetings,
2810
Éric Moreau
Have you runned the SETUP.EXE created by the Package & Deployment Wizard of VB? There are a lot of dependencies to install in addition to your application.
Hi!
New version of JET can be found here:
http://support.microsoft.com/support/kb/articles/q239/1/14.asp?FinishURL=%2F
If you put there a Jet redistribution pack, the setup1.exe does not have ability to launch it, need to use the setup1.vbp source code to add this capacity, that means it will execute the pathc and clean left over and temp files after.
The setup1.exe can handle install of MDAC_TYP.exe pack (if you have SP 4 or 5 installed on VB)
Similary need to make this Jet40SP5_9xNT.exe condition for the setup1.exe program, also there are different OS targetted versions of this JET, one for ME and Win2000. You shuld take care of this when you redistribute.
Matti
New version of JET can be found here:
http://support.microsoft.com/support/kb/articles/q239/1/14.asp?FinishURL=%2F
If you put there a Jet redistribution pack, the setup1.exe does not have ability to launch it, need to use the setup1.vbp source code to add this capacity, that means it will execute the pathc and clean left over and temp files after.
The setup1.exe can handle install of MDAC_TYP.exe pack (if you have SP 4 or 5 installed on VB)
Similary need to make this Jet40SP5_9xNT.exe condition for the setup1.exe program, also there are different OS targetted versions of this JET, one for ME and Win2000. You shuld take care of this when you redistribute.
Matti
ASKER
Guys,
I have not deployed or packaged anything.
I just run the application either uncomplied or compiled.
Do not know about deployment, setup and packaging...
2810
I have not deployed or packaged anything.
I just run the application either uncomplied or compiled.
Do not know about deployment, setup and packaging...
2810
You will find the "Package & Deployment Wizard" feature in the "Microsoft Visual Basic 6.0 Tools" menu. Run it and choose the Package option. Then follow the wizard. This will generate 3 files (setup.exe, setup1.lst, xx.cab) for you to run onto client PCs. This will install almost everything needed to run your application.
ASKER
Emoreau,
I will give it a try this weekend.
Cheers,
2810
ASKER
Hi,
I have used the Package&Deployment wiward and added the MDAC_TY.exe to create a set-up file. I have run it on the newly installed machine and I still get the run-time error 3633 when running my VB application. This leaves me to believe that I need to use the Jet redistribution pack.
Should I now just run the Jet40SP5_9xNT.exe on my newly installed machine, or include it in my set-up package?
Matti's comment probably has the answer, but I do not understand one bit of it...
Cheers,
2810
Hi!
Did you read the Microsoft document page?
http://support.microsoft.com/support/kb/articles/q239/1/14.asp?FinishURL=%2F
There are different, Windows version sensitive JET40 packs.
If you do make the setup toolkit (PD-Wizard) installer to launch this file, need to modify the setup1.exe program.
That setup1.vbp code is a bit mess. So i can do a few cut and paste snippets but need to know what service pack you have there on VB. That full setup toolkit project is very large and can't paste it wholly here. Most likely if you have the MDAC 2.6 it's SP5 but need to be sure.
If you look the code setup1.vbp (take backup copy before you modify it) and see the MDAC_typ.exe and how it install it you can do own modifications for Jet40SP5_9xNT.exe
Also there is functions GetWinPlatform and IsWindowsNT
To make version check for this file ME returns .9 for minor, 2000 5 for major
This 3 versions makes this modification difficult you have 3 separate versions of this file, if this setup is for endusers this probably have to do it, but if you do install it, You can just execute the JET install patch or if you have this need only for few machines this is easier solution.
Also you can lock the installer to work only on NT4. Other option is use MDAC_typ.exe version 2.5 which has JET included, but then you need reinstall your development macine.
Beware that you can't reliable uninstall MDAC 2.6 MS claims this.
What you want to do now?
Matti
Did you read the Microsoft document page?
http://support.microsoft.com/support/kb/articles/q239/1/14.asp?FinishURL=%2F
There are different, Windows version sensitive JET40 packs.
If you do make the setup toolkit (PD-Wizard) installer to launch this file, need to modify the setup1.exe program.
That setup1.vbp code is a bit mess. So i can do a few cut and paste snippets but need to know what service pack you have there on VB. That full setup toolkit project is very large and can't paste it wholly here. Most likely if you have the MDAC 2.6 it's SP5 but need to be sure.
If you look the code setup1.vbp (take backup copy before you modify it) and see the MDAC_typ.exe and how it install it you can do own modifications for Jet40SP5_9xNT.exe
Also there is functions GetWinPlatform and IsWindowsNT
To make version check for this file ME returns .9 for minor, 2000 5 for major
This 3 versions makes this modification difficult you have 3 separate versions of this file, if this setup is for endusers this probably have to do it, but if you do install it, You can just execute the JET install patch or if you have this need only for few machines this is easier solution.
Also you can lock the installer to work only on NT4. Other option is use MDAC_typ.exe version 2.5 which has JET included, but then you need reinstall your development macine.
Beware that you can't reliable uninstall MDAC 2.6 MS claims this.
What you want to do now?
Matti
ASKER
Matti,
I use VB 6.0 version 8176, and have never run any service packs as far as I know.
Just to be clear I do not want to distribute my VB apllication to the rest of the world, I just want to make it run on this ONE new PC with NT4 on.
What is this setup1.exe file?
Cheers,
2810
I use VB 6.0 version 8176, and have never run any service packs as far as I know.
Just to be clear I do not want to distribute my VB apllication to the rest of the world, I just want to make it run on this ONE new PC with NT4 on.
What is this setup1.exe file?
Cheers,
2810
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Matti,
Service pack 5 did the trick for me.
Luckily did not have to do anything with the setup1.exe...
Thanks,
Patrick
Service pack 5 did the trick for me.
Luckily did not have to do anything with the setup1.exe...
Thanks,
Patrick
Hi!
We still are in same problem MDAC_typ.exe 2.6 do not have JET engine any more.
This is the firts you have asked here
http://support.microsoft.com/support/kb/articles/Q280/5/13.ASP?LN=NL&SD=gn&FR=0
This is only about situation when you plan to use MDAC 2.6 patch only to redistribute data acces components, there was earlier recomentations to do this in MDAC version 2.5. this document now tell about problems if still do so using version 2.6
That MS document has this note:
"NOTE: MDAC 2.6 and higher no longer include the Jet engine. If you are using MDAC 2.6 or higher, you need to use the Jet redistribution pack."
To make the installer working it add's automaticly dependency files to the Wizard setup you made.
The Servive pack update now was the key in this the Wizard and it started working and make proper distribution disks, now it has taken whit those Jet and other data acces components. As it later in this thread turn out that update and bug fix has not been installed.
Matti
We still are in same problem MDAC_typ.exe 2.6 do not have JET engine any more.
This is the firts you have asked here
http://support.microsoft.com/support/kb/articles/Q280/5/13.ASP?LN=NL&SD=gn&FR=0
This is only about situation when you plan to use MDAC 2.6 patch only to redistribute data acces components, there was earlier recomentations to do this in MDAC version 2.5. this document now tell about problems if still do so using version 2.6
That MS document has this note:
"NOTE: MDAC 2.6 and higher no longer include the Jet engine. If you are using MDAC 2.6 or higher, you need to use the Jet redistribution pack."
To make the installer working it add's automaticly dependency files to the Wizard setup you made.
The Servive pack update now was the key in this the Wizard and it started working and make proper distribution disks, now it has taken whit those Jet and other data acces components. As it later in this thread turn out that update and bug fix has not been installed.
Matti