Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We currently have NAV 2018 installed and I am trying to use an ODATA web service in VS 2015 by creating a Service Reference. I am currently receiving this error: The custom tool 'DataServicesCoreClientGenerator' failed. Data service client code-generation failed: Schema specified is not valid. Errors: (0,0) : error 0005: The 'Name' attribute is invalid - Th value '_Fault_Log_No_x003C_x003E_x0027_x0027_' is invalide according to its datatype 'http://schedmas.microsoft.com/ado/2007/05/edm:TSimpleIdentifier' - The Pattern constraint failed.
So when entering the Address in the Service Reference I use this format: https://hostname:port/instance/OData/ We are using SSL, so I don't know if this makes a difference. We are also using NavUserPassword to login. What is interesting is that after hitting Go on the Address it prompts me for my credentials 3 times. Once the 3rd time is complete it seems to grab the information. I can see my web services endpoints that I set up in NAV. But once I hit ok on the Service Reference window it looks like it is trying to set it up and then errors out with the above message. Also, on another note, on this same machine if I go to IE,Chrome, or Edge I put in the https://hostname:port/instance/OData/ and it prompts me for my credentials and I enter them, it shows the Web Service information just fine.
Is there anyone that has any input on how to get past this error? Could this be something with VS2015? Could this be with a setup with NAV? I tried to recreated this issue on a local computer with a self signed SSL and Using NavUserPassword and I was able to set up my Service Reference just fine.
I've searched online and I haven't found anything that has helped us yet. Any help would be appreciated.
Can you view the services from Web Browser ? also try running VS as administrator
Thank you for the reply. Yes, when I go to a web browser and use this format: https://hostname:port/instance/OData/ I get asked for my credentials once, I enter them, and then it works.
I have also tried to run as administrator as well as a different user such as the Service Account User that the Service Instance uses. No luck on those either. Any other ideas?
Did you try the SOAP url ? Does that work ?
If this happens after adding the service reference in Visual Studio, right click the service reference and select Update Service Reference.
So when trying to do Update Service Reference I get this error message:
So then I closed the solution and reopened it.
Did the Update Service Reference and it once again asked for my credentials 3 times. Once it connects and I click okay it gives me this message:
Any other ideas?
Thanks so much for taking time to help me figure this out.
So I tried soap and it worked. I had to used the full link that was provided within NAV Web Services and I was able to create the Service Reference. So Soap works but Odata does not. We are wanting to use Odata though.
I was finally able to figure out why we were receiving this error message. I had to go through each Web Service removing them one by one. After each removal I created a service reference to see if it fixed it. Come to find out it ended up being two Web Services that were the culprits. After removing those two I was finally able to get passed the errors I was receiving, and was able to create the Service Reference in Visual Studio 2015!
Which web services?? :)
Hi gnilsen, I am having the same problem, can u tell me which web services you removed. thanks
Business Applications communities