You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

kb956572 and sql 2008 filestream

microsoft.public.windowsupdate

did anyone noticed problem with the kb956572 update and filestream on
SQL 2008 (without SP1)?
we have upgraded a windows 2003 SP2 with an instance of SQL 2008 and
with the update kb956572 we get the following errors on the activation
of a database with filestream enabled:

STREAMFCB::Startup: Operating system error 0x80070005(Access is
denied.) occurred while creating or opening file 'D:\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\xxxxFileStre amData'. Diagnose
and correct the operating system error, and retry the operation

A file activation error occurred. The physical file name 'D:\Microsoft
SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\xxxxFileStre amData' may be
incorrect. Diagnose and correct additional errors, and retry the
operation.

Some logging with procmon does not reveal anything supicious
(the directory is opened without errors).
since the update changes the way the impersonification is made for
some accounts (as far i understand) I've been thinking on changing the
account of msssqlserver service (currently is NT AUTHORITY
\NetworkService - the default from the setup).
Is a viable workaround?

andrea dal farra wrote:
> Hello to all,
>
> did anyone noticed problem with the kb956572 update and filestream on
> SQL 2008 (without SP1)?
> we have upgraded a windows 2003 SP2 with an instance of SQL 2008 and
> with the update kb956572 we get the following errors on the activation
> of a database with filestream enabled:
>
> STREAMFCB::Startup: Operating system error 0x80070005(Access is
> denied.) occurred while creating or opening file 'D:\Microsoft SQL
> Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\xxxxFileStre amData'. Diagnose
> and correct the operating system error, and retry the operation
>
> FCB::Startup () failed: Could not open file D:\Microsoft SQL Server
> \MSSQL10.MSSQLSERVER\MSSQL\DATA\xxxxxxxFileStreamD ata for file number
> 65537. OS error: 0x80070005(Access is denied.).
>
> A file activation error occurred. The physical file name 'D:\Microsoft
> SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\xxxxFileStre amData' may be
> incorrect. Diagnose and correct additional errors, and retry the
> operation.
>
> Some logging with procmon does not reveal anything supicious
> (the directory is opened without errors).
> since the update changes the way the impersonification is made for
> some accounts (as far i understand) I've been thinking on changing the
> account of msssqlserver service (currently is NT AUTHORITY
> \NetworkService - the default from the setup).
> Is a viable workaround?
>
>
> thanks
>
>
See that reported. Some have recommended changing to a true domain
account rather than network service.

disgruntled wrote:
> I uninstalled the kb and it fixed it
>
> "andrea dal farra" wrote:
>
>> On Apr 17, 7:58 pm, Susan Bradley <sbrad...@pacbell.net> wrote:
>>
>>> See that reported. Some have recommended changing to a true domain
>>> account rather than network service.
>> On a test machine switching to local service works fine.
>>
>> thanks
>>
Uninstalling is not the answer. You still need the patch.