June 23, 2009 at 4:20 pm
Hi Folks
well after three days I finally got a clean install of SQL Server 2005 Developer.
So now, I am stuck again
I figured the worst part was over, but guess not
I have stopped al my SQL services and tried to run the SP2 and of course it does not work due to authentication issue. Why, i do not know as SQL Server 2005 installed with "Windows Authentication"
Anyway if someone has come across this issue can you please let me in on it:
Here is what I am getting in the log at the bottom:
06/23/2009 14:52:24.637 Starting service: MSSQLServer
06/23/2009 14:52:30.262 Started service: MSSQLServer
06/23/2009 14:52:30.293 SQL Agent Service SQLSERVERAGENT was not previously running
06/23/2009 14:52:30.824 Authenticating user using Windows Authentication
06/23/2009 14:52:30.824 Validating database connections using Windows Authentication
06/23/2009 14:52:31.168 Pre-script database connection check was successful - proceeding with script execution
06/23/2009 14:52:31.590 Received sysadmin status for instance: MSSQLSERVER
06/23/2009 14:52:31.590 Validating database connections using Windows Authentication
06/23/2009 14:52:31.824 Pre-script database connection check was successful - proceeding with script execution
06/23/2009 14:52:31.824 User authentication was successful
06/23/2009 14:52:31.824 Stopping service: MSSQLServer
06/23/2009 14:52:33.856 Stopped service: MSSQLServer
06/23/2009 14:52:44.106 Error, cannot determine sysadmin status for instance: MSSQLSERVER
06/23/2009 14:52:44.106 HResult 0x2, Level 16, State 1
06/23/2009 14:52:44.106 Named Pipes Provider: Could not open a connection to SQL Server [2].
06/23/2009 14:52:44.106 Sqlcmd: Error: Microsoft SQL Native Client : 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 connections..
06/23/2009 14:52:44.106 Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
Thanks
Jim
June 24, 2009 at 11:32 am
I assume you connect to the instance fine with SSMS or other tools? Is there any other process connecting to SQL? What happens often is that the install looks to go to single user mode and can't connect.
It almost seems here like a protocol issue. I'd be sure that the shared memory protocol is on (connect with (local) to verify) and be sure remote connections are on.
June 24, 2009 at 3:42 pm
First, you don't need to stop the services prior to upgrading. It works much better if you leave the services started, that way the install can actually connect to SQL Server and validate administrative privileges.
Start SQL Server Surface Area configuration and verify that SQL Server has both named pipes and TCP/IP configured.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
June 25, 2009 at 3:22 pm
Hi Jeffrey
well that is good to know as it said to shut down all SQL Server processes first. Anyway, I know i only included TCP/IP on install, so I will look at that also.
Thanks
Jim
June 25, 2009 at 3:27 pm
HI Steve
okay, you lost me at SSMS
I just created SQL Server 2005 for Developer and got a clean install finally, and that is as far as I am so far.
Next step was to install SP2 and that is when I got problem.
The only processes are SQL Server processes for developer that were running and I shutdown prior to SP2 install
How do I check this ?
"I'd be sure that the shared memory protocol is on (connect with (local) to verify) and be sure remote connections are on. "
Thanks for the Assist
Jim
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply