Apache Directory Server: Leaded: Error

[pedroquarks]

Hello Dear community,
I'll really need your help/advice, because I've been with a big issue which I can not figure out per weeks. I've installed apache2 on my PC, with Debian(GNU/Linux 9.3 -stretch) and I have a error which I can not fix. The error is:
Setting up apacheds (2.0.0~M15-4) ...
Failed to start apacheds.service: Unit apacheds.service is not loaded properly: Invalid argument.
See system logs and 'systemctl status apacheds.service' for details.
invoke-rc.d: initscript apacheds, action "start" failed.
● apacheds.service - Apache Directory Server
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
Feb 16 15:06:22 debian systemd[1]: [/lib/systemd/system/apacheds.service:11] Executable path is not absolute, ignoring: ${JAVA_HOME}/bin/java ${JAVA_OPTS} -Dapacheds.controls=${ADS_CONTROLS} …}/
Feb 16 15:06:22 debian systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Feb 16 15:06:22 debian systemd[1]: [/lib/systemd/system/apacheds.service:11] Executable path is not absolute, ignoring: ${JAVA_HOME}/bin/java ${JAVA_OPTS} -Dapacheds.controls=${ADS_CONTROLS} …}/
Feb 16 15:06:22 debian systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Feb 16 15:26:09 debian systemd[1]: [/lib/systemd/system/apacheds.service:11] Executable path is not absolute, ignoring: ${JAVA_HOME}/bin/java ${JAVA_OPTS} -Dapacheds.controls=${ADS_CONTROLS} …}/
Feb 16 15:26:09 debian systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Feb 16 15:26:09 debian systemd[1]: [/lib/systemd/system/apacheds.service:11] Executable path is not absolute, ignoring: ${JAVA_HOME}/bin/java ${JAVA_OPTS} -Dapacheds.controls=${ADS_CONTROLS} …}/
Feb 16 15:26:09 debian systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Feb 16 15:26:09 debian systemd[1]: [/lib/systemd/system/apacheds.service:11] Executable path is not absolute, ignoring: ${JAVA_HOME}/bin/java ${JAVA_OPTS} -Dapacheds.controls=${ADS_CONTROLS} …}/
Feb 16 15:26:09 debian systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package apacheds (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
apacheds
E: Sub-process /usr/bin/dpkg returned an error code (1)
and with:
$ systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-02-16 17:14:04 -03; 12s ago
Process: 19096 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Feb 16 17:14:03 debian systemd[1]: apache2.service: Failed with result 'exit-code'.
Feb 16 17:14:04 debian systemd[1]: apache2.service: Service hold-off time over, scheduling restart.
Feb 16 17:14:04 debian systemd[1]: Stopped The Apache HTTP Server.
Feb 16 17:14:04 debian systemd[1]: apache2.service: Start request repeated too quickly.
Feb 16 17:14:04 debian systemd[1]: Failed to start The Apache HTTP Server.
Feb 16 17:14:04 debian systemd[1]: apache2.service: Unit entered failed state.
Feb 16 17:14:04 debian systemd[1]: apache2.service: Failed with result 'exit-code'.
Feb 16 17:14:09 debian systemd[1]: apache2.service: Start request repeated too quickly.
Feb 16 17:14:09 debian systemd[1]: Failed to start The Apache HTTP Server.
Feb 16 17:14:09 debian systemd[1]: apache2.service: Failed with result 'exit-code'.
and also,
$ journalctl -xe
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Unit apache2.service has begun starting up.
Feb 16 17:14:03 debian apachectl[19096]: apache2: Could not open configuration file /etc/apache2/apache2.conf: No such file or directory
Feb 16 17:14:03 debian apachectl[19096]: Action 'start' failed.
Feb 16 17:14:03 debian apachectl[19096]: The Apache error log may have more information.
Feb 16 17:14:03 debian systemd[1]: apache2.service: Control process exited, code=exited status=1
Feb 16 17:14:03 debian systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Unit apache2.service has failed.
-- The result is failed.
Feb 16 17:14:03 debian systemd[1]: apache2.service: Unit entered failed state.
Feb 16 17:14:03 debian systemd[1]: apache2.service: Failed with result 'exit-code'.
Feb 16 17:14:04 debian systemd[1]: apache2.service: Service hold-off time over, scheduling restart.
Feb 16 17:14:04 debian systemd[1]: Stopped The Apache HTTP Server.
-- Subject: Unit apache2.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Unit apache2.service has finished shutting down.
Feb 16 17:14:04 debian systemd[1]: apache2.service: Start request repeated too quickly.
Feb 16 17:14:04 debian systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Unit apache2.service has failed.
-- The result is failed.
Feb 16 17:14:04 debian systemd[1]: apache2.service: Unit entered failed state.
Feb 16 17:14:04 debian systemd[1]: apache2.service: Failed with result 'exit-code'.
Feb 16 17:14:04 debian kernel: perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
Feb 16 17:14:09 debian systemd[1]: apache2.service: Start request repeated too quickly.
Feb 16 17:14:09 debian systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Unit apache2.service has failed.
-- The result is failed.
Feb 16 17:14:09 debian systemd[1]: apache2.service: Failed with result 'exit-code'.
Feb 16 17:15:01 debian CRON[19209]: pam_unix(cron:session): session opened for user barman by (uid=0)
Feb 16 17:15:01 debian CRON[19210]: (barman) CMD ([ -x /usr/bin/barman ] && /usr/bin/barman -q cron)
Feb 16 17:15:01 debian CRON[19209]: pam_unix(cron:session): session closed for user barman
I've been looking for an answer but without any good news, and I've tryed to install any other package and I can not do it, because the at the end through the terminal came up always the same messange, about Loaded: error (Reason: Invalid argument).
I will appreciate your time and attention.
thank you!