• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • ConnectToNewObject( "Word.Application" ) return -3

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved ConnectToNewObject( "Word.Application" ) return -3

  1. Issue
0
Votes
Undo
  1. Mihai Apostol
    Mihai Apostol
  2. PowerBuilder
  3. Tuesday, 13 September 2022 02:56 AM UTC

Hi Guys,

PB Version 2019 R3 build 2703.  

Some days ago some of our users have started having issues with ConnectToNewObject( "Word.Application" ) command. It returns -3 that means "Object could not be created". This happens on both, MOffice 2019 and 365(32 bits version). The latest updates have been applied. For exemple the MO 2019 has the 2208 Build 16.01.15601.20078. For some of users the workaround is to remove the file normal.dotm. But this does not work for all. There are no other WINWORD.EXE running at the same time. 

Do you have any idea?

Thank you!

Appeon Server Locations
unable to assign values to SQLErrText
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 13 September 2022 17:00 PM UTC
  2. PowerBuilder
  3. # 1

Hi Mihai;

  The ConnectToNewObject() in PB utilizes the MS-Windows registry settings of the OLE server in order to establish an OLE connection. So to me, this problem sounds like an update might have been applied to various PC's that changed the MS-Word OLE registry settings (my best guess).  I would consult your IT Team to see what changes were recently applied as-of-late to this area. My $0.02.  HTH

Regards ... Chris

 

Comment
Patricia Guzman
  1. Patricia Guzman
  2. Monday, 22 January 2024 19:28 PM UTC
Hello,

Do you have any updates to this issue? I got the same error "Object could not be created (-3)". This happens when I use Office 365. I used to use Office 2013 and I did not have any problems. Please let me know if you found any solution to this problem. Thanks in advance, Patricia

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 22 January 2024 19:42 PM UTC
Hi Pat;

I've been using O365 for years with PB using OLE. However, older versions of MS-Office only used a 32 bit client (OLE Server) - which was great for your 32 bit only PB apps. However with the newer O365, you can install either a 32 bit or 64 bit client. So you might have to check with your operations team as to which client (if any) is installed. I have both bitnesess installed.

Regards... Chris
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 23 January 2024 19:56 PM UTC
PS: also, when your organization is installing the O365 client software, they might not be installing and/or registering the O365 "in process" sever (aka OLE Server) for MS-Word. This is what your PB Apps want to open a connection with when using the PB OLE feature. This question might be worth checking with your operations support team if this "in-process server" is actually being installed / registered (O/S registry). Food for thought. .. HTH
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.