Skip to Content
0
Former Member
Jun 24, 2009 at 03:57 PM

Archivelink to assap authentication error - documentum

1445 Views

Hi,

On our project we have configured SAP ArchiveLink Content Repositories (OAC0) that link to Documentum Archive Services for SAP (assap). Documents attached using FB03 for example would physically be saved in a Documentum repository. This was tested several times and was working correctly.

After a reboot of the Documentum server the archivelink component could no longer authorize itself on the documentum assap component.

The following error message is displayed in sap.

HTTP error: 400 Petici n incorrecta  Bad Request:
No connection to Docbase 'Doc_dev':  No connection
to Docbase 'Doc_dev(8)':  [DM_SESS

The Documentum assap error log indicates the following:

[2009-05-27 17:14:39,015|INFO |Thread-1              |com.documentum.ei.al.ALServlet|logVersionInfo|216 ]	
[2009-05-27 17:15:06,625|WARN |Thread-1              |com.documentum.ei.repository.ConnectionPool|<init>|85  ]	locksByDbConnections.size() == 0 is true
[2009-05-27 17:15:08,484|WARN |Thread-1              |com.documentum.ei.al.ALServlet|init|85  ]	Process Statistics Collection Disabled!
[2009-05-27 17:18:09,343|ERROR|http-8080-2           |com.documentum.ei.repository.ConnectionPool|initializeDocbase|366 ]	Session was not established for 'Doc_dev(1)'; trying one more time
com.documentum.ei.repository.exception.NoConnectionException: No connection to Docbase 'Doc_dev(1)':  [DM_SESSION_E_AUTH_FAIL]error:  "Authentication failed for user admindoc with docbase Doc_dev.Doc_dev@dw3doc."at com.documentum.ei.repository.ConnectionPool.getSession(ConnectionPool.java:199)
	at com.documentum.ei.repository.ConnectionPool.initializeDocbase

We have tried the username and password in Documentum Administrator and it works. Also in the ArchiveLink configuration in Documentum the connection seems to be ok. It is just from SAP that we are not able to connect anymore.

If anyone has encountered a similar situation before or has an idea of where we could look for the error. Your input would be very much appreciated.

Thanks & Regards,

Giwan