EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB32126: "MSIDeliveryEngine::hDelivery: Delivery Failed.....The TCP protocol is not configured on this machine" error is logged in the DSSErrors.log when an e-mail is not delivered using MicroStrategy Distribution Services 9.0.x running on Microsoft Windo


Community Admin

• Strategy


E-mails are not delivered using MicroStrategy Distriubtion Services 9.0.x on a Microsoft Windows operating system and the following error is logged in the DSSErrors.log at the time the issue occurs: "Distribution Service: MSIDeliveryEngine::hDelivery: Delivery Failed. Error string from ExecuteMultiProcess Error while sending email: MNet::SocketAddress::GetLocalMachineDomainNameServer() - FAIL. The TCP protocol is not configured on this machine. Registry error: NameServer and DhcpNameServer keys are not set up".

SYMPTOM:
E-mails are not delivered using Strategy Distriubtion Services 9.0.x on a Microsoft Windows operating system. The following error is logged in the DSSErrors.log at the time the issue occurs:
Distribution Service: MSIDeliveryEngine::hDelivery: Delivery Failed. Error string from ExecuteMultiProcess Error while sending email: MNet::SocketAddress::GetLocalMachineDomainNameServer() - FAIL. The TCP protocol is not configured on this machine. Registry error: NameServer and DhcpNameServer keys are not set up
 
CAUSE:
The TCP protocol is not properly configured on the Strategy Intelligence Server 9.0.x machine. One of the possible causes for the TCP protocol being incorrectly configured is an improper definition of the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
ACTION:
Contact the Windows System Administrator to properly configure the TCP protocol on the Strategy Intelligence Server 9.0.x machine.
The following is a general guide on what may need to be done; it is not intended to resolve the issue on all operating systems so make sure to contact the Windows System Administrator for complete steps:

  • If using DHCP, set the DHCPDomain and/or Domain registry values. For example, if the domain is 'xyz.com' set the string values as:

    Sample Code/Error
    DHCPDomain = xyz.com
    Domain = xyz.com

     
  • If using a static IP, set the DHCPNameServer and/or NameServer to use the IP address(es) of the Domain Name Server (DNS). If multiple addresses are required for these string values, the IP addresses must be split using a space, and not a comma. For example, if the DNS IP address is 123.456.789.000 and 123.456.789.111, set the string values as:

    Sample Code/Error
    DHCPNameServer = 123.456.789.00 123.456.789.111
    NameServer = 123.456.789.00 123.456.789.111

Once the registry string values are correctly defined, reboot the machine for them to take effect.


Comment

0 comments

Details

Knowledge Article

Published:

June 2, 2017

Last Updated:

June 2, 2017