• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Failed to load library: PBORC.DLL with PB 2022 R2 utilities

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

Resolved Failed to load library: PBORC.DLL with PB 2022 R2 utilities

  1. Issue
0
Votes
Undo
  1. Alexander Busch
    Alexander Busch
  2. PowerBuilder
  3. Thursday, 7 December 2023 20:21 PM UTC

We are experiencing an issue with Orca220 that has arisen since the upgrade from PB 2022 R1 to PB 2022 R2. On our server, we uninstalled the old utilities and installed the new ones with version 22.1.0.2828. Afterwards, we rebooted the system but otherwise have not made any adjustments. We also use pbc220. The problem now is that when we execute the command 'orcascr220 createpbls.orca', we receive an error:

Appeon (R) OrcaScript interpreter version 22.1 Using ANSI source file createpbls.orca. Error: Failed to load library: PBORC.DLL.

This error did not occur under PB 2022 R1. The version of the dll is correct (22.1.0.2828). The Path variable in the system environment is also set with the correct path. I have also tried to manually register the DLL, but even then there is an error message that the dll cannot be loaded. The server in use is Windows Server 2019 Datacenter.

How to Create pbl from pgb and sr* files ?!
Feature Request: setSort() Natural-sort-option
Responses (4)
Arnd Schmidt
Arnd Schmidt Accepted Answer Pending Moderation
  1. Thursday, 7 December 2023 20:54 PM UTC
  2. PowerBuilder
  3. # 1

Hi Alexander,

if you also have PB IDE installed then you better set the runtime_version via command argument or switch the PB IDE.

https://docs.appeon.com/pb2022/pbug/OrcaScript_Commands.html

"If this argument is not set, then the runtime version configured in the PowerBuilder IDE will be used; and if no PowerBuilder IDE is installed on the current machine, then the latest runtime within the same major version as OrcaScript will be used. "

hth

Arnd

Comment
Alexander Busch
  1. Alexander Busch
  2. Thursday, 7 December 2023 21:03 PM UTC
No, unfortunately, we only installed the utilities on the server and not the IDE. So that cannot be the issue.
  1. Helpful
Arnd Schmidt
  1. Arnd Schmidt
  2. Friday, 8 December 2023 12:16 PM UTC
But you also installed the Runtime 22.1.0.2828?
  1. Helpful
Alexander Busch
  1. Alexander Busch
  2. Wednesday, 27 December 2023 16:10 PM UTC
Yes, of course. PB Utilities and Runtime 22.1.0.2828 only
  1. Helpful
There are no comments made yet.
kitty he @Appeon
kitty he @Appeon Accepted Answer Pending Moderation
  1. Friday, 8 December 2023 03:36 AM UTC
  2. PowerBuilder
  3. # 2

Hi Alexander,

 

  1. Does it work successfully with any simple ORCA command? For example: orcascr220 -h
  2. Please try to use dependency checking software depends.exe to check whether the dependent dlls of pborc.dll exist in the environment.

 

Regards,

Kitty

Comment
Alexander Busch
  1. Alexander Busch
  2. Wednesday, 27 December 2023 16:14 PM UTC
1. yes

2. tried, but we lack experience to use this tool. But we used it on the server (where the error occurs) and locally (where everything works fine) and both seem identical in the depends.exe.
  1. Helpful
There are no comments made yet.
Alexander Busch
Alexander Busch Accepted Answer Pending Moderation
  1. Wednesday, 27 December 2023 16:12 PM UTC
  2. PowerBuilder
  3. # 3

We have now set up another Windows Server 2022 Datacenter Edition and installed only the current c++ runtimes as well as the PB Utilities and runtime 22.1.0.2828 on it. Unfortunately the same error message. Everything works locally under Windows 11. Apparently there are problems with server operating systems (2019 + 2022 Datacenter)? We can't really cope with the dependency walker.

Comment
There are no comments made yet.
kitty he @Appeon
kitty he @Appeon Accepted Answer Pending Moderation
  1. Thursday, 28 December 2023 04:56 AM UTC
  2. PowerBuilder
  3. # 4

Hi Alexander,

 

I reproduced the problem in a Server 2022 environment. The preliminary analysis from the development indicates that it may be a problem caused by the upgrading to VS 2022 with 2022 R2. The specific cause needs to be further analyzed by the development. I will update it here in time when the problem is solved.

 

Merry Christmas and a Happy New Year!

 

Regards,

Kitty

Comment
Alexander Busch
  1. Alexander Busch
  2. Wednesday, 24 January 2024 20:40 PM UTC
Hello Kitty,



is there any news on this topic yet?



Regards,

Alexander
  1. Helpful
kitty he @Appeon
  1. kitty he @Appeon
  2. Thursday, 25 January 2024 02:24 AM UTC
Hi Alexander,



We fixed this issue in 2022 R3. It is recommended that you upgrade to PB 2022 R3 build 3289 to see if it resolves your issue.



Regards,

Kitty

  1. Helpful
Alexander Busch
  1. Alexander Busch
  2. Monday, 25 March 2024 12:44 PM UTC
Hi Kitty,

we just updated and the issue is fixed. Thanks for your help!
  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.