December 24, 2003 at 5:34 am
i'm having issues with starting sql server and i get the following error messages:
server: msg 17, level 16, state 1, line 0
[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied
and
server: msg 2, level 16, state 1, line 0
[microsoft][ODBC SQL Server Driver][dbnetlib]connectionOpen(connect())
connection Broken.
and the error logs has this message
SQL Server Error:10004,communication link failure[SQLSTATE 08S01]
what i did before the above errors is tried moving modellogs from a shared disk resource to another shared disk resource and the first error i got had to do with sql server dependencies and sql server and sql server agents services are in failed state since then.
December 24, 2003 at 5:42 am
have you moved the model logs back to their original location and try a restart? Did you detatch the model database before moving the files? I'm not even sure you can detach the model database.
Wes
December 24, 2003 at 6:04 am
yes i've tried moving the modellog back to it's original location but with no success and i detached before moving the modellog file but now sql server don't seem to work no more.
December 24, 2003 at 7:38 am
Did you add trace flag -T3608 to startup parameter and restart SQL Server before moving Model database?
December 24, 2003 at 7:42 am
yes i did
December 24, 2003 at 7:45 am
all i need is for sql server to start in the cluster and everything i've tried is not working at the moment. i've copied the modellog files back to it's original location and tried to bring sql server back online but still with no luck
December 24, 2003 at 7:59 am
Make sure all resources your SQL Server depends on all online before you bring SQL Server resource online.
Here are the steps to move Model database.
1. Add -T3608 to startup parameter.
2. Take SQL Server offline.
3. Detach Model database.
4. Move MDF or LDF or both to new location which disk resource has been configured SQL Server resource depends on.
5. Re-attach Model database.
6. Bring SQL Server online.
7. Remove -T3608 parameter.
8. Bring SQL Server online back to normal.
December 24, 2003 at 8:02 am
i started having problems from stage 4 and more of stage 5 i'll say
December 24, 2003 at 8:22 am
Can you start SQL Server manually?
Run sqlservr.exe -c -T3608 in command prompt from node which ownes all resources.
December 24, 2003 at 12:54 pm
from article 224071
_________________________________________
NOTE: You will not be able to access any user databases at this time. You should not perform any operations other than the steps below while using this trace flag. To add trace flag 3608 as a SQL Server startup parameter: After adding trace flag 3608, perform the following steps:
Stop and restart SQL Server.
Detach the model database as follows: use master
go
sp_detach_db 'model'
go
Move the Model.mdf and Modellog.ldf files from D:\Mssql7\Data to E:\Sqldata.
Reattach the model database as follows: use master
go
sp_attach_db 'model','E:\Sqldata\model.mdf','E:\Sqldata\modellog.ldf'
go
Remove the -T3608 trace flag from the startup parameters box in the Enterprise Manager.
Stop and restart SQL Server. You can verify the change in file locations using sp_helpfile: use model
go
sp_helpfile
go
___________________________________________
Make sure the node you are running from currently owns all the resources and the disk resource you were moving to is also in the failover group and added to failover dependencies for SQL.
I would then try to do what Allen is suggesting and do a command prompt start with no recover flag on and see what comes back up.
Wes
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply