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

Resolved PB 2017R3 The ordinal 2678 could not be located

  1. Issue
0
Votes
Undo
  1. Ganesan Rajan
    Ganesan Rajan
  2. PowerBuilder
  3. Friday, 8 November 2019 11:54 AM UTC

Hi,

One of my team member is receiving below error message when trying to launch PB2017 R3 in windows 10 64bit machine.

The ordinal 2678 could not be located in the dynamic link library C:\Program Files (x86)\Appeon\shared\PowerBuilder\pbsys170.dll

We made following attempts to make it work, but failed

1) Uninstall and Reinstall PB.

2) Run the PB as Administrator

He has been using PB2017 for months, but getting this issue all of a sudden.

Help will be much appreciated.

Thanks,

Ganesan

 

 

  1. Error
  2. PowerBuilder (Appeon)
Datawindow debugger pfc_w_dwdebugger not opening
Powerbuilder 2017 R3 - Open (w_window, w_mainwindo...
Responses (3)
Chris Keating
Chris Keating Accepted Answer Pending Moderation
  1. Friday, 8 November 2019 15:05 PM UTC
  2. PowerBuilder
  3. # 1

The error "The ordinal %!could not be located in the dynamic link library %2" indicates that the called DLL is missing a method that is being invoked. That usually means a version mismatch. 

Please check that the pbsys170.dll is the same version as the rest of the PowerBuilder runtime.

 

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 8 November 2019 16:05 PM UTC
Yes, the fact that "suddenly" it doesn't work anymore, might indicate a (non) update to a newer patch or something like that. Good point!
  1. Helpful
There are no comments made yet.
Ganesan Rajan
Ganesan Rajan Accepted Answer Pending Moderation
  1. Friday, 8 November 2019 12:26 PM UTC
  2. PowerBuilder
  3. # 2

Hi,

Thanks for your response. Installed VC++run time from below web page

https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads

But still facing same issue.

Thanks,

Ganesan

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 8 November 2019 12:39 PM UTC
Sorry to hear that. Can you run it and immediately have a look at the event viewer of windows to see if there's anything weird going on there?
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 8 November 2019 12:40 PM UTC
Another possibility is to run the "process monitor" https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

or 2dependency walker" to see what goes wrong where.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 8 November 2019 11:58 AM UTC
  2. PowerBuilder
  3. # 3

I think you might have to re-install C++ Runtilme 32 bit / 64 bit

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.