Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 31, 2005 03:49 PM by Rafa
May 27, 2005 03:10 PM|LINK
Copying from XP to Server 2003 was originally the case, so I just installed VWD on the server, deleted the original PWSSK, then created the new one and get the DATABASE IS READ ONLY error. I also checked in Security settings in IIS, Windows Authentication
is chosen. Also, in the file structure, the .mdf files in the APP_DATA folder have 'WRITE' and 'SPECIAL PERMISSIONS' checked for the internet guest account.
Any other suggestions?
May 27, 2005 06:37 PM|LINK
May 27, 2005 07:44 PM|LINK
May 27, 2005 08:38 PM|LINK
May 27, 2005 08:46 PM|LINK
in windows 2003 sql needs the "network service" account, in windows xp I believe it uses the "aspnet" account. The thing is though, is that once sql 2005 gets these permissions it becomes a pain to get them back... I found the best way is to create the app_data
folder before copying to 2003 and setting the permissions beforehand so it inherits them correctly
May 31, 2005 03:38 PM|LINK
I removed the PWSSK that I created in XP and created a new one (in the same folder) with Visual Web Dev on the server itself. Would that still cause the problems in SQL Express?
May 31, 2005 03:49 PM|LINK