Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 270 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Service layer needs waking up
Toddy_Boy
Member Posts: 231
This is a little strange behaviour I've not encountered before on 3 tier architecture.
I have a website site that calls web services published from Navision, however on occassion the website returns an error, 'Cannot log into SQL Server' when calling a web service after a long period without use. This is resolved by RDPing to the Nav Services machine, open a browser and call the web services i.e http://localhost:7047/DynamicsNav/WS/co ... e/Services
Once the published services are displayed the website performs perfectly, it's as if the service layer falls asleep and needs prompting to wake up.
Any ideas would be welcome?
Steve
I have a website site that calls web services published from Navision, however on occassion the website returns an error, 'Cannot log into SQL Server' when calling a web service after a long period without use. This is resolved by RDPing to the Nav Services machine, open a browser and call the web services i.e http://localhost:7047/DynamicsNav/WS/co ... e/Services
Once the published services are displayed the website performs perfectly, it's as if the service layer falls asleep and needs prompting to wake up.
Any ideas would be welcome?
Steve
Life is for enjoying ... if you find yourself frowning you're doing something wrong
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I have a similar problem. The 'loss' of visibility of the webservices occurs when there was an error in the webservice. The user - calling the services from outside our domain - receives a NAV error message, and from that moment the services are not accessible from that client anymore. From a client in our own domain there's no problem: the service is still running fine & is reachable. After a few minutes, the services are addressable again for the user outside the domain, without any action on our behalf. It seems to be some kind of a time-out?
Any help on this would be appreciated!
Regards
Greys
That is another exact scenario I am encountering #-o
Are you aware of anything that can be tinkered with to resolve this? I've written a few websites that operate this way and have never encountered this behaviour.
Steve