November 4, 2011 at 2:05 am
hey,
As you my have guessed fell asleep at that point :/
just tried sqlcmd -S 127.0.0.1,1434
got a new error.
an error has occurred while establishing a connection to the server. when connecting to sql server 2005 this failure may be caused by the fact that under the default settings sql server does not allow remote conenctions
(obviously as it was a live server it did allow remote connections :/)
November 4, 2011 at 3:05 am
ok so current situation:
The service will start with
NET START MSSQLSERVER /c /f /T3608
I then try and log in with sqlcmd and get failures.
I dont know the SA password (But its definitly in that authentication mode to allow it)
I have tempdb, model, msdb pointing to Z:/ instead of Z:\
If i try and connect with sqlcmd or ssms from my client machine i always get user time out errors or that remote connections arent allowed
very stuck and not suer where to go..
November 4, 2011 at 3:13 am
in event viewer i can see im single user mode as the sharepoint account is trying to access it and getting
Login failed for user 'xxxxxxxx'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: 192.168.7.180]
I can also get surface area to load up (I had to stop it looking at localhost and go for the cluster name
November 4, 2011 at 8:52 am
Did some more checking and got a second opinion.
At this point, it looks like you should
1. Rebuild master
2. restore system backups or replace/rebuild system db files with the old system db files
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 4, 2011 at 9:17 am
Hi all,
Ok after getting some sleep seems my head got a little clearer..
Got it all working now finally.
the things that solved the problem (and clearly would have helped if that i told you)
1: IT was a cluster. so all my hours of typing 127.0.0.1 would of course fail. You need to use the sql cluster ip address / dns name
2: I managed to get SSMS open when in single connection but forgot that the object explorer counts as a connection. So when i tried to open a New Query I was told no. Closed down the Object Explorer then opened just a Query and got in.
After doing them it made it a lot easier...
Now to change the SA to something else AND DOCUMENT IT!
Massive thanks to SQLRNNR for all the help... sticking with me really helped a lot as i was getting quite the stress levels...
Just to conclude.
I made sure all the traceflag queries were out of the Configuration manager and used
NET START MSSQLSERVER /c /f /T3608
-- Not sure why it worked from command line and not the GUI
Then went to my SSMS on my workstation opened it and closed the Object Explorer. Opened New Query, and connected to the "cluster name"
Got in and changed all the system file paths to there correct locations.
turned off the Service
Made sure all the files were where they should be
Restarted the Service without the traceflags and switchs
Hey presto.. a lovely SQL Server 2005 machine is reborn!
Thanks again
S
November 4, 2011 at 9:31 am
Awesome - congrats.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply