February 14, 2009 at 10:18 am
I have a sql 2005 server. I changed the service accounts to network service in preparation for a domain name change.
I have a couple of databases with multiple log files. One one one drive nd the second on a second drive.
When the sql server service restarted these database could not be opened. The error I am getting is that it can not access the log file on the second drive. I have checked and made sure that the files are available and open to the service, network service accounts. I still ca not open. I tried to use the sp_attach_single_file_db and I get an error saying that it can not connect. I am also getting an error saying that the database was not shut down cleanly. How can I get this back up?
February 14, 2009 at 11:11 am
Did you our SQL Server Configuration Manager to perform the service account change ?
if not... change it back the way you did and then use SCM to configure the new service account. (it handles the grants as well)
double check the location of the log files it cannot access.
Check the service account has been granted read/write for that folder at windows level.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data and code to get the best help
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 16, 2009 at 7:37 am
Yes, I did use the configuration manager. I was able to get this working. I changed the name of the mdf file so that SQL could not find it. I then restarted the sql server service. Once done. I copied the LDF over to the data drive where the mdf i was and renamed everything back to the original names. I went into the sql server management studio and reattached the database. It came back up fine. I had checked the rights on the files on the L drive and could not see any reason that sql had an issue getting to it. Thank you for your response.
February 16, 2009 at 8:33 am
Check the SQL error log. There should be some info in there. Please post any relevant log entries
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 16, 2009 at 8:54 am
The error logs just say that sql cannot access the ldf files. So I move the LDF files to a drive and folder that works.
February 16, 2009 at 10:47 am
isn't it stating a location for the log files it searches ?
Can you post the results of sp_helpdb 'yourdb'
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data and code to get the best help
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 16, 2009 at 11:47 pm
scottdever (2/16/2009)
The error logs just say that sql cannot access the ldf files.
It should have given a reason (Operating system error.....)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 16, 2009 at 11:55 pm
did you address the ldf file using UNC ??
Pointing to a remote disk or fileshare ??
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data and code to get the best help
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 17, 2009 at 8:17 am
It was using standard local file paths... l:\sql logs\ggg.ldf
The error in the log said that it did not have permission to access the file...and then it gave the file path. It is up and running now that I moved the LDF.
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply