Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

unable to connect to server Expand / Collapse
Author
Message
Posted Monday, September 2, 2013 6:43 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 5:12 AM
Points: 139, Visits: 398
Hi all.

here we are trying to connect to server which is not accessible and it through the below error.

Error:The operating system returned error 2(The system cannot find the file specified.) to SQL Server during a write at offset 0x00000230b20000 in file 'H:\Data\TempDB\tempdb.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.


The operating system returned error 2(The system cannot find the file specified.) to SQL Server during a read at offset 0000000000000000 in file 'H:\Data\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

We checked through the event logs and found that there were fatal errors on drive, and looks like disk issue.

An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 10054, output error: 0).

we have restarted the server but it is not yet up.
Post #1490606
Posted Tuesday, September 3, 2013 3:08 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:50 PM
Points: 6,191, Visits: 13,340
What have you done to address the issue below??

New persopn (9/2/2013)
We checked through the event logs and found that there were fatal errors on drive, and looks like disk issue.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1490826
Posted Tuesday, September 3, 2013 8:52 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:10 PM
Points: 33,095, Visits: 15,202
It looks like you have issues on your H: drive. SQL Server is just reporting issues from the OS when it tries to access the file, just as you'd receive if you tried to open the file in notepad.

You need to fix your disk issues here. If this is just tempdb, you can potentially start SQL Server in single user mode, and then move tempdb.

http://voiceofthedba.wordpress.com/2013/07/15/sql-server-needs-tempdb/







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1490993
Posted Tuesday, September 3, 2013 9:02 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Monday, July 14, 2014 2:06 PM
Points: 3,865, Visits: 7,130
What kind of disk subsystem is this server running on? SAN? Attached Storage? Internal drives?

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1490998
Posted Tuesday, September 3, 2013 10:54 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 5:12 AM
Points: 139, Visits: 398
here we dont have the san setup. we are using internal storage.
Post #1491038
Posted Tuesday, September 3, 2013 11:05 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Monday, July 14, 2014 2:06 PM
Points: 3,865, Visits: 7,130
If you have the option to add a new drive and initialize it, you could add the drive, take the old one offline, mount the new drive with the same drive letter, restart the server. Providing that you can copy any other files that were on the "old" drive to the new one, TempDB will get created on the new drive.

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1491044
Posted Wednesday, September 4, 2013 12:32 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:50 PM
Points: 6,191, Visits: 13,340
New persopn (9/3/2013)
here we dont have the san setup. we are using internal storage.

can you provide more detail on the local storage setup such as raid, number of disks and logical configuration?


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1491148
Posted Wednesday, September 4, 2013 4:10 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 5:12 AM
Points: 139, Visits: 398
we have 6 drives in that server
Post #1491207
Posted Thursday, September 5, 2013 7:15 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 9:22 PM
Points: 115, Visits: 229
Looks it is storage issue. Check if there is any error belongs to Msg 823. If it is then work with storage team. If there are no data files expect Tempdb then follow below procedure.
1) Attach new drive
2) Change the drive letter to H
3) Create the folders Data\TempDB and copy the Tempdb files to H:\Data\TempDB
4) Start the SQL services
Thanks,


Thanks,
I’m nobody but still I’m somebody to someone………….
Post #1491772
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse