Help with EWS Dev sandbox needed

Hello,

I'm trying to set up a DEV sandbox on Windows 7 (64 bit) running Livelink 971 UTF-8 with SQL Server. Livelink is up and running, but I cannot get the services working. The instructions seem to be for IIS 6.0 or lower and I'm running IIS 7.5. I have a similar environment set up for CS 10u4 on Windows 7 x64 and Oracle and it worked fine. I probably did something in the one environment that I forgot in the other but for the life of me I can't think of what it could be nor when comparing the environments side by side can I see anything. The error message I'm getting when I try to connect to the service WSDL URL is the following:

HTTP Error 500.22 - Internal Server Error

An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

Can anyone give me a short-list of things to check to get tot he bottom of this? As I said, I was able to configure it for CS 10 on an identical platform with no such troubles.

-Hugh

Find more posts tagged with

Comments

Bhupinder_Singh

For help with IIS 7, Rob Coutts’ documentation on how to configure IIS 7 with CS10 is part of this document:

Case Study - Deploying Content Server 10 on Windows 2008 R2 and SQL Server 2008 - https://knowledge.opentext.com/knowledge/llisapi.dll/Open/18165792

- Bhupinder

Hugh_Ferguson

I'm not sure if this will solve my particular problem as you don't have roles in WIndows 7, although it does contain useful information for LL971 setups in a IIS 7.5 environment.

Upon digging a bit more, I discovered that the CS 10 version of the dotnet web app's config had additional values in it.

<system.webServer>

</modules>

</system.webServer>

I added these. That didn't work until I ran the .NET tool for both v3.0 (ServiceModelReg). Now I'm getting this error, which is telling me that something is wrong with the LAPIService DLL:

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'LapiService' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Source Error:

Line 57: <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

Line 58: <add assembly="System.Web.Mobile, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

Line 59: <add assembly="*"/>

Line 60: <add assembly="System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>

Line 61: <add assembly="System.IdentityModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>

Source File: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Config\web.config Line: 59

Assembly Load Trace: The following information can be helpful to determine why the assembly 'LapiService' could not be loaded.

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].

Has anyone come across this particular error, and if so, what was the workaround?

-Hugh

Hugh_Ferguson

ADDENDUM: I used regedit to add that debug flag into my registry and got the following additional logging info:

=== Pre-bind state information === LOG: User = IIS APPPOOL\DefaultAppPool LOG: DisplayName = LapiService (Partial) LOG: Appbase = file:///C:/OPENTEXT/LL971/webservices/dotnet/les-services/ LOG: Initial PrivatePath = C:\OPENTEXT\LL971\webservices\dotnet\les-services\bin Calling assembly : (Unknown). === LOG: This bind starts in default load context. LOG: Using application configuration file: C:\OPENTEXT\LL971\webservices\dotnet\les-services\web.config LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Aspnet.config LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config. LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind). LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/Temporary ASP.NET Files/les-services/a9bd8de8/7de1c9bc/LapiService.DLL. LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/Temporary ASP.NET Files/les-services/a9bd8de8/7de1c9bc/LapiService/LapiService.DLL. LOG: Attempting download of new URL file:///C:/OPENTEXT/LL971/webservices/dotnet/les-services/bin/LapiService.DLL. ERR: Failed to complete setup of assembly (hr = 0x8007000b). Probing terminated.

Does this give any sort of meaningful indication as to what's wrong? I suspect it has to do with varying versions of .NET framework but I'm not sure how. My Win 7 x64 environments all have .NET 4.0, and the connection pools for IIS are 2.0 and 4.0 (the defaults being 2.0) Once again, this all works in the CS 10 version of the environment, but client has LL 971 so I have to build to that.

-Hugh

Appu_Nair1

Hugh,

Without going too complicated into the weeds I am sharing my config and my experiences in a IIs7.5 W2k8

My livelink is installed and working in e:\webapps\opentext

I exposed e:\webapps\opentext\webservices\les-services as a APPLICATION

The Livelink-WebServices Application pool looks like this

Our Webservices does not like the standard Web.Config coming from OT so I inserted this line there

Everything else is standard OT.

</baseAddressPrefixFilters>

</serviceHostingEnvironment>

</system.serviceModel>

My colleague Ossie Moore has told this forum why we end up doing this this can be safely omitted in your case

That is think is my config

There’s a boat load of IIS config. A friendly OT architect gave me a command line that does it without you sitting at the GUI

The box needs Asp.NET otherwise nothing will work.

This command line will do the entire configuring of IIS7/7.5

CMD /C START /w PKGMGR.EXE /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-HttpErrors;IIS-ApplicationDevelopment;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS-RequestMonitor;IIS-Security;IIS-WindowsAuthentication;IIS-RequestFiltering;IIS-Performance;IIS-HttpCompressionStatic;IIS-WebServerManagementTools;IIS-ManagementScriptingTools;IIS-NetFxExtensibility;IIS-ManagementService;IIS-IIS6ManagementCompatibility;IIS-LegacyScripts;IIS-Metabase;IIS-WMICompatibility; IIS-WebDAVPublishing and make it almost look ike this when you see the GUI

cid:image002.png@01CE683D.EFAD2A40

The Authentication of the livelink CWS is anonymous. If you need SSO with DirSvcs I will share takes a lot more work to get it done but I have that running as well.

Do have a compare with mine on yours as well

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Thursday, June 13, 2013 2:12 PM
To: eLink Recipient
Subject: [EXTERNAL]Help with EWS Dev sandbox needed

Help with EWS Dev sandbox needed

Posted by hughf@ca.ibm.com (Ferguson, Hugh) On 06-13-2013 15:08

I'm not sure if this will solve my particular problem as you don't have roles in WIndows 7, although it does contain useful information for LL971 setups in a IIS 7.5 environment.

Upon digging a bit more, I discovered that the CS 10 version of the dotnet web app's config had additional values in it.

<system.webServer>

</modules>

</system.webServer>

I added these. That didn't work until I ran the .NET tool for both v3.0 (ServiceModelReg). Now I'm getting this error, which is telling me that something is wrong with the LAPIService DLL:

Configuration Error

Line 57: <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

Line 58: <add assembly="System.Web.Mobile, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

Line 59: <add assembly="*"/>

Line 60: <add assembly="System.Runtime.Serialization, Ver sion=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>

Line 61: <add assembly="System.IdentityModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>

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].

Has anyone come across this particular error, and if so, what was the workaround?

-Hugh

[To post a comment, use the normal reply function]
Topic:	Help with EWS Dev sandbox needed
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

Hello Hugh,

I have seen similar errors when trying to access the WebServices and it is usually 1 of 2 things:
1. Because LL 9.7.1 is a 32 bit application, you may need to use the 32-bit version of .NET and/or enable 32-bit applications within IIS where the Web Services are deployed.
2. You may also be missing a role on your server, but as you mentioned, you are using Windows 7. I'm not sure how this would work on Windows 7 but I have a screenshot of the roles enabled on my Windows Server 2008 R2. Keep in mind, I have the CS10 version of WebServices deployed.

This leads me to my next point... According to the 9.7.1 SDK documentation, Windows 7 and Windows Server 2008 are not supported. There are a couple of reasons for this and why it doesn't work on Win7. In order to install/deploy the .NET version of the Web Services, you need both the Microsoft .NET Framework 3.5 Service Pack 1 AND Microsoft Visual J# Version 2.0 Redistributable Package - Second Edition (x86). If you go to Microsoft's website and try to download the Visual J# Version 2.0 Redistributable Package (x86); it mentions that this is only supported on Windows XP and Server 2003. It is not support and cannot be installed on any 64-bit OS. For reference, you can review the 9.7.1 EWS prerequisites here:
https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=19572224&objAction=browse&viewType=1

I recently tried to deploy the 9.7.1 version of EWS on Windows Server 2008 SP2 (which is different than R2) and I was successful. However, you will still receive a runtime error because of the missing dependancy on the Visual J# Version 2.0 Redistributable Package (x86). If you need to use the 9.7.1 version of EWS, I would suggest deploying it on Windows Server 2003. You can also use the Java version of EWS which can be deployed on Tomcat.

Regards,

André Roy
Principal Technical Analyst | Customer Support

André_Roy

attaching screenshot of Roles.

Quoted Andre Roy on 2013-06-13 15:51:

Hello Hugh,

André Roy
Principal Technical Analyst | Customer Support

roles.png

Appu_Nair1

BTW I am running into errors like you have if I tried to use the webservices binaries on IIS 7/7.5

I know that VJslib is installed on the livelink 9.7.1 instance to make webservices work in 9.7.1.I am not sure

if you can do that in 64bit stuff anymore requires more knowledgeable people than me.

Probably if you can send a command from a proper cs10 webservice into a 9.7.1 server that would fix you

Hugh_Ferguson

I totally forgot about 32 bit vs 64 bit. Thanks. I have given up trying to get this working on a WIn 7, and for my sandbox am trying to use Tomcat instead. I assume I can still reference tomcat from Visual Studio (client is using a C#/Microsoft shop for their development).

-Hugh

Kumar Dwarakanath

Guys Try Setting Application Pool Identity to NetworkService . This solved my problem for IIS 7 2008

Regards,

Kumar