web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Business Portal Instal...
Microsoft Dynamics GP (Archived)

Business Portal Installation

(0) ShareShare
ReportReport
Posted on by Community Member

Hi,

I have Business Portal installation going, and when it reached the step asking for eConnect COM User, i entered a valid login info but got prompted error below.

"The domain must be an actual domain."

I tried different combination of domain names but it still couldn't get passed.

Thing is, eConnect is said to be the prerequisite for 'Order Management', but in this environment eConnect is already setup and running, using domain user as service account.

So my questions are:-

1. How to get past the domain name check that prompted the error above?

2. Or, how to get past the eConnect COM User step in the installation altogether?

*This post is locked for comments

I have the same question (0)
  • Jonathan Fear Profile Picture
    Jonathan Fear Microsoft Employee on at

    Hi Ivan,

    That is strange because I would expect BP to see that eConnect is already installed and configured although I would have to test this out. You don't have multiple domains that you are working with do you?

  • Community Member Profile Picture
    Community Member on at

    Hi Jonathan,

    Thanks for the reply. In fact this server is in single domain environment.

    I tried excluding the Order Management from the BP installation, and it went through well.

    Now when i use the Add Feature to add the Order Management, again it prompted the screen for eConnect COM User, then when i entered the info again it prompted the same "The domain must be an actual domain."

    Perhaps you can test out on your side?  

    As a side note, I've installed eConnect using the BP installer media, and also the standalone installer downloaded from PartnerSource. Either ways doesn't help in this matter.

  • Jonathan Fear Profile Picture
    Jonathan Fear Microsoft Employee on at

    Hi Ivan,

    Are you installing an a server that is a Domain Controller?

  • Community Member Profile Picture
    Community Member on at

    Hi Jonathan,

    No. The server i', installing BP is not a Domain Controller.

  • Jonathan Fear Profile Picture
    Jonathan Fear Microsoft Employee on at

    Sounds like this might be a Domain controller issue. Are you on a environment that is using multiple domains if so you need a full two-way trust between the two of them.

    When you're on the server doing the install of BP 6.0, if you open the command prompt (which you may need to right-click and choose 'Run As Administrator' on to open), then type in WHOAMI, what does it return for the user account? Have you tried using this user account for the eConnect COM+ user domain and ID to see if it still fails?

    Also, as a test, have you tried adding this domain account you're attempting to use, as a local administrator on both the SharePoint and SQL Servers both of which should be on the same exact domain, then try launching the BP 6.0 install and attempt to use the account again as the eConnect COM+ account? Remember, the account also needs to be a member of the DYNGRP role for the Dynamics GP databases.

    We've also seen this error occur if the domain name is different than the NetBios name. Usually in cases like this, we have to use the NetBios name to install the web applications for Dynamics GP, such as Business Portal.

    Other than the above, there isn't really a way to force the BP install to accept the domain name, it either accepts it when it verifies it or doesn't, from the handful of cases that we've even seen this type of message, it is usually some type of setup on the domain controller having to do with the domain name, such as an alias or NetBios being different as mentioned.

    Otherwise you may want to turn on a Windows Installer log and see if that has more information.

  • Community Member Profile Picture
    Community Member on at

    Hi Jonathan,

    Thanks for the detailed explanation.

    I've tried the list of your suggestions previously (as stated below), but result the same error.

    1. Run Installer as Administrator >> YES

    2. Use logged in user account as eConnect COM+ User >> YES

    3. Add domain account as local admin in SharePoint Server >> YES

    4. Add domain account as local admin in SQL Server >> YES

    5. SharePoint Server & SQL Server in same domain >> YES

    6. Domain account is member of DYNGRP role in SQL Server >> YES

    So without much further clue, i'd need help on the below.

    1. How to check the NetBios name of the domain name this server is joined to?

    2. How to turn on the Windows Installer Log?

        >>  Currently i can't find any installation log, and nothing recorded in the System / Application Event Log.

  • Jonathan Fear Profile Picture
    Jonathan Fear Microsoft Employee on at

    Hi Ivan,

    1. You can find the NetBOIS name when you go to Properties on My Computer. You then can compare this in AD. If you have questions on that you need to talk with the person who handles AD at your company.

    2. www.bing.com/search

  • Community Member Profile Picture
    Community Member on at

    Hi Jonathan,

    For the installer log, i'd need to first check with the administrators to enable that.

    As for the NetBIOS name, i'm not sure if this is relevant:-

    (using contoso.com as example)

    This server is joined to the domain abc.contoso.com

    The domain name contoso.com is a "public" domain which is listed in public DNSes, while abc.contoso.com is an "internal" domain, which is only listed in internal DNS.

    As such, is there any possibility that the NetBIOS name is abc.contoso?  Or is it only possible to have 'abc' as the NetBIOS name?

  • Community Member Profile Picture
    Community Member on at

    Hi Jonathan,

    Didn't hear from you the last few days, guess you must be off for holidays.

    Anyway, i'm pondering another workaround for this error, since i still couldn't get it through. Since it's asking to enter the info to create the eConnect COM+ User and failed, is there any way that i could first create the COM+ User, then let the installer to detect its existence then skip through that step?

    If that is a possible way around, any idea how i can do that?

  • Verified answer
    Jonathan Fear Profile Picture
    Jonathan Fear Microsoft Employee on at

    Hi Ivan,

    There isn't a way around setting up the user and the COM object. The issue is with the domain information you are using. At this point I am going to recommend you open a support incident as the issue is too complex to continue troubleshooting on the forums.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans