Post reply

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

  • July 9, 2013 at 1:30 pm

    #277247

    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.

  • July 9, 2013 at 1:39 pm

    #1630964

    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

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • July 9, 2013 at 1:55 pm

    #1630969

    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.

  • July 9, 2013 at 2:25 pm

    #1630978

    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

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply