Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
How did you find out that NIS is blocking the creation or usage of ADS files? ADS files have definately been tested and I’m not aware of any ADS issues.
There are two reasons I think NIS is blocking this. First, the only change I made to my system was installing NIS 2009. Secondly, information found on the internet saying that antivirus software (generally speaking) can result in these kind of errors.
Prior to installing NIS 2009 I uninstalled Trend Micro Internet Security software, but I can't see how this should affect this?
Anyway, to investigate this further I'm plannig of uninstall NIS to see if this solves the problem. My question is then: can I reinstall NIS on the same computer without beeing counted as new computer? You see, I have already installed NIS on two other computers so I don't have any keys left :)
Arild
I general, you should be able to reinstall on the same computer without using up a license. Should you run into a problem you can contact support and explain what happened and they can resolve it for you.
Hello again
I have now uninstalled NIS and the SQL Server error messages are now gone. No error when starting SQL Server.
I really like NIS 2009 so do you have any suggestion how I can make SQL Server work with NIS?
Arild
Hello again
I just want to inform you that I now have reinstalled NIS 2009 and the error messages and SQL Server problems are back.
Arild
eikari, thanks for the feedback. I may have reproduced the same issue on my own machine and will be asking some folks to look into it.
Hi Reese,
I upgraded from NAV2008 and have a similar issue with SQL Server 2005 on my Windows XP SP2 workstation:
"FCB::RemoveAlternateStreams: Operating system error 6(The handle is invalid.) occurred while creating or opening file 'E:\Data\MSSQL\SQL2005\Data\sysdb.mdf'. Diagnose and correct the operating system error, and retry the operation."
There is an Application event log entry for each database.
I too uninstalled NIS 2009 using the norton removal tool and rebooted to make sure, and the problem did go away. After reinstalling NIS 2009 the problem came back. What, if any, recommended exclusions can we specify to prevent this short of uninstalling? I cannot afford database corruption.
Also, any idea if/when a patch is planned?
Thanks,
- Brian
Hi,
I got the same problem. NIS 2009 and SQL Express installed through my Pinnacle TV Center Pro software. Error messages are all over event log:
Event Type: Error
Event Source: MSSQL$SQLEXPRESS
Event Category: (2)
Event ID: 17207
Date: 10/10/2008
Time: 3:56:07 PM
User: N/A
Computer: *******
Description:
FCB::RemoveAlternateStreams: Operating system error 6(The handle is invalid.) occurred while creating or opening file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\tempdb.mdf'. Diagnose and correct the operating system error, and retry the operation.
Uninstalling NIS09 solves this. Note though I had the same when using NIS2008 as well, it does not seem to be an NIS09 problem only.
Would appreciate some info on a workaround or confirmation of an upcoming fix/patch.
Thank You.
I thought this was only a NIS 2009 problem... 
My problem is that if this is not solved in reasonable time, I have no other solution than uninstall NIS 2009 and buy from Trend or other manufactor. As a computer developer/consultant I need to use my local SQL Server all the time, and not having it are making things a lot more difficult for me and my business.
Is this something we can expect to see any solution to soon?
Thanks everyone for the additional feedback.
We have reproduced the error message in the logs but database functionality continues to work. Since the error message does not occur without our product installed, we are currently investigating that behavior. We have isolated it to a component that did not exist in the 2008 products so something different is involved there and we'll have to look into that separately.
As far as timeframe for a fix is concerned, I can't commit to any dates but you shouldn't expect it within the next couple of days but I also hope that it won't be more than a month.
Ok, we’ve isolated the problem that introduces the log message and believe that we know how to fix it. Unfortunately, there’s no way to work around the issue as a user of the products. We anticipate that we will be able to deliver the fix in the next product update. I still can’t commit to an exact time for when that will occur though.
Thanks for keeping us updated on what is happening.
I also hope you soon can give us a more details about when the next product update will be released. 
eikari, I have sent you a question via the community Private Messenger system, please look for the 
in the upper right hand corner of any community page.
I am also having this problem with Sql Server and Norton Antivirus. In my case it has certainly impacted the speed of my system and I encourage you to get a fix out there fast. I hate to think we have to wait for some sort of comprehensive update instead of simply getting a patch to solve our problem.
Hello Nukezm,
Before we can release the patch, we need to test the patch to ensure that it doesn't create any new problem or cause system failure. We hope to complete testing on this patch in a timely manner.
Keep an eye on these forums, and we will post an announcement when a new patch is release.
Thanks for you patience!
Tim,
Thanks for your prompt reply. I understand and look forward to the patch at the completion of your testing.
Any idea about when this fix (update) will be released?
Thanks
Hello Nukezm,
We can't really comment on any dates at this time. However, I can tell you we're getting really close.
Uh - this problem went away yesterday. Did you folks fix it or am I just lucky?