Re: SQL Express non-functional outside of VS 2005
- From: Mike P <MikeP@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Jan 2006 07:09:03 -0800
Roger,
Thank you for responding so quickly. It will take me time to digest your
Nov article. Like I mentioned, I have a lot of new things to learn.
As additional info, the example web site I am working with is the VS-created
Personal Web Site. It runs fine inside of VS. When using IIS as the server,
it serves up properly but won't allow a connection. I will have to dig
through all the documentation to learn how it all works and find my
mistakes... a painful trial for someone who has, by necessity, stuck to MS
Access since 1995 (sys admins at work would not allow anything else).
--
Mike
Engineer (Part-time, brute-force, novice, just-to-solve-a-problem coder)
"Roger Wolter[MSFT]" wrote:
> Not sure exactly what you mean by attaching from IIS. Do you have an
> ASP.Net page you're using?
>
> By default, VS creates connections with the "User Instance" option. This
> means a private SQL Server instance is created just for your user and the
> database is attached to this instance. If your ASP.Net application also
> uses a user instance connection string, it will create an different SQL
> Instance running as ASPUSER. If VS has the database open when you try to
> run your ASP page, the ASPUSER instance will find that the file is already
> in use by you and thus the open will fail. VS has a lot of logic built in
> so that if you hit F5 to run your application, VS will close the file so
> ASPUSER can open it. If you don't do this and attempt to run your
> application from the browser while VS still has the database open, it will
> fail.
>
> There's a more complete explanation of how this works here:
>
> http://msdn.microsoft.com/sql/express/default.aspx?pull=/library/en-us/dnsse/html/sqlexpuserinst.asp
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> "Mike P" <MikeP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:54DAC164-5CD5-407B-895E-19A8BE8D899B@xxxxxxxxxxxxxxxx
> > Folks,
> >
> > Just installed VS 2005 -- HUGE improvement over 6.0 (now I have to learn
> > all
> > the new languages... moving from desktop to web apps to run distributed
> > projects, workflows, and dashboards at work).
> >
> > SQL Express runs just fine inside VS. When I try to run from IIS I get no
> > connection. Services tab shows SQL Express up and running. Approaching
> > it
> > from MS Access as an ADP finds no SQL server to connect to, as well.
> >
> > On-line help assumes I have more of a clue than I do. This is a 20-second
> > fix for you gurus but a 3-week part-time journey thru pain and agony for
> > me.
> >
> > Help, please.
> > --
> > Mike
> > Engineer (part-time-, brute-force-, novice-, just-to-solve-a-problem-
> > coder)
>
>
>
.
- References:
- Re: SQL Express non-functional outside of VS 2005
- From: Roger Wolter[MSFT]
- Re: SQL Express non-functional outside of VS 2005
- Prev by Date: Re: Setting Up SQL Server 2005 to work with MS Access
- Next by Date: Re: 64-bit SQL and memory
- Previous by thread: Re: SQL Express non-functional outside of VS 2005
- Next by thread: Re: SQL 2005 Express Edition
- Index(es):
Relevant Pages
|
|
