gfi backup scheduler service not running

#Gfi backup scheduler service not running update#
#Gfi backup scheduler service not running upgrade#
#Gfi backup scheduler service not running windows#

If you are not using the latest LanGuard version, Upgrade LanGuard. If you see these or similar errors, address them using the solution from Resolving 'Could not connect to database backend' Error in GFI LanGuard Console article.

'Login failure error repeated for all 10 attempts, stopped trying.'.

Source = 'Microsoft SQL Server Native Client 11.0', Description = 'Login failed for user.

'Error EOleException: 'Invalid connection string attribute''.

Check the debug log lanss_vXXX_attendantservice.csvfor the relevant errors:.

Ensure that the service account has a sysadmin role assigned within the SQL server.

The information stored in the database is being used to display the results in the Dashboard or Activity Monitor. In rare cases, the backend database connectivity issues might be the root cause of the scheduled scans' results not appearing in the Activity Monitor. Reregister it following the solution steps from this article. Eliminate them one by one.Ī possible root cause for the remote actions not starting is when the sub-module agentmanagercom.dll is not registered correctly in the GFI LanGuard server. If the scan results still do not appear there, the issue can be caused by some rare root causes explained below. Schedule a scan and check the results in the Activity Monitor.

Do the same for the Logon as a batch job policy.

Ensure the scanning account used and the Identity account of the LNSSCommunicator are included (add them if not included).

Locate the Replace a process level token policy and open the Properties dialog.

#Gfi backup scheduler service not running windows#

Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.Open the Local Security Policy editor (under Control Panel or running by gpedit.msc).

Open Dcomcnfg ( Start > Run > type dcomcnfg.exe and press Enter), navigate to Computers > My Computer > DCOM Config > LNSSCommunicator), right-click to open Properties, and switch to the Identity tab.If Alternative Credentials are specified AND Use per computer credentials when available IS checked AND the computer has Per-computer Credentials assigned in the Dashboard > Computer Properties dialog, then the specified Per-computer Credentials will be used.If Alternative Credentials are specified AND Use per computer credentials when available is NOT checked, then the specified Alternative Credentials will be used.If there are no credentials specified AND Use per computer credentials when available is NOT checked, then the GFI LanGuard Attendant Service account will be the one to be used.Determine the account being used for scanning by checking the scheduled scan > Properties > Logon Credentials tab:.Logon as a batch file right is needed for the remediation operations.Įnsure service account correct credentials and permissionsĪdd the account used for scanning and the account used for the LNSSCommunicator module to the Replace a process level token and Logon as a batch job local security policies as follows:.

#Gfi backup scheduler service not running update#

Without it, the scanning account will launch the scheduled scan and update the ' Last Scanned' column value but then fail to launch the lnsscomm.exe process, and the scan will not actually happen. The account used for scanning must have the Replace a process level token right to launch the lnsscomm.exe process.The most common root cause for such an issue is that the account used for scanning or the account used for the LNSSCommunicator module is lacking permissions: Remediation jobs also do not run and do not show in Activity Monitor. Scheduled scans do not seem to be working / running on schedule, and their results do not appear in the Activity Monitor.