NetWorker service cannot be configured to start at boot after installing NW 19.10.0.2 on a Suse Linux server

NetWorker service cannot be configured to start on boot on NetWorker 19.10.0.2 on SLES 14 or SLES 15.

Enabling the service from the command line generated these messages-.

#systemctl enable networker.service
Synchronizing state of networker.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable networker
ln -sf ../networker /etc/init.d/rc3.d/S50networker
ln: failed to create symbolic link '/etc/init.d/rc3.d/S50networker': No such file or directory

The NetWorker service starts when manually started.

NetWorker 19.10 copies the networker service script to /etc/init.d and /etc/rc.d/init.d.

When systemctl encounters a script in the /etc/init.d directory that shares the same name as the service unit being controlled, it presumes a conventional SysV init-style service is being managed. Therefore, it attempts to activate the SysVinit compatibility layer for its management.

Workaround:

1. Rename /etc/init.d/networker as /etc/rc.d/networker:

   mv /etc/init.d/networker /etc/rc.d/networker

2. Enable the service:

   systemctl enable networker.service

SLES 14 and SLES 15 have a different file structure vs. pre-SLES 15 SP4.

A host that started out as SLES 12 SP5 and was then upgraded to SLES 15 SP4 has the following:
/etc/rc.d -> init.d
/etc/init.d
/etc/init.d/rc0.d
/etc/init.d /rc1.d
/etc/init.d /rc2.d
/etc/init.d/rc3.d
/etc/init.d/rc4.d
/etc/init.d/rc5.d

However, a host that starts at SLES 15 SP4 has separate /etc/rc.d, /etc/init.d, and /etc/rc.d/init.d. It does not have ANY of the rcX.d directories.