Nav 4.0, SQL 2005 - ODBC Data source name not found
                
                    JDVyska                
                
                    Member Posts: 179                
            
                        
            
                    I'm having an interesting quirk with 4.0 SP1.  I've installed the client on the server running SQL2005 (Minimum install options).
Whenever I try to open a database, if I lookup on Server Name or Database Name, I get the error message:
But, any client machines on the network running 4.0 SP1 executable can connect to this SQL 2005 server just fine.
To my knowledge, you don't have to setup a DSN for Navision. Does anyone have any theories on what might be the Navision/SQL2005 resolution for this?
(Googled the error message, but that primarily produces a LOT of results about Beta SQL2005 installation issues.)
Thanks!
Jeremy
Edit: Sort of solved.
                Whenever I try to open a database, if I lookup on Server Name or Database Name, I get the error message:
The following ODBC error occurred: Error: [Microsoft][ODBC Driver Manager] Data source name was not found and no default driver was specified.
But, any client machines on the network running 4.0 SP1 executable can connect to this SQL 2005 server just fine.
To my knowledge, you don't have to setup a DSN for Navision. Does anyone have any theories on what might be the Navision/SQL2005 resolution for this?
(Googled the error message, but that primarily produces a LOT of results about Beta SQL2005 installation issues.)
Thanks!
Jeremy
Edit: Sort of solved.
JEREMY VYSKA
CEO, Spare Brained Ideas, Göteborg, Sweden
New (April 2021) Getting Started with Microsoft Dynamics 365 Business Central Book Available: "Your First 20 Hours with Business Central"
CEO, Spare Brained Ideas, Göteborg, Sweden
New (April 2021) Getting Started with Microsoft Dynamics 365 Business Central Book Available: "Your First 20 Hours with Business Central"
0                
            Answers
- 
            SP2 is comming out in couple of weeks, maybe this will be fixed.0
 - 
            For anyone else running into this issue, what we found was, however the SQL
2005 environment was setup, the SQL ODBC drivers installed was simply called
"SQL Native Client" instead of "SQL Server". Navision seems to not use the
"SQL Native Client", even under SP1.
The fix we had to do to continue on was to install the SQL 2000 ODBC driver,
then it was fine. Here's hoping Navision is not expecting to use any of the
new functionality in the "SQL Native Client"
JJEREMY VYSKA
CEO, Spare Brained Ideas, Göteborg, Sweden
New (April 2021) Getting Started with Microsoft Dynamics 365 Business Central Book Available: "Your First 20 Hours with Business Central"0 
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
 - 323 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
 
