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

[Ben]

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

 

[vindys]

I guess this can help.

http://www.microsoft.com/communitie...&tid=2e2a7d2a-1dab-4ae2-9c8d-01992a89a802&p=1

Let us know if this helps

 

[Ben]

Doesn't appear to fix the problem as it is related to an actual component on
my machine, rather than permissions. Appears to be compatability between the
two. I did come across that before posting, but thank you for adding it
here. It will help others that come across this in the future.

- Ben

 

[vindys]

Other options which I saw while I google was to register some dlls which must
be there in Windows/System32


regsvr32 scrrun.dll
regsvr32 Atl.dll
regsvr32 btn32a20.ocx

Another try will be to reinstall IE

Let us know if any thing works with you. Also which OS you running on?

 

[dibby44]

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]

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

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.

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

 

[vindys]

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/B...sort=Position&view=Quick&select=2066094&fr=26

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

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.

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

 

[Ben]

I think MS just needs to fix this. Re-installing Office won't even fix it
because the solution is to uninstall the interop. Customers are upset with
me that my app doesn't run if they have the Interops installed, but VBA
doesn't work period if this component is installed. It's an MS bug that I
can't control. Hope they get around to fixing this at some point.

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/B...sort=Position&view=Quick&select=2066094&fr=26

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

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.


:

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

 

[Bruce Peters]

Hi,

Just a note to say "thanks" for posting your discovery. We had a similar problem and your advice fixed the trouble for us. We had removed Office 2007, leaving Office 2003, but had failed to remove the Primary Interop Assemblies. These, by themselves, were sufficient to prevent our VB6 code from creating "Word.Application" objects, even though VB Scripts, running from the same directory, succeeded.

Bruce