Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Configuration of Dynamic Media is not saved getting 500 status Code

Avatar

Level 4

Hi,

 

When we try to create the Dynamic Media Configuration, After entering our email address and password, we were able to access the company and company folder and fill out all of the necessary fields. However, when we clicked the "Save" button, we received the error message, "ERROR Failed to Save Configuration". When we inspect the network tab/bin/wcmcommand returns a status code of 500. Further investigation revealed that the authorfarm was returning a dispatcher status code of 500, despite our having granted /bin/* access to allow access. We are unsure of the cause of the failure and the 500 status code. Any information would be greatly appreciated.

1 Accepted Solution

Avatar

Correct answer by
Level 4

Hi,

We found the RCA. The problem is that when we create a Dynamic Media Configuration, the configuration is saved under the following path: /conf/global/settings/cloudconfigs. We couldn't find the cloudconfigs folder under /conf/global/settings when we dug deeper. That is why it returns a 500 error. We created the folder manually. It is now working as expected.

View solution in original post

3 Replies

Avatar

Level 4

Hi @Pallavi_Shukla_ ,

 

We are currently using AEM 6.5 SP9. We restarted the AEM Server but it didn't help us either.

We looked into the following links. The first link does not return their company list, but we do get our company list, but our configuration is not saved.

We looked at the second link as well, but it wasn't very helpful.

We're getting a 500 error. According to the dispatcher log, one of the farm files rejected /bin/wincommand, but we still allow /bin/*.

We opened a ticket with our Adobe CSE to investigate further on this.

Avatar

Correct answer by
Level 4

Hi,

We found the RCA. The problem is that when we create a Dynamic Media Configuration, the configuration is saved under the following path: /conf/global/settings/cloudconfigs. We couldn't find the cloudconfigs folder under /conf/global/settings when we dug deeper. That is why it returns a 500 error. We created the folder manually. It is now working as expected.