• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • PB 2017 R2: Converting PB COM target to .NET Assembly

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

Resolved PB 2017 R2: Converting PB COM target to .NET Assembly

  1. Issue
0
Votes
Undo
  1. Don Olliver
    Don Olliver
  2. PowerBuilder
  3. Friday, 23 March 2018 21:41 PM UTC

We are evaluating using PB 2017 R2 to convert a number of PB 11.5 COM components to .NET assemblies. All of these instantiate datawindows using PFC / PFE extensions.

I migrated one component to .NET, then attempted to load it from another .NET assembly. The load failed with this stack trace:

Sybase.DataWindow.DataWindowServerLoadFailedException: DataWindow Server PBDWM150.DLL or required DLLs (atl71.dll, msvcp71.dll or msvcr71.dll)  not found.
   at Sybase.DataWindow.DataStore.InitDataStore()
   at Sybase.DataWindow.DataStore..ctor()
   at Sybase.PowerBuilder.WinWebDataWindowCommon.DataStoreWrapper..ctor(PBDataStore ds)
   at Sybase.PowerBuilder.WinWebDataWindowCommon.PBDataStore..ctor()
   at c__pfc_n_ds..ctor()
   at c__n_ds..ctor()

All PB 2017 Runtime Packager files, including Sybase dlls, have been installed. In addition, I added the following (as stated in Help):

atl71.dll
ATL80.dll
atl100.dll
gdiplus.dll
msvcp71.dll
msvcp80.dll
msvcp100.dll
msvcr71.dll
msvcr80.dll
msvcr100.dll

Any suggestions for troubleshooting? My next step is to begin narrowing down possibilities by removing functionality from n_ds and pfc_n_ds.

Thanks,

Don Olliver

​

UPDATE: The message is embedded in Sybase.PowerBuilder.DataWindow.Win.dll.

 

  1. .NET Assembly
  2. Data
.NET Core based, with cross-OS support in PB 2018
any structure
Responses (3)
Markus Bienek
Markus Bienek Accepted Answer Pending Moderation
  1. Wednesday, 2 May 2018 09:58 AM UTC
  2. PowerBuilder
  3. # 1

Hi,

unfortunately I have no answer, I just have the same problem.

Have you found a solution?

 

Regards

Comment
Don Olliver
  1. Don Olliver
  2. Friday, 1 June 2018 21:10 PM UTC
Hi Markus,



Although my code did not reference it, the solution was to install PBDWM170.dll. I believe it includes a modified version of datawindow.net, which is probably required for datawindow access in a PB 2017 .NET assembly.



Don

  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Sunday, 25 March 2018 19:42 PM UTC
  2. PowerBuilder
  3. # 2

You need to include the PFC and PFE libraries in with your .NET assembly.

 

Olan

Comment
Don Olliver
  1. Don Olliver
  2. Monday, 26 March 2018 13:33 PM UTC
The DeployLog.txt file shows that both libraries are included.

  1. Helpful
There are no comments made yet.
Alfredo Aldama
Alfredo Aldama Accepted Answer Pending Moderation
  1. Saturday, 24 March 2018 17:36 PM UTC
  2. PowerBuilder
  3. # 3

 

Hi, 

I see this:

You have a reference to PBDWM150.DLL  in someplace, you must have a reference to PBDWM170.DLL (or equivalent in your version PB 2017)  and you have PBDWM150.DLL

Sybase.DataWindow.DataWindowServerLoadFailedException: DataWindow Server PBDWM150.DLL or required DLLs (atl71.dll, msvcp71.dll or msvcr71.dll)  not found.

 

I hope that the observation will serve you

Regards !

 

Comment
Don Olliver
  1. Don Olliver
  2. Sunday, 25 March 2018 14:29 PM UTC
Thank you, but our code is not referencing that DLL. I believe this exception is thrown by one of the other PB 2017 runtime DLLs.



Don

  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.