May 19, 2016 at 3:12 am
Hi Guys,
We have added one of our DR servers to a domain. Since that I cannot start the SQL Server Service. The service is running as Local System. In the error log I first had a message about the master database but I replaced the mdf with a template one and now I am getting SPN errors.
It says that it successfully registered the SPN and the it could not de-register the SPN?
I have never had a situation like this where the server is added to a domain after setting up SQL.
Any advise would be appreciated.
Below is the last four lines of the error log:
2016-05-19 10:54:42.81 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ fqdn ] for the SQL Server service.
2016-05-19 10:54:42.81 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [fqdn:port ] for the SQL Server service.
2016-05-19 10:54:42.94 spid15s The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ fqdn ] for the SQL Server service. Error: 0x2af9, state: 61. Administrator should deregister this SPN manually to avoid client authentication errors.
2016-05-19 10:54:42.94 spid15s The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [fqdn:port] for the SQL Server service. Error: 0x2af9, state: 61. Administrator should deregister this SPN manually to avoid client authentication errors.
May 19, 2016 at 5:32 am
Hi,
have you checked with your domain admins, if there is a valid SPN in the domain for you SQL-Server?
Kind regards,
Andreas
May 19, 2016 at 6:17 am
kreuzer (5/19/2016)
have you checked with your domain admins, if there is a valid SPN in the domain for you SQL-Server?
Or worse, the server could be using a previous registered SPN. Meaning that this server could have been used for another purpose then given to you without being properly wiped and set up anew.
Definitely check with the domain admins.
May 19, 2016 at 10:47 pm
Hi guys,
No I have not yet checked with the domain admins. I have dealt with something like this before. This server use to be the live database server, then it became the DR database server. I has been the DR for about 2 years now. The server was never on a domain, now the network admins added it to a domain and I cannot start up my SQL service. I can however start up the browser and the other services such as reporting services and Integration services. I was thinking of taking the server off the domain again just to test if I can start up the services again. How would I go about this now?
May 19, 2016 at 11:38 pm
Hi,
are all services from the sql server starting with local accounts?
Are you able to start the sql server services with a domain account?
If you are working with DR or HA, you should use domain accounts to start services, to avoid problems with access to server ressources.
Kind regards,
Andreas
May 19, 2016 at 11:54 pm
No I cannot even start it with a domain account. This is just the DR server, we don't have a DR solution in place any more.
The SPN is the last error in the log. The thing that is strange is that when I try to start the service with the CMD I get a 945 error which says that the model DB is inaccessible. Why is that? I haven't moved the model DB? I then tried to copy the template model DB tothe original path of the system databases but I still get the same error.
May 20, 2016 at 5:15 am
Have you tried repairing the install?
May 22, 2016 at 11:20 pm
I have tried using cmd but I got an error, can't remember what, will check and post. If I repair it using the setup, which folder do I point it to as the installation media folder? Every folder I choose this thing has a problem with. I have pointed it to the folder that contains the setup exe but it doesn't work.
The first error I have in the log is the following:
Starting up database 'msdb'.
2016-05-23 07:07:05.98 spid5s Error: 17204, Severity: 16, State: 1.
2016-05-23 07:07:05.98 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
The problem is I don't have an e drive????
May 23, 2016 at 5:35 am
crazy_new (5/22/2016)
If I repair it using the setup, which folder do I point it to as the installation media folder? Every folder I choose this thing has a problem with. I have pointed it to the folder that contains the setup exe but it doesn't work.
Run the setup.exe instead of trying to repair through the Control Panel. Setup should have a maintenance tab which you can use to repair the instance.
May 23, 2016 at 9:02 am
crazy_new (5/22/2016)
I have tried using cmd but I got an error, can't remember what, will check and post. If I repair it using the setup, which folder do I point it to as the installation media folder? Every folder I choose this thing has a problem with. I have pointed it to the folder that contains the setup exe but it doesn't work.The first error I have in the log is the following:
Starting up database 'msdb'.
2016-05-23 07:07:05.98 spid5s Error: 17204, Severity: 16, State: 1.
2016-05-23 07:07:05.98 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
The problem is I don't have an e drive????
THAT would be the problem. The file location in SQL Server for the at least that particular database wasn't changed before the system was taken down. If you could stand up an E: drive (at least temporarily) with the path above and copy the MSDBData.mdf file to it (and, once, done, another other similar drive location errors), then you'll be able to fire up the box to make the necessary changes.
There are some alternatives but I don't know what they are because I've not yet needed them. Hopefully Gail Shaw or one of the other MCMs will see this and offer one of those alternative solutions.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2016 at 9:09 am
May 23, 2016 at 9:25 am
I ran the repair and it did not fix the issue. The Database Engine Services, Data Quality Services, Full-Text and Semantic Extractions for Search and the SQL Server Replication features failed. And the database Engine has the same error in the logs, that the specified files could not be located(pointing to an e:\............... and I don't have an e drive). Is there any other way to resolve this or is my only option to uninstall the current SQL and reinstall it?
May 23, 2016 at 9:28 am
gfoxxy93 (5/23/2016)
Good post covering failed startup scenarios by msdnSQL Server Service Not starting[/url]
Looks like you can change a few regusty values to repoint data files whilst SQL server engine is offline.
You're doing your URLs wrong. You need text in between the tags for it to be clickable. Even if it's just a repeat of the link.
May 23, 2016 at 9:30 am
Ahhh on mobile ATM. Didn't realise.
May 23, 2016 at 9:30 am
crazy_new (5/23/2016)
I ran the repair and it did not fix the issue. The Database Engine Services, Data Quality Services, Full-Text and Semantic Extractions for Search and the SQL Server Replication features failed. And the database Engine has the same error in the logs, that the specified files could not be located(pointing to an e:\............... and I don't have an e drive). Is there any other way to resolve this or is my only option to uninstall the current SQL and reinstall it?
It may be quicker for you to uninstall and reinstall.
The E: drive file it's looking for... it appears to be for SQL Server Express. Is that the version of SQL Server you're fighting with? Or is it another version of SQL Server?
EDIT: There might be a work around at this link. Try it out.
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply