missing dll files

Thanks Mike

I am not that computer savvy and will do as you suggest and I will post the
details of the problem.

When reinstalling a program I need to use for my work the following messages
popped up:

The following files did no self-register:

C: programfiles\CommonFiles\System\OLE DB\msdaps.dll

and also \OLE DB\OLEDB32.DLL

under both these it said " A device attached to the system is not functioning"

So I then clicked OK to each of these and got this that didn't self register:
OLEDB\MSDASQL.DLL so I clicked OK again and tried
registering. I typed in the serial # and coundn't get past that. I get the
message:

Run-time error 429
ActiveX component can't create object

So I can't access the program and that's all there is. Can anyone help.

I must tell you I had previously used the program and just couldn't accesss
it yesterday due to the runtime error message and then uninstalled and
re-installed it.
Now I am just stalled

Suggesstion would be greatly appreciated




"Mike M" wrote:

> No such site exists or should be needed. All dll and other files that
> form part of the Win Me operating system will be in the CAB files which
> will be usually located at either C:\Windows\Options\Cabs or
> C:\Windows\Options\Install depending upon the media used to originally
> install Win Me. If the file is from an application, reinstall the
> application.
>
> Rather than try and find an unnecessary potentially suspect third party
> site may I suggest that you post details of the problems you are
> experiencing so that someone here can try and help and hopefully explain
> how to fix your problems.
> --
> Mike Maltby
> MS-MVP Windows
> mike.maltby RemoveThis @gmail.com
>
>
> nanj2911 <nanj2911 RemoveThis @discussions.microsoft.com> wrote:
>
> > What is a safe, secure sight to download form to fix windows me
> > problems Can I use RegCure or is there one with stronger
> > recommendation
>
>

>
> So I then clicked OK to each of these and got this that didn't self
register:
> OLEDB\MSDASQL.DLL so I clicked OK again and tried
> registering. I typed in the serial # and coundn't get past that.

Much better than the broken cup holder. ;-
Norman

A couple of points.

You omitted to mention the application you were installing but perhaps
that was intentional.

Registering of a file has nothing to do with the application's serial
number but instead is the file concerned making the necessary adjustments
for its operation in the system registry.

Both msdaps.dll and oledb32.dll in the C:\program files\Common
Files\System\OLE DB\ folder are Win Me system files, should be present on
all Win Me systems and are both protected against being either deleted or
replaced by Win Me's system file protection mechanism unless the installer
includes the appropriate signed security catalogue. Can you confirm that
both of these files are present on your system? Their details should be
as follows:
Win Me as released in June 2000
msdaps.dll v2.50.4403.2 188 KB (192,784 bytes) 8 June 2000
oledb32.dll v2.50.4403.8 472 KB (483,600 bytes) 8 June 2000

These two files will have been updated by the various updates for the
Microsoft Data Access Component (MDAC) from the Windows Update site or
Microsoft Download Centre. The latest versions here following the
installation of MDAC 2.8 SP1 from the Download Centre are:
msdaps.dll v2.81.1117.0 188 KB (192,512 bytes) 28 April 2004
oledb32.dll v2.81.1117.0 448 KB (458,752 bytes) 28 April 2004

I wonder if your problem might be the result of installing the 911562
patch from the Windows Update site for MDAC 2.8 which breaks MDAC (the
same may also be true for earlier MDAC versions). Can you access Win Me's
Help & Support or do you see an error such as "Please report the following
error number to Microsoft support: -2147143679".

Try the following:
Download and install MDAC 2.8 SP1 from
http://download.microsoft.com/download/4/a/a/4aafff19-9d21-4d35-ae81-0...8dcbbbf
Check whether you can now access Help & Support.
Now visit the Windows Update site download and install KB911562 again.
Don't worry the patch for MDAC 2.8 SP1 has none of the problems associated
with the patch for MDAC 2.8 which is I suspect the version you are running
at present.

Check whether you can now install your application

> I must tell you I had previously used the program and just couldn't
> access it yesterday due to the runtime error message and then
> uninstalled and re-installed it.

You might have been better served by using system restore and rolling your
system back to a date before you first encountered problems, providing
that that was no more than say a week ago. You may still want to consider
that option but I would try my suggestion above first.
--
Mike Maltby
MS-MVP Windows
mike.maltby RemoveThis @gmail.com


nanj2911 <nanj2911 RemoveThis @discussions.microsoft.com> wrote:

> Thanks Mike
>
> I am not that computer savvy and will do as you suggest and I will
> post the details of the problem.
>
> When reinstalling a program I need to use for my work the following
> messages popped up:
>
> The following files did no self-register:
>
> C: programfiles\CommonFiles\System\OLE DB\msdaps.dll
>
> and also \OLE DB\OLEDB32.DLL
>
> under both these it said " A device attached to the system is not
> functioning"
>
> So I then clicked OK to each of these and got this that didn't self
> register: OLEDB\MSDASQL.DLL so I clicked OK
> again and tried
> registering. I typed in the serial # and coundn't get past that. I
> get the message:
>
> Run-time error 429
> ActiveX component can't create object
>
> So I can't access the program and that's all there is. Can anyone
> help.
>
> I must tell you I had previously used the program and just couldn't
> accesss it yesterday due to the runtime error message and then
> uninstalled and re-installed it.
> Now I am just stalled
>
> Suggesstion would be greatly appreciated

Thanks Mike,

I did the download MDAC 2.8 SPI and then the KB9...
and was able to re-install the software and it works. Yes! Thanks you so
very much



"Mike M" wrote:

> A couple of points.
>
> You omitted to mention the application you were installing but perhaps
> that was intentional.
>
> Registering of a file has nothing to do with the application's serial
> number but instead is the file concerned making the necessary adjustments
> for its operation in the system registry.
>
> Both msdaps.dll and oledb32.dll in the C:\program files\Common
> Files\System\OLE DB\ folder are Win Me system files, should be present on
> all Win Me systems and are both protected against being either deleted or
> replaced by Win Me's system file protection mechanism unless the installer
> includes the appropriate signed security catalogue. Can you confirm that
> both of these files are present on your system? Their details should be
> as follows:
> Win Me as released in June 2000
> msdaps.dll v2.50.4403.2 188 KB (192,784 bytes) 8 June 2000
> oledb32.dll v2.50.4403.8 472 KB (483,600 bytes) 8 June 2000
>
> These two files will have been updated by the various updates for the
> Microsoft Data Access Component (MDAC) from the Windows Update site or
> Microsoft Download Centre. The latest versions here following the
> installation of MDAC 2.8 SP1 from the Download Centre are:
> msdaps.dll v2.81.1117.0 188 KB (192,512 bytes) 28 April 2004
> oledb32.dll v2.81.1117.0 448 KB (458,752 bytes) 28 April 2004
>
> I wonder if your problem might be the result of installing the 911562
> patch from the Windows Update site for MDAC 2.8 which breaks MDAC (the
> same may also be true for earlier MDAC versions). Can you access Win Me's
> Help & Support or do you see an error such as "Please report the following
> error number to Microsoft support: -2147143679".
>
> Try the following:
> Download and install MDAC 2.8 SP1 from
> http://download.microsoft.com/download/4/a/a/4aafff19-9d21-4d35-ae81-0...8dcbbbf
> Check whether you can now access Help & Support.
> Now visit the Windows Update site download and install KB911562 again.
> Don't worry the patch for MDAC 2.8 SP1 has none of the problems associated
> with the patch for MDAC 2.8 which is I suspect the version you are running
> at present.
>
> Check whether you can now install your application
>
> > I must tell you I had previously used the program and just couldn't
> > access it yesterday due to the runtime error message and then
> > uninstalled and re-installed it.
>
> You might have been better served by using system restore and rolling your
> system back to a date before you first encountered problems, providing
> that that was no more than say a week ago. You may still want to consider
> that option but I would try my suggestion above first.
> --
> Mike Maltby
> MS-MVP Windows
> mike.maltby.TakeThisOut@gmail.com
>
>
> nanj2911 <nanj2911.TakeThisOut@discussions.microsoft.com> wrote:
>
> > Thanks Mike
> >
> > I am not that computer savvy and will do as you suggest and I will
> > post the details of the problem.
> >
> > When reinstalling a program I need to use for my work the following
> > messages popped up:
> >
> > The following files did no self-register:
> >
> > C: programfiles\CommonFiles\System\OLE DB\msdaps.dll
> >
> > and also \OLE DB\OLEDB32.DLL
> >
> > under both these it said " A device attached to the system is not
> > functioning"
> >
> > So I then clicked OK to each of these and got this that didn't self
> > register: OLEDB\MSDASQL.DLL so I clicked OK
> > again and tried
> > registering. I typed in the serial # and coundn't get past that. I
> > get the message:
> >
> > Run-time error 429
> > ActiveX component can't create object
> >
> > So I can't access the program and that's all there is. Can anyone
> > help.
> >
> > I must tell you I had previously used the program and just couldn't
> > accesss it yesterday due to the runtime error message and then
> > uninstalled and re-installed it.
> > Now I am just stalled
> >
> > Suggesstion would be greatly appreciated
>
>

nanj2911 <nanj2911 DeleteThis @discussions.microsoft.com> wrote:

> Thanks Mike,
>
> I did the download MDAC 2.8 SPI and then the KB9...
> and was able to re-install the software and it works. Yes! Thanks
> you so very much

N,

Thanks so very much for that feedback as it will be most helpful when
trying to help someone with similar problems. I've seen plenty of reports
of problems following the installation of the KB911562 hotfix for older
versions of MDAC but none like the one you were seeing so it was good that
we struck lucky with a broken MDAC install/update as being the cause of
your problems.

Cheers,
--
Mike Maltby
MS-MVP Windows
mike.maltby DeleteThis @gmail.com

I appreciate this info as well. Think I was a victim of that 2.8 update as
well. And have hesitated to do the update again. Nice to know that all is OK
with 2.8SP1.
I'm guessing this is a critical update only in certain circumstances. Or has
been superseded. I have neither KB911562 or 2.8SP1 on my system, but do have
version 2.6. Not showing need of critical update at windows update either.
But did note that MS recommends doing 2.8SP1 as 2.6 is no longer supported.
Norman

"Mike M" <No_Spam.RemoveThis@Corned_Beef.Only> wrote in message
news:uFc3hr2OHHA.2468@TK2MSFTNGP06.phx.gbl...
> nanj2911 <nanj2911.RemoveThis@discussions.microsoft.com> wrote:
>
> > Thanks Mike,
> >
> > I did the download MDAC 2.8 SPI and then the KB9...
> > and was able to re-install the software and it works. Yes! Thanks
> > you so very much
>
> N,
>
> Thanks so very much for that feedback as it will be most helpful when
> trying to help someone with similar problems. I've seen plenty of reports
> of problems following the installation of the KB911562 hotfix for older
> versions of MDAC but none like the one you were seeing so it was good that
> we struck lucky with a broken MDAC install/update as being the cause of
> your problems.
>
> Cheers,
> --
> Mike Maltby
> MS-MVP Windows
> mike.maltby.RemoveThis@gmail.com
>
>