Home Dashboard Directory Help
Search

Operating system error -2147024891: "0x80070005(Access is denied.)". by MEGATestSolutions


Status: 

Closed
 as External Help for as External


7
0
Sign in
to vote
Type: Bug
ID: 435855
Opened: 4/28/2009 1:29:35 PM
Access Restriction: Public
2
Workaround(s)
view
10
User(s) can reproduce this bug

Description

Executing the SQL Query to create a database with Filestream, prompts an error, as follows;
Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\FileStreamTSCDB321". Operating system error -2147024891: "0x80070005(Access is denied.)".


CREATE DATABASE Archive
ON
PRIMARY ( NAME = Arch1,
    FILENAME = 'c:\data\archdat1.mdf'),
FILEGROUP FileStreamGroup1 CONTAINS FILESTREAM( NAME = Arch3,
    FILENAME = 'c:\data\filestream1')
LOG ON ( NAME = Archlog1,
    FILENAME = 'c:\data\archlog1.ldf')
GO
Details
Sign in to post a comment.
Posted by Microsoft on 5/3/2010 at 11:16 AM
Hi,
    Windows team has released a hotfix for Windows XP as well. It is available at http://support.microsoft.com/?id=978835Updated by Connect Synchronizer; see History tab for changed fields. Thanks for reporting this issue. If there are any further issues in this area, feel free to contact us


Posted by Microsoft on 3/19/2010 at 11:29 AM
Windows team has released a hotfix for Windows XP as well. It is available at http://support.microsoft.com/?id=978835
Posted by DKSchmidt on 1/21/2010 at 6:38 AM
This problem had us bugged down for a week before we found this issue page. It works fine on 2008 Server and on Windows 7 Pro - but the main development workstation running XP nothing works. Because of an update for a completely different issue, we'll now have to deliver a system that saves potentially big files in VARBINARY(MAX) fields directly in the table.

It's harsh, but this may be a big incitament for developers to move to Vista/7?

Please fix this in time for my next project.
Posted by FH_Matthias on 1/8/2010 at 2:05 AM
Will there be in the (near) future an Hotfix for Win XP SP3?

We intent to release a new version of our Software using SQL 2008 Filestream function, but >90 % of our customers are currently using Win XP SP3 as OS.

During test on different Maschines we found that the described workarounds (changing the Account) does not work on all. Also this is not a solution for all of our customers.

It would be really interesting for us to know is there would be a solution or if we have to remove the FILESTREAM function from our software.
Posted by an777 on 12/18/2009 at 3:07 PM
When is the KB973573 version for Windows XP SP3 will be available from Microsoft? Changing the service account is not the best option. Iis Microsoft planning to get out the XP version? Thanks.
Posted by Claiton Lovato Junior on 11/3/2009 at 9:59 AM
I also can reproduce this error on a Windows XP Pro x86 with the KB956572 installed.
Even that the original thread also uses the same OS details the solution posted on the KB973573 only refers to Windows Server 2K3 and XP Pro x64 and all the downloads are only for Windows Server 2K3.
I Could workaround this creating a new user for SQL Server but would like to see a version of the KB973573 for my OS too.

Cheers,
Claiton Lovato
Posted by Microsoft on 11/2/2009 at 8:57 AM
Thank you for providing details on the issue. We have worked with the Windows team on a hotfix addressing it.
The fix is available at http://support.microsoft.com/kb/973573.
Posted by JaBurd on 10/15/2009 at 6:14 AM
This is a MAJOR issue. Many production environments (government) cannot support a workaround of "Create an Admin user and have SQL Server Service use that account.”

