• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Cannot load Rich text edit control: Windows error code 0 : pbctxtext170.dll is missing

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

Resolved Cannot load Rich text edit control: Windows error code 0 : pbctxtext170.dll is missing

  1. Issue
0
Votes
Undo
  1. Manojkumar Lingeswaran
    Manojkumar Lingeswaran
  2. PowerBuilder
  3. Wednesday, 7 February 2018 07:36 AM UTC

Hi All,

While opening the application EXE, the below mentioned error message has been displayed with the old version of PB2017 version.

Cannot load Rich text edit control: Windows error code 0 : pbctxtext170.dll is missing

On Adding the mentioned DLL also, the same error message has been displayed. We have added the below mentioned DLL's

pbctxtext170.dll

pbctctext170.dll

Then, we have installed the recent upgrade of Pb2017 R2 Version which has been released a week before. On trying with the recent version, the same error message has been displayed.

Can some one please help to sort out this problem ASAP.

Thanks and Regards

Manojkumar L

  1. Error
Reports are not generating after installing the 20...
Testing Frameworks on VSTS/AWS
Responses (6)
Richard Carrier
Richard Carrier Accepted Answer Pending Moderation
  1. Wednesday, 6 February 2019 16:39 PM UTC
  2. PowerBuilder
  3. # 1

We just went thru the entire upgrade process, created another full setup and we simply get the same message again.

 

Was this ever actually resolved for anyone and just assumed to be. 

 

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 6 February 2019 15:59 PM UTC
  2. PowerBuilder
  3. # 2

Hi Richard;

   FYI: I just test my RTE App's this AM using PB2017R3 MR01 (Build 1880) and had no issues with the RTE or RT DW. Neither by running the App via the IDE or running from a 32 or 64 bit EXE (on my development PC).

Regards ... Chris

Comment
Load more comments
Richard Carrier
  1. Richard Carrier
  2. Wednesday, 6 February 2019 17:00 PM UTC
I think I hopefully see the issue and its a mistake on my part. YA HOOO.
  1. Helpful
Richard Carrier
  1. Richard Carrier
  2. Wednesday, 6 February 2019 17:17 PM UTC
Yes, that worked. Chris, thank you for validating this , it forced my to find my mistake in packaging the setup.



Richard
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 6 February 2019 17:29 PM UTC


Whew .. that's great news - glad that you found the answer to your issue! :-)
  1. Helpful
There are no comments made yet.
Richard Carrier
Richard Carrier Accepted Answer Pending Moderation
  1. Tuesday, 5 February 2019 23:40 PM UTC
  2. PowerBuilder
  3. # 3

I can state that I've been on R3-1858 and still get that message. All my DLL's seemto be in order.

 

I'm testing now with the latest release.

 

Thanks

Richard

Comment
Load more comments
Richard Carrier
  1. Richard Carrier
  2. Wednesday, 6 February 2019 00:25 AM UTC
Yes , Will do , Thanks !
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 6 February 2019 17:55 PM UTC
If the problem still persists and your DLLs are in order then please open a support ticket. Thanks.
  1. Helpful
Richard Carrier
  1. Richard Carrier
  2. Wednesday, 6 February 2019 18:00 PM UTC
It's been resolved
  1. Helpful
There are no comments made yet.
Richard Carrier
Richard Carrier Accepted Answer Pending Moderation
  1. Tuesday, 5 February 2019 16:57 PM UTC
  2. PowerBuilder
  3. # 4

Hello All ,

 

We are getting the exact same error and I though for sure I did not have the Dll's mixed up. Does anyone know if this issue was resolved ?

 

Thanks 

Richard

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 5 February 2019 17:20 PM UTC
Hi Richard;

PB2017 R2 is now just over a year old now and was replaced by PB2017R3. The maintenance release on the R3 version was also just released last week. There have been many changes to the PB run-time over these other two releases that affect both the TX and TE Controls that support the RTE Control and RT DW. I would strongly suggest upgrading to a latest supported version of PB if you are also using R2.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 7 February 2018 19:31 PM UTC
  2. PowerBuilder
  3. # 5

Hi Manojkumar,

 

Marco is right. You need the latest runtime. You can find more about this in the "PowerBuilder Techniques.pdf" document. On page 261: https://www.appeon.com/system/files/product-manual/application_techniques.pdf

 

I hope this helps.

 

 

Regards,

Comment
Manojkumar Lingeswaran
  1. Manojkumar Lingeswaran
  2. Thursday, 8 February 2018 11:03 AM UTC
Thanks Govind for sharing the document. Will try and let you know the feedback.

  1. Helpful
There are no comments made yet.
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Wednesday, 7 February 2018 13:06 PM UTC
  2. PowerBuilder
  3. # 6

Hi Manojkumar,

R2 comes with its refreshed runtime, and you need to use this one.
Your .EXE and the associated runtime are a matched pair.
I never expect to have a runtime from a previous MR to work fully with a newer one.

Best,

Marco

Comment
Manojkumar Lingeswaran
  1. Manojkumar Lingeswaran
  2. Thursday, 8 February 2018 10:50 AM UTC
Thanks Marco. Will Try and Let you know the details.

  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.