Data Mover service is not starting anymore (#04704983)

[glenn_]

Hello,

out of nothing the data mover service is not starting anymore. So my tape backup isn't working anymore either. I already had this problem some time ago but I could solve it by reinstalling everything. This time, that didn't work. When trying to start the service "Veeam Data Mover" it is being stopped again directly after.

The log file Svc.VeeamTransport.log lists the following error:

Code: Select all

[17.03.2021 14:07:33.434] < 12856> rpc      | WARN|Waiting for endpoint to be released
[17.03.2021 14:07:37.438] < 12856>          | WARN|Der Endpunkt ist doppelt
[17.03.2021 14:07:37.438] < 12856>          | >>  |Failed to register TCP/IP RPC endpoint. Port: [6162].
[17.03.2021 14:07:37.438] < 12856>          | >>  |--tr:Error code: 0x000006cc
[17.03.2021 14:07:37.438] < 12856> rpc      | Starting RPC listening. Failed.
[17.03.2021 14:07:37.438] < 12856> nfs      | ERR |Failed to start transport service.
[17.03.2021 14:07:37.438] < 12856> nfs      | >>  |Failed to register TCP/IP RPC endpoint.
[17.03.2021 14:07:37.438] < 12856> nfs      | >>  |--tr:Failed to start RPC listening.
[17.03.2021 14:07:37.438] < 12856> nfs      | >>  |--tr:Failed to initialize RPC runtime for 'Transport' service.

It seems that Microsoft message queue service is already running on port 6162. So is it possible to change the port number?

Kind regards,
Glenn

[Egor Yakovlev]

Seems like MSMQ went on a non-default service port.
I would check that service first.

/Thanks!

[pirx]

Interesting and maybe completely unrelated, yesterday I updated to latest Veeam v10 patch and I was unable to update the components (proxies etc) because the Veeam transport service was not removed during update (they were removed but the server was still running...). Windows patches were installed on all affected servers before Veeam patch. Support did not really know why this happened, some servers we had to rebooted, some seem to have fixed themselves after some time so that we could finally update all components.

[glenn_]

Seems like MSMQ went on a non-default service port.
I would check that service first.

Thank you for your quick response. Actually I don't know what the MSMQ is running for on this server. So I just stopped the service, nothing bad happened and Veeam is running again.