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.
Author |
Topic |
dr223
Constraint Violating Yak Guru
444 Posts |
Posted - 2009-10-21 : 06:26:13
|
Hallo, I have a server name GPRDLONTB02SEC which was connecting fine and I managed to access my databases. But since I had limited space on my C drive, I optioned to move the tempdb to another external harddisk (as during production the tempdb autogrowth becomes huge) with the following query; USE master go ALTER DATABASE tempdb MODIFY FILE (NAME = tempdev, FILENAME = 'E:\tempdb.mdf') go ALTER DATABASE tempdb MODIFY FILE (NAME = templog, FILENAME = 'E:\templog.ldf') go Now, I restarted the PC and opened SQL server when I try to connect to server GPRDLONTB02SEC, I receive the error "The Server was not found or was not accessible. Error: 40 - Could not open a connection to SQL server(Microsoft SQL Server; Error:2).N/B: I tried to connect to another server GPRDLONTB02SEC2 and it works fine. Furthermore, on the bottom right corner of the screen, there is a server icon when I open it and select Restart - it restarts for like 2 seconds (changes to Green) and then it is Stopped (returns to Red). Please can anyone advise me what action I can take to resolve my problem..Thanks |
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2009-10-21 : 08:41:09
|
Sounds like the SQL Server service is not running.Can you confirm this? Check the windows services or configuration manager.Then check the SQL Server Error log file.And the windows Event viewer for error messages that explain why the service cannot start.Maybe the sql service account does not have permission to the E: drive. |
 |
|
dr223
Constraint Violating Yak Guru
444 Posts |
Posted - 2009-10-21 : 09:28:19
|
Please find attached the Errorlog file... Can you please advice me what to do. I have to have tempdb.mdf and templog.ldf in my extrenal harddisk as I have limited space in my C drive.. Thanks 2009-10-15 13:02:56.58 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)2009-10-15 13:02:56.58 Server (c) 2005 Microsoft Corporation.2009-10-15 13:02:56.58 Server All rights reserved.2009-10-15 13:02:56.58 Server Server process ID is 3088.2009-10-15 13:02:56.58 Server Authentication mode is MIXED.2009-10-15 13:02:56.58 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.2009-10-15 13:02:56.58 Server This instance of SQL Server last reported using a process ID of 2192 at 15/10/2009 13:00:50 (local) 15/10/2009 12:00:50 (UTC). This is an informational message only; no user action is required.2009-10-15 13:02:56.58 Server Registry startup parameters:2009-10-15 13:02:56.58 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf2009-10-15 13:02:56.58 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG2009-10-15 13:02:56.58 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf2009-10-15 13:02:56.60 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.2009-10-15 13:02:56.60 Server Detected 1 CPUs. This is an informational message; no user action is required.2009-10-15 13:02:56.69 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.2009-10-15 13:02:56.72 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.2009-10-15 13:02:57.74 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.2009-10-15 13:02:57.74 Server Database mirroring has been enabled on this instance of SQL Server.2009-10-15 13:02:57.74 spid5s Starting up database 'master'.2009-10-15 13:02:58.02 spid5s SQL Trace ID 1 was started by login "sa".2009-10-15 13:02:58.07 spid5s Starting up database 'mssqlsystemresource'.2009-10-15 13:02:58.10 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.2009-10-15 13:02:58.83 spid5s Server name is 'GPRDLONTB02SEC'. This is an informational message only. No user action is required.2009-10-15 13:02:58.85 Server A self-generated certificate was successfully loaded for encryption.2009-10-15 13:02:58.85 spid9s Starting up database 'model'.2009-10-15 13:02:58.85 Server Server is listening on [ 'any' <ipv4> 1433].2009-10-15 13:02:58.85 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].2009-10-15 13:02:58.85 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].2009-10-15 13:02:58.86 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].2009-10-15 13:02:58.86 Server Dedicated admin connection support was established for listening locally on port 1434.2009-10-15 13:02:58.91 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.2009-10-15 13:02:58.93 spid12s Starting up database 'msdb'.2009-10-15 13:02:58.93 spid13s Starting up database 'Phoenix'.2009-10-15 13:02:58.93 spid14s Starting up database 'AdventureWorks'.2009-10-15 13:02:58.94 spid15s Starting up database 'Test'.2009-10-15 13:02:59.39 spid9s Clearing tempdb database.2009-10-15 13:02:59.44 spid9s Error: 5123, Severity: 16, State: 1.2009-10-15 13:02:59.44 spid9s CREATE FILE encountered operating system error 3(error not found) while attempting to open or create the physical file 'E:\tempdb.mdf'.2009-10-15 13:02:59.55 spid9s Error: 17207, Severity: 16, State: 1.2009-10-15 13:02:59.55 spid9s FCB::Open: Operating system error 3(error not found) occurred while creating or opening file 'E:\tempdb.mdf'. Diagnose and correct the operating system error, and retry the operation.2009-10-15 13:02:59.55 spid9s Error: 17204, Severity: 16, State: 1.2009-10-15 13:02:59.55 spid9s FCB::Open failed: Could not open file E:\tempdb.mdf for file number 1. OS error: 3(error not found).2009-10-15 13:02:59.55 spid9s Error: 5120, Severity: 16, State: 101.2009-10-15 13:02:59.55 spid9s Unable to open the physical file "E:\tempdb.mdf". Operating system error 3: "3(error not found)".2009-10-15 13:02:59.55 spid9s Error: 1802, Severity: 16, State: 4.2009-10-15 13:02:59.55 spid9s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.2009-10-15 13:02:59.55 spid9s Error: 5123, Severity: 16, State: 1.2009-10-15 13:02:59.55 spid9s CREATE FILE encountered operating system error 3(error not found) while attempting to open or create the physical file 'E:\tempdb.mdf'.2009-10-15 13:02:59.55 spid9s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.2009-10-15 13:02:59.55 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. |
 |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-10-22 : 14:09:07
|
either E:\tempdb.mdf doesn't exist or the SQL Service account doesn't have permissions on it |
 |
|
|
|
|
|
|