Database is read-only.

Question

Hi

I have been learning on how to use the new features of the .NET 2.0, and Well I using VS2005 and everything is pretty straight foward. I did a Membership webform where you log in and create users and roles etc. I installed the SQL Server 2005 express as my Data provider and thats where my Tables are. I used the aspnetsql_reg comand to integrate the server to this application. Anyway my problem started when i decided to copy my project to my IIS server and well when I run the app from the Browser tells me that he Database It's set to Read-Omly and therefore it cant update it. This happens right after log in. but then I open the App. on hte VS and it runs find.

This is the error:

 Exception Details: System.Data.SqlClient.SqlException: Failed to update database "C:\INETPUB\WWWROOT\ESPM\APP_DATA\ASPNETDB.MDF" because the database is read-only.

If anyone have any ideas I would really aprecciate.

Answer 1

I got the same error - no doubt you have solved it by now - can you share....?

Thanks
ian

Answer 2

Actually I haven't but I thikn i know where it is going. I thikn it has to be with the IIS, and something has to do with the permissions of write on the user that is use to access de app. Other than that I am out of ideas.

how about you ??

Answer 3

I went through deleting the files, using SSEUTIL to detach database, reset permissions on the folders and then copy back. Still no good - and I can't find any other ideas on the Internet.......
Thanks anyway
Ian

Answer 4

I went through deleting the files and using the SSEUTIL program as well. I still have not been able to resolve this issue. Has anyone else figured it out?

Thanks
Zane

Answer 5

I am having the exact same problem, and would really like to know if anyone has found the answer to this.

Answer 6

Ditto!  Nothing I can do will make it work.  I would MUCH prefer to run it on SQL Server 2000, but there are tons of tables, views, stored procedures, and even a few functions in the express databases.  Not worth manually copying each one.

If anyone figures this out, please let us know.  I googled:

"ASPNETDB.MDF" read only

and found only THREE links on google groups, this being one of them.

• I created a new personal web site (using Visual Studio .NET 2005 Beta 2, not VWD)
• Setup security via the notes in welcome.html
  
• ran it successfully locally on my dev machine straight from VS.NET
  
• Copied the web to my server.
• Tried to run it from the server and got the same read only errors everyone else is getting.

I haven't tried this yet, but I'm wondering if running it locally, or administering it locally on the dev machine, then copying those modified database files up, somehow screws with it.  I'm going to try creating a totally fresh personal web site, do NO config and NO running locally, copy that up to the server, then see what happens.

Answer 7

With a bit of searching on Google I found out that this is a bug from an older release. Microsoft claimed to have fixed it in the latest release but the problem still excists :(

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=dd6d161b-df08-40bc-b9ed-fbca71949ddc

Guess we have to wait..and wait..and wait

Answer 8

Can you try the following steps.

1. Check the file attributes on the MDF to make sure its writable.
2. Make sure the user has permissions to the file.
3. Run the following query;
use master
select name, status from sysdatabases

If you are using AttachDBFilename in the connection string you will need to insert some debug code that does a debug print/console.writeline or something to get the output once the conneciton has been made and before any sql has been executed.

If you are using regular connections then just run the above from sqlcmd or express manager

Answer 9

I spent so long on this (and other bugs/problems with VS .Net 2005) that I gave up. Went back to using VS 2003 and regular SQL Server for the security database. It boggles my mind that something so simple can cause so many problems - I have read 20 different solutions to get this ever-so-simple-idea working - WTF are people doing?

Answer 10

I have been struggling with this for the past week or so.  Just as I was ready to give up and go back to VS2003 I decided to try one last thing.  Now it works! 

Here is the process I went through:
I first deleted my site files from c:\inetpup\wwwroot.  Then using the sseutil, I detatched every database I was using for the site including the aspnetdb.mdf.  I then changed the permissions on the wwwroot folder to allow full control for user aspnet (using IIS 5.1).  Then from inside VS2005, I copied the site again to the root of the IIS server.

As I mentioned earlier, this finally worked for me.  I hope it works for you as well.

Answer 11

This worked for me!

Thanks a lot!

Answer 12

You got it right my friend ! And you don't even have to remove your application before and to put it back after .. juste add the permissions to aspnet. Thank a lot !

Answer 13

Actually all you have to do is give write permissions to ASPNET for the App_Data directory instead of all of wwwroot (you probably don't want to do that).

Its probably advisable to use a real sql database anyway but for testing purposes these files aren't too bad.

Answer 14

So to be clear to resolve the issue where you have a .mdf database file generated by VS2005 and it gives you read-only errors you must do these things:

1.) Make sure your virtual directory is running ASP.NET v2.*
2.) Give the user ASPNET full control over the App_Data directory found within your website.
3.) Restart IIS to refresh its permissions.

Answer 15

I do hope you found a solution to your problem, I had the same problem and I managed to solve it.

1st I read somewhere that you have to give Network Service full permissions over the wwwroot and app_data, but, after doing this myself it din't help much.   Then I noticed that the cookie disabled "eye sort of icon that appeares at the bottom of the browser when a cookie has been rejected" was coming on whenever this error came about, so I set my browser to accept all cookies from my site and BRAVO!!!, things seem to work fine now, hope this helps anyone looking for a solution to this.

Saying that, am not sure myself whether it was a combination of the two things as mentioned above or just one.

Good luck.

Answer 16

How are you all

I faced the same problem as you faced and i tried to apply your solutions. Unfortenatlly I couldn't. But i was trying to find a way to add the permession to the asp as you said and i found a way to do that without giving permissions for a specifice folder whish is:

1) right click on my computer

2) point to manag and click

3) go to the directory local users and groups/ users

4) right click on ASPNET and choose properties

5) select the Member OF tab

6) final add addministrators permission

I hope that is the right solution

Best wishes

 

Answer 17

Are these solutions are directed at Windows Server users rather than Windows XP users? The features described for giving a user account (be it "NT Authority/Network Service" on IIS 6 or "ASPNET" on IIS 5.1) do not seem to be available to me.

A previous poster said "give write permissions to ASPNET for the App_Data directory" but with my Windows XP and IIS 5.1 setup, I right-click on the App_Data directory, select "Properties" and I can select general read only/write permissions but there is no means to do so for a particular user.

If I have missed the method please show me the steps, thanks.

Answer 18

Mark, am using the same setup as you are i.e. Windows XP and IIS 5.1, after selecting "properties on the "App_Data" directory,

1.  Select the security tab

2. CLick on Add... under "Group or User names:" table

3. On the next window, select Advanced, another window appears and on this, select or rather click on "find now" and a list of Groups and Users should appear on the bottom table.

4.  Click on ASPNET followed by OK, and the same on the next 2 windows.

Hope that does the trick for you.

Answer 19

