Try the following steps to get your MDFs working again:
1. Delete the MDF/LDF files from the App_Data directory of the website under inetpub\wwwroot.
2. Download and install the SSEUTIL command line tool from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=FA87E828-173F-472E-A85C-27ED01CF6B02&displaylang=en
3. Using sseutil, issue a command that looks something like: sseutil -child "NT AUTHORITY\NETWORK SERVICE" -detach D:\ . You will need to change the account name and the detach path to match your machine settings. If on IIS5/5.1, then ASPNET will be the correct user account. Also, you can determine the detach path pretty easily by issuing sseutil -list to see where the problematic MDFs are currently attached. The "D:\" in the sample command line is just the first few characters that sseutil uses to auto-detach all databases that begin with "D:\". Change the path as neeeded for your machine.
4. Set the ACLs on App_Data directory under inetpub\wwwroot to grant R/W to the appropriate process account - NETWORK SERVICE on WS03 or ASPNET on IIS5/5.1.
5. Re-copy the MDF/LDF files from the directory where the file-based website exists back into App_Data under inetpub\wwwroot. After the copy occurs, check that the MDF/LDF files have now inherited the new ACLs.
6. Re-run the application (ignore any connection errors that might occur - just hit refresh in the browser).
We are working on a fix in SSE that will eliminate the manual reconfiguration for RTM.
說是只有beta1,2的有...我怎麼還遇到了?
提供另一個快速的解決當前問題的方法
把兩個檔案的read-only去掉...加一個app_offline.htm,然後運行,然後去掉加上的app_offline.htm,就可以了.