Howdy, Stranger!
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
- 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
- 305 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Why SQL server cannot found until an hour later?
spycraft
Member Posts: 66
Hi all,
I have the following scenario to share and I appreciate any feedback or advice:
My client is on Navision 3.6 SQL server option (SQL2000). The complaint is that the SQL server cannot be found by Navision client after server reboot. He has to keep trying for about an hour before he is able to find the SQL server.
What could have caused the SQL server not to be found until a later time?
Regards,
Spy
I have the following scenario to share and I appreciate any feedback or advice:
My client is on Navision 3.6 SQL server option (SQL2000). The complaint is that the SQL server cannot be found by Navision client after server reboot. He has to keep trying for about an hour before he is able to find the SQL server.
What could have caused the SQL server not to be found until a later time?
Regards,
Spy
0
Comments
Can the server be pinged ?
Are the clients terminated before the server is rebooted ?
Can you map the administrative share c$ (for instance, but any other shared folder will do) on that machine ?
The problem you describe can be situated anywhere in the OSI network layering model, so without any more information it is impossible to find an answer.
My feedback below:
Has the server got a fixed IP adress ?
[Spy] yes
Can the server be pinged ?
[Spy] Have to check with client and feedback.
Are the clients terminated before the server is rebooted ?
[Spy] Have to check with client and feedback.
Can you map the administrative share c$ (for instance, but any other shared folder will do) on that machine ?
[Spy] Have to check with client and feedback.
Has the server got a fixed IP adress ?
[Feedback from Client] yes , it does
Can the server be pinged ?
[Feedback from Client] yes, it does
Are the clients terminated before the server is rebooted ?
[Feedback from Client] Yes it does
Can you map the administrative share c$ (for instance, but any other shared folder will do) on that machine ?
[Feedback from Client] There are no administrative share or other shared folders in that server.
Regards,
Spy
It might also be a good idea to check if the SQL Server can be found by for instance the Enterprise Manager during that hour.