Hi all,

I have a Windows server 2003 SP2 server that has one SQL 2005 SP2 instance
and one SQL Express 2005 instance installed.

On one of my databases in the SQL express instance I am getting the
following error logged in the application event log about every hour,
although the database seems to be running fine.

FCB::RemoveAlternateStreams: Operating system error (null) occurred while
creating or opening file 'C:\Program Files\Microsoft SQL
Server\MSSQL.4\MSSQL\Data\Bagshaw200801_Data.MDF'. Diagnose and correct the
operating system error, and retry the operation.

I cannot tell what is causing it, please could somebody help me.

Thank you in advance.

Hello Brandon,

Take a look at the following link:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=181344&SiteID=17

--
Ekrem Önsoy

"Brandon" discussions.microsoft.com> wrote in message
news:2E02C529-ED6F-4D85-9FE7-B202A3325BDC@microsoft.com...

Thanks very much for your reply, I did look at this same post and removed the
SQL server installation and database fodlers from real time virus scanning, I
just have not been able to restart the server as of yet. This will be done
after business hours today.

What did concern me a bit was the fact that this post refers to operating
system error 6, and mine refers to operating system error null.

We are running Trend Officescan Enterprise AV.

Thanks for any other help that you may provide.

"Ekrem Önsoy" wrote:

Do the Windows Event Logs say anything about this error?

--
Ekrem Önsoy

"Brandon" discussions.microsoft.com> wrote in message
news:2E2D2B01-4117-489B-A352-0FE1F1861DA8@microsoft.com...

...

This is the error in the Windows Application event log. The error in SQL
Manager looks the same.

"Ekrem Önsoy" wrote:

You said that you get this error "every hour" so this makes me think that
there must be some Scheduled Job in SQL Server or Windows or another
software that is executed and caused this error.

Will you tell me what softwares are being run on this server where this SQL
Server 2005 Express Edition is installed? For example, is this a Domain
Controller at the same time? Or Exchange Server is installed? Or Antivirus
softwares?

Review your scheduled jobs that run every hour and let us know about them.
So we may reach to some evidence about this error.

--
Ekrem Önsoy

"Brandon" discussions.microsoft.com> wrote in message
news:5BABAB0B-F182-490F-A60E-1D269629AE38@microsoft.com...

Thanks again for your help.

It is a member server and hosts two applications. One is a proprietary
applicaiton and the other is Trend Micro Interscan. It is also running Trend
Micro Officescan as the antivirus software. Interscan is using a database on
a different instance and is not receiving mail as of yet, this still has to
be put into production. I unloaded officescan and restarted the instance and
the problem still occurs.

I have been looking closely at this error and saw that it is not actually
every hour, but when users start the software up a entry is placed in the
event log "starting up database..." and thereafter this error is logged.

I have forwarded this to the support people of the proprietary software but
anticipate them saying that it is a database problem and not related to their
software.

There are no scheduled jobs running on the server.

Thanks again.

"Ekrem Önsoy" wrote:

...

Well, I don't have anything to guess anymore. However you said that this is
a SQL Server 2005 Express Edition. So, in this edition of SQL Server the
"AutoClose" property is true by default. And because of this property, when
the last connected user disconnects, your database is closed and all
resources allocated for it is freed.

I think you get this error when another user tries to connect to this
database so it's opened again and you get this error somehow.

If this database is being used frequently and if you have enough resources
to allocated for this instance of SQL Server then how about setting this
AutoClose property to False? You can find this property in that database's
properties\Options.

This just a suggestion, not a solution.

--
Ekrem Önsoy

"Brandon" discussions.microsoft.com> wrote in message
news:D97F0409-1B63-4E7D-875B-354E6E49A78E@microsoft.com...

Thanks for all your help Ekrem, even if your sugestion does not solve the
problem the logs will look a lot better untill I can find a proper solution.

I posed this Q to a lot of SQL admins and you have by far been the most
helpfull.
Thanks!

"Ekrem Önsoy" wrote:

Can you send me the SQL Error Log which contains this error? My email
address is "ekrem AT compecta DOT com".

Maybe we can find something there.

--
Ekrem Önsoy

"Brandon" discussions.microsoft.com> wrote in message
news:0167BC7D-D896-4E78-B6FB-62F206E9695F@microsoft.com...