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
"MSSQLSERVER service could not be started"
Shenpen
Member Posts: 386
It is common for consultants to have several MS SQL servers and multiple MBS products installed, f.e. Navi 3.7, Navi 4.0 and MS CRM Sales for Outlook. The problem is that all of these install MSDE (as a default instance).
Today I hacked some translations in the fin.stx file, and found that it has a checksum so if I change anything, Navision throws an error message upon starting and quits. I replaced the file with one from the install CD but it did not help. So I had to reinstall Navi 4.0, and then I got the "MSSQLSERVER service could not be started" error message. I checked my SQL servers, and I found that it means the default instance server cannot be started due to some kind of login error. Some kind of problem happend, don't know why. Even if I checkmarked that "do not install MSDE", Navision found the MSSQLSERVER service, assumed that it's his MSDE, tried to start it, it could not, and then didn't want to go further in the installation. So basically it was impossible to install Navision.
I tried many kind of repairs, and finally what worked: I simply reinstalled the default instance of SQL server. Actually my default instance was a MSDE, but the reinstall removed it and installed an SQL server.
And then Navision installed fine, with checking "do not install MSDE" =D>
Today I hacked some translations in the fin.stx file, and found that it has a checksum so if I change anything, Navision throws an error message upon starting and quits. I replaced the file with one from the install CD but it did not help. So I had to reinstall Navi 4.0, and then I got the "MSSQLSERVER service could not be started" error message. I checked my SQL servers, and I found that it means the default instance server cannot be started due to some kind of login error. Some kind of problem happend, don't know why. Even if I checkmarked that "do not install MSDE", Navision found the MSSQLSERVER service, assumed that it's his MSDE, tried to start it, it could not, and then didn't want to go further in the installation. So basically it was impossible to install Navision.
I tried many kind of repairs, and finally what worked: I simply reinstalled the default instance of SQL server. Actually my default instance was a MSDE, but the reinstall removed it and installed an SQL server.
And then Navision installed fine, with checking "do not install MSDE" =D>
Do It Yourself is they key. Standard code might work - your code surely works.
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
What do you think of my "Tricks to protect inventory value" topic? Do implementatons work the same way in Czech Republic like in Hungary, described by that topic?
Do It Yourself is they key. Standard code might work - your code surely works.