SQL Connection is Broken - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

SQL Connection is Broken

Author

Topic

sphadke
Yak Posting Veteran

55 Posts

Posted - 2004-04-05 : 17:22:17

Hi,

need some help here. I was trying to detach the msdb and model databases to move them to another server. To do this I added the following parameter on EM right click on server name -> properties -> General Tab -> start up parameters -T3608

I stopped the SQL Server and restarted it and detached the msdb and model after I did that I stopped and restarted SQL Server without removing the -T3608 parameter. Error 22528 SQL-DMO This server connection has been unexpectedly broken and cannot be reconnected

any ideas on how to fix this??

thanks

Sachin

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-05 : 17:32:09

Anyone who ever moves system databases should live by this link:

http://support.microsoft.com/default.aspx?scid=kb;en-us;224071&Product=sql

You need to go into the registry and take out the -T3608 flag using regedit.

HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>MSSQLServer>MSSQLServer>Paramaters

It will be SQLArg3.

I think you are going to run into another problem though. When you move both the msdb and model databases at the same time, you have to detach, move, then attach before removing the -T3608 flag. You can then restart.

I think you need to move the files back to their original position and start the server back up to get the server to come back up. It's been a while since I've ran into this though.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

sphadke
Yak Posting Veteran

55 Posts

Posted - 2004-04-05 : 17:52:59

ok I added the -T3608 back and this is the error I get

2004-04-05 17:00:57.63 spid52 Clearing tempdb database.
2004-04-05 17:00:57.65 spid52 WARNING: problem activating all tempdb files. See previous errors. Restart server with -f to correct the situation.

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-05 : 18:58:29

Restart with -f then. This should reinitialize your tempdb. If you have not reattached the databases yet, you need to move them back also. Then go through the process as I described in the previous post.

Let me know how it goes.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

sphadke
Yak Posting Veteran

55 Posts

Posted - 2004-04-05 : 19:06:05

Ok I got the -T3608 removed. I restored the model and msdb and went on to move the tempDb and this is what I did.. I know I should have read re-read what I was doing

Alter database tempdb modify file (name = tempdev, filename = 'E:\Sqldata\templog.ldf')
go

yikes!! Looks like i corrupted my master db. Is trying to rebuild the masterDB the only option i have now?? or do I need to reinstall SQL?

Sachin

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-05 : 19:08:06

Wow. Can't say I've ever ran into that one before. Have you tried starting with -f?

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

sphadke
Yak Posting Veteran

55 Posts

Posted - 2004-04-05 : 19:08:48

yes it wont start.. it's looking for templog.ldf as my primary database file.

Sachin

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-05 : 19:26:25

Do you have your tempdb log file as the same name. If not, just rename the file to what you have it. You can then do another modify and rename it.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

sphadke
Yak Posting Veteran

55 Posts

Posted - 2004-04-05 : 19:28:30

I tried that too.. that didnt work

Sachin

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-05 : 19:40:00

Have you tried naming it templog.ldf.mdf or templog.mdf? I don't know what else to suggest. I hate running setup over again though.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

sphadke
Yak Posting Veteran

55 Posts

Posted - 2004-04-05 : 19:44:26

I tried everything.. I think running the setup again is the last option :sigh:

Sachin

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-05 : 19:51:25

Let me know how it goes. I've done a lot of conversions and moving of system databases in the last few years. It can suck when things like this happen.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

sphadke
Yak Posting Veteran

55 Posts

Posted - 2004-04-05 : 23:02:37

It's finally done (and what a mess) lucky enough it was a development server and not production.
It's a nightmare when it comes to restoring 30 db's.

Sachin

MuadDBA

628 Posts

Posted - 2004-04-06 : 08:31:27

Bummer...I was going to suggest attaching your master database to another server with a different DB name, then re-updating the database, then detaching it and putting it back where it was.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources