Installation issues with Content Web services

Im new to running Web Services with Livelink and tried to get it up and running on my local machine.

Im running Windows 7 with a IIS 7.5 trying to set up the Web services 9.7.1, got several other WCF solutions up and running on the machine so general configuration is ok.

After following the installation instruction (with modifications for using IIS 7.5) and verifying it with this adress as described in manual.

http://localhost/les-services/DocumentManagement.svc

I get the following error message.

-----------

Parser Error Message: The CLR Type 'OpenText.Livelink.Service.Core' could not be loaded during service compilation. Verify that this type is either defined in a source file located in the application's \App_Code directory, contained in a compiled assembly located in the application's \bin directory, or present in an assembly installed in the Global Assembly Cache. Note that the type name is case-sensitive and that the directories such as \App_Code and \bin must be located in the application's root directory and cannot be nested in subdirectories.

Source Error:

Line 1: <%@ ServiceHost Service="OpenText.Livelink.Service.DocMan.DocumentManagement_WCF" Factory="OpenText.Livelink.Service.Core" %>

Source File: /les-services/DocumentManagement.svc Line: 1

------------

The application pool is set to run w32 applications as mentioned in the FAQ.

Anyone who has seen this and can point me in right direction? I can add it to the gac if needed but none of it is mentioned in the installation instructions.

Regards

Urban

Find more posts tagged with

Comments

Ferdinand Prantl

I run into this problem when I wanted to have different WS in different virtual directories supported from physically different directories on the disk, like:

C:\OPENTEXT\webservices\dotnet\les-services

C:\OPENTEXT\webservices\dotnet\les-services-recordsmanagement

Because every virtual directory is working as a web application and includes its own bin, without GAC it doesn't see each other's bin content. I ended up copying the shared DLLs to every bin (including the OpenText.Livelink.Service.Core.dll.)

However, the DocumentManagement is packaged together with core, that's why I'd find weird that you got this error. Maybe you can make sure that your bin directory is complete and that you created the virtual directory as web application in IIS (with the execute applications flag - which is necessary to have a local bin there).

--- Ferda

sgrasley

Hi, Urban.

Do you have Visual J# 2.0 Second Edition x64 redistributable installed? Also, try changing the Managed Pipeline mode for your Application Pool. To use Integrated mode, I think you need to add the following to your web.config (after the system.web section):

    <system.webServer>
        <modules>
            <add name="LogModule" type="OpenText.Livelink.Service.Core.LogModule" preCondition="managedHandler"/>
        </modules>
        <validation validateIntegratedModeConfiguration="false"/>
    </system.webServer>

Hugh_Ferguson

I was getting exactly this problem. I finally got it working when I recreated my virtual directory as an application (basically, this is something new if you're used to IIS 6.0 or earlier). I then got a security exception, and after googling the error, found the answer on stackoverflow.com. if you get a security exception on the les-services application, you may need to go to your Application Pools settings (near the top of the IIS 7.X snap-in), click on Application Pool Defaults (in the right corner), then down under Process Model, change Identity to NetworkService from ApplicationPoolIdentity.

When I finally got my WSDL URL going, I oddly enough got a blank page but one which had tons of the expected XML content in the page source.

-Hugh Ferguson