from the suggestion of the people from www.asp.net ( http://forums.asp.net/1/904462/ShowPost.aspx#904462 ) here is what i got now:

error after disabling "Write" capability from ACL:
System.Data.SqlClient.SqlException: Failed to update database "C:\INETPUB\WWWROOT\TECHPAD\APP_DATA\ASPNETDB.MDF" because the database is read-only. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

error after ENABLING "Write" capability from ACL:
System.Data.SqlClient.SqlException: Cannot open user default database. Login failed. Login failed for user 'MANEC\ASPNET'. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

this makes me think its so hard to study VWD and SQLExpress for a newbie like me. when I run the webpages from the built-in webserver of VWD it may work fine but when on IIS it will not work (or vice-versa). so confusing. maybe bcoz im very new to this.

i find it hard to do all of these setups. i wanna learn this though. PLS HELP.

Answer 20

i created another website project in VWD but got the same issue. this is my observation:

in SQL Server Management. it really says the database is readonly
figure1 --> http://geocities.com/fbi_file01/fig1.jpg

you can try to change the read-only status to false but...
figure2 --> http://geocities.com/fbi_file01/fig2.jpg

..you will only get this error message
figure3 --> http://geocities.com/fbi_file01/fig3.jpg

PLS HELP ME to figure this out. i tried all the suggestion here but didnt work.

Answer 21

i noticed that this problem occurs as soon as i created a manual connection (that uses a sql server authentication and not integrated authentication). right after i tested the manual connection and run the page  that  uses membership class, i will get this problem. i cant understand why these are all happening.

pls help. its been a week im thinking abt this.

Answer 22

Hi,

I've had this problem too. I'm running IIS 6.0 on a Windows 2003 Server. I changed the permissions on the directory containing ASPNETDB.MDF to allow the Network Service write permission and ASP.NET write permission. ASPNETDB.MDF also needs the same permissions on it. I think you may have to reboot or restart IIS to see the changes take.

Answer 23

which folder am i going to change the permission? the folder on the IIS?

from other forum they suggested to disable the app_data folder right before u publish the website on IIS but when u try that, my winXP (sp2) wont allow me. when u uncheck the read-only it goes back when u check it again the properties.

ill try ur suggestion. thanks boston.

Answer 24

Jamokay wrote:

Mark, am using the same setup as you are i.e. Windows XP and IIS 5.1, after selecting "properties on the "App_Data" directory, 1.  Select the security tab 2. CLick on Add... under "Group or User names:" table 3. On the next window, select Advanced, another window appears and on this, select or rather click on "find now" and a list of Groups and Users should appear on the bottom table. 4.  Click on ASPNET followed by OK, and the same on the next 2 windows. Hope that does the trick for you.

Thanks, Jamokay

The problem I discovered was that it was necessary to uncheck the setting for "Use simple file sharing (recommended)" under the View tab in the Folder Options control panel applet to enable the Security tab to be displayed.

After following the next steps the problem was resolved.

Answer 25

Manech, have you tried the solution presented by Jamokay in his post above? It worked for both of us. Here it is again:

Jamokay wrote:

Mark, am using the same setup as you are i.e. Windows XP and IIS 5.1, after selecting "properties on the "App_Data" directory, 1.  Select the security tab 2. CLick on Add... under "Group or User names:" table 3. On the next window, select Advanced, another window appears and on this, select or rather click on "find now" and a list of Groups and Users should appear on the bottom table. 4.  Click on ASPNET followed by OK, and the same on the next 2 windows. Hope that does the trick for you.

This solution is for IIS 5.1. If you are using IIS 6 you will need to choose the user "Network Service" rather than "ASPNET".

Changing the ACL read only/write settings as you described doesn't solve the problem. The App_Data folder is in your website virtual directory in IIS.

If you can't see the Security tab see my reply to Jamokay's post.

Don't forget after doing this to restart the IIS Admin service using the Services administrative tool at Control Panel > Administrative Tools > Services.

 Hope that solves it for you too.

Answer 26

i believe i have tried Jamokay's suggestion but let me try one more time.

i cant move on with the logic of my project just because of this technicality. this consumed so much of my time. i just wish there's an alternate way of doing all of this.

thanks Mark J.

Answer 27

Add on to Justin's solution:

1.) Make sure your virtual directory is running ASP.NET v2.*
2.) Give the user ASPNET and NETWORK SERVICE modify control over the App_Data directory found within your website.
3.) Restart IIS to refresh its permissions.

Answer 28

How do I give the user 'ASPNET' full control over the App_Data directory?

Best regards Bjorn Sigurd

Answer 29

I was having this problem, and wanted to add a few things to how I resolved this.  First off I see a lot of people saying to give "full access" to that folder (App_Data directory) - I found that it only needs modify permissions.  Personally I don't like giving full access to anything so I tried from the bottom up with permissions until one worked - and it worked perfect with modify instead of full.

