This is just an informational message meaning that the MSDTC service is

unavailable at the time when SQL Server is started. It won't result in any

problems with subsequent distributed transactions provided the MSDTC service is available later when the distributed transaction takes place.

The solution is to start MSDTC before SQL Server - by manually starting MSDTC before SQL Server or explicitly setting a service dependency between SQL Server and MSDTC.