Getting error in Enterprise Library entry in Admin Client

Hello Team,

We are performing HTTP to HTTPS configuration in our entire system. In Archive server admin client, we are getting a error when we log in and expand the enterprise library. The error is :

Getting category type failed!
An unknown error occurred. (ObjectTypeName=com.sap.archivelink.base)
Error getting object type!

We also could not find out the Enterprise library IDs that we have created earlier. As a result we are unable to download the documents from content server.

Please help us to resolve the issue.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

AdrianBackler

Hi
So, am I right to understand you started with a working HTTP environment? And, by changing to HTTPS you get these errors? And, if you revert to HTTP all is well?
Have you implemented HTTPS step-by-step? Which components now use HTTPS? Are the certificates self-signed, signed by your own (or other non-public) issuer, or by a well-known public issuer (with their certifcates in Windows and Java keystores?
As always, log files are very helpful in these cases when trying to find the reasons behind various errors.
You say you cannot download documents from Content Server. Is that direct downloads through a web browser? Or what is the scenario?
Thanks
Adrian

Sanmoy Sen

Yes, when we revert the HTTPS, it is working fine. We have implemented HTTPS step by step. Our Archive server, OTDS, OTCS and SAP all are in HTTPS. Certificates are signed by well known public issuer. We are unable to download the document from Content server URL. We are unable to upload document manually in OTCS as well.

AdrianBackler

Hi
The reason for asking about step by step was to know which service changing from HTTP to HTTPS stopped things working.
Also, is my assumption that you are referring to Content Server documents that are stored in Archive Server:

We are unable to download the document from Content server URL. We are unable to upload document manually in OTCS as well.

What about EFS content?

Sticking with my assumption, please enable WARNING, INFO and DEBUG logging for the Archive Storage Provider then reproduce the problem downloading from Content Server. Afterwards, upload the easp_dsh.log* file(s).
Thanks
Adrian

Appu Nair

That sounds like an involved debugging not possible within the forum in any case if you increase thread logging and connect logging you would know why errors are happening. Is your Livelink configured with a storage rule that allows only AS as storage or is there an EFS that you have setup. To make something go to an EFS the service user of Content Server should be an administrator on that machine and you should arrange a storage rule that will fire first and will place it in EFS. Can you add a versionless object in your setup like a folder in your livelink.To me, it sounds like an install gone bad which cannot be analyzed without engaging proper OT support. As @AdrianBackler said AS implies EASP.dsh logging can tell you what if communication to AS is happening correctly but a Livelink with EFS can be quickly made to see if the LL install install is workable or not.