After Publish from VS2005 to IIS 5.1, SQLExpress doesnt work

I created an app in vs2005 and everything works perfectly in the development environment. I've published the site to my local IIS, but when I try to log in, it doesn't allow me. I'm assuming that it has something to do with the db not working correctly. Unfortunately I don't know how to debug to see where the problem is coming from now that it's running on my 'live' IIS. Does anyone have any ideas on what could be the problem. I have some settings in the web.config, which have been working perfectly.

<appSettings>
<addkey="UserName"value=""/>
<addkey="Password"value=""/>
<addkey="Server"value="xxxxxx\sqlexpress"/>
<addkey="Database"value="xxxxx_xxx_users"/>
<addkey="UseTrusted"value="True"/>
</appSettings>

I had a local guy at the office here saying that the ASP.NET user needs to be granted access to sqlexpress2005, but I wasn't sure on how to do that.

So all in all, My app works in Visual Studio 2005, and not in IIS. There are no errors when loading various pages. They all load correctly and without error. It seems that it's just when I try to do anything with the DB.

Thanks for the help. I appreciate it!

Have you modified you connection string to point to you IIS database? Are you sure that your provider support SQL express some of them provide space on Full SQL server.

Have you moved your database together with page to new server? If yes it is possible that because ASPNET user database is encrypted with machine specific key your IIS server key will not and you have no access to database.

And it is also true that if you use windows security your ASP account have to have login associated with it on SQL Server.

I hope that it helps a little,

Thanks

|||

Hey thanks for the reply.

Have you modified you connection string to point to you IIS database?
I have not modified the connection string because it is using the same database being used, thus why I don't know why this isn't working.

Are you sure that your provider support SQL express some of them provide space on Full SQL server.?
This is just on my local machine here, and yes, I'm using sqlexpress

Have you moved your database together with page to new server?
Yes, we tried it on our webserver, and the same thing happened

I am using an ASPNET 2.0 login control, but it creates an instance of my user class which authenticates the user directly from my sqlexpress db, which is used in the whole application, and then authenticates based on username and password.

I am using windows authentication.

Ok after doing a little authentication taking out, it turns out that the only thing not working is the login. All the other db queries work perfectly. It's just the login that is failing. I took a look at one of the tutorial videos and noticed that scott went into the ASP.NET Configuration page and created users and member groups there. Does that need to happen? It creates it's own database for users that's pretty locked down. I want to be able to use my own database I created.

Any ideas?

|||

Are all tables working one and login in the same databse? Does you user have rights to connect to them and select from them? does it has rights to excute your stored procedures connected to login?

Thanks

|||It turns out it was the aspnet user access in sql express. I gave the user permission and all is a go now. Thanks for the help!

Advise on Licensing SSRS on NLB IIS farm

Hi All,
I have the following question, in my organization we employ a policy of
splitting out our enterprise infrastructure, IIS separated from SQL Server
etc.
We currently have a number of SQL Server 2000 and 2005 clusters and also two
NLB IIS farms (each with 4 nodes).
If I install SQL Server Reporting Services on the NLB farms (databases on
two of the SQL Server Clusters) to make this product available to to people
here then am I right in assuming that firstly I will need Enterprise Edition
of Reporting Services 2005 installed on my NLB's as this is the only edition
capable of scale out SSRS deployment.
Secondly and more importantly will I also need in addition a separate SQL
Server 2005 Enterprise Edition license on each of the nodes involved in the
NLB's (8 nodes therefore 8 licenses)?
If this is the case then I am really concerned at this supposed low cost
reporting solution from Microsoft, as I would then for this scenario need
minimum 10 Enterprise Edition SQL Server 2005 licenses (8 for the NLB nodes
and 1 for each failover cluster (Active/Passive) )
This is no longer a cheap solution for our reporting needs.
Thanks for your help.
Kind Regards,
DesYou have the licensing correct. Enterprise is the only one which supports a
web farm and any server that has Reporting Services installed must have a
server license. How expensive it is for you depends on how you license (CAL
or per processor).
If you price Crystal in such a configuration you will find that it is even
more expensive.
Unless you have one heck of a lot of reports and users then I sincerely
doubt that you need such a configuration.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Des FitzGerald" <dfitz@.dr-sql.com> wrote in message
news:C3A94D89.73DF%dfitz@.dr-sql.com...
> Hi All,
> I have the following question, in my organization we employ a policy of
> splitting out our enterprise infrastructure, IIS separated from SQL Server
> etc.
> We currently have a number of SQL Server 2000 and 2005 clusters and also
> two
> NLB IIS farms (each with 4 nodes).
> If I install SQL Server Reporting Services on the NLB farms (databases on
> two of the SQL Server Clusters) to make this product available to to
> people
> here then am I right in assuming that firstly I will need Enterprise
> Edition
> of Reporting Services 2005 installed on my NLB's as this is the only
> edition
> capable of scale out SSRS deployment.
> Secondly and more importantly will I also need in addition a separate SQL
> Server 2005 Enterprise Edition license on each of the nodes involved in
> the
> NLB's (8 nodes therefore 8 licenses)?
> If this is the case then I am really concerned at this supposed low cost
> reporting solution from Microsoft, as I would then for this scenario need
> minimum 10 Enterprise Edition SQL Server 2005 licenses (8 for the NLB
> nodes
> and 1 for each failover cluster (Active/Passive) )
> This is no longer a cheap solution for our reporting needs.
> Thanks for your help.
> Kind Regards,
> Des
>|||Hi Bruce,
Its not a case of a lot of users or reports - it is a case of a fault
tolerance / disaster recovery solution, we have network load balanced web
farms to facilitate this setup.
The 2 web NLB farms are for integration and production, these need to be
there for our environment, the decision was taken as we are a multi site
organization to have 2 nodes of each NLB in each of our main offices and
then of these 2 nodes each one is in a separate server room, thus 4 nodes =2 per site and of the 2 per site each is separated per server room, disaster
recovery and fault tolerance taken care of.
We will need per processor licensing as intranet reports are made and CAL
will be too expensive.
This is an extremely expensive solution in this case - I have no idea of the
cost of Crystal reports and this is no place to get into this argument as it
does not help.
I just think that Microsoft should de-couple SSRS from SQL Server and make
it Microsoft Reporting Server or something like this with its own licensing
model, the databases can still be stuck to SQL Server but this would make it
more transparent and quite possibly cheaper as Enterprise SQL Server 2005
Processor licenses are not cheap and if the database and reporting server
sides are split as recommended my MS then this does lead to an expensive
solution when each of the IIS NLB nodes need separate licenses.
Thanks for the answer though.
Cheers,
Des
On 08/01/2008 18:00, in article OyC$EghUIHA.280@.TK2MSFTNGP03.phx.gbl, "Bruce
L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote:
> You have the licensing correct. Enterprise is the only one which supports a
> web farm and any server that has Reporting Services installed must have a
> server license. How expensive it is for you depends on how you license (CAL
> or per processor).
> If you price Crystal in such a configuration you will find that it is even
> more expensive.
> Unless you have one heck of a lot of reports and users then I sincerely
> doubt that you need such a configuration.
>|||Hi Bruce,
A final question for you, if I have SSRS 2000 and SSRS 2005 installed on
these NLBs (8 nodes total as mentioned) do I therefore also need separate
SQL Server 2000 and SQL Server 2005 Enterprise Edition CPU licenses for
these nodes?
So a total of 16 Enterprise Edition CPU licenses for the Reporting Services
setup?
Cheers,
Des
On 08/01/2008 18:00, in article OyC$EghUIHA.280@.TK2MSFTNGP03.phx.gbl, "Bruce
L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote:
> You have the licensing correct. Enterprise is the only one which supports a
> web farm and any server that has Reporting Services installed must have a
> server license. How expensive it is for you depends on how you license (CAL
> or per processor).
> If you price Crystal in such a configuration you will find that it is even
> more expensive.
> Unless you have one heck of a lot of reports and users then I sincerely
> doubt that you need such a configuration.
>|||I'm confused, you want to have both RS 2000 and RS 2005 installed on each
server?
Why would you do that? RS 2000 reports run fine in RS 2005. And they run
much faster.
In case you do want to do this, I believe a SQL 2005 license allows running
both 200 and 2005 so you would not need two licenses. However, I would check
with whoever you buy licenses from.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Des FitzGerald" <dfitz@.dr-sql.com> wrote in message
news:C3AA8E77.7B74%dfitz@.dr-sql.com...
> Hi Bruce,
> A final question for you, if I have SSRS 2000 and SSRS 2005 installed on
> these NLBs (8 nodes total as mentioned) do I therefore also need separate
> SQL Server 2000 and SQL Server 2005 Enterprise Edition CPU licenses for
> these nodes?
> So a total of 16 Enterprise Edition CPU licenses for the Reporting
> Services
> setup?
> Cheers,
> Des
>
> On 08/01/2008 18:00, in article OyC$EghUIHA.280@.TK2MSFTNGP03.phx.gbl,
> "Bruce
> L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote:
>> You have the licensing correct. Enterprise is the only one which supports
>> a
>> web farm and any server that has Reporting Services installed must have a
>> server license. How expensive it is for you depends on how you license
>> (CAL
>> or per processor).
>> If you price Crystal in such a configuration you will find that it is
>> even
>> more expensive.
>> Unless you have one heck of a lot of reports and users then I sincerely
>> doubt that you need such a configuration.
>