1. Gregory Rusak
  2. PowerBuilder
  3. Monday, 18 March 2019 23:27 PM UTC

On one of our production servers (and so far only one), we are experiencing the same OLE Error as what was reported by Boris Krylov in https://www.appeon.com/standardsupport/search/view?id=1355#.

Unfortunately, in that Post, Boris did not mention which application was "Unitializing COM interface for the thread".

Has anyone else had an issue with the RTE control? See attached screen shots.

Thanks

PowerBuilder 2017 R2

Windows Server 2012 R2 Standard

Kind Regards,

Greg

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 19 March 2019 19:13 PM UTC
  2. PowerBuilder
  3. # 1

Hi Roland;

   Yes, I read through the ticket and Boris was "guessing" that another 3rd party OLE control was interfering by closing the OLE (Com) interface thread. Its hard to say one way or the other IMHO.

   In the meantime, this error might also be related to a file issue ...

FYI:  https://communities.bentley.com/products/microstation/w/microstation__wiki/14631/hresult-80030003-can-t-create-new-file

 

Regards ... Chris

 

  

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 19 March 2019 16:57 PM UTC
  2. PowerBuilder
  3. # 2

I read Boris' ticket.

 

He was using the built-in Rich Text control. The problem was that a third party control he didn't specify was causing interference with the built-in Rich Text control.

 

Comment
  1. Gregory Rusak
  2. Tuesday, 19 March 2019 18:33 PM UTC
Right, exactly what we are doing. It would be nice to know which 3rd party control was causing issues so that we can do the same. Hoping someone else has come across this issue with the new RTE control.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 19 March 2019 12:49 PM UTC
  2. PowerBuilder
  3. # 3

Hi Greg;

  FWIW: Boris's ticket was for another 3rd party product and not the RTE Control. The built-in RTE control does not use OLE. So I am at odds here to explain your error message.

Regards ... Chris

Comment
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.