locked
CRM Dynamics Connector NAV setup error message RRS feed

  • Question

  • Hello,

    I am trying to configure the Dynamics Connector for NAV. After installation the Adapter settings dialog pops up and the CRM connection settings test is passed successfully, but the NAV is not:

    I created an Integration account in the NAV CRONOS demo database with SUPER role and enabled "Connector" checkbox in the synchronization settings of Marketing Setup. And we have 3 server instances running, which is usually no problem and just the reason why it's called "DynamicsNAV2" on the screenshot.

    Neither with the default instance "DynamicsNAV" nor with Administrator account the test is able to succeed. Always the message appears immediately.

    Does someone has an idea what's could be wrong?

    More helpful would be to know where I can find the log file for the Connector, to investigate this more deep and to provide more detailed information.

    Regards

    Friday, April 27, 2012 12:16 PM

Answers

  • Now I am able to connect. Actually you should have a look into the Application logs on the NAV server (Administrative Tools > Event Viewer) and search for information events of the "MicrosoftDynamicsNAVServer", to find the entry in which the Web Services address is mentioned ("Microsoft Dynamics NAV Business Web Services are available at http://<MACHINE>.(<DOMAIN>).<COMPANY>.<TLD>:7047/DynamicsNAV2/WS/Services."). Since I did not use the FQDN(?) or address of that form I was not able to connect correctly, I guess.

    To be honest, I tried even this address several times before and I don't know the actual reason why it is working now, but restarts of services or re-set of the NAV "enable Connector" settings might help.

    In case you come across similar errors: you can try to go through all my posts here to find some possible sources of errors. But take care, the HTTP error codes for the NAV instances (as by default logged in the folder C:\WINDOWS\system32\LogFiles\HTTPERR on the NAV server) are sometimes misleading :)

    Regards

    • Marked as answer by G Jones Thursday, May 3, 2012 5:15 AM
    • Edited by G Jones Thursday, May 3, 2012 5:17 AM
    Thursday, May 3, 2012 5:15 AM

All replies

  • The above error was my fault, since I used the wrong port 7046 instead of 7047 as stated in the configuration file. Also I set the firewall exception on the CRM server but not on the NAV server (for port 7047).

    Now the NAV instance replies with an HTTP/400 error message ("Invalid hostname"):

    Only if I take the default "DynamicsNAV" as instance name it doesn't say it's invalid (returns HTTP/401 followed by HTTP/500), which looks like the Connector only works with default instance? I will try to further investigate this.

    Also I couldn't find any other log file than in C:\ProgramData\Microsoft Dynamics\Connector for Microsoft Dynamics\Logs. But at least - after opening port 7047 - it creates a log file for NAV connection, which is however not very descriptive to me:

    INFO TID:1 [2012-04-30T12:50:01.2098138+05:30]: Tracing for Assembly: Microsoft.Dynamics.Integration.Adapters.Nav2009.Configuration, FileVersion = 2.0.422.2
    INFO TID:1 [2012-04-30T12:50:01.2550134+05:30]: Start
       INFO TID:1 [2012-04-30T12:50:02.6237752+05:30]: Launching Windows application for configuration with command line arguments: BOTH
          INFO TID:1 [2012-04-30T12:51:49.8949455+05:30]: Configuration was canceled by the user.
       INFO TID:1 [2012-04-30T12:51:49.9499767+05:30]: 
       INFO TID:1 [2012-04-30T12:51:49.9499767+05:30]: Configuration Argument: INSTALLTYPE has value: BOTH
       INFO TID:1 [2012-04-30T12:51:49.9499767+05:30]: Configuration Argument: BaseWebServicesUrl has value: http://192.168.1.50:7047/DynamicsNAV/WS
       INFO TID:1 [2012-04-30T12:51:49.9509594+05:30]: Configuration Argument: DOMAIN has value: <DOMAIN>
       INFO TID:1 [2012-04-30T12:51:49.9509594+05:30]: Configuration Argument: USERNAME has value: Administrator
       INFO TID:1 [2012-04-30T12:51:49.9509594+05:30]: Configuration Argument: CRMADMINDOMAIN has value: <DOMAIN>
       INFO TID:1 [2012-04-30T12:51:49.9509594+05:30]: Configuration Argument: CRMADMINNAME has value: Administrator
       INFO TID:1 [2012-04-30T12:51:49.9509594+05:30]: Finished running the NAV Adapter Configuration utility.
    INFO TID:1 [2012-04-30T12:56:10.9733215+05:30]: Tracing for Assembly: Microsoft.Dynamics.Integration.Adapters.Nav2009.Configuration, FileVersion = 2.0.422.2
    INFO TID:1 [2012-04-30T12:56:10.9841268+05:30]: Start
       INFO TID:1 [2012-04-30T12:56:11.3357902+05:30]: Launching Windows application for configuration with command line arguments: BOTH
          INFO TID:1 [2012-04-30T14:19:05.1449396+05:30]: Configuration was canceled by the user.
       INFO TID:1 [2012-04-30T14:19:05.1557438+05:30]: 
       INFO TID:1 [2012-04-30T14:19:05.1557438+05:30]: Configuration Argument: INSTALLTYPE has value: BOTH
       INFO TID:1 [2012-04-30T14:19:05.1557438+05:30]: Configuration Argument: BaseWebServicesUrl has value: http://192.168.1.50:7047/DynamicsNAV2/WS
       INFO TID:1 [2012-04-30T14:19:05.1557438+05:30]: Configuration Argument: DOMAIN has value: <DOMAIN>
       INFO TID:1 [2012-04-30T14:19:05.1557438+05:30]: Configuration Argument: USERNAME has value: Administrator
       INFO TID:1 [2012-04-30T14:19:05.1557438+05:30]: Configuration Argument: CRMADMINDOMAIN has value: <DOMAIN>
       INFO TID:1 [2012-04-30T14:19:05.1557438+05:30]: Configuration Argument: CRMADMINNAME has value: Administrator
       INFO TID:1 [2012-04-30T14:19:05.1557438+05:30]: Finished running the NAV Adapter Configuration utility.
    • Edited by G Jones Tuesday, May 1, 2012 9:34 AM
    Monday, April 30, 2012 8:58 AM
  • The HTTPERR logfile looks like this:

    [...] 2012-05-01 08:55:30 192.168.1.107 57236 192.168.1.50 7047 HTTP/1.1 POST /DynamicsNAV2/WSSystemService 400 - Hostname - 2012-05-01 08:59:20 192.168.1.11 3708 192.168.1.50 7047 HTTP/1.1 GET /DynamicsNAV2/WS/SystemService 400 - Hostname - 2012-05-01 09:03:52 127.0.0.1 2474 127.0.0.1 7047 HTTP/1.1 GET /DynamincsNAV/WS/Services 400 - Hostname - 2012-05-01 09:05:18 127.0.0.1 2479 127.0.0.1 7047 HTTP/1.1 GET /DynamicsNAV2/WS/Services 400 - Hostname - 2012-05-01 09:05:36 127.0.0.1 2486 127.0.0.1 7047 HTTP/1.1 GET /DynamicsNAV2/WS/Services 400 - Hostname - 2012-05-01 09:23:27 192.168.1.11 3847 192.168.1.50 7047 HTTP/1.1 GET /DynamicsNAV2/WS/Services 400 - Hostname - 2012-05-01 09:23:30 192.168.1.11 3829 192.168.1.50 7047 - - - - - Timer_ConnectionIdle - 2012-05-01 10:48:09 192.168.1.11 4298 192.168.1.50 7047 HTTP/1.1 GET /DynamicsNAV2/ws/CRONUS_International_Ltd./Services 400 - Hostname - 2012-05-01 11:06:32 192.168.1.107 57412 192.168.1.50 7047 HTTP/1.1 POST /DynamicsNAV2/WSSystemService 400 - Hostname - 2012-05-01 11:07:46 192.168.1.50 3097 192.168.1.50 7047 HTTP/1.1 GET /DynamicsNAV2/WS/Services 400 - Hostname - 2012-05-01 11:12:47 192.168.1.107 57444 192.168.1.50 7047 HTTP/1.1 POST /DynamicsNAV2/WSSystemService 400 - Hostname - 2012-05-01 11:14:22 192.168.1.11 4540 192.168.1.50 7047 HTTP/1.1 GET /DynamicsNAV2/WS/CRONUS_International_Ltd./Services 400 - Hostname - 2012-05-01 11:19:55 192.168.1.11 4559 192.168.1.50 7047 - - - - - Timer_ConnectionIdle - 2012-05-01 12:18:08 192.168.1.107 57544 192.168.1.50 7047 HTTP/1.1 POST /DynamicsNAV2/WSSystemService 400 - Hostname -

    Actually for the particular NAV instance, which you want to use with Connector, a Web Services service is required, which was not the case for the NAV instance I tried to connect to. As a result, the HTTP/400 errors shown above are being created.

    Following this very good article http://msdn.microsoft.com/en-us/library/dd301437.aspx lets you easily create such services.

    Still, I cannot connect to the Web Services on http://192.168.1.50:7047/DynamicsNAV2/WS (which is supposed to be the right address, instead it "returns" HTTP/404 error - not found) with the Dynamics Connector NAV adapter, however am able to access the xml file under http://192.168.1.50:7047/DynamicsNAV2/WS/Services

    Any suggestions what can be wrong? (I know this is rather a CRM forum than NAV, but basically the Dynamics CRM to ERP Connector is not working, so I think here is kind of the right place to ask)
    • Edited by G Jones Thursday, May 3, 2012 4:38 AM
    Tuesday, May 1, 2012 12:34 PM
  • Now I am able to connect. Actually you should have a look into the Application logs on the NAV server (Administrative Tools > Event Viewer) and search for information events of the "MicrosoftDynamicsNAVServer", to find the entry in which the Web Services address is mentioned ("Microsoft Dynamics NAV Business Web Services are available at http://<MACHINE>.(<DOMAIN>).<COMPANY>.<TLD>:7047/DynamicsNAV2/WS/Services."). Since I did not use the FQDN(?) or address of that form I was not able to connect correctly, I guess.

    To be honest, I tried even this address several times before and I don't know the actual reason why it is working now, but restarts of services or re-set of the NAV "enable Connector" settings might help.

    In case you come across similar errors: you can try to go through all my posts here to find some possible sources of errors. But take care, the HTTP error codes for the NAV instances (as by default logged in the folder C:\WINDOWS\system32\LogFiles\HTTPERR on the NAV server) are sometimes misleading :)

    Regards

    • Marked as answer by G Jones Thursday, May 3, 2012 5:15 AM
    • Edited by G Jones Thursday, May 3, 2012 5:17 AM
    Thursday, May 3, 2012 5:15 AM
  • I solved this issue setting to true this value:

    <add key="WebServicesUseNTLMAuthentication" value="true"></add>

    in the C:\Program Files (x86)\Microsoft Dynamics NAV\60\Service\CustomSettings.config files

    Andrea

    Monday, May 7, 2012 2:50 PM
  • I solved the issue by doing all of these things listed above...and it still didn't work...instead of only restarting the service I restarted the whole server...then it worked perferctly...no need to understand...I just accept it :D
    Saturday, January 12, 2013 9:52 PM