Error: The configuration area at 'path' is not writeable. Please choose a writeable location.. | Community
Skip to main content
September 27, 2017
Solved

Error: The configuration area at 'path' is not writeable. Please choose a writeable location..

  • September 27, 2017
  • 13 replies
  • 4567 views

...using the '-configuration' command line option.

Can somebody explain me exactly how to enter this command line? I suppose I need to navigate in DOS to the correct executable location, then type the name of the executable followed by '-configuration' then enter the new path? Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Lee__A

For workbench configuration changes, edit the "workbench.ini" file and add the -Duser.home=<path working dir>.

13 replies

October 3, 2017

Thank-you that was the correct solution!

Lee__AAccepted solution
Employee
September 29, 2017

For workbench configuration changes, edit the "workbench.ini" file and add the -Duser.home=<path working dir>.

smacdonald2008
New Participant
September 28, 2017

I will ask AEM Form ppl to look here.

September 28, 2017

Isn't this exactly where we are or did you move the topic?

joerghoh
Employee
September 28, 2017

Maybe in the "Forms" subforum at Adobe Experience Manager Forms

Thanks,

Jörg

September 28, 2017

Should I post in another part of the forum?

joerghoh
Employee
September 28, 2017

OK, it's about the AEM Forms ... then I cannot help here, sorry.

Jörg

September 28, 2017

I need to change the path where the workbench data is written. It's pointing to a network location that no longer exist. It seems from the error message that a command must be entered like probably:

C:\Program Files (x86)\Adobe Experience Manager Forms Workbench\workbench\workbench.exe /configuration (then the new path??).

joerghoh
Employee
September 28, 2017

Hi,

I understand your problem, but I still don't know at what point you get this message. Can you elaborate?

smacdonald2008
New Participant
September 28, 2017

We are checking with internal AEM ppl. Will post back what we heard.