Author: Bob Lin

Situation: The client has a problem to run a backup in Veeam. After he stops the backup job, he can’t starts some Veeam services with this message: Service on Local Computer started and then stopped.

Troubleshooting: We find this Event:

Source: Veeam Backup and Replication Service
Event ID: 0
Level: Error
Description:
Service cannot be started. System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.TcpListener.Start(Int32 backlog)
at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider, IAuthorizeRemotingConnection authorizeCallback)
at Veeam.Common.Remoting.CSrvTcpChannelRegistration..ctor(String channelName, Int32 port, IDictionary channelProperties, Boolean bEnableRemotingPerfLog)
at Veeam.Common.Remoting.CSrvTcpChannelRegistration.MakeWithAttempt…
From “Only one usage of each socket address (protocol/network address/port) is normally permitted”, we can tell, perhaps, someone is running the same program or some services are still runing.

Logoff all users and use Task Manger to end all relative services. That should fixes the problem.

Situation: The client has a problem to run a backup in Veeam. After he stops the backup job, he can’t starts some Veeam services with this message: Service on Local Computer started and then stopped.

Troubleshooting: 1. Wait. Since he stops the backup, it may take a long time to complete.

2. Perhaps, some services are still running. Run Task Manager to check any related services are running. End the services or process manually.

Log Name: Application
Source: Veeam Backup and Replication Service
Date: 8/4/2020 10:21:07 AM
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HSAVMHOST02.hsapayroll.com
Description:
Service cannot be started. System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.TcpListener.Start(Int32 backlog)
at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider, IAuthorizeRemotingConnection authorizeCallback)
at Veeam.Common.Remoting.CSrvTcpChannelRegistration..ctor(String channelName, Int32 port, IDictionary channelProperties, Boolean bEnableRemotingPerfLog)
at Veeam.Common.Remoting.CSrvTcpChannelRegistration.MakeWithAttempt…
Event Xml:
0 2 0 0x80000000000000 115161 Application HSAVMHOST02.hsapayroll.com Service cannot be started. System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.TcpListener.Start(Int32 backlog) at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse) at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data) at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel() at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider, IAuthorizeRemotingConnection authorizeCallback) at Veeam.Common.Remoting.CSrvTcpChannelRegistration..ctor(String channelName, Int32 port, IDictionary channelProperties, Boolean bEnableRemotingPerfLog) at Veeam.Common.Remoting.CSrvTcpChannelRegistration.MakeWithAttempt…

Situation: The client has a problem to access a shared network drive. Event some users can access it, but it is very slow.

Troubleshooting: From the Event Viewer, we find this Event:

Log Name: Veeam Backup
Event ID: 790
Level: Error
Description:
Retry of Agent Backup job ‘FILESVR01 – Q Drive’ finished with Failed.
Job details: Processing FILESVR01

The client has a Veeam Agent backup running o midnight. But it is failed. Then it continue to try until morning 8 AM starting to work. However, that cause slow or can’t be accessed. Stopping the backup fixes the problem.

Situation: The client has a problem to start Veeam Backup service. The Event Vewer log show this error.

vent ID: 0
Level: Error
Description:
Service cannot be started. Veeam.Backup.Common.CRegeneratedTraceException: Failed to start service —> Veeam.Backup.Common.CRegeneratedTraceException: Unable to sure whether all catalog folders are created. —> Veeam.Backup.Common.CRegeneratedTraceException: Failed to create folder ‘H:\VBRCatalog’. —> System.IO.DirectoryNotFoundException: Could not find a part of the path ‘H:\VBRCatalog’.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Veeam.Backup.Common.FileSystemEx.CreateFolder(String path)
— End of inner exception stack trace —
at Veeam.Backup.Common.CExceptionUtil.RegenTraceExc(Exception originalExc, String formatString, Object[] args)
at Veeam.Backup.Common.FileSystemEx.CreateFolder(String path)
at Veeam.Backup.CatalogFsLib.CCatStorePaths.MakeSureAllFoldersCreat…

Troubleshooting: The message is clear: “Failed to create folder ‘H:\VBRCatalog’. —> System.IO.DirectoryNotFoundException: Could not find a part of the path ‘H:\VBRCatalog'”.They installed the Veeam on an external USB initially. Then move the backup location to different drive but the configurebackup folder still locates in the USB. Moe the configurebackup folder to the same drive as the backup.

Situation: The client has QNAP storage. They can’t send notification with this error: Failed to send a test message using SMTP Service.

Troubleshooting: 1. SMTP settings is correct and test is fine.

2. However, test sent to Recipient failed.

3. We find Microsoft article, “How to set up a multifunction device or application to send email using Microsoft 365 or Office 365” mentioned: “Option 1 (recommended): Authenticate your device or application directly with a Microsoft 365 or Office 365 mailbox, and send mail using SMTP AUTH client submission. This option is not compatible with Microsoft Security Defaults or multi-factor authentication (MFA). If your environment uses Microsoft Security Defaults or MFA, we recommend using Option 2 or 3 below”.

$. the option 2 and option 3 are “Option 2: Send mail directly from your printer or application to Microsoft 365 or Office 365 (direct send)” and “Option 3: Configure a connector to send mail using Microsoft 365 or Office 365 SMTP relay”.

4. We use option 2 fixes the problem. Here is the settings

We recommend adding an SPF record to avoid having messages flagged as spam. If you are sending from a static IP address, add it to your SPF record in your domain registrar’s DNS settings as follows:

Please refer to this how to:

How to setup Notification on QNAP

Situation: When attempting to open a Network Interface Card (NIC) or click on the Property of the NIC, you may receive this popup message: An unexpected error occurred.

Cause: It may cause because some DLL files or registry settings were damaged; it could a bad hardware like cable.

Resolution: 1. Unplug the network cable and then try it.

2. Run SFC (System File Checker ) Utility to check and fix Corrupted System Files. To do that, run command prompt,

Type sfc /scannow, and then press ENTER

3. Modify the registry.

• Type cmd in the search bar, and select run as administrator.
• In the Command Prompt, type regsvr32 %systemroot%\system32\ole32.dll, and then click OK.
• In the RegSvr32 dialog box, click OK.
• Restart the computer.

Situation: when attempting to install Malwarebytes Endpoint Agent, you may receive this message: The installer has insufficient privileges to access this directory.

Resolution: Cancel the installation. Delete the old Malwarebytes Endpoint Agent folder. Try again.

Situation: The client has Malwarebytes cloud version. They find some machines don’t scan or need to scan for over one week.

Troubleshooting: 1. Make sure both Malwarebytes service and Malwarebytes Agent service are running.

2. Or you need to re-install the Malwarebytes Endpoint Agent. To do that, 1) uninstall it from Control Panel. 2) If the uninstall doesn’t work, try Support Command Tool downloaded from Malwarebytes. Refer to this post:

Malwarebytes Endpoint Agent Uninstall Failed with code: 80070643

3) Then re-install Malwarebytes Endpoint Agent.

I follow this post to remove Malwarebytes Endpoint Agent, but the Support Tool runs forever.

Malwarebytes Endpoint Agent Uninstall Failed with code: 80070643

Troubleshooting: The tool you are running is for Malwarebytes for client not for Agent. The Support Tool for agent is command line. The command looks like this:

msstcmd.exe /y /cleanup.

Situation: When attempting to uninstall Malwarebytes Endpoint Agent, it failed with code: 80070643.

Troubleshooting: Download Support command tool form Malwarebytes to uninstall it. For example

mbstcmd /y /cleanup

Please view this step by step video: