Re: 80040154|Class_not_registered



Thanks for responding Val.

I am certain that the error stems from an ADO call. The error occurs when
the recordset is opened. The line reads recordSet.Open strQry, objConn. The
cursor location is being set in the line immediately before this one. The
error does not occur when the cursor location is commented out or when it is
set to server-side.

I have reinstalled MDAC, but the problem persists. Component Checker only
shows a mismatch with msxml3. My current version is higher that expected for
MDAC 2.7 SP1 Refresh.
--
db


"Val Mazur (MVP)" wrote:

> Hi,
>
> It could be that MDAC installation was corrupted somehow. Try to run
> Component Checker utility from MDAC to see if MDAC is OK. Are you sure that
> you get this error because you make some call in ADO? Could you trace to see
> which specific line of code causes it?
>
> --
> Val Mazur
> Microsoft MVP
>
> http://xport.mvps.org
>
>
>
> "DeeBee" <DeeBee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:7BD48D2A-A8ED-4136-B51D-45B81B36DDFA@xxxxxxxxxxxxxxxx
> >I am troubleshooting an ASP application running on a Windows 2000 server.
> > Until recently, a client-side cursor (recordset.cursorLocation = 3) could
> > be
> > used successfully. Now a "class not registered" is raised by this code.
> > However, a server-side cursor (recordset.cursorLocation = 2) does NOT
> > raise
> > an error. I need some help in determining the cause of this behavior.
> >
> > Obviously, something has changed somehow on the server. I have reinstalled
> > MDAC 2.7 SP1 Refresh to no avail. The code works on another similarly
> > configured server.
> >
> > Regmon shows no access denied, and Filemon shows no failures.
> >
> > Thanks in advance for any assistance rendered.
> > --
> > db
>
>
>
.



Relevant Pages

  • Re: MDAC question
    ... > The application server runs VB6 code. ... > decided to check the MDAC versions on my two physical servers. ... the ADO Data library are your applications using? ... not the cause since ConnectionRead is called by drivers and providers. ...
    (microsoft.public.vb.general.discussion)
  • Re: MDAC question
    ... > The application server runs VB6 code. ... > decided to check the MDAC versions on my two physical servers. ... the ADO Data library are your applications using? ... not the cause since ConnectionRead is called by drivers and providers. ...
    (microsoft.public.data.ado)
  • Re: MDAC question
    ... > The application server runs VB6 code. ... > decided to check the MDAC versions on my two physical servers. ... the ADO Data library are your applications using? ... not the cause since ConnectionRead is called by drivers and providers. ...
    (microsoft.public.vb.database)
  • Re: MDAC question
    ... > The application server runs VB6 code. ... > decided to check the MDAC versions on my two physical servers. ... the ADO Data library are your applications using? ... not the cause since ConnectionRead is called by drivers and providers. ...
    (microsoft.public.vb.database.ado)
  • ADO RecordCount with OLE DB Provider
    ... I had implemented an OLE DB provider wich expose the IRowsetScroll interface ... able to get the ADO rs.RecordCount when my cursor location is server. ... IRowsetScroll::GetApproximatePosition is not called even my cursor location ... When I called ADO ...
    (microsoft.public.data.ado)