Additionally, user accounts will most likely be required to periodically change their passwords causing additional headaches and downtime.
Posted by devolm on 6/9/2009 at 12:26 PM
I have found a workaround for this problem. In reading the information on KB956572, it was mentioned that it affected services running as Local System or Network Service. I changed the loging account for Sql Server Service to an user account with admin privledge and found that it corrects the problem.
Posted by Murray Francis on 5/25/2009 at 8:22 PM
Further to my above comment, I have now definitely identified the culprit of this error, it is the Windows Update patch KB956572 (http://support.microsoft.com/kb/956572/)

The error I described in my earlier post with Access Denied on SQL 2008 Filestream appears after applying the patch KB956572.

This error is happening on a Virtual machine development box I have, which luckily I had a backup of the vhd before applying the recent round on Windows Updates.

I have restored the vhd to the earlier backup and applied each Windows Update individually with a reboot after each one, and have narrowed it down to be caused by KB956572

I am about to deploy this application to the client site, and urgently need Microsoft to address this issue as I cannot afford for this to occur on site site.
Posted by Farid Zidan on 5/23/2009 at 2:46 PM
Same thing. I had AdventureWorks2008 installed successfully, but it stopped working. I uninstalled sample databases and re-ran SQL2008.AdventureWorks_All_Databases.x86.msi, all databases get installed successfully except AdventureWorks2008. I have Developer Edition 2008 running on Windows XP SP3 (32-bit). Here is the error log entries:

2009-05-23 17:34:26.54 spid51     Configuration option 'filestream access level' changed from 2 to 2. Run the RECONFIGURE statement to install.
2009-05-23 17:34:26.54 spid51     FILESTREAM: effective level = 2, configured level = 2, file system access share name = 'SQLSERVER'.
2009-05-23 17:34:30.90 spid51     Starting up database 'AdventureWorks2008'.
2009-05-23 17:34:31.12 spid51     Error: 17207, Severity: 16, State: 1.
2009-05-23 17:34:31.12 spid51     STREAMFCB::Startup: Operating system error 0x80070005(Access is denied.) occurred while creating or opening file 'F:\Data\Ms\Microsoft SQL Server\MSSQL10.SQLSERVER\MSSQL\DATA\Documents'. Diagnose and correct the operating system error, and retry the operation.
2009-05-23 17:34:31.14 spid51     Error: 17204, Severity: 16, State: 1.
2009-05-23 17:34:31.14 spid51     FCB::Startup () failed: Could not open file F:\Data\Ms\Microsoft SQL Server\MSSQL10.SQLSERVER\MSSQL\DATA\Documents for file number 65537. OS error: 0x80070005(Access is denied.).
Posted by Murray Francis on 5/19/2009 at 5:26 AM
I am having the same problem. I have had a SQL 2008 database with FileStream in use for months now, and last week after some Windows Updates were applied I am now getting the following error in event log:

STREAMFCB::Startup: Operating system error 0x80070005(Access is denied.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\FS_XXXX'. Diagnose and correct the operating system error, and retry the operation.

This is with MSSQLSERVER service running as NetworkService, running on Windows Server 2003 SP2.
Posted by Microsoft on 5/8/2009 at 12:05 PM
Thank you for the prompt response. We have identified addtitional information that would help us with the investigation. Could you please answer these questions?
• Does rebooting fix the problem?
• What are the permission settings on the c:\data directory (output of the "cacls c:\data /T" command)?
SQL Server Engine Team
Posted by MEGATestSolutions on 5/7/2009 at 4:24 PM
•Do you have multiple instances of SQL Server installed?
Happens on both single or multiple instances installed

•What user accounts are the instances using?
Authentication mode is WINDOWS-ONLY.
SQL Trace ID 1 was started by login "sa".

•Could you provide the complete SQL Server error log?
See below error log
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2009-05-07 08:59:35.04 Server     Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
    Jul 9 2008 14:43:34
    Copyright (c) 1988-2008 Microsoft Corporation
    Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)

2009-05-07 08:59:35.04 Server     (c) 2005 Microsoft Corporation.
2009-05-07 08:59:35.04 Server     All rights reserved.
2009-05-07 08:59:35.04 Server     Server process ID is 3880.
2009-05-07 08:59:35.04 Server     Authentication mode is WINDOWS-ONLY.
2009-05-07 08:59:35.04 Server     Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2009-05-07 08:59:35.04 Server     This instance of SQL Server last reported using a process ID of 2648 at 5/7/2009 12:35:26 AM (local) 5/7/2009 7:35:26 AM (UTC). This is an informational message only; no user action is required.
2009-05-07 08:59:35.04 Server     Registry startup parameters:
     -d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
     -e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
     -l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2009-05-07 08:59:35.20 Server     SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-05-07 08:59:35.20 Server     Detected 2 CPUs. This is an informational message; no user action is required.
2009-05-07 08:59:36.01 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-05-07 08:59:36.26 Server     Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2009-05-07 08:59:36.35 spid5s     Starting up database 'master'.
2009-05-07 08:59:39.38 spid5s     Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-05-07 08:59:39.73 spid5s     Recovery completed for database master (database ID 1) in 1 second(s) (analysis 246 ms, redo 98 ms, undo 74 ms.) This is an informational message only. No user action is required.
<{39B75A24-0837-4CEC-AFDF-B960027AE07E}>RsFxNso initialized. InstanceId = 00000001
<{50080099-5EC4-4EAF-A2A2-63C3DA97F8EB}>FsAgent is initialized
<{09C4480B-DBA4-49B7-956F-68A8B8B2445D}>FsAgent is up and running
2009-05-07 08:59:42.20 spid5s     FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'SQLEXPRESS'.
2009-05-07 08:59:46.35 spid5s     SQL Trace ID 1 was started by login "sa".
2009-05-07 08:59:47.90 spid5s     Starting up database 'mssqlsystemresource'.
2009-05-07 08:59:49.70 spid5s     The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-05-07 08:59:55.39 spid15s     Starting up database 'model'.
2009-05-07 08:59:55.54 spid5s     Server name is 'TASEON26\SQLEXPRESS'. This is an informational message only. No user action is required.
2009-05-07 09:00:00.18 spid15s     Recovery completed for database model (database ID 3) in 1 second(s) (analysis 213 ms, redo 0 ms, undo 403 ms.) This is an informational message only. No user action is required.
2009-05-07 09:00:02.85 spid15s     Clearing tempdb database.
2009-05-07 09:00:12.53 spid15s     Starting up database 'tempdb'.
2009-05-07 09:00:15.90 Server     A self-generated certificate was successfully loaded for encryption.
2009-05-07 09:00:16.59 spid15s     Recovery completed for database tempdb (database ID 2) in 1 second(s) (analysis 186 ms, redo 0 ms, undo 546 ms.) This is an informational message only. No user action is required.
2009-05-07 09:00:19.03 Server     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2009-05-07 09:00:19.03 Server     Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2009-05-07 09:00:19.29 Server     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2009-05-07 09:00:22.90 spid18s     The Service Broker protocol transport is disabled or not configured.
2009-05-07 09:00:23.00 spid18s     The Database Mirroring protocol transport is disabled or not configured.
2009-05-07 09:00:23.92 Server     The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/Taseon26.taseon.com:SQLEXPRESS ] for the SQL Server service.
2009-05-07 09:00:23.92 Server     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-05-07 09:00:27.78 spid18s     Service Broker manager has started.
2009-05-07 09:00:55.34 spid5s     Starting up database 'msdb'.
2009-05-07 09:01:10.01 spid5s     Recovery is complete. This is an informational message only. No user action is required.
2009-05-07 09:02:24.37 spid22s     A new instance of the full-text filter daemon host process has been successfully started.
2009-05-07 13:42:32.74 spid51     Starting up database 'ReportServer$SQLEXPRESS'.
2009-05-07 13:42:32.91 spid51     2 transactions rolled forward in database 'ReportServer$SQLEXPRESS' (5). This is an informational message only. No user action is required.
2009-05-07 13:42:32.95 spid51     0 transactions rolled back in database 'ReportServer$SQLEXPRESS' (5). This is an informational message only. No user action is required.
2009-05-07 13:42:32.95 spid51     Recovery is writing a checkpoint in database 'ReportServer$SQLEXPRESS' (5). This is an informational message only. No user action is required.
2009-05-07 13:42:33.15 spid51     Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2009-05-07 13:42:33.31 spid51     Starting up database 'TSCDBTN320'.
2009-05-07 13:42:35.59 spid51     Starting up database 'TSCDBTN320'.
2009-05-07 13:42:37.01 spid51     Starting up database 'TSCDBTN320'.
2009-05-07 14:56:20.82 spid52     Starting up database 'TSCDBTN320'.
2009-05-07 14:56:23.71 spid53     Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2009-05-07 14:56:23.88 spid53     Using 'xpstar.dll' version '2007.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2009-05-07 14:56:24.68 spid53     Starting up database 'ReportServer$SQLEXPRESS'.
2009-05-07 14:56:24.93 spid53     Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2009-05-07 14:56:25.21 spid53     Starting up database 'ReportServer$SQLEXPRESS'.
2009-05-07 14:56:25.51 spid53     Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2009-05-07 14:57:32.21 spid53     Starting up database 'ReportServer$SQLEXPRESS'.
2009-05-07 14:57:32.47 spid53     Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2009-05-07 16:17:30.74 spid51     Starting up database 'ReportServer$SQLEXPRESS'.
2009-05-07 16:17:31.02 spid51     Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2009-05-07 16:17:31.16 spid51     Starting up database 'TSCDBTN320'.
2009-05-07 16:17:39.52 spid53     Starting up database 'ReportServer$SQLEXPRESS'.
2009-05-07 16:17:39.72 spid53     Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2009-05-07 16:17:39.94 spid53     Starting up database 'TSCDBTN320'.
2009-05-07 16:17:40.06 spid53     Starting up database 'ReportServer$SQLEXPRESS'.
2009-05-07 16:17:40.52 spid53     Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2009-05-07 16:17:40.72 spid53     Starting up database 'TSCDBTN320'.
2009-05-07 16:17:54.28 spid52     Starting up database 'Archive'.
2009-05-07 16:17:54.45 spid52     Error: 17207, Severity: 16, State: 1.
2009-05-07 16:17:54.45 spid52     STREAMFCB::Startup: Operating system error 0x80070005(Access is denied.) occurred while creating or opening file 'c:\data\filestream1'. Diagnose and correct the operating system error, and retry the operation.
2009-05-07 16:17:54.47 spid52     Error: 17204, Severity: 16, State: 1.
2009-05-07 16:17:54.47 spid52     FCB::Startup () failed: Could not open file c:\data\filestream1 for file number 65537. OS error: 0x80070005(Access is denied.).


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Posted by Microsoft on 5/7/2009 at 4:01 PM
Thank you for reporting this issue.

We are currently investigating the problem. Can you please provide following additional information to help with the investigation?
•Do you have multiple instances of SQL Server installed?
•What user accounts are the instances using?
•Could you provide the complete SQL Server error log?
If you need any clarifications on these asks, please feel free to contact us.
SQL Server Engine Team
Sign in to post a workaround.
Posted by scouse01 on 8/5/2009 at 3:56 AM
Devolm, I am new to SQL Server 2008 and I'm having the same problems. I have created a new account and gave it admin privilege. I then changed the user login and logged in as the new user. I opend SQL Server 2008 and added the the new user from Security but I am still unable to execute the SQL2008.AdventureWorks_All_Databases.x86.msi
It still only allows me to delete the file....... Please can you provide a step-by-step instruction, as I'm a beginner.....
Posted by devolm on 6/9/2009 at 12:29 PM
As mentioned in my comment, this problem can be worked around by using a user account for the Sql Server Service instead of the Local System or Network Service account. In my testing, I used an account with admin privledges.