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
- 310 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
Prob Install first Database Part in other Location than C:\
JoeSan
Member Posts: 8
Hi,
I tried to install Attain 3.60 Database Server in userdefined mode in order to put both the binaries and the first database part into Path H:\Navision instead of using the standard Path C:\Program Files\Navision Database\.
When i use the client for creating a database, Attain now creates the first database file (which also means the database name) in C:\Windows\System32\.
Does anybody know how to change this without having to connect by using the full database path from all clients later? (which - afaik - causes database locking)
Regards,
JoeSan
I tried to install Attain 3.60 Database Server in userdefined mode in order to put both the binaries and the first database part into Path H:\Navision instead of using the standard Path C:\Program Files\Navision Database\.
When i use the client for creating a database, Attain now creates the first database file (which also means the database name) in C:\Windows\System32\.
Does anybody know how to change this without having to connect by using the full database path from all clients later? (which - afaik - causes database locking)
Regards,
JoeSan
0
Comments
If you have installed a Database server once it knows where the database is the clients just need to know the server name. If the database has been created in the wrong place the simplest option is to stop the Server service, move the database parts to where you really want them to be then use the Server command from a Command prompt to reset teh server service. The command would look something like
Server "full root to DB part1.fdb"+"fullroot to part2.fdb", installasservice
Then you restart the service and connect clients to that service.
Regards
Ian
Thank you for your reply, that should be the solution.
I couldnt find anything in the Manuals, does this change the paths permanently?
JoeSan
regards
Ian