Receiving HTTP 400 bad request when create content repository

[#1]

Hi,

I have a request to create content repository using oac0, I copied it from a working content repository, and the configurations are same, but my content repository is not working, I'm using easyware as HTTP server. I tried to create it by using csadmin, but I'm getting same error message and not able to create it, can anyone please help on this?

[Former Member]

Seems, I need to send ceritificate after create repository and need to active it in content server/easyware? But how to active it?

[DavidLY]

Hi,

For standard configuration you do not need to do anything else.

You can check that the system PSE is available (t-code strust) and then

send the certificate using t-code oaht.

Regards,

David

[Former Member]

Hi David,

I tried to use oaht, I clicked on "executed" button, but I got nothing, does this means certificate send without error?

Can you tell me how to check certificate via strust? There are some certificates, how do I know which one is for my content repository?

Thanks & Regards,

Mingjuan

[DavidLY]

Hi,

Yes. This means by using oaht in your case the certificate send without error.

Regarding STRUST you just need to make sure the System PSE is in status Green.

Regards,

David

[Former Member]

Seems I did everything correctly, also certificate status is green....Not sure why I'm still getting this error.

Thanks & Regards,

Mingjuan

[DavidLY]

Have you checked from the easyware side and made sure it accepted the certificate.

Regards,

David

[Former Member]

I'm not sure how to check certificate from easyware side, but I do request easyware support team to check if anything wrong with easyware system. Thank you.

Thanks & Regards,

Mingjuan Zhang

[Former Member]

Hi David,

After create repository in Easyware, we can do connection test successfully. But I have one more question, do we need to create schema or storage in easyware for this content repository? How?

Thanks & Regards,

Mingjuan Zhang

[DavidLY]

Hello,

The easyware is a third party content server, means the transaction csadmin must not used. The vendor has to inform you about the necessary script, but it is definitely not

"ContentServer/ContentServer.dll".

Regards,

David

[Former Member]

Hi David,

Thank you for replying me.

I'm not using "ContentServer/ContentServer.dll", I know this is for content server.

For easyware, I'm using another script, I copied this script from a working content repository.

AB is working content repository, it is working fine, and I can see it in csadmin.

I copied AB to a new content repository CD, now CD is not working, configuration is extacly same for AB and CD, but test connection is failing for CD. if we should not use csadmin, can you please tell me if any other configuration need to be done here?

Thanks & Regards,

Mingjuan

[DavidLY]

Hi,

You can check in transaction SLG1 to find more information regarding this after the test connection.

Regards,

David

[Former Member]

Hi,

Yes, I can see more details in slg1, but seems no useful information. Below is details, can you please have a look if anything wrong?

TEXT       HTTP/1.1 400 Bad Request

TEXT       server: Apache-/1.1

TEXT       content-type: text/html;charset=utf-8

TEXT       content-length: 975

TEXT       date: Tue, 30 Aug 2016 07:31:22 GMT

TEXT       connection: close

TEXT       ~remote_addr:

TEXT       ~uri_scheme_expanded: NONE

URL      

V1         400

V2         Bad Request

%LOGNUMBER 00000000000000165762

Thanks & Regards,

Mingjuan