Database Server sometimes connects to wrong database

afarr
Member Posts: 287
We have a client with two databases, Live and Test. These are .fdb files, not SQL.
The objects are version 4.00 W1, but the client used in NAV 2009 R2 (build 32012).
There is a database server for each database, ABC-LIVE (which is working fine) and ABC-TEST.
When I login by Remote Desktop to ABC-Server, the machine that hosts the services and database files, I can open ABC-TEST without problem.
For what it’s worth, ABC-Server is Win 2008 R2, 64-bit with 24 GB RAM.
The folder containing the Test database is shared with everyone, and users have full control on that folder.
However, when connecting from a PC, after opening ABC-TEST, we are actually connected to the Live database. This happens on two different PCs.
If we go to File – Database – Information, we can see the server name ABC-TEST, but the name of the database file is that of Live. The companies listed, and the data, are that of Live, so we are actually connecting to Live.
The hosts and services files have the same settings as on ABC-Server.
I also renamed the zup file (on ABC-Server and on the PC), and re-installed the service, but the problem still occurred on the PC, while on ABC-Server we connect without problem.
Have you ever encountered this?
Any suggestions are welcome.
The objects are version 4.00 W1, but the client used in NAV 2009 R2 (build 32012).
There is a database server for each database, ABC-LIVE (which is working fine) and ABC-TEST.
When I login by Remote Desktop to ABC-Server, the machine that hosts the services and database files, I can open ABC-TEST without problem.
For what it’s worth, ABC-Server is Win 2008 R2, 64-bit with 24 GB RAM.
The folder containing the Test database is shared with everyone, and users have full control on that folder.
However, when connecting from a PC, after opening ABC-TEST, we are actually connected to the Live database. This happens on two different PCs.
If we go to File – Database – Information, we can see the server name ABC-TEST, but the name of the database file is that of Live. The companies listed, and the data, are that of Live, so we are actually connecting to Live.
The hosts and services files have the same settings as on ABC-Server.
I also renamed the zup file (on ABC-Server and on the PC), and re-installed the service, but the problem still occurred on the PC, while on ABC-Server we connect without problem.
Have you ever encountered this?
Any suggestions are welcome.
Alastair Farrugia
0
Answers
-
I don't see it as causing your issue, but you should not share the folder containing the database files. The users don't need any rights to those files. Only the account runnign the services does. As a general practice a DB server (native or SQL) should be effectively "locked down". Meaning that no non-admin users have direct access.
In terms of your problem, I've not seen this behavior. So not really sure.There are no bugs - only undocumented features.0 -
We found a solution for this, by connecting with the explicit IP and port number e.g. 111.111.111.111:2409 instead of ABC-TEST as the server nameAlastair Farrugia0
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