I am really at my wits end. I have been trying for days to find an answer to this, and have tried so many things.
I simply keep getting the error that localhost (Phantomlap in my case)/ASPNET cannot access the DB. This is a synopsis:.
Tools I am using:
V Studio 2005, IIS 5.1, XP Pro SP 2, SqlServer 2005 (using the EXPRESS server).
Configurations:
web.config:
<connectionStrings>
<remove name="localsqlserver"/>
<add name="localsqlserver" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\aspnetdb.mdf;Integrated Security=true;User Instance=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
Website is stored at:
C:Inetpubwwwroot
(within that I have an App_Data folder with following permission):
(I allowed, via security, the ASPNET account read/write access)
SQL Server status:
Phantomlap/aspnet user is added
Phantomlap/aspnet security as just about everything checkmarked
Please note--I am using SQLServer Express--I am not entirely sure I added the ASPNET account correctly--is there a tutorial on how to do this?
Please help,
Kind Regards
The real issue here is that User Instances are just not designed for web applications. Are you running this as a file based web site from within VWD (i.e. F5) or is this an IIS based site in production. If you're in production, you should likely start by changing to a standard connection with your database attached to the parent instance of SQL rather than trying to use the dynamic attach behavior of User Instances.
I've never seen anyone from the VWD team provide good instructions on how to work with applications once a database has been added.
Mike
|||Thats you and me both, how on earth can they let something like this go so long without a fix. Look I pay good knows how much for an IDE, test the thing within Visual Studio great, up load to the server and connect via IIS and then have to to more ruddy fiddles than a Linux command line fan. My user\ASPNET is registered with correct permissions on SQL Server 2005 Ok, the attached database should work straight off through IIS. Someone needs to get their backside kicked for letting this half baked problem drag on so long, asp boards are awash with people stuck on this.|||What error it exactly shows?|||HI,
Refer below KBs for the workaround of your problem
http://support.microsoft.com/kb/316989/en-us
http://support.microsoft.com/kb/824308/en-us
http://support.microsoft.com/kb/301240/en-us
http://support.microsoft.com/kb/308157/en-us
HTH
Hemantgiri S. Goswami
