AdventureWorks2008 placeholder.txt is corrupted
-
Sunday, June 07, 2009 1:49 AMI just received a copy of the MCTS 70-433 Training Kit. When I try to install the AdventureWorks2008 sample database from the CD, I am able to Attach the database, but if I reboot the computer or try to perform a backup of the database I get this error:
FILESTREAM's file system log record 'placeholder.txt' under log folder '\\?\C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\Documents\$FSLOG' is corrupted. (Microsoft SQL Server, Error: 5511)
All Replies
-
Monday, June 08, 2009 4:56 AM
hi everybody... i have the same issue... :(
I dont know how can i put online the database after it get suspect.
Regards- Edited by Nicolas Neri - n_neri Monday, June 08, 2009 4:57 AM
-
Monday, June 08, 2009 12:22 PM
Hi Nicolas,
I found a workaround for this problem. It is a lot of work but it's the only possibility I know of so far.- Delete the AdventureWorks2008 database in SSMS.
- Follow the hyperlink from the Chapter 1 introduction, http://msftdbprodsamples.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=18407
- Download the x86.msi or appropriate package. It is around 60 MB.
- Run the downloaded file. It will install several databases in your test server.
- Go back to SSMS to see the new copy of AdventureWorks2008.
Enjoy
- Proposed As Answer by Nicolas Neri - n_neri Monday, June 08, 2009 6:08 PM
- Marked As Answer by miqrogroove Wednesday, June 17, 2009 3:17 PM
-
Monday, June 08, 2009 6:05 PMThanks a lot...
Now i can work with AdventureWorks without restoring every day :P
See you -
Tuesday, June 30, 2009 2:53 PMHello,
I also had the same problem. My solution was a little different. I moved placeholder.txt to the parent folder (it could even be deleted). I restarted the service and then I was able to backup the database. The database no longer showed up as suspect. I don't know if it would help in your case, but it worked in my situation.
Regards,
Sami -
Monday, July 13, 2009 5:12 PM
Hi Nicolas,
I found a workaround for this problem. It is a lot of work but it's the only possibility I know of so far.- Delete the AdventureWorks2008 database in SSMS.
- Follow the hyperlink from the Chapter 1 introduction, http://msftdbprodsamples.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=18407
- Download the x86.msi or appropriate package. It is around 60 MB.
- Run the downloaded file. It will install several databases in your test server.
- Go back to SSMS to see the new copy of AdventureWorks2008.
Enjoy
The SQL2008.AdventureWorks_All_Databases.x64.msi is the correct installer package for SQL Server 2008 x64. I had to uninstall all previous databases, then run the installer to get it to work. -
Tuesday, March 22, 2011 2:58 AM
Sami,
This worked perfectly!!!
Thank you,
Oscar
-
Wednesday, September 28, 2011 10:08 PM
Hello,
Thanks Sami - your solution worked for me too.
Howard
-
Thursday, October 27, 2011 7:04 PM
Hello,
I also had the same problem. My solution was a little different. I moved placeholder.txt to the parent folder (it could even be deleted). I restarted the service and then I was able to backup the database. The database no longer showed up as suspect. I don't know if it would help in your case, but it worked in my situation.
Regards,
SamiHi Sami
Can you please tell me where is this placeholder.txt file located. I got the same problem but its not with installation or deattaching the databases. The problem is that my database gone in to suspected mode due to auto fail during recovery :)

