Solved

Explanation required on SETUP and DEPLOYMENT ERRORS

Posted on 2004-04-25
7
475 Views
Last Modified: 2013-12-25
I've written and completed my very first application using VB6.0  as front-end and XPAccess as back-end Dbase. I used ADO technology for the Dbase access and manipulation and also DBGrid for viewing of query results.

The application will need to be installed on 6 client PC's. I've used the package and deployment wizard to create an installation package. Now when installing on the first client PC, I encounted the following errors;

1. VB 6.0 setup Toolkit:Setup1.exe - ordinal NOT found " The ordinal 17 could not be located in the dynamic link library MAPI32.dll.

2. An error occured while registering the file 'C:\windows\system32\MSEXCH35.dll'

3. An error ossured while registering the file 'C:\windows\system32\MSADO20.tlb'

What do the errors mean and how do I go about correcting/fixing them?
0
Comment
Question by:DVEAPI
7 Comments
 
LVL 53

Accepted Solution

by:
Dhaest earned 250 total points
ID: 10915545
First try to solve the third problem. Possible that all your problems are solved then.
3) When installing VB progs on win2000 i'm getting :
"Error While Error While registering MSADO21.tlb"

--> The only way you can fix it is to distribute and run MDAC_TYP.EXE manually before your setup and ignore the error while the setup is running.
more info on data access components here
http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28001860


Otherwise it's possible you have to do install dcom98 also
1-2) Try to install DCOM98.exe (a sure requirement of ADO).
(http://www.microsoft.com/com/dcom/dcom98/dcom1_3.asp)
0
 
LVL 18

Expert Comment

by:Sethi
ID: 10915578
1 and 2 points to the fact that you are using Microsoft Outlook library. In case yes then you can't distribute Microsoft Office files and the user need to have them installed on theirmachines.

3. as Dhaest points correctly, is due to MDAC not being on the client machine. Install MDAC 2.7 Refresh or 2.8 from Microsoft's site and it will solve the problem.
0
 
LVL 1

Expert Comment

by:Idarac
ID: 10924275
If you are using the VB 6.0 deployment wizard do not use it on WIndows XP. You will run into problems.

I keep a machine here with Windows 98 and VB 6.0 for doing my packaging.
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

Author Comment

by:DVEAPI
ID: 10924721
But I'm using a Windows XP machine for my development work and packaging. What other problems are yu exactly referring to?
0
 
LVL 1

Expert Comment

by:Idarac
ID: 10927848
Just the kind of errors you having.

OCXs and dlls not registering.

In fact it was a chore to go back and dig out the installed files on XP.

I didn't go any further investigating why the files would not install using the XP install as I had windows 98 another computer so I keep it just for VB 60 and deploying.

I don't know of anyone who actually got the deployment to work using XP and I can't say why it won't work.
0
 

Author Comment

by:DVEAPI
ID: 10936292
Thanks to you all for your contributions towards my problems. I've eventually got my application installed successfully on 1 client machine which is also a XP machine. How? I downloaded the updated MDAC file from Microsoft site as adviced, installed it on my PC, LAN and the client PC. Deleted the old package from my PC, created another executable file, and rerun the package wizard for a new installable package. Went to the client PC, uninstalled the first application and reinstalled and guess what?. It worked. But I made sure to download the new executable file as well that got it working from my PC to the Client PC over the LAN.

Thanks again. This is a great site.
0
 

Author Comment

by:DVEAPI
ID: 10983547
A very big thankyou to the helpful suggestions. Those were greatly appreciated.
It has now opened up my understanding of what to look out for in similar situations in future.

Rgds,
Dairi
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction I needed to skip over some file processing within a For...Next loop in some old production code and wished that VB (classic) had a statement that would drop down to the end of the current iteration, bypassing the statements that were c…
Most everyone who has done any programming in VB6 knows that you can do something in code like Debug.Print MyVar and that when the program runs from the IDE, the value of MyVar will be displayed in the Immediate Window. Less well known is Debug.Asse…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question