Re: Class not registered on local machine (Error 463) Clarified
I could be much more precise - here is a simplified example of what we are
We have an interface class, called iBSWrapper in the itsBSInterfaces DLL.
For simplicity sake, we'll say that the only method on iBSWrapper is
Pubic Function GetData() AS ADODB.RecordSet
itsBSInterfaces DLL is registered on the client machine and on the MTS
Server (outside of MTS)
We then have a VB Component running under MTS that IMPLEMENTS
itsBSInterfaces.iBSWrapper as has code the return a recordset in the
We have DLL's registered on the client machine like this (m_strAppServer is
passed in to the DLL from the EXE. m_strAppServer contains the name of the
Private m_iBSWrapper As itsBSInterfaces.IBSWrapper
Private Sub CreateMTSWrapper()
On Error GoTo ERROR_LABEL
Const strWRAPPER As String = "itsBSCountry.CBSCountryWrapper"
If Not m_iBSWrapper Is Nothing Then Exit Sub
If Len(Trim(m_strAppServer)) = 0 Then
' for development against local DLLs
Set m_iBSWrapper = CreateObject(strWRAPPER)
' run under MTS
Set m_iBSWrapper = CreateObject(strWRAPPER, m_strAppServer)
If Err.Source <> App.EXEName Then
'source was deliberately set by this proc or a proc called here, so
pass it back as-is
Err.Raise Err.Number, Err.Source, Err.Description
'vb just raised this error here
Err.Raise Err.Number, TypeName(Me), Err.Description
I did not register any of the DLL's or typelib's for the DLL's running
under MTS on the client machine.
The Set m_iBSWrapper = CreateObject(strWRAPPER, m_strAppServer) is what is
failing with the "class ..." error message.
Principal Software Engineer
(using VB6 SP3/MTS/SQL Server 6.5 SP5a./MDAC 18.104.22.16802.3)
(Please respond to the newsgroup.)
DaveSatz <firstname.lastname@example.org> wrote in message
> I get this error when I try to use Set objectvariable =
> CreateObject("progID", ["servername"]), including the ServerName.
> All of our MTS components are designed using a custom interface using the
> IMPLEMENTS keyword. The DLL's that gets this error have a reference to
> Interface DLL, but not actual MTS components. They are looking for a
> to our custom interface on the MTS Component only. The client side DLL's
> never reference a property or method on the MTS components other than the
> interface. This allows you to compile the application without the MTS
> registered on your machine. I also expected it to allow me to run the
> application without the MTS DLL's registered on the client machine. I am
> correct ?
> David Satz
> Principal Software Engineer
> Hyperion Solutions
> (using VB6 SP3/MTS/SQL Server 6.5 SP5a./MDAC 22.214.171.12402.3)
> (Please respond to the newsgroup.)
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL