I was once again wrestling with a Dynamic Connector install.
The hardest thing about using the Dynamic Connector is as soon as you get an error, it’s practically impossible to find any help for it, I think this is due to not much has been written, they didn’t agree on a name for ages so you can’t prefix your search with something distinctive (e.g. connector is too ambiguous).
It’s quite frustrating when you searching for help and I keep getting diverted to my own blog, which didn’t have the answer (come on Hosk sort that out| what do you think I am doing right now)
The problem was trying to connect to the NAV Webservices. I had enabled the connector webservices inside NAV (marketing, enable connector) and I had started the webservice and I could even connect to the web service using internet explorer but as soon as I tried to connect to the webservice inside of the connector I was getting an unauthorized error.
I checked the user I was using was a domain user, they were an admin on the machine (not needed but a good sign I thought), they had the super role in NAV. The user had all the credentials, so why was it throwing this message.
I changed the url I was typing to try
server name
localhost
full server with .local on it
none of the above worked.
What finally worked was to put in the ipaddress and then it worked without any problems.
I have to admit I don’t understand why this works and the others don’t but I have some vague idea it’s a security setting, possibly related to SPN but I’m not sure and I don’t really know how the web services in NAV work (what web server are they hosted in?)
Whilst searching for the problem I also found these articles which might be useful
how to turn on logging
Interesting forum discussion with other possible solutions
http://social.microsoft.com/Forums/hi-IN/crmdevelopment/thread/43aa5d1a-3326-4349-a183-881c76e7b0ce
Konstantin
August 16, 2012
Hi Ben,
) then you should go trough SPN nightmare.
Here is nothing wrong with Connector. Any third party application which using NAV Web Services will have same error message.
Where is your NAV Server installed? Same box as SQL server (with NAV Database) or you have two different servers?
If they separated (headache solution
If they on the same box , then here is probably some other issue
Cheers, Konstantin
Surmeet
November 9, 2012
Hi,
In NAV webservice config settings, make NTLM=true. It will fix this issue.
Regards,
Surmeet Singh