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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP 2018 R2 error when Testing e-mail action

(0) ShareShare
ReportReport
Posted on by

Dear All,

Kindly help, on this issue.

Test Failed, Check your Server information for GP Web Services.

RomRyan

*This post is locked for comments

I have the same question (0)
  • Derek Albaugh Profile Picture
    Microsoft Employee on at

    What exactly are you doing when you get this message? We need more information....

    If this is from the 'Test E-Mail Action' in the Workflow Setup window, to test the Web Services, verify you've entered the correct server name that Web Services is installed onto, along with the port number being used, which is normally 48620 by default.

    If you've done this, verify your Web Services is installed and working correctly, using the following:

    1. Verify that you can successfully access these four URLs:

      a. http://<webservername>:48620/Dynamics/GPService

      b. http://<webservername>:48620/DynamicsGPWebServices

      c. http://<webservername>:48620/DynamicsSecurityService

      d. http://<webservername>:48621/

         Note: Replace <webservername> with the actual server name that Web Services for Dynamics GP is installed onto. Port 48620 and 48621 are default and could possibly be different on your machine if changed during installation.

         Note2: In each of these pages, there will be a wsdl link(s), clicking on them should take you to an XML page.

    2. If you can access these URLs without error, then launch the Dynamics Security Console under Control Panel > Administrative Tools:

       **NOTE: You’ll need to be logged on as a Security Admin for Web Services to have access to the Dynamics Security Console and Exceptions Console.

      a. On the right-hand side, click on 'Select Applications'. A small window showing 'Dynamics GP Web Services' marked inside should show. Click OK on this window.

      b. On the left-hand side of the Dynamics Security Console, expand 'Dynamics GP Web Services'

      c. Click on 'Policy' and verify that you can see a list of policies in the middle pane without any errors.

      d. Click on 'Entity ID Assignments' and verify that no error shows in the middle pane of the Console. Try adding a Salesperson, sales territory, Customer, Vendor, etc., just to verify that Web Services can pull the company information from Dynamics GP. You don’t have to actually create the entity ID.

    3. Lastly, in Control Panel > Administrative Tools, launch the Dynamics GP Web Services Exceptions Console and verify you can click on both the 'System' and 'Validation' exceptions link without seeing any errors in the middle pane of the Console.

    4. Lastly, run the following script against your DYNAMICS/system database for Dynamics GP:

               Select * from WSInstallStatus

      You should see 5 records in this table for the DYNAMICS/system database and 4 records each for all company databases that have Web Services installed on them. If you're on GP 2018, they all should show a version of 18.0.xxxx and the Status should be 0 (zero) for all of them, indicating the loaders successfully installed.

      Make sure you see the company database(s) that you need/want to approve workflows through email listed in this table, otherwise it won't work.

    Thank you

  • Suggested answer
    kdd281 Profile Picture
    469 on at

    I used this link to help me to install web services : www.azurecurve.co.uk/.../hands-on-with-mdgp-2018-rtm-install-web-services-runtime

    Check your firewall too.

  • Romryan Profile Picture
    on at

    Derek,

    I have checked everything using your detailed procedure and everything is ok as your expectations. What I realised is that on the window for workflow set up, on enable e-mail section for workflows (Dynamics GP Web Services Server), I had ticked "This server requires a secure connection (SSL)" , once I unticked, the test email access for workflow is now a success. The only issue I have now is the top part of this window regarding smtp.office365.com. The test emails are all failing. I have gone to an extent of setting a database mail at SQL server level and at this stage its failing too. This was a direct process on other mail servers but its proves futile on office 365. I have everything correct including, my valid office 365 email, port 587 and the basic authentication part but no breakthrough.

    RomRyan

  • Romryan Profile Picture
    on at

    Kdd281,

    The firewalls have been down. The test email option is till not firing emails on office 365.

  • Verified answer
    Derek Albaugh Profile Picture
    Microsoft Employee on at

    Using an O365 account/SMTP information for the Workflow Setup window, I've always used port 587 and marked the option for 'This server requires a secure connection (SSL)'.

    Then under 'SMTP Authentication', mark Basic Authentication and enter the O365 credentials again, to match the Email Address you entered above in the same window.

    The SMTP server is smtp.office365.com.

    For a outlook.com email account, I've used the server name of smtp-mail.outlook.com, port 587 and again marked the 'This server requires a secure connection (SSL)' option. Then you'd also mark Basic Authentication and enter the same outlook.com email address and password as mentioned above in the Workflow Setup window.

    The other thing I'll mention with the Workflow Setup window and the Test Emails, is that we've seen where, when O365 accounts are being used and they have multi-factor authentication (MFA) enabled on them, it can cause the test emails not to be sent out, so if you have MFA enabled, try disabling it and testing.

    Also, overall in Dynamics GP, not necessarily just with the Workflow emails, we've seen where, as O365 now mainly uses 'modern' authentication, if the basic/legacy authentication is disabled, that can cause the emails not to work at all, so something to look at.

    The best way to determine if it is an issue with the O365 account credentials/SMTP server information, is to create a non-O365 Outlook.com email address, login to this address one time so you can verify it (otherwise you won't be able to use it until you do), then enter this new outlook.com email address credentials and SMTP information as mentioned above, into the Workflow Setup window, save changes and try a test email to see if it goes out.

    More times than not, the outlook.com configuration will successfully send the test emails...….

    Thanks

  • Romryan Profile Picture
    on at

    Derek,

    Thanks so much. I really appreciate your help. I am sorted the issue was my O365 email was MFA enabled. I was given another email that wasn't MFA enabled and it has worked.

    Thanks again.

    RomRyan

  • Derek Albaugh Profile Picture
    Microsoft Employee on at

    Thanks for the update.

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans