1. David Watson
  2. PowerBuilder
  3. Wednesday, 15 May 2019 18:39 PM UTC

We are currently experiencing a dll failure issue after upgrading from Windows 2008 R2 to Windows 2012 R2 with the pbdwe170.dll.

Looking at some docs, it appears this dll is related to database access.  Below is the screenshot from the event log.

Can you provide information or documentation that will help us determine the cause/fix for this issue?

 

Attachments (1)
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 15 May 2019 18:47 PM UTC
  2. PowerBuilder
  3. # 1

Hi David;

  FYI: The PBDWEnnn.dll  is the "DataWindow Expression" evaluator module and handles things like computed fields, filter, sort and expressions used in various DWO property settings.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Mohammud Daulgha Accepted Answer Pending Moderation
  1. Sunday, 15 December 2019 23:51 PM UTC
  2. PowerBuilder
  3. # 2

We are experiencing the same issue in one of the production environment. As the issue does not happen in any of our development machines. Can someone share an ideas or steps to find the root cause of the issue will help to resolve the issue.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 16 December 2019 19:21 PM UTC
  2. PowerBuilder
  3. # 3

Hi David;

   Also, two observations from your screen capture attachment ...

1) The PBDWE170 DLL is normally stored in the "Appeon" folder and not the Sybase folder as per your attachment. Please re-check your deployment.

2) The PBDWE170 DLL in the attachment is from build 1666. This is an old version of PB2017 (relatively speaking). I would strongly suggest moving up to the LTS (long term support) version of PB2017R3 - build 1880.

Food for thought

Regards ... Chris

 

Comment
There are no comments made yet.
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 17 December 2019 07:45 AM UTC
  2. PowerBuilder
  3. # 4

Hi David,

 

Due to that we can’t reproduce this issue locally, it is hard for us to find out the root cause of it for now.

Can you provide a small reproducible case for us? If yes, please go to Appeon Support Ticket system(https://www.appeon.com/standardsupport/newbug) to open a new ticket with this small case thus it can be properly received and tracked.

 

Regards,

Ken

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.