SoapFaulCodeName Core.LoginFailed |SoapFaulCodeNamespace urn|Core.service.livelink.opentext.com Inva

We are having an install issue with SAP/ELS/OTCS installation.

I have completed the build of Content Server, Archive Server, and Enterprise Library Services, from Tomcat manager, all the services are running, from w3monc I get all green lights (as I do when I run dpinfo). However when I run the diagnostic program from the ECC client and I receive the following error (which involves further errors as a result):

SoapFaulCodeName: Core.LoginFailed |SoapFaulCodeNamespace: urn:Core.service.livelink.opentext.com Invalid username/password specified

I have confirmed that:

I can access Content Server that have been inputed into the Enterprise Library Server Settings
the archivelink account within ELS has been added to the CSAdmin role within Archive Server
the archivelink account has been setup within Content Server with full admin privileges and that when directly connecting to Content Server it will authenticate
that I can connect to the Archive Server via the Admin Client
that my account (BARBENM) can both connect to SAP ECC client, as well through to Content Server (via Windows Authentication).
The CAP Connector module is installed, and pointed at the Archive Server

I am assuming that the error is coming out of the CAPService

2012-02-20 15:25:10,623 ERROR [http-8080-Processor23] otx.LES : com.opentext.livelink.service.core.coreservices.CoreServicesRequestContext - Unable to access the CapSessionInfo.

Is there a way to test or force the CAP webservice being provided to confirm that its status is up or down?

This is impacting on our timelines and it appears to be some form dark art required to get these services working and I would like to get to the bottom.

Thanks in advance

Matthew Barben

Find more posts tagged with

Comments

Radu_Fantaziu

Hi,

Just some questions:

Could you please send us the rcs.log file?

Could you see (using MMC-Admin) if all the services are running?

Are you using SAP-SSO for authentication?

Regards,

Radu

Appu_Nair

Is livelink on Oracle(case sensistive database) then creating the users in lower case may be your problem as I see this from your posting.Or to see if you have a case sensistive database you could try creating 'barbenm' again,if this succeeds you have a case sensitive database

"that my account (BARBENM) can both connect to SAP ECC client, as well through to Content Server (via Windows Authentication)."

The flow is like that .SAP may present your login id from SAP thru a auth token which consists of your usersid in SAP.It may be decrypted by the CAP driver as 'BARBENM'

Then it tries to login you as 'BARBENM' using the LESAUTHdriver that you setup standard les impersonateuser call.

If you put wantlapilogs=true in livelink you can see the arguments that RCS is trying to pass into livelink.RCS is like you writing a Enterprise library services code fragment against livelink,it is a client to livelink at that point.

I use a case sensitive oracle so we create all our domain users as lowercase stripping out the domain info.We have a very similar setup as well.

Matthew_Barben

Hi Radu,

I have raised an OSS note with the following logs taken during the test:

Tomcat.zip - Tomcat logs, including the rcs.log
ArchiveServer.zip - Archive Server logs
ContentServer.zip - Content Server logs
sysreport.zip - Content Server system report.

I can confirm from the Admin Client that the cap service is running.

For Content Server we are using Windows Authentication NTLM.

Matthew_Barben

Hi Appu,

With the windows authentication on the Content Server side IIS is passing through the authentication as 'barbenm'. As a result to reduce the amount of authentciation failures due to the Oracle DB I set the AD sync Username Case Sensitivity setting to 'lowercase'

This enables windows authentication to work for OTCS. This approach has worked for our DEV, QA and Training systems. Now we are approaching the production build and we are not seeing this issue.

As a test I also created a new user called 'BARBENM' (as opposed to my windows authenticated 'barbenm') and the test still failed. It is almost as if the authentication is being corrupted by the time it reaches Content Server.

I will have a look at turning on the lapi logs, however when I was looking at the server through builder I was seeing :

02/21/2012 10:17:28 [3105863754] 0000001886: CAPI.Log: Arguments = 'A<1,?,''name''=''otx.sap.rm.SystemArchiveLink''>'
02/21/2012 10:17:28 [3105863841] 0000001887: CAPI.Log: ServiceMethod = 'GetELType'
02/21/2012 10:17:28 [3105863926] 0000001888: CAPI.Log: ServiceName = 'EnterpriseLibrary'
02/21/2012 10:17:28 [3105864007] 0000001889: CAPI.Log: _ApiName = 'InvokeService'
02/21/2012 10:17:28 [3105864088] 0000001890: CAPI.Log: _ClientVersion = '9.7.1'
02/21/2012 10:17:28 [3105864169] 0000001891: CAPI.Log: _ConnectionName = ''
02/21/2012 10:17:28 [3105864248] 0000001892: CAPI.Log: _DomainName = ''
02/21/2012 10:17:28 [3105864332] 0000001893: CAPI.Log: _ImpersonateUserDomain = ''
02/21/2012 10:17:28 [3105864467] 0000001894: CAPI.Log: _LLENVIRON_ASSOC = 'A<1,?,''REMOTE_ADDR''=''172.16.22.45''>'
02/21/2012 10:17:28 [3105864560] 0000001895: CAPI.Log: _Request = 'llweb'
02/21/2012 10:17:28 [3105864641] 0000001896: CAPI.Log: _UserName = ''
02/21/2012 10:17:28 [3105864700] 0000001897: CAPI.Log: _UserPassword = 'XXXXXXXXXX'
02/21/2012 10:17:28 [3105866231] 0000001898: ****** CAPIAllocConnect called ...
02/21/2012 10:17:28 [3105866358] 0000001899: KSqlOCI10::SubclassConnect() before OCIServerAttach

Winfried_Hellmann

I seem to have the same problem. Did you come up with a solution?

I just openend a new post for this: Invalid username/password