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>

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"

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