Samba service refusing to start

Hi, I'm looking for a bit of help with my Clearos install. I recently installed a few various items from the marketplace, however after using the new features for a bit I decided to uninstall them as they weren't working as I was hoping. These include:

2FA for Webconfig
Directory Server

After uninstalling these I've noticed that Samba is now refusing to start. When I click the start button from within the UI I receive no error message, it just doesn't start. I've ran the command "service smb status" and the results are below:

Server Version: 7.5

● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-12-07 13:54:12 CST; 5min ago
Process: 10644 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 10644 (code=exited, status=1/FAILURE)

Dec 07 13:54:12 server.domain.com smbd[10644]: [2018/12/07 13:54:12.342288, 0] ../source3/passdb/secrets.c:362(fetch_ldap_pw)
Dec 07 13:54:12 server.domain.com smbd[10644]: fetch_ldap_pw: neither ldap secret retrieved!
Dec 07 13:54:12 server.domain.com smbd[10644]: [2018/12/07 13:54:12.342372, 0] ../source3/passdb/pdb_ldap.c:6542(pdb_init_ldapsam_common)
Dec 07 13:54:12 server.domain.com smbd[10644]: pdb_init_ldapsam_common: Failed to retrieve LDAP password from secrets.tdb
Dec 07 13:54:12 server.domain.com smbd[10644]: [2018/12/07 13:54:12.342404, 0] ../source3/passdb/pdb_interface.c:180(make_pdb_method_name)
Dec 07 13:54:12 server.domain.com smbd[10644]: pdb backend ldapsam:ldap://127.0.0.1 did not correctly init (error was NT_STATUS_NO_MEMORY)
Dec 07 13:54:12 server.domain.com systemd[1]: smb.service: main process exited, code=exited, status=1/FAILURE
Dec 07 13:54:12 server.domain.com systemd[1]: Failed to start Samba SMB Daemon.
Dec 07 13:54:12 server.domain.com systemd[1]: Unit smb.service entered failed state.
Dec 07 13:54:12 server.domain.com systemd[1]: smb.service failed.


It appears that it's a password issue. Which password needs to be corrected and how would I correct this? The root password hasn't been changed and I can still successfully login via ssh and the UI.

Note: the server name has been replaced with server.domain.com for privacy.

Thank you,
Toasty