RE: Runtime Error -2147310770(8002801d): Automation Error.

I guess most answers on internet are just to reinstall Office or to redo
windows itself as I dont think thr is a specific answer found on this. Or
some one who found exact keys on registry which is corrupted

http://www.experts-exchange.com/Microsoft/Development/MS_Access/Q_20519031.html
http://www.codeproject.com/KB/COM/BigInteger.aspx?fid=216748&df=90&mpp=25&noise=3&sort=Position&view=Quick&select=2066094&fr=26

"Ben" wrote:

Hello,

Thank you all for the replies. I am running XP with SP2. I initially tried
registering all DLL's in Windows\system32 (for %i in (*.dll, *.ocx) do
regsvr32 %i /s). I think this is just a true bug that occurs when the Office
2007 Interop Assemblies are installed, and you are using Word 2003. There
appears to be no solution or workaround for this. I did see something about
re-installing IE, but it looked like it was only related to an earlier
version of IE (ie5 maybe). That is the only thing I did not try, but does
not look too promosing. Thanks again,

- Ben

"dibby44" wrote:

Not sure if helpful but I came across a similar problem this week. Running
Office 2007, and trying to open Outlook from Access 2003 in vb code, always
stopped at
CreateObject("Outlook.Application").
Eventually found that I was running Access as Administrator [see Properties,
Compatibility box to amend] but not Outlook as Administrator. Amended to run
Access Not As Administrator, and now works OK. Yet another quirk of
privilege levels in Office 2007!
Dave B.


"Ben" wrote:

Hi All,

I ran into a problem on a few machines with an application that is failing
on a simple call:

Set WordApp = CreateObject("Word.Application")

The application cannot be modified at this point, so conversations on
binding methods are not relavent :) The full error is:

Runtime Error -2147310770(8002801d): Automation Error. Library not
registered.

Word 2003 (SP2) is installed on these machines, and I found that in order to
resolve this error, I had to uninstall the Office 2007 Primary Interop
Assemblies. This is clearly a defect that needs to be resolved. Has anyone
else run into this? I am wondering if it always happens if this component is
installed, or if it was just a combination of something environmental on my
machines, and having this component installed. Attention on this from
Microsoft would be much appreciated! Thank you!

- Ben
.

Relevant Pages

  • Re: Is complete home security possible?
    ... >> than an administrator level account, I will an error message on FS98, ... I have a clean disk image made from Norton Ghost, ... >> and I regularly ghost my machines once a month. ... Well, I keep important files on a second hard disk in the NAT Box, ...
    (comp.security.firewalls)
  • Re: Admin Password change causes problem ?
    ... security of other network attached machines. ... > This is not a Domain, just a group of machines set up as workgroup ... how many had a login with Administrator ...
    (microsoft.public.win2000.security)
  • Re: remote shutdown
    ... Remote computer is on peer network, and I can ping the remote ... Those should work great - if you are a system administrator of the ... Two machines in a workgroup. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Pulling hair out - and there aint much left
    ... remote services are not running or disabled on the target machines ... you have no local administrator rights (since you have not described your ... if the machines came pre-configured way back when and do not conform to ... > and am presented with a dialog for a logon. ...
    (microsoft.public.win2000.networking)
  • Re: network security suggestions needed
    ... administrator passwords should be changed immediately when there is turnover ... unrestricted administrator access to all machines using peer-to-peer ... > server at DSL company, ... > the finance department are Win2k, ...
    (microsoft.public.win2000.security)