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

Resolved Error trying to deploy web app

  1. How-to
0
Votes
Undo
  1. David Vasconcelos
    David Vasconcelos
  2. PowerBuilder
  3. Monday, 10 December 2018 17:52 PM UTC

Getting the following error when trying to deploy to our Web Server.  Anyone know what the following error could be?  I am able to connect to the web, powerserver and AEM.  I am running PB2017 R1.

Thanks, Dave V.

 

OLE ADSDSOObject LDAP/AD Query Intermittently Retu...
Run a String (Similar to dw evaluate/Exec Immediat...
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 10 December 2018 20:55 PM UTC
  2. PowerBuilder
  3. # 1

Hi David;

   What version & build of PowerServer are you using?

AEM:

Regards ... Chris

Comment
Load more comments
David Vasconcelos
  1. David Vasconcelos
  2. Wednesday, 12 December 2018 14:00 PM UTC
We do have the certificates in place, not sure why we are getting the error. But if its for deployment reasons only then we can live with it off. On another note. We are using your STD ldap service and we are having issues with it running on our Web Server.. We deployed it onto the web server, Do we also need to include any PB runtime files? We did the elevated permission per you document but we get the following error.

Line 384:

Line 385:

Line 386:

Line 387:

Line 388:



****** This is the error from the trace file..

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

*****************************************************************

If any thing looks odd or not installed if you could let me know that would be great.

AND again thanks for you time and effort helping me out.

Dave V>

  1. Helpful
David Vasconcelos
  1. David Vasconcelos
  2. Wednesday, 12 December 2018 14:02 PM UTC
Looks like the first copy did not come in so trying again

Line 384: compilation defaultLanguage="c#" debug="true">

Line 385: assemblies>

Line 386: add assembly="Sybase.PowerBuilder.Core, Version=17.0.0.0, Culture=neutral, PublicKeyToken=98a699138181d746"

Line 387: add assembly="Sybase.PowerBuilder.Common, Version=17.0.0.0, Culture=neutral, PublicKeyToken=98a699138181d746"

Line 388: add assembly="Sybase.PowerBuilder.Web.WebService, Version=17.0.0.0, Culture=neutral, PublicKeyToken=98a699138181d746"
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 12 December 2018 16:11 PM UTC
Hi David;



PB2017Rx would produce a .Net 4.x compliant web service. However, it does require the PB ".Net run time" to be deployed on to the IIS server. You can use the PB Packager utility to build the .Net PB runt-time MSI. However, you need to ...



a) create a PBPack.ini file the PB "Shared" folder

b) Add the following to the INI ...

[Packager]

DotNetComponents=1



HTH

Regards ... Chris
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Monday, 10 December 2018 18:10 PM UTC
  2. PowerBuilder
  3. # 2

you need to configure the PS toolkit and have it be able to connect to powerserver.  The toolkit isn't able to connect to powerserver (firewall issues?).  Test this in the toolkit configuration:

 

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.