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
- 304 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
Connection to sql server was lost or never established
paurola
Member Posts: 43
I just had an interesting problem. A coworker had installed NAV2013 on a new laptop and accidentally created a new named instance of SQL Server (seen this ever happen?;-). So she wanted the database to be moved to the default instance of SQL. I backed up the database and restored it into the default instance, then I stopped the NAV Service and changed the service properties so that it connects to the default instance.
Then, what the heck... NAV Service was running but the RTC-client would not connect to the database, it was showing error:
"The connection to sql server was lost or never established". The development environment started fine but did not find the service tier either.
It took a while until I found the reason what was causing this... There was something wrong with Network service account in the Nav db. I suppose the restore of the NAV db somehow had messed up the rights for this account and the service was not able to access the nav data. So I added the Network Service to SQL Server Logins and made it the owner of the restored DB -problem solved.
I post this because I'd like to hear if anyone has the knowledge what really happened and if this could have been avoided somehow.
Then, what the heck... NAV Service was running but the RTC-client would not connect to the database, it was showing error:
"The connection to sql server was lost or never established". The development environment started fine but did not find the service tier either.
It took a while until I found the reason what was causing this... There was something wrong with Network service account in the Nav db. I suppose the restore of the NAV db somehow had messed up the rights for this account and the service was not able to access the nav data. So I added the Network Service to SQL Server Logins and made it the owner of the restored DB -problem solved.
I post this because I'd like to hear if anyone has the knowledge what really happened and if this could have been avoided somehow.
1