The "account" we ended up giving access to was IISWPG.

I was having this problem with both SQL databases and Access Databases (different project, simliar issues) - both were resolved by doing this on the folder where the databse resides.

G'luck all.

Dave Allen

 

Answer 30

Add read/write permission to ASPNETUSER to App_Data and it will work.

Answer 31

Hi,

I had tested it, the easy way is give ASP.NET Machine Account full control to both .mdf  and .LDF files. Also do the same for App_Data.

Right click to the folder/file and select properties -> Go to security Tab and click Add. Type ASPNET. Then give it full control. I should work now. Good luck

------------

- saifulnizam

Answer 32

When an unknown  user browses to an iis application asp file (not asp.net 2.0 ...aspx) and attempts to update an access db (or any other file) the actual user is the 'Everyone' user so Everyone must have r/w capacity. This is not the case when an iis virtural directory is first set up.

This can be simulated by creating a dummy application and then loading some of the database sample files that come with iis (iissample) into the dymmy applications virtural directory. You will find that the Authors.mdb will not update (an error occurs) when browsing to the  the AddDelete_VBScript.asp or the Update_VBScript.asp sample asp files.

To enable r/w for everyone select the directory (actual virtural directory) and go to properities. The select the security tab. Pick 'Group or user names: 'Everyone' then check the 'Allow full control' checkbox.

After setting full control for the 'Group or user name: Everyone' then the database will have write capacity. 

Hope this helps - Jerome

Answer 33

This just happened to me - in my case the project was under source control and wasn't checked out, which caused the mdf to be marked as Read-Only.

 

Ryan Shripat

Mindbase Consulting

www.mindbaseconsulting.com

Answer 34

"failed to update database" becuase it is "read only".
i also have the same problem, and i have done with it.
microsoft explanation was using "sseutil.exe", which is not help at all.
actually it just a matter of security.
try this steps, to solving that message.

Step 1:
Open My Computer from the desktop, and from the Tools menu select Folder Options.
Click on the View tab, and scroll to the end of the Advanced Settings box.
Near the bottom, you will find an entry named "Use simple file sharing (recommended)".
Uncheck this box, and click the OK button.
Now when you right-click on a file or folder and select Properties, you will see the Security tab.

step 2:
On a computer running Windows XP Professional, you just need to grant the ASPNET account permissions.
Use Windows Explorer to browse to the root folder of your Personal Website.
Right click on the folder and choose properties. Then click on the Security Tab.
Click the Add button, the Advanced button, and then the Find Now button.
Then click on the ASPNET item in the list and click Ok, and Ok again.
Then click the Allow Modify checkbox and click Ok.

You can follow the same steps for the Network Service account.

i hope this can answer everyone problem about this message.

Best regards,

ice
(looking for H1B Visa to work in USA)
kiong_hari at hotmail dot com

Answer 35

I've been wrestling with this issue for a few days now, and have looked all over the 'net trying to find a solution.  I'm using Windows 2000 Server with IIS5.  None of the fixes worked for me, most notably the whole entire SSEUTIL.EXE stuff. 

Here's what works for me, and it's one simple thing:

