• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 475
  • Last Modified:

moving visual basic program to window server 2003

moving a vb application to window server 2003.  Installed visual studio 6 on the window server 2003 so it have the same references as on my workstation.  When it runs, it fails because "ActiveX Component can't create object   RunTime Error '429'
The problem is in the DTS.package code - it fails at the last statement "Set goPackage = goPackageOld "
---------------------------------------------------------------------------------------
Option Explicit
Public goPackageOld As New DTS.Package
Public goPackage As DTS.Package2
Public Sub datapump()
        MsgBox "datapump started1"
        Set goPackage = goPackageOld
0
phiadmin
Asked:
phiadmin
  • 3
  • 3
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
Need to check the references.   Just because you installed VB6 doesn't mean you have all the DLLs or type libs that a project may reference as they may be from other installs and products (such as SQL Server).

If you set a specific reference, it's expecting the reference to be the same version and it being in the same place as it was before.

Jim.
0
 
aikimarkCommented:
does it matter that one of these variables is a DTS.Package and the other is a DTS.Package2 ?
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<does it matter that one of these variables is a DTS.Package and the other is a DTS.Package2 ? >>

 Looks like they either had two references set or maybe two different class wrappers written for one DTS package.

 Don't think that's a mistake, but without seeing the rest of the code, it's hard to say if it is or not.

 Still sounds like a reference problem though in anycase...

Jim.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
phiadminAuthor Commented:
I am not an expert on vb, just trying to maintain this process until it is replace by a new ERP.

The program works on my workstation so I should not have to change the code.

The 7 references are the same on both system
The Microsoft DTSPackage Object Library reference the same DTSPKG.dll
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<The 7 references are the same on both system
The Microsoft DTSPackage Object Library reference the same DTSPKG.dll >>

 Do the references include DAO?  If so:

1. Uncheck the reference in the VB6 program and close it
2. Drop to a command prompt and un-register it:

regsvr32 -u "c:\program files\common files\microsoft shared\dao\dao360.dll"

3. Re-register it:

regsvr32 "c:\program files\common files\microsoft shared\dao\dao360.dll"

4. Open the VB6 program, select the reference and check it, then try it.

If you don't have a reference for DAO, then one of the other references is broken.  It will be one of the ones before the DTS reference.  You'll have to investigate each one.   It needs to be in the same location and the same version as the one where the program works.

 If you still stuck, paste a screen shot of the references.

Jim.
0
 
phiadminAuthor Commented:
We are going to install sqlServer on the server to test if that will fix the problem
0
 
phiadminAuthor Commented:
after installing SQL SERVER, the vb code ran ok
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now