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

Resolved OLE ConnectToObject dll in debug

  1. Issue
0
Votes
Undo
  1. Patrizio Sorace
    Patrizio Sorace
  2. PowerBuilder
  3. Thursday, 8 February 2018 10:22 AM UTC

Hello,

I've a PB Classic 12.6 application which use a DLL written in .NET.
The application has been successfully converted by powerbuilder 2017 and it works.

The problem is that if I use myOLEObject.ConnectToObject('mydll.class') it seems to work pretty well after deploying, but I get an error -3 if I start directly on Powerbuilder for debugging the application.

The dll is correctly registered, I also tried to install it in the GAC cache, and even if I can now remove the dll from the deployed project path and run "normally" without errors, I still get error -3 when trying to start the application from Powerbuilder.
I've tried to put the dll in many paths (windows/system32, Program Files (x86)\Appeon\PowerBuilder 17.0) but I still get the same error.

What else can I try to make it work also directly from Powerbuilder while debugging ?

  1. DLL
Android says "Can't open file" when tapping AWS ap...
PB runtime dll's required (PB2017 R2)
Responses (2)
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Thursday, 8 February 2018 13:29 PM UTC
  2. PowerBuilder
  3. # 1

Hi

Just to be clear the PB 2017 application works fine when it is deployed, i.e. you run the EXE.?

Does the EXE work on the development machine ok? if so then it is reasonable to assume that the DLL is installed ok.

Are you building a 32-bit EXE?

There is not enough information for us to give any suggestions at this point.

Regards

David

Comment
Patrizio Sorace
  1. Patrizio Sorace
  2. Monday, 12 February 2018 07:47 AM UTC
Hello,

yes the exe work fine on development machine, actually it works on a lot of different PC without problem, so I'm sure that dll is ok.

The application is 32bit exe.

The problem seems to be related on something missing on powerbuilder 2017 configuration.

  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Thursday, 8 February 2018 16:13 PM UTC
  2. PowerBuilder
  3. # 2

Hi Patrizio,

You may need to install the PBRuntime files for .Net. You can find the installer in the following path: C:\Program Files (x86)\Appeon\PowerBuilder 17.0\DotNET\pbiu\BootStrapper\Packages\1-PBRuntime\pbruntime.msi

Please try to install this into the client computer and do let us know if this helped.


Regards,

Comment
Patrizio Sorace
  1. Patrizio Sorace
  2. Monday, 12 February 2018 07:49 AM UTC
The problem is not related to the client PC, but to the development machine.

The deployed exe works fine, I got problem only if I start directly from powerbuilder.

Anyway I've tried to install the runtime on development machine, but nothing seems to change.

  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.