At the time of placing the .MDF files into the App_Data folder (whether manually or through VS's "copy website" tool) the app_data folder MUST have both ASPNET and IWAM_ read/write privileges.  The IWAM_ account can be removed from the folder after the database files are copied.  Without IWAM_ when the files are first placed into the folder I get the read-only issue every time.

If you forget to place IWAM_ privileges onto the folder ahead of time and the "read-only" issue rears its head, this is how I resolve it:

1.  Stop the SQL Server instance using SQL Server Management Express (right-click the server and click Stop).

2.  Use the task list to kill the "sqlserv.exe" process, since it remains running and prevents the database files from being deleted and/or updated.

3.  Right-click the App_Data folder in question, select Security, and add the IWAM_ account with write/modify privileges.

4.  Place the .MDF/LDF files into the app_data folder either manually or by using VS to copy or publish the files.

5.  Re-start the SQL Server instance using SQL Server Management Express (right-click the server and click Start)

I hope this works for others, as I myself was becoming sufficiently frustrated to the point of *almost* giving up on SQL Express.

t. crossman

Answer 36

Thats cool,

But does anyone know how we can set appropriate permissions thorough installation process? I need to install my site on many servers, so I am using a visual studio web setup project and it authomatically copies my database files too which is good. But then when i wanna update something i receive databas read only error. Is there a way that installer set the permissions authomatically?

Cheers

Answer 37

I'm having a similar problem.
I am running WinXP x64 edition, and using IIS 6.0
I use the Visual Web Developer 2005 Express Edition to develop my sites.
For some curious reason however, whenever I run my site using the program, it works fine!

I've done everything mentioned here, and nothing works!

Answer 38

Yep, this works, thanks iceb0ys!!!

Microsoft waste another afternoon of mine, thanks Bill.

Answer 39

I resolved this problem by adding Network service in the user.

Right click on your folder or .MDF file, click properties, click Security and add NETWORK SERVICE. Give right and modify rights. This resolved problem for me.

Answer 40

Hello,

I hope you got this problem fixed by now but just incase you haven't here's the solution.

-goto [C:\Inetpub\wwwroot\] using windows explorer

-right-click on [wwwroot] folder

-select properties then click the [security] tab at the top

-click the [ADD] button then the [Advanced] button then the [Find Now] button on the right

-highlight the ASPNET user and click the [OK] button

-click the [advanced] button again then the [Find Now] button again

-this time highlight the Network Service user and click [OK]

-click [ok] in the [select users and groups window]

-now that you are back in the [Security tab] highlight ASP.NET Machine Account (username/ASPNET) and put a check in the write box under the allow column

-now highlight  NETWORK SERVICE and put a check in the write box under the allow column

-click [ok]

-try your site.

I hope this helps.

MicroCrafters.tripod.com

Answer 41

Adding the NETWORK Service did the trick

 

Thanks!

 

Answer 42

Thanks from me too, iceb0ys.  Wish I had an H1B to give you.  This works great on XP Pro.

  Step 1 is the key step that makes Step 2 possible.  The only thing I would add is that the "ASPNET account" shows up as "Internet Guest Account" on my system, and I only applied Modify permissions to the App_Data folder that actually contained the mdfs, etc.  That seemed to be enough, and maybe a little safer.

" Step 1:
Open My Computer from the desktop, and from the Tools menu select Folder Options.
Click on the View tab, and scroll to the end of the Advanced Settings box.
Near the bottom, you will find an entry named "Use simple file sharing (recommended)".
Uncheck this box, and click the OK button.
Now when you right-click on a file or folder and select Properties, you will see the Security tab.

step 2:
On a computer running Windows XP Professional, you just need to grant the ASPNET account permissions.
Use Windows Explorer to browse to the root folder of your Personal Website.
Right click on the folder and choose properties. Then click on the Security Tab.
Click the Add button, the Advanced button, and then the Find Now button. Then click on the ASPNET item in the list and click Ok, and Ok again.
Then click the Allow Modify checkbox and click Ok."

Answer 43

I simply gave the ASPNET account full control of the root folder of my website (which isn't in c:\inetpub\wwwroot).

Answer 44

A small question: Can you detail the steps invloved in giving the user ASPNET full control please

Really need help with this. Thanks

Answer 45

Hello. I have the same issue but I am new on this and I don’t understand it properly. Could you explain more detailed what did you made to solve the issue? I mean Did you change the properties just on “App-Data” folder? Or directly on  “ASPNETDB.MDF file, it was using the file explorer or IIS. I made changes on both and is working on my local server and also all the machines in the local net. But I install it on a production server out of my office. But still no working. Of course, I don’t have access to the outside server. Do you have any additional suggestion?.

 

 

Server Error in '/' Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

Same error appeared on me local network. before appeared the below but no more. just still appearing the first error on the external server and I think is related to the same issue  

 

Error de servidor en la aplicación '/'.

---

Failed to update database "F:\VIRTUAL WEB\APP_DATA\ASPNETDB.MDF" because the database is read-only.

Descripción: Excepción no controlada al ejecutar la solicitud Web actual. Revise el seguimiento de la pila para obtener más información acerca del error y dónde se originó en el código.

Detalles de la excepción: System.Data.SqlClient.SqlException: Failed to update database "F:\VIRTUAL WEB\APP_DATA\ASPNETDB.MDF" because the database is read-only.

Error de código fuente:

Se ha generado una excepción no controlada durante la ejecución de la solicitud Web actual. La información sobre el origen y la ubicación de la excepción pueden identificarse utilizando la excepción del seguimiento de la pila siguiente.

Seguimiento de la pila:

[SqlException (0x80131904): Failed to update database "F:\VIRTUAL WEB\APP_DATA\ASPNETDB.MDF" because the database is read-only.]    System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +857530    System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735142    System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188    System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838    System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +149    System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +886    System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +132    System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) +415    System.Data.SqlClient.SqlCommand.ExecuteNonQuery() +135    System.Web.Security.SqlMembershipProvider.CreateUser(String username, String password, String email, String passwordQuestion, String passwordAnswer, Boolean isApproved, Object providerUserKey, MembershipCreateStatus& status) +3612    System.Web.UI.WebControls.CreateUserWizard.AttemptCreateUser() +305    System.Web.UI.WebControls.CreateUserWizard.OnNextButtonClick(WizardNavigationEventArgs e) +105    System.Web.UI.WebControls.Wizard.OnBubbleEvent(Object source, EventArgs e) +453    System.Web.UI.WebControls.CreateUserWizard.OnBubbleEvent(Object source, EventArgs e) +149    System.Web.UI.WebControls.WizardChildTable.OnBubbleEvent(Object source, EventArgs args) +17    System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35    System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115    System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +163    System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7    System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11    System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102

 

 

Thanks in advance and best regards

 

 

Answer 46

Turn Off the Firewall.

Answer 47

Your answer to this was quite helpful.  My process was similar but I didn't have to detach the DB or delete the site.  Following some of the other posts concerning this issue, I changed the security of wwwroot to allow ASPNET user full control and added the ASPNET user to my application directory under the wwwroot.  Then I restarted IIS and everything worked.  I'm using XP SP2, IIS 5.1, SQLExpress 2005, and VWD 2005.  Hope this helps someone else as well.

Answer 48

I had been fighting this problem for ages, this worked perfectly.

 

I now face the default setting do not allow remote connections error but i think i can manage to change that.

 

The ASP.NET read only erro on publishing a sql database seems a common problem, with this being one of the only correct answers i have found

 

Thank you.

Answer 49

This worked 1st time,

Im learning expression web and the db was an assignment

the beginning expression web book has problems,

I think i will take an sql class next.

thanks

brp

Answer 50

I got the same error but because I detached the DB then overwritten the data files with new files.  The solution is to give the users below full right on the datafile and log file

 

 NETWORK SERVICE 

SQLServer2005MSSQLUser$<server name>$<instance name>

Answer 51

It's permission problem !!! Add asp.net user( ASPNETDB.MDF->Properties>Security->Add.... and add ASP.NET user client)

Answer 52

thank you so much.  I followed your 3 steps and it worked.

Answer 53

Hello, I'm lost.

I'm using Windows Vista with Visual Studio 2008 and I haven't got the user ASPNET.

How can I do it?

Thanks

Answer 54

Hi Cecius,

Guve Network Service permissions to your webfolder, that should work.