Whilst I bang away at this on my own I figured I should throw it out to the collective wisdom. I noticed recently that both CreateObject and NewObject are failing to instantiate an object for Word 2016. GetObject works fine to retrieve a running instance. Excel works fine.
oo=CREATEOBJECT([word.application])
results in OLE error code 0x80080005: Server execution failed.
Google fu has failed me so far. If anyone here has had success automating Word 2016, please share your magic tricks.
Thanks.
--
rk
For anyone following along, I've managed to make it past the most basic of problems with object creation. Looks like I had some registry conflict because I had parts of Office 2010 installed (Access, Visio). I uninstalled 2010 which then completely broke COM. Finally I followed that up with a quick repair of O2016 and could once again create COM objects. Now I can go back to working on the thing that I really wanted to do.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, December 05, 2016 12:10 PM To: profoxtech@leafe.com Subject: COM Automation problem with Word 2016
Whilst I bang away at this on my own I figured I should throw it out to the collective wisdom. I noticed recently that both CreateObject and NewObject are failing to instantiate an object for Word 2016. GetObject works fine to retrieve a running instance. Excel works fine.
oo=CREATEOBJECT([word.application])
results in OLE error code 0x80080005: Server execution failed.
Google fu has failed me so far. If anyone here has had success automating Word 2016, please share your magic tricks.
Thanks.
--
rk
Well, never mind.
On Mon, Dec 5, 2016 at 12:39 PM, Richard Kaye rkaye@invaluable.com wrote:
For anyone following along, I've managed to make it past the most basic of problems with object creation. Looks like I had some registry conflict because I had parts of Office 2010 installed (Access, Visio). I uninstalled 2010 which then completely broke COM. Finally I followed that up with a quick repair of O2016 and could once again create COM objects. Now I can go back to working on the thing that I really wanted to do.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, December 05, 2016 12:10 PM To: profoxtech@leafe.com Subject: COM Automation problem with Word 2016
Whilst I bang away at this on my own I figured I should throw it out to the collective wisdom. I noticed recently that both CreateObject and NewObject are failing to instantiate an object for Word 2016. GetObject works fine to retrieve a running instance. Excel works fine.
oo=CREATEOBJECT([word.application])
results in OLE error code 0x80080005: Server execution failed.
Google fu has failed me so far. If anyone here has had success automating Word 2016, please share your magic tricks.
Thanks.
--
rk
[excessive quoting removed by server]
Thanks, Ted.
I do recall issues with older versions of Office and One Click or Click to Install mode being strongly discouraged although I don't think there's any other now to install Office. It's a bit annoying that I had to dump Access and Visio to get it to work but it was a better solution than hours of registry hacking.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Monday, December 05, 2016 1:38 PM To: profoxtech@leafe.com Subject: Re: COM Automation problem with Word 2016
Well, never mind.
On Mon, Dec 5, 2016 at 12:39 PM, Richard Kaye rkaye@invaluable.com wrote:
For anyone following along, I've managed to make it past the most basic of problems with object creation. Looks like I had some registry conflict because I had parts of Office 2010 installed (Access, Visio). I uninstalled 2010 which then completely broke COM. Finally I followed that up with a quick repair of O2016 and could once again create COM objects. Now I can go back to working on the thing that I really wanted to do.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, December 05, 2016 12:10 PM To: profoxtech@leafe.com Subject: COM Automation problem with Word 2016
Whilst I bang away at this on my own I figured I should throw it out to the collective wisdom. I noticed recently that both CreateObject and NewObject are failing to instantiate an object for Word 2016. GetObject works fine to retrieve a running instance. Excel works fine.
oo=CREATEOBJECT([word.application])
results in OLE error code 0x80080005: Server execution failed.
Google fu has failed me so far. If anyone here has had success automating Word 2016, please share your magic tricks.
Thanks.
--
rk
[excessive quoting removed by server]
http://www.overclockers.com/forums/showthread.php/725542-How-to-install-both... https://support.office.com/en-us/article/Install-and-use-different-versions-...
On 06-Dec-2016 12:14 AM, Richard Kaye wrote:
Thanks, Ted.
I do recall issues with older versions of Office and One Click or Click to Install mode being strongly discouraged although I don't think there's any other now to install Office. It's a bit annoying that I had to dump Access and Visio to get it to work but it was a better solution than hours of registry hacking.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Monday, December 05, 2016 1:38 PM To: profoxtech@leafe.com Subject: Re: COM Automation problem with Word 2016
Well, never mind.
On Mon, Dec 5, 2016 at 12:39 PM, Richard Kaye rkaye@invaluable.com wrote:
For anyone following along, I've managed to make it past the most basic of problems with object creation. Looks like I had some registry conflict because I had parts of Office 2010 installed (Access, Visio). I uninstalled 2010 which then completely broke COM. Finally I followed that up with a quick repair of O2016 and could once again create COM objects. Now I can go back to working on the thing that I really wanted to do.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, December 05, 2016 12:10 PM To: profoxtech@leafe.com Subject: COM Automation problem with Word 2016
Whilst I bang away at this on my own I figured I should throw it out to the collective wisdom. I noticed recently that both CreateObject and NewObject are failing to instantiate an object for Word 2016. GetObject works fine to retrieve a running instance. Excel works fine.
oo=CREATEOBJECT([word.application])
results in OLE error code 0x80080005: Server execution failed.
Google fu has failed me so far. If anyone here has had success automating Word 2016, please share your magic tricks.
Thanks.
--
rk
[excessive quoting removed by server]
Thanks, Andy. I've had multiple versions installed for ages. Some recent Office 2016 update must have broken it.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of AndyHC Sent: Tuesday, December 06, 2016 8:17 AM To: profoxtech@leafe.com Subject: Re: COM Automation problem with Word 2016
http://www.overclockers.com/forums/showthread.php/725542-How-to-install-both... https://support.office.com/en-us/article/Install-and-use-different-versions-...
On 06-Dec-2016 12:14 AM, Richard Kaye wrote:
Thanks, Ted.
I do recall issues with older versions of Office and One Click or Click to Install mode being strongly discouraged although I don't think there's any other now to install Office. It's a bit annoying that I had to dump Access and Visio to get it to work but it was a better solution than hours of registry hacking.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Monday, December 05, 2016 1:38 PM To: profoxtech@leafe.com Subject: Re: COM Automation problem with Word 2016
Well, never mind.
On Mon, Dec 5, 2016 at 12:39 PM, Richard Kaye rkaye@invaluable.com wrote:
For anyone following along, I've managed to make it past the most basic of problems with object creation. Looks like I had some registry conflict because I had parts of Office 2010 installed (Access, Visio). I uninstalled 2010 which then completely broke COM. Finally I followed that up with a quick repair of O2016 and could once again create COM objects. Now I can go back to working on the thing that I really wanted to do.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, December 05, 2016 12:10 PM To: profoxtech@leafe.com Subject: COM Automation problem with Word 2016
Whilst I bang away at this on my own I figured I should throw it out to the collective wisdom. I noticed recently that both CreateObject and NewObject are failing to instantiate an object for Word 2016. GetObject works fine to retrieve a running instance. Excel works fine.
oo=CREATEOBJECT([word.application])
results in OLE error code 0x80080005: Server execution failed.
Google fu has failed me so far. If anyone here has had success automating Word 2016, please share your magic tricks.
Thanks.
--
rk
[excessive quoting removed by server]
Check to ensure that Word is actually installed on the machine and not Office 365 "in the cloud."
Check that you are running the 32-bit version of Word and not the 64-bit one: http://www.howtogeek.com/howto/24259/beginner-discover-if-youre-running-the-...
On Mon, Dec 5, 2016 at 12:10 PM, Richard Kaye rkaye@invaluable.com wrote:
Whilst I bang away at this on my own I figured I should throw it out to the collective wisdom. I noticed recently that both CreateObject and NewObject are failing to instantiate an object for Word 2016. GetObject works fine to retrieve a running instance. Excel works fine.
oo=CREATEOBJECT([word.application])
results in OLE error code 0x80080005: Server execution failed.
Google fu has failed me so far. If anyone here has had success automating Word 2016, please share your magic tricks.
Thanks.
--
rk
[excessive quoting removed by server]
-
AndyHC -
Richard Kaye -
Ted Roche