• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • System Error Encountered: Error Opening PBSHELL.dll

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

Resolved System Error Encountered: Error Opening PBSHELL.dll

  1. Issue
0
Votes
Undo
  1. Team BFMS
    Team BFMS
  2. PowerBuilder
  3. Tuesday, 26 March 2019 12:43 PM UTC

Hi, 

We are encountering the following error when we try to access a field in our power-builder application.

"Error opening DLL library pbshell.dll for the external function in the constructor event of an object". When we looked in the power-builder shared folder i couldn't locate pbshell.dll. How should we proceed?

 

Please check the screenshot in the attachments.

 

Environment: Powerbuilder 9 and Appeon powerbuilder 2017 R3 both has the same error

Operating system: Windows 10

 

Thanks in advance,

Bfms team

Attachments (1)
shell32.JPG shell32.JPG
  1. Configuration
  2. DLL
  3. Error
  4. PowerBuilder (Appeon)
  5. PowerBuilder (SAP)
Show Display Column when saving in Excel.
How to obtain the name of an object function
Responses (4)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 26 March 2019 17:05 PM UTC
  2. PowerBuilder
  3. # 1

I believe it is a PBNI extension developed by Roy Kiesler and at one time was available on the Team Sybase website. The website is no longer running.

The file must be located somewhere in the system path on the machine that works. Look in C:\Windows or C:\Windows\System32 andany other folder in the path.

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

It is not part of the standard PowerBuilder runtime. You'll have to find it on somebody else's machine and copy it from there.

I think it might be an old PBNI example. I'm not sure if it is in the Appeon Code Samples, I can't find it.

 

Comment
Team BFMS
  1. Team BFMS
  2. Tuesday, 26 March 2019 16:52 PM UTC
I couldn't find on any other machine. It did not exist. But it's working fine in another machine. Am not sure why this error still popped on my machine.



Thankyou
  1. Helpful
There are no comments made yet.
Brad Mettee
Brad Mettee Accepted Answer Pending Moderation
  1. Tuesday, 26 March 2019 15:14 PM UTC
  2. PowerBuilder
  3. # 3

As far as I can tell, there's no file called PBSHELL.DLL anywhere on my system either. I have PB 10.2, 12.5.2 and PB 2017 build 1681 installed.

Is it doing it on all machines or just yours?

Have you run virus scans? 

Is the n_cpp_shell32 object something you can check into? (this sounds like it's part of the PFC, is it?)

Comment
Team BFMS
  1. Team BFMS
  2. Tuesday, 26 March 2019 16:54 PM UTC
Hi Brad, Thanks for your response.



It working well on other machines. We don't use any PFC's in our application



Thankyou,

Naveen
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 26 March 2019 14:57 PM UTC
  2. PowerBuilder
  3. # 4

Hi;

   This object looks like an old PFC object class. Something to do with CPlusPlus I believe.

FWIW: There is no such DLL (AFAIK) in recent PB versions named PBShell. I wonder if the "n_cpp_shell32" object class is trying to call the MS-Windows "Shell32.dll"?

Regards ... Chris

Comment
Team BFMS
  1. Team BFMS
  2. Tuesday, 26 March 2019 16:59 PM UTC
Hi Chris,



Yes when we actually migrated to web we came across this:



Unsupported Code:



Line Number:

0

Location:

N_cpp_shell32 in structures_and_nvo.pbl

Unsupported Item:

N_cpp_shell32

Type:

Cplusplus

Reason:

External class userobject 'n_cpp_shell32' is unsupported



Priority:

Have to modify

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 26 March 2019 18:52 PM UTC


I bet that this is from the days of PB 6.0 / 6.5 when PB from PowerSoft also included the Watcom C++ compiler. IN those days, you were able to build a PB C++ User Object. The C++UO would allow your to code in C++ and it could compile your UO into a DLL. You could then call the C++UO like you do today with an NVUO. That feature was removed by Sybase when PB itself was migrated from using the Watcom C++ compiler over to the Microsoft C++ compiler. I think that was done in the PB 7 frame.

  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.