OData Webservice returns:Resource not found for the segment

primeap
Member Posts: 37
Hi
I have a strange behaviour on my testmachine..
seems like the nav service for the webserivices im tesiting is "broken"...
the Request returns Resource not found for the segment [WSName] ...
Seems like a WCF-Error.
It came up after i was editing a table and page, it came "another is using this table" bla bla i can not modify it.. so that was strange because this is my testmachine so the another was maybe a stucked webservice??
anyway.. after restarting all the subsequent requests came with that Resource not found for the segment ... before that it was working.
I tryied to restart all the services and reboot the pc.. nothing helped...
the webservices are correctly published....
what should I try next? Recreating the Services instances?
any advise? Much appreciated..
I have a strange behaviour on my testmachine..
seems like the nav service for the webserivices im tesiting is "broken"...
the Request returns Resource not found for the segment [WSName] ...
Seems like a WCF-Error.
It came up after i was editing a table and page, it came "another is using this table" bla bla i can not modify it.. so that was strange because this is my testmachine so the another was maybe a stucked webservice??
anyway.. after restarting all the subsequent requests came with that Resource not found for the segment ... before that it was working.
I tryied to restart all the services and reboot the pc.. nothing helped...
the webservices are correctly published....
what should I try next? Recreating the Services instances?
any advise? Much appreciated..
0
Best Answer
-
ok got it.
I added in the customer table 2 new fields "No..," and "No.."..
this caused to break the Odata Service..
So when publishing the customer page card it caused this error.
Sadly Navision did not warn when editing the page, but only when restarting the Service or at the request you get *Segment not found* because navision was not able to populate the wcf service correctly.
hope it helps someone out there..5
Answers
-
Hi,
what app are you using to consume WS? Maybe there is an issue? (If you changed page and it's populated as WS)
Igor Pchelnikov0 -
I do it with postman in chrome browser, in IE too it came 404 Error. I will try now to recreate the server instance..0
-
I have now some more information in the eventlog:Metadata for Page 21 that is published as a web service is not valid for OData.0
-
ok got it.
I added in the customer table 2 new fields "No..," and "No.."..
this caused to break the Odata Service..
So when publishing the customer page card it caused this error.
Sadly Navision did not warn when editing the page, but only when restarting the Service or at the request you get *Segment not found* because navision was not able to populate the wcf service correctly.
hope it helps someone out there..5
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions