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

The operating system returned error 5(Access is denied.) to SQL Server during a write at offset 0x00000000012000 in file 'D:\data\data.mdf' Expand / Collapse
Author
Message
Posted Tuesday, July 9, 2013 1:30 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 2:16 PM
Points: 55, Visits: 294
I do not know what the heck is going on here. The production database get's backed up and we restore it and run checkpoint against it and get this error below. We have sql2005 with SP 4 on it. We found this KB article (http://support.microsoft.com/kb/934713) that had similar behavior so that's why we upgraded to SP 4 from SP 2. Still no change. When we restart the service this db goes into recovery mode.



The operating system returned error 5(Access is denied.) to SQL Server during a write at offset 0x00000000012000 in file 'D:\data\data.mdf'

Anybody experience the same behavior? Any help is much appreciated. Thanks.
Post #1471822
Posted Tuesday, July 9, 2013 1:39 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 4:43 AM
Points: 12,895, Visits: 32,090
is this on a sAN, where the SAN ends up coming on line AFTER the SQl service is already started?
i've seen a similar situation on my developer machine.

if you stop and start the service, but not the server, does the database come online?


Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1471831
Posted Tuesday, July 9, 2013 1:55 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 2:16 PM
Points: 55, Visits: 294
yes I believe it's on a SAN (IT guy is on vacation). This happens when we restart the service only and not the server.

So what was your fix on this?

Thanks.
Post #1471837
Posted Tuesday, July 9, 2013 2:25 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 4:43 AM
Points: 12,895, Visits: 32,090
JP10 (7/9/2013)
yes I believe it's on a SAN (IT guy is on vacation). This happens when we restart the service only and not the server.

So what was your fix on this?

Thanks.


my issues not the same as yours; in my case i had to set a service dependency, so SQL would start after the SAN service was already started.

as i remember it, you can VIEW the dependencies in Services.msc, but cannot set it there ;
to set them it was a command line argument named "sc"?, and we had to point it to a service that exists that represents the SAN, i don't have it in front of me, or i'd screenshot it.
sorry.


Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1471847
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse