The web server is very quick for all other sites and pages, but for some
reason, bringing up the reports page is a dog. Can take anywere from 10 secs
to a minute.
Anyone else see this problem... Guessing it's a conf or install issue, but I
have no clue.
All comments appreciated.Check your ASP.NET/Application Restarts counter. some antivirus software
monitors config files. If that's it then exclude those files.
--
Douglas McDowell
douglas@.nospam.solidqualitylearning.com
"Rick Matthys" <RickMatthys@.discussions.microsoft.com> wrote in message
news:E91C1E04-A3AA-4D0A-888E-26CA79A2AD31@.microsoft.com...
> The web server is very quick for all other sites and pages, but for some
> reason, bringing up the reports page is a dog. Can take anywere from 10
> secs
> to a minute.
> Anyone else see this problem... Guessing it's a conf or install issue, but
> I
> have no clue.
> All comments appreciated.
Showing posts with label web. Show all posts
Showing posts with label web. Show all posts
Monday, March 19, 2012
.sql control string
My development environment includes Visual Web Developer, SQL Server 2005 Express and SQL Server Management Studio Express. I have a .sql control string that creates a database. The control string is in my App_Data folder within my web site. When I use SQL Server Managment Studio Express to run the .sql control string and create the tables etc. it does it in my SQLEXPRESS folder and not in the web.
How do I run the .sql file so it will create the database in my App_Data folder within the web site?
Thanks,
Kyleq
Hi Kyleq,
Please make sure that your SQL Server Management Studio Express has connected to the correct database.
A simple .mdf file cannot be working properly, we must
1. Attach it to a SQL Server instance.
2. Connection the SQL Server Management Studio Express to that instance and to that database.
3. Run the .sql scripts.
4. Detach the database.
Please read the following for more information:
http://msdn2.microsoft.com/en-us/library/ms228037.aspx
HTH. If this does not answer your question, please feel free to mark the post as Not Answered and reply. Thank you!
.sql attachments will not open
Hi,
I have developed a web app where documents may be uploaded onto a server, and then opened of downloaded from the server by the users. Every type of file can be opened and downloaded apart from .sql. The main types of files that are uploaded are .txt, .dox, .pdf, .xls and .psd (photoshop), they all work apart from .sql
just wondering does somthing different have to be done for .sql files?
I have developed a web app where documents may be uploaded onto a server, and then opened of downloaded from the server by the users. Every type of file can be opened and downloaded apart from .sql. The main types of files that are uploaded are .txt, .dox, .pdf, .xls and .psd (photoshop), they all work apart from .sql
just wondering does somthing different have to be done for .sql files?
the uploading is working, it is not that the file doesnt exist on the server
Regards,
Frank
Its depends upon the client folder/file settings. You can't control from the Server.
If you need more information you can post this Q on ASP.NET forum.
Sunday, March 11, 2012
.NET, SQL, and firewall
We're having a problem with a local intranet site and SQL. The web server
sits behind a firewall. There is an instance of SQL on it with one, primary
database with users, permissions, and roles types of data. The main SQL
server sits on the network domain. Each SQL instance links to the other.
The PROBLEM is that when traffic is heavy on the site, the web server SQL
will sometimes "Lock up", failing to return queries. Restarting the MSSQL
service on the web server always corrects the problem, but we shouldn't be
having it. Anyone recognize the symptoms?
--
Thanks,
CGWUsing Task Manager check what process is taking all the CPU.
I've had a problem with a client where their firewall could only handle say
2Mbits/second which is quite small considering it was an intranet
application with lots of clients, so the bottleneck looked like SQL not
handling the load, but it was actually the firewall.
If you need to go through a firewall to go from the web box through to the
SQL box check what bandwidth it can handle and then check how much the
network between them is utilised.
Tony.
--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
> We're having a problem with a local intranet site and SQL. The web server
> sits behind a firewall. There is an instance of SQL on it with one,
> primary
> database with users, permissions, and roles types of data. The main SQL
> server sits on the network domain. Each SQL instance links to the other.
> The PROBLEM is that when traffic is heavy on the site, the web server SQL
> will sometimes "Lock up", failing to return queries. Restarting the MSSQL
> service on the web server always corrects the problem, but we shouldn't be
> having it. Anyone recognize the symptoms?
> --
> Thanks,
> CGW|||Amazing. Our dept head guessed it could be the firewall, but I had my doubts
since the instance of SQL we seemed to be having trouble with sits on the
same machine (and same side of the firewall) as the .NET application. <Bad
form for the boss to be right, but then he often is>. Thanks for the help.
We'll check it out.
--
Thanks,
CGW
"Tony Rogerson" wrote:
> Using Task Manager check what process is taking all the CPU.
> I've had a problem with a client where their firewall could only handle say
> 2Mbits/second which is quite small considering it was an intranet
> application with lots of clients, so the bottleneck looked like SQL not
> handling the load, but it was actually the firewall.
> If you need to go through a firewall to go from the web box through to the
> SQL box check what bandwidth it can handle and then check how much the
> network between them is utilised.
> Tony.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "CGW" <CGW@.discussions.microsoft.com> wrote in message
> news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
> > We're having a problem with a local intranet site and SQL. The web server
> > sits behind a firewall. There is an instance of SQL on it with one,
> > primary
> > database with users, permissions, and roles types of data. The main SQL
> > server sits on the network domain. Each SQL instance links to the other.
> >
> > The PROBLEM is that when traffic is heavy on the site, the web server SQL
> > will sometimes "Lock up", failing to return queries. Restarting the MSSQL
> > service on the web server always corrects the problem, but we shouldn't be
> > having it. Anyone recognize the symptoms?
> > --
> > Thanks,
> >
> > CGW
>
>|||Your welcome.
I think it's one of those ticking time bombs - I bet there are a lot of
installations that have the same problem but they don't know (yet anyway).
Its quite easy to miss.
--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:50E86CDF-E776-4A04-B8AF-DF39B7B2A886@.microsoft.com...
> Amazing. Our dept head guessed it could be the firewall, but I had my
> doubts
> since the instance of SQL we seemed to be having trouble with sits on the
> same machine (and same side of the firewall) as the .NET application. <Bad
> form for the boss to be right, but then he often is>. Thanks for the help.
> We'll check it out.
> --
> Thanks,
> CGW
>
> "Tony Rogerson" wrote:
>> Using Task Manager check what process is taking all the CPU.
>> I've had a problem with a client where their firewall could only handle
>> say
>> 2Mbits/second which is quite small considering it was an intranet
>> application with lots of clients, so the bottleneck looked like SQL not
>> handling the load, but it was actually the firewall.
>> If you need to go through a firewall to go from the web box through to
>> the
>> SQL box check what bandwidth it can handle and then check how much the
>> network between them is utilised.
>> Tony.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlserverfaq.com - free video tutorials
>>
>> "CGW" <CGW@.discussions.microsoft.com> wrote in message
>> news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
>> > We're having a problem with a local intranet site and SQL. The web
>> > server
>> > sits behind a firewall. There is an instance of SQL on it with one,
>> > primary
>> > database with users, permissions, and roles types of data. The main SQL
>> > server sits on the network domain. Each SQL instance links to the
>> > other.
>> >
>> > The PROBLEM is that when traffic is heavy on the site, the web server
>> > SQL
>> > will sometimes "Lock up", failing to return queries. Restarting the
>> > MSSQL
>> > service on the web server always corrects the problem, but we shouldn't
>> > be
>> > having it. Anyone recognize the symptoms?
>> > --
>> > Thanks,
>> >
>> > CGW
>>
sits behind a firewall. There is an instance of SQL on it with one, primary
database with users, permissions, and roles types of data. The main SQL
server sits on the network domain. Each SQL instance links to the other.
The PROBLEM is that when traffic is heavy on the site, the web server SQL
will sometimes "Lock up", failing to return queries. Restarting the MSSQL
service on the web server always corrects the problem, but we shouldn't be
having it. Anyone recognize the symptoms?
--
Thanks,
CGWUsing Task Manager check what process is taking all the CPU.
I've had a problem with a client where their firewall could only handle say
2Mbits/second which is quite small considering it was an intranet
application with lots of clients, so the bottleneck looked like SQL not
handling the load, but it was actually the firewall.
If you need to go through a firewall to go from the web box through to the
SQL box check what bandwidth it can handle and then check how much the
network between them is utilised.
Tony.
--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
> We're having a problem with a local intranet site and SQL. The web server
> sits behind a firewall. There is an instance of SQL on it with one,
> primary
> database with users, permissions, and roles types of data. The main SQL
> server sits on the network domain. Each SQL instance links to the other.
> The PROBLEM is that when traffic is heavy on the site, the web server SQL
> will sometimes "Lock up", failing to return queries. Restarting the MSSQL
> service on the web server always corrects the problem, but we shouldn't be
> having it. Anyone recognize the symptoms?
> --
> Thanks,
> CGW|||Amazing. Our dept head guessed it could be the firewall, but I had my doubts
since the instance of SQL we seemed to be having trouble with sits on the
same machine (and same side of the firewall) as the .NET application. <Bad
form for the boss to be right, but then he often is>. Thanks for the help.
We'll check it out.
--
Thanks,
CGW
"Tony Rogerson" wrote:
> Using Task Manager check what process is taking all the CPU.
> I've had a problem with a client where their firewall could only handle say
> 2Mbits/second which is quite small considering it was an intranet
> application with lots of clients, so the bottleneck looked like SQL not
> handling the load, but it was actually the firewall.
> If you need to go through a firewall to go from the web box through to the
> SQL box check what bandwidth it can handle and then check how much the
> network between them is utilised.
> Tony.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "CGW" <CGW@.discussions.microsoft.com> wrote in message
> news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
> > We're having a problem with a local intranet site and SQL. The web server
> > sits behind a firewall. There is an instance of SQL on it with one,
> > primary
> > database with users, permissions, and roles types of data. The main SQL
> > server sits on the network domain. Each SQL instance links to the other.
> >
> > The PROBLEM is that when traffic is heavy on the site, the web server SQL
> > will sometimes "Lock up", failing to return queries. Restarting the MSSQL
> > service on the web server always corrects the problem, but we shouldn't be
> > having it. Anyone recognize the symptoms?
> > --
> > Thanks,
> >
> > CGW
>
>|||Your welcome.
I think it's one of those ticking time bombs - I bet there are a lot of
installations that have the same problem but they don't know (yet anyway).
Its quite easy to miss.
--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:50E86CDF-E776-4A04-B8AF-DF39B7B2A886@.microsoft.com...
> Amazing. Our dept head guessed it could be the firewall, but I had my
> doubts
> since the instance of SQL we seemed to be having trouble with sits on the
> same machine (and same side of the firewall) as the .NET application. <Bad
> form for the boss to be right, but then he often is>. Thanks for the help.
> We'll check it out.
> --
> Thanks,
> CGW
>
> "Tony Rogerson" wrote:
>> Using Task Manager check what process is taking all the CPU.
>> I've had a problem with a client where their firewall could only handle
>> say
>> 2Mbits/second which is quite small considering it was an intranet
>> application with lots of clients, so the bottleneck looked like SQL not
>> handling the load, but it was actually the firewall.
>> If you need to go through a firewall to go from the web box through to
>> the
>> SQL box check what bandwidth it can handle and then check how much the
>> network between them is utilised.
>> Tony.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlserverfaq.com - free video tutorials
>>
>> "CGW" <CGW@.discussions.microsoft.com> wrote in message
>> news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
>> > We're having a problem with a local intranet site and SQL. The web
>> > server
>> > sits behind a firewall. There is an instance of SQL on it with one,
>> > primary
>> > database with users, permissions, and roles types of data. The main SQL
>> > server sits on the network domain. Each SQL instance links to the
>> > other.
>> >
>> > The PROBLEM is that when traffic is heavy on the site, the web server
>> > SQL
>> > will sometimes "Lock up", failing to return queries. Restarting the
>> > MSSQL
>> > service on the web server always corrects the problem, but we shouldn't
>> > be
>> > having it. Anyone recognize the symptoms?
>> > --
>> > Thanks,
>> >
>> > CGW
>>
.NET, SQL, and firewall
We're having a problem with a local intranet site and SQL. The web server
sits behind a firewall. There is an instance of SQL on it with one, primary
database with users, permissions, and roles types of data. The main SQL
server sits on the network domain. Each SQL instance links to the other.
The PROBLEM is that when traffic is heavy on the site, the web server SQL
will sometimes "Lock up", failing to return queries. Restarting the MSSQL
service on the web server always corrects the problem, but we shouldn't be
having it. Anyone recognize the symptoms?
--
Thanks,
CGWUsing Task Manager check what process is taking all the CPU.
I've had a problem with a client where their firewall could only handle say
2Mbits/second which is quite small considering it was an intranet
application with lots of clients, so the bottleneck looked like SQL not
handling the load, but it was actually the firewall.
If you need to go through a firewall to go from the web box through to the
SQL box check what bandwidth it can handle and then check how much the
network between them is utilised.
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
> We're having a problem with a local intranet site and SQL. The web server
> sits behind a firewall. There is an instance of SQL on it with one,
> primary
> database with users, permissions, and roles types of data. The main SQL
> server sits on the network domain. Each SQL instance links to the other.
> The PROBLEM is that when traffic is heavy on the site, the web server SQL
> will sometimes "Lock up", failing to return queries. Restarting the MSSQL
> service on the web server always corrects the problem, but we shouldn't be
> having it. Anyone recognize the symptoms?
> --
> Thanks,
> CGW|||Amazing. Our dept head guessed it could be the firewall, but I had my doubts
since the instance of SQL we seemed to be having trouble with sits on the
same machine (and same side of the firewall) as the .NET application. <Bad
form for the boss to be right, but then he often is>. Thanks for the help.
We'll check it out.
--
Thanks,
CGW
"Tony Rogerson" wrote:
> Using Task Manager check what process is taking all the CPU.
> I've had a problem with a client where their firewall could only handle sa
y
> 2Mbits/second which is quite small considering it was an intranet
> application with lots of clients, so the bottleneck looked like SQL not
> handling the load, but it was actually the firewall.
> If you need to go through a firewall to go from the web box through to the
> SQL box check what bandwidth it can handle and then check how much the
> network between them is utilised.
> Tony.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "CGW" <CGW@.discussions.microsoft.com> wrote in message
> news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
>
>|||Your welcome.
I think it's one of those ticking time bombs - I bet there are a lot of
installations that have the same problem but they don't know (yet anyway).
Its quite easy to miss.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:50E86CDF-E776-4A04-B8AF-DF39B7B2A886@.microsoft.com...[vbcol=seagreen]
> Amazing. Our dept head guessed it could be the firewall, but I had my
> doubts
> since the instance of SQL we seemed to be having trouble with sits on the
> same machine (and same side of the firewall) as the .NET application. <Bad
> form for the boss to be right, but then he often is>. Thanks for the help.
> We'll check it out.
> --
> Thanks,
> CGW
>
> "Tony Rogerson" wrote:
>
sits behind a firewall. There is an instance of SQL on it with one, primary
database with users, permissions, and roles types of data. The main SQL
server sits on the network domain. Each SQL instance links to the other.
The PROBLEM is that when traffic is heavy on the site, the web server SQL
will sometimes "Lock up", failing to return queries. Restarting the MSSQL
service on the web server always corrects the problem, but we shouldn't be
having it. Anyone recognize the symptoms?
--
Thanks,
CGWUsing Task Manager check what process is taking all the CPU.
I've had a problem with a client where their firewall could only handle say
2Mbits/second which is quite small considering it was an intranet
application with lots of clients, so the bottleneck looked like SQL not
handling the load, but it was actually the firewall.
If you need to go through a firewall to go from the web box through to the
SQL box check what bandwidth it can handle and then check how much the
network between them is utilised.
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
> We're having a problem with a local intranet site and SQL. The web server
> sits behind a firewall. There is an instance of SQL on it with one,
> primary
> database with users, permissions, and roles types of data. The main SQL
> server sits on the network domain. Each SQL instance links to the other.
> The PROBLEM is that when traffic is heavy on the site, the web server SQL
> will sometimes "Lock up", failing to return queries. Restarting the MSSQL
> service on the web server always corrects the problem, but we shouldn't be
> having it. Anyone recognize the symptoms?
> --
> Thanks,
> CGW|||Amazing. Our dept head guessed it could be the firewall, but I had my doubts
since the instance of SQL we seemed to be having trouble with sits on the
same machine (and same side of the firewall) as the .NET application. <Bad
form for the boss to be right, but then he often is>. Thanks for the help.
We'll check it out.
--
Thanks,
CGW
"Tony Rogerson" wrote:
> Using Task Manager check what process is taking all the CPU.
> I've had a problem with a client where their firewall could only handle sa
y
> 2Mbits/second which is quite small considering it was an intranet
> application with lots of clients, so the bottleneck looked like SQL not
> handling the load, but it was actually the firewall.
> If you need to go through a firewall to go from the web box through to the
> SQL box check what bandwidth it can handle and then check how much the
> network between them is utilised.
> Tony.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "CGW" <CGW@.discussions.microsoft.com> wrote in message
> news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
>
>|||Your welcome.
I think it's one of those ticking time bombs - I bet there are a lot of
installations that have the same problem but they don't know (yet anyway).
Its quite easy to miss.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:50E86CDF-E776-4A04-B8AF-DF39B7B2A886@.microsoft.com...[vbcol=seagreen]
> Amazing. Our dept head guessed it could be the firewall, but I had my
> doubts
> since the instance of SQL we seemed to be having trouble with sits on the
> same machine (and same side of the firewall) as the .NET application. <Bad
> form for the boss to be right, but then he often is>. Thanks for the help.
> We'll check it out.
> --
> Thanks,
> CGW
>
> "Tony Rogerson" wrote:
>
.NET, SQL, and firewall
We're having a problem with a local intranet site and SQL. The web server
sits behind a firewall. There is an instance of SQL on it with one, primary
database with users, permissions, and roles types of data. The main SQL
server sits on the network domain. Each SQL instance links to the other.
The PROBLEM is that when traffic is heavy on the site, the web server SQL
will sometimes "Lock up", failing to return queries. Restarting the MSSQL
service on the web server always corrects the problem, but we shouldn't be
having it. Anyone recognize the symptoms?
Thanks,
CGW
Using Task Manager check what process is taking all the CPU.
I've had a problem with a client where their firewall could only handle say
2Mbits/second which is quite small considering it was an intranet
application with lots of clients, so the bottleneck looked like SQL not
handling the load, but it was actually the firewall.
If you need to go through a firewall to go from the web box through to the
SQL box check what bandwidth it can handle and then check how much the
network between them is utilised.
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
> We're having a problem with a local intranet site and SQL. The web server
> sits behind a firewall. There is an instance of SQL on it with one,
> primary
> database with users, permissions, and roles types of data. The main SQL
> server sits on the network domain. Each SQL instance links to the other.
> The PROBLEM is that when traffic is heavy on the site, the web server SQL
> will sometimes "Lock up", failing to return queries. Restarting the MSSQL
> service on the web server always corrects the problem, but we shouldn't be
> having it. Anyone recognize the symptoms?
> --
> Thanks,
> CGW
|||Amazing. Our dept head guessed it could be the firewall, but I had my doubts
since the instance of SQL we seemed to be having trouble with sits on the
same machine (and same side of the firewall) as the .NET application. <Bad
form for the boss to be right, but then he often is>. Thanks for the help.
We'll check it out.
Thanks,
CGW
"Tony Rogerson" wrote:
> Using Task Manager check what process is taking all the CPU.
> I've had a problem with a client where their firewall could only handle say
> 2Mbits/second which is quite small considering it was an intranet
> application with lots of clients, so the bottleneck looked like SQL not
> handling the load, but it was actually the firewall.
> If you need to go through a firewall to go from the web box through to the
> SQL box check what bandwidth it can handle and then check how much the
> network between them is utilised.
> Tony.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "CGW" <CGW@.discussions.microsoft.com> wrote in message
> news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
>
>
|||Your welcome.
I think it's one of those ticking time bombs - I bet there are a lot of
installations that have the same problem but they don't know (yet anyway).
Its quite easy to miss.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:50E86CDF-E776-4A04-B8AF-DF39B7B2A886@.microsoft.com...[vbcol=seagreen]
> Amazing. Our dept head guessed it could be the firewall, but I had my
> doubts
> since the instance of SQL we seemed to be having trouble with sits on the
> same machine (and same side of the firewall) as the .NET application. <Bad
> form for the boss to be right, but then he often is>. Thanks for the help.
> We'll check it out.
> --
> Thanks,
> CGW
>
> "Tony Rogerson" wrote:
sits behind a firewall. There is an instance of SQL on it with one, primary
database with users, permissions, and roles types of data. The main SQL
server sits on the network domain. Each SQL instance links to the other.
The PROBLEM is that when traffic is heavy on the site, the web server SQL
will sometimes "Lock up", failing to return queries. Restarting the MSSQL
service on the web server always corrects the problem, but we shouldn't be
having it. Anyone recognize the symptoms?
Thanks,
CGW
Using Task Manager check what process is taking all the CPU.
I've had a problem with a client where their firewall could only handle say
2Mbits/second which is quite small considering it was an intranet
application with lots of clients, so the bottleneck looked like SQL not
handling the load, but it was actually the firewall.
If you need to go through a firewall to go from the web box through to the
SQL box check what bandwidth it can handle and then check how much the
network between them is utilised.
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
> We're having a problem with a local intranet site and SQL. The web server
> sits behind a firewall. There is an instance of SQL on it with one,
> primary
> database with users, permissions, and roles types of data. The main SQL
> server sits on the network domain. Each SQL instance links to the other.
> The PROBLEM is that when traffic is heavy on the site, the web server SQL
> will sometimes "Lock up", failing to return queries. Restarting the MSSQL
> service on the web server always corrects the problem, but we shouldn't be
> having it. Anyone recognize the symptoms?
> --
> Thanks,
> CGW
|||Amazing. Our dept head guessed it could be the firewall, but I had my doubts
since the instance of SQL we seemed to be having trouble with sits on the
same machine (and same side of the firewall) as the .NET application. <Bad
form for the boss to be right, but then he often is>. Thanks for the help.
We'll check it out.
Thanks,
CGW
"Tony Rogerson" wrote:
> Using Task Manager check what process is taking all the CPU.
> I've had a problem with a client where their firewall could only handle say
> 2Mbits/second which is quite small considering it was an intranet
> application with lots of clients, so the bottleneck looked like SQL not
> handling the load, but it was actually the firewall.
> If you need to go through a firewall to go from the web box through to the
> SQL box check what bandwidth it can handle and then check how much the
> network between them is utilised.
> Tony.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "CGW" <CGW@.discussions.microsoft.com> wrote in message
> news:6E9E95C2-765F-4772-B15C-82678F955255@.microsoft.com...
>
>
|||Your welcome.
I think it's one of those ticking time bombs - I bet there are a lot of
installations that have the same problem but they don't know (yet anyway).
Its quite easy to miss.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"CGW" <CGW@.discussions.microsoft.com> wrote in message
news:50E86CDF-E776-4A04-B8AF-DF39B7B2A886@.microsoft.com...[vbcol=seagreen]
> Amazing. Our dept head guessed it could be the firewall, but I had my
> doubts
> since the instance of SQL we seemed to be having trouble with sits on the
> same machine (and same side of the firewall) as the .NET application. <Bad
> form for the boss to be right, but then he often is>. Thanks for the help.
> We'll check it out.
> --
> Thanks,
> CGW
>
> "Tony Rogerson" wrote:
Thursday, March 8, 2012
.Net Framework 2.0 and Sql Server 2005
Does anyone know if there are any issues with .Net Framework 2.0 and SQL Server 2005?
Here is my problem .....
I have a web application running on a Windows 2003 Server SE with IIS 6.0. We recently migrated all of our databases to SQL Server 2005 and now we are getting an exception when retrieving data from the DB (Exception Below). We have switched our databases back to Sql Server 2000 and the problem does not occur. Any Help would be much appreciated.
-Ryan
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 7/3/2006
Time: 10:15:46 AM
User: N/A
Computer: WEBSERVER12
Description:
EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 system.data, P5 2.0.0.0, P6 4333aea2, P7 1946, P8 25, P9 system.invalidoperationexception, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 77 00 33 00 77 00 .w.3.w.
0018: 70 00 2e 00 65 00 78 00 p...e.x.
0020: 65 00 2c 00 20 00 36 00 e.,. .6.
0028: 2e 00 30 00 2e 00 33 00 ..0...3.
0030: 37 00 39 00 30 00 2e 00 7.9.0...
0038: 31 00 38 00 33 00 30 00 1.8.3.0.
0040: 2c 00 20 00 34 00 32 00 ,. .4.2.
0048: 34 00 33 00 35 00 62 00 4.3.5.b.
0050: 65 00 31 00 2c 00 20 00 e.1.,. .
0058: 73 00 79 00 73 00 74 00 s.y.s.t.
0060: 65 00 6d 00 2e 00 64 00 e.m...d.
0068: 61 00 74 00 61 00 2c 00 a.t.a.,.
0070: 20 00 32 00 2e 00 30 00 .2...0.
0078: 2e 00 30 00 2e 00 30 00 ..0...0.
0080: 2c 00 20 00 34 00 33 00 ,. .4.3.
0088: 33 00 33 00 61 00 65 00 3.3.a.e.
0090: 61 00 32 00 2c 00 20 00 a.2.,. .
0098: 31 00 39 00 34 00 36 00 1.9.4.6.
00a0: 2c 00 20 00 32 00 35 00 ,. .2.5.
00a8: 2c 00 20 00 73 00 79 00 ,. .s.y.
00b0: 73 00 74 00 65 00 6d 00 s.t.e.m.
00b8: 2e 00 69 00 6e 00 76 00 ..i.n.v.
00c0: 61 00 6c 00 69 00 64 00 a.l.i.d.
00c8: 6f 00 70 00 65 00 72 00 o.p.e.r.
00d0: 61 00 74 00 69 00 6f 00 a.t.i.o.
00d8: 6e 00 65 00 78 00 63 00 n.e.x.c.
00e0: 65 00 70 00 74 00 69 00 e.p.t.i.
00e8: 6f 00 6e 00 20 00 4e 00 o.n. .N.
00f0: 49 00 4c 00 0d 00 0a 00 I.L.....What is odd is that we have set up the same application on a diferent machine running Windows 2003 Server Web Edition with IIS 6.0 and it works fine. I have checked the versions of the framework and they are identical. The only difference between the two apps is that we are running SSL and connecting to the database through a VPN tunnel on the app that throws the exception.|||
I'm not aware of issues between SQL 2005 and .NET Framework 2.0 as the later is required to run the former.
You might try asking about this on the .NET Data Access forum on MSDN or trying over on the ASP.NET forums at www.asp.net, which is where all the ASP.NET folks hang out. (Obvious I suppose) Those two foums would be better equipt to help troubleshoot the server configuration and application code to track down the source of the error.
Mike
.Net Framework 2.0 and Reporting Services
When I installed 2.0 on the Web Server Reporting Services stopped working
properly. Is it possible to run them side by side. The server also has 1.1
running.
ThanksOn Fri, 25 Mar 2005 04:59:02 -0800, DJONES
<DJONES@.discussions.microsoft.com> wrote:
>When I installed 2.0 on the Web Server Reporting Services stopped working
>properly. Is it possible to run them side by side. The server also has 1.1
>running.
>Thanks
In theory,
When .NET Framework 2.0 reaches RTM it is supposed to be possible to
run them side by side without problem.
In practice, in the short term, there are assorted issues.
Why do you have .NET Framework 2.0 on your Web server? Which build?
Andrew Watt
MVP - InfoPath|||Thanks for the reply...
I'm working on the Proof of Concept phase of a project using 2.0. I wonder
if it would work with VS loaded on the Web Server instead...
"Andrew Watt [MVP - InfoPath]" wrote:
> On Fri, 25 Mar 2005 04:59:02 -0800, DJONES
> <DJONES@.discussions.microsoft.com> wrote:
> >When I installed 2.0 on the Web Server Reporting Services stopped working
> >properly. Is it possible to run them side by side. The server also has 1.1
> >running.
> >
> >Thanks
> In theory,
> When .NET Framework 2.0 reaches RTM it is supposed to be possible to
> run them side by side without problem.
> In practice, in the short term, there are assorted issues.
> Why do you have .NET Framework 2.0 on your Web server? Which build?
> Andrew Watt
> MVP - InfoPath
>|||I would suggest that the best thing is to ask your question (with a
more detailed description of your situation) on the Reporting Services
2005 NG. It's called microsoft.private.sqlserver2005.reportingsvcs.
Despite its name it's public.
You will see me there too. But I like to leave the pain of version
incompatibilities to others - so at this stage I only install one
version of SQL Server 2005 on a machine. Some of the others on that
group may have a solution to your situation though.
I would expect Visual Studio 2005 to cause you the same problem -
since it too will install .NET Framework 2.0.
Andrew Watt
MVP - InfoPath
On Fri, 25 Mar 2005 07:15:03 -0800, DJONES
<DJONES@.discussions.microsoft.com> wrote:
>Thanks for the reply...
>I'm working on the Proof of Concept phase of a project using 2.0. I wonder
>if it would work with VS loaded on the Web Server instead...
>"Andrew Watt [MVP - InfoPath]" wrote:
>> On Fri, 25 Mar 2005 04:59:02 -0800, DJONES
>> <DJONES@.discussions.microsoft.com> wrote:
>> >When I installed 2.0 on the Web Server Reporting Services stopped working
>> >properly. Is it possible to run them side by side. The server also has 1.1
>> >running.
>> >
>> >Thanks
>> In theory,
>> When .NET Framework 2.0 reaches RTM it is supposed to be possible to
>> run them side by side without problem.
>> In practice, in the short term, there are assorted issues.
>> Why do you have .NET Framework 2.0 on your Web server? Which build?
>> Andrew Watt
>> MVP - InfoPath|||We have similar situation - fix was two-fold, all done in IIS.
First, create an applicaton pool specifically for the two reporting
services applications, then set the properties of each application to
use that pool. Applications using different frameworks cannot "swim in
the same pool".
Second, ensure that the reporting services applications are configured
to use the 1.1 framework and not the 2.0 - the tedious way is to check
(and change, if needed) every mapping through the IIS properties pages.
The faster way is to use the command line applications to do this
configuration - but I think injudicious use of the command line can
remap all the applications at once - which could be what happened when
you installed the 2.0 framework.|||The command line tool aspnet_regiis has options to check the current script
mappings and to install certain versions for a particular virtual root only
rather than all virtual roots:
aspnet_regiis -lk
aspnet_regiis -s <path>
Make sure to run the aspnet_regiis.exe from the correct version directory
under \Windows\Microsoft.Net\Framework
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Parker" <psmith@.iquest.net> wrote in message
news:1112015101.606172.149480@.g14g2000cwa.googlegroups.com...
> We have similar situation - fix was two-fold, all done in IIS.
> First, create an applicaton pool specifically for the two reporting
> services applications, then set the properties of each application to
> use that pool. Applications using different frameworks cannot "swim in
> the same pool".
> Second, ensure that the reporting services applications are configured
> to use the 1.1 framework and not the 2.0 - the tedious way is to check
> (and change, if needed) every mapping through the IIS properties pages.
> The faster way is to use the command line applications to do this
> configuration - but I think injudicious use of the command line can
> remap all the applications at once - which could be what happened when
> you installed the 2.0 framework.
>
properly. Is it possible to run them side by side. The server also has 1.1
running.
ThanksOn Fri, 25 Mar 2005 04:59:02 -0800, DJONES
<DJONES@.discussions.microsoft.com> wrote:
>When I installed 2.0 on the Web Server Reporting Services stopped working
>properly. Is it possible to run them side by side. The server also has 1.1
>running.
>Thanks
In theory,
When .NET Framework 2.0 reaches RTM it is supposed to be possible to
run them side by side without problem.
In practice, in the short term, there are assorted issues.
Why do you have .NET Framework 2.0 on your Web server? Which build?
Andrew Watt
MVP - InfoPath|||Thanks for the reply...
I'm working on the Proof of Concept phase of a project using 2.0. I wonder
if it would work with VS loaded on the Web Server instead...
"Andrew Watt [MVP - InfoPath]" wrote:
> On Fri, 25 Mar 2005 04:59:02 -0800, DJONES
> <DJONES@.discussions.microsoft.com> wrote:
> >When I installed 2.0 on the Web Server Reporting Services stopped working
> >properly. Is it possible to run them side by side. The server also has 1.1
> >running.
> >
> >Thanks
> In theory,
> When .NET Framework 2.0 reaches RTM it is supposed to be possible to
> run them side by side without problem.
> In practice, in the short term, there are assorted issues.
> Why do you have .NET Framework 2.0 on your Web server? Which build?
> Andrew Watt
> MVP - InfoPath
>|||I would suggest that the best thing is to ask your question (with a
more detailed description of your situation) on the Reporting Services
2005 NG. It's called microsoft.private.sqlserver2005.reportingsvcs.
Despite its name it's public.
You will see me there too. But I like to leave the pain of version
incompatibilities to others - so at this stage I only install one
version of SQL Server 2005 on a machine. Some of the others on that
group may have a solution to your situation though.
I would expect Visual Studio 2005 to cause you the same problem -
since it too will install .NET Framework 2.0.
Andrew Watt
MVP - InfoPath
On Fri, 25 Mar 2005 07:15:03 -0800, DJONES
<DJONES@.discussions.microsoft.com> wrote:
>Thanks for the reply...
>I'm working on the Proof of Concept phase of a project using 2.0. I wonder
>if it would work with VS loaded on the Web Server instead...
>"Andrew Watt [MVP - InfoPath]" wrote:
>> On Fri, 25 Mar 2005 04:59:02 -0800, DJONES
>> <DJONES@.discussions.microsoft.com> wrote:
>> >When I installed 2.0 on the Web Server Reporting Services stopped working
>> >properly. Is it possible to run them side by side. The server also has 1.1
>> >running.
>> >
>> >Thanks
>> In theory,
>> When .NET Framework 2.0 reaches RTM it is supposed to be possible to
>> run them side by side without problem.
>> In practice, in the short term, there are assorted issues.
>> Why do you have .NET Framework 2.0 on your Web server? Which build?
>> Andrew Watt
>> MVP - InfoPath|||We have similar situation - fix was two-fold, all done in IIS.
First, create an applicaton pool specifically for the two reporting
services applications, then set the properties of each application to
use that pool. Applications using different frameworks cannot "swim in
the same pool".
Second, ensure that the reporting services applications are configured
to use the 1.1 framework and not the 2.0 - the tedious way is to check
(and change, if needed) every mapping through the IIS properties pages.
The faster way is to use the command line applications to do this
configuration - but I think injudicious use of the command line can
remap all the applications at once - which could be what happened when
you installed the 2.0 framework.|||The command line tool aspnet_regiis has options to check the current script
mappings and to install certain versions for a particular virtual root only
rather than all virtual roots:
aspnet_regiis -lk
aspnet_regiis -s <path>
Make sure to run the aspnet_regiis.exe from the correct version directory
under \Windows\Microsoft.Net\Framework
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Parker" <psmith@.iquest.net> wrote in message
news:1112015101.606172.149480@.g14g2000cwa.googlegroups.com...
> We have similar situation - fix was two-fold, all done in IIS.
> First, create an applicaton pool specifically for the two reporting
> services applications, then set the properties of each application to
> use that pool. Applications using different frameworks cannot "swim in
> the same pool".
> Second, ensure that the reporting services applications are configured
> to use the 1.1 framework and not the 2.0 - the tedious way is to check
> (and change, if needed) every mapping through the IIS properties pages.
> The faster way is to use the command line applications to do this
> configuration - but I think injudicious use of the command line can
> remap all the applications at once - which could be what happened when
> you installed the 2.0 framework.
>
.NET DiffGram
I am running VS Studio 2003 and a VB.NET web application. I have installed
SQLXML 3 SP3 on both my .NET machine and my SQL server machine, and SOAP 3 on
db Server machine.
I have created a Diffgram from a dataset with writexml to stream and xsd
with SQL relations mapped. Yet when it tries to execute the SQLXMLcommand, I
continually get an Invalid Authorization Specification error.
I have not found anything about it online. Please let me know what I can do
to help the situation. I would love to use Diff gram instead of hand writing
the same XML consuming code into SQL server.
thanks
Hello,
Could you please send the repro so I can take a look ?
Thanks,
Monica Frintu
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
|||This is an interesting error. Do you get this error while you are executing
the SqlXmlcommand? It would help a lot, if you can send your diffgram and
the managed code to execute it.
Bertan ARI
This posting is provided "AS IS" with no warranties, and confers no rights.
"gehrigsranch" <gehrigsranch@.discussions.microsoft.com> wrote in message
news:6BDCC7A7-0E15-46FD-810B-46558F0CB035@.microsoft.com...
>I am running VS Studio 2003 and a VB.NET web application. I have installed
> SQLXML 3 SP3 on both my .NET machine and my SQL server machine, and SOAP 3
> on
> db Server machine.
> I have created a Diffgram from a dataset with writexml to stream and xsd
> with SQL relations mapped. Yet when it tries to execute the
> SQLXMLcommand, I
> continually get an Invalid Authorization Specification error.
> I have not found anything about it online. Please let me know what I can
> do
> to help the situation. I would love to use Diff gram instead of hand
> writing
> the same XML consuming code into SQL server.
> thanks
SQLXML 3 SP3 on both my .NET machine and my SQL server machine, and SOAP 3 on
db Server machine.
I have created a Diffgram from a dataset with writexml to stream and xsd
with SQL relations mapped. Yet when it tries to execute the SQLXMLcommand, I
continually get an Invalid Authorization Specification error.
I have not found anything about it online. Please let me know what I can do
to help the situation. I would love to use Diff gram instead of hand writing
the same XML consuming code into SQL server.
thanks
Hello,
Could you please send the repro so I can take a look ?
Thanks,
Monica Frintu
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
|||This is an interesting error. Do you get this error while you are executing
the SqlXmlcommand? It would help a lot, if you can send your diffgram and
the managed code to execute it.
Bertan ARI
This posting is provided "AS IS" with no warranties, and confers no rights.
"gehrigsranch" <gehrigsranch@.discussions.microsoft.com> wrote in message
news:6BDCC7A7-0E15-46FD-810B-46558F0CB035@.microsoft.com...
>I am running VS Studio 2003 and a VB.NET web application. I have installed
> SQLXML 3 SP3 on both my .NET machine and my SQL server machine, and SOAP 3
> on
> db Server machine.
> I have created a Diffgram from a dataset with writexml to stream and xsd
> with SQL relations mapped. Yet when it tries to execute the
> SQLXMLcommand, I
> continually get an Invalid Authorization Specification error.
> I have not found anything about it online. Please let me know what I can
> do
> to help the situation. I would love to use Diff gram instead of hand
> writing
> the same XML consuming code into SQL server.
> thanks
Tuesday, March 6, 2012
.NET and SQL Server on Separate Machines
Hi all,
We're working on an ASP.Net Web Application that makes several calls to a
SQL Server database. Everything was running correctly when the database
and the web server were on the same computer, but we have sinced moved
them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
Serv 2003 Ent.
The connection string in our web.config file originally looked like this:
<add key="ConnectionString"
value="server=localhost;Trusted_Connection=true;da tabase=Store;" />
After moving the database (and changing the server in the connection
string), we started to receive this error: "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection."
We ended up changing the connection string to look like this:
<add key="ConnectionString" value="Integrated Security=SSPI;Initial
Catalog=Store;Data Source=192.168.0.12;" />
This string only works if we add the following to the .config file:
<authentication mode="Windows" />
<identity impersonate="true" />
Unfortunately, the web application was designed to use forms
authentication, so we're still looking for a valid connection string.
We've tried setting Trusted_Connection=false and providing a username and
password, but we get the same error as before - only with the provided
username listed instead of (null). We've tried setting the database to
mixed mode, and Win Auth only and got the same results.
Any help would be greatly appreciated.
Jason DeCock
Elk River Systems, Inc.
http://www.elkriversystems.com
Standard SQL Authentication would not have Integrated Security in the
string. This implies we are requesting
NT authentication.
Your connection string should look something like this:
Provider=SQLOLEDB.1;Persist Security Info=False;User
ID=SQLUserNameHere;Initial Catalog=Northwind;Data
Source=SQLServerNameHere,1433;Network Library=DBMSSOCN;Use Encryption for
Data=False
There's also some good documentation here;
http://msdn.microsoft.com/library/de...us/dnnetsec/ht
ml/SecNetHT03.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||I'm guessing you did a new install of SQL2k ... if I recall correctly, one
of the default Network Configurations includes NamedPipes as well as TCP/IP
... which in turn will lead to some issues with being able to use TCP/IP.
Try clearing NamedPipes.
This may also be a role/user access issue on the Win3 server.
"Big Mo" <jdecock@.gonzaga.nospam.edu> wrote in message
news:Pine.LNX.4.44.0406171221360.21793-100000@.barney.gonzaga.edu...
> Hi all,
> We're working on an ASP.Net Web Application that makes several calls to a
> SQL Server database. Everything was running correctly when the database
> and the web server were on the same computer, but we have sinced moved
> them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
> Serv 2003 Ent.
> The connection string in our web.config file originally looked like this:
> <add key="ConnectionString"
> value="server=localhost;Trusted_Connection=true;da tabase=Store;" />
> After moving the database (and changing the server in the connection
> string), we started to receive this error: "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection."
> We ended up changing the connection string to look like this:
> <add key="ConnectionString" value="Integrated Security=SSPI;Initial
> Catalog=Store;Data Source=192.168.0.12;" />
> This string only works if we add the following to the .config file:
> <authentication mode="Windows" />
> <identity impersonate="true" />
> Unfortunately, the web application was designed to use forms
> authentication, so we're still looking for a valid connection string.
> We've tried setting Trusted_Connection=false and providing a username and
> password, but we get the same error as before - only with the provided
> username listed instead of (null). We've tried setting the database to
> mixed mode, and Win Auth only and got the same results.
> Any help would be greatly appreciated.
>
> --
> Jason DeCock
> Elk River Systems, Inc.
> http://www.elkriversystems.com
>
|||One way out would be
- configure your iis asp.net worker process to run under a domain account
(need to modify your machine.config file)
- add this domain account as a valid login to your sql server.
hth
vikram
"Big Mo" <jdecock@.gonzaga.nospam.edu> wrote in message
news:Pine.LNX.4.44.0406171221360.21793-100000@.barney.gonzaga.edu...
> Hi all,
> We're working on an ASP.Net Web Application that makes several calls to a
> SQL Server database. Everything was running correctly when the database
> and the web server were on the same computer, but we have sinced moved
> them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
> Serv 2003 Ent.
> The connection string in our web.config file originally looked like this:
> <add key="ConnectionString"
> value="server=localhost;Trusted_Connection=true;da tabase=Store;" />
> After moving the database (and changing the server in the connection
> string), we started to receive this error: "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection."
> We ended up changing the connection string to look like this:
> <add key="ConnectionString" value="Integrated Security=SSPI;Initial
> Catalog=Store;Data Source=192.168.0.12;" />
> This string only works if we add the following to the .config file:
> <authentication mode="Windows" />
> <identity impersonate="true" />
> Unfortunately, the web application was designed to use forms
> authentication, so we're still looking for a valid connection string.
> We've tried setting Trusted_Connection=false and providing a username and
> password, but we get the same error as before - only with the provided
> username listed instead of (null). We've tried setting the database to
> mixed mode, and Win Auth only and got the same results.
> Any help would be greatly appreciated.
>
> --
> Jason DeCock
> Elk River Systems, Inc.
> http://www.elkriversystems.com
>
We're working on an ASP.Net Web Application that makes several calls to a
SQL Server database. Everything was running correctly when the database
and the web server were on the same computer, but we have sinced moved
them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
Serv 2003 Ent.
The connection string in our web.config file originally looked like this:
<add key="ConnectionString"
value="server=localhost;Trusted_Connection=true;da tabase=Store;" />
After moving the database (and changing the server in the connection
string), we started to receive this error: "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection."
We ended up changing the connection string to look like this:
<add key="ConnectionString" value="Integrated Security=SSPI;Initial
Catalog=Store;Data Source=192.168.0.12;" />
This string only works if we add the following to the .config file:
<authentication mode="Windows" />
<identity impersonate="true" />
Unfortunately, the web application was designed to use forms
authentication, so we're still looking for a valid connection string.
We've tried setting Trusted_Connection=false and providing a username and
password, but we get the same error as before - only with the provided
username listed instead of (null). We've tried setting the database to
mixed mode, and Win Auth only and got the same results.
Any help would be greatly appreciated.
Jason DeCock
Elk River Systems, Inc.
http://www.elkriversystems.com
Standard SQL Authentication would not have Integrated Security in the
string. This implies we are requesting
NT authentication.
Your connection string should look something like this:
Provider=SQLOLEDB.1;Persist Security Info=False;User
ID=SQLUserNameHere;Initial Catalog=Northwind;Data
Source=SQLServerNameHere,1433;Network Library=DBMSSOCN;Use Encryption for
Data=False
There's also some good documentation here;
http://msdn.microsoft.com/library/de...us/dnnetsec/ht
ml/SecNetHT03.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||I'm guessing you did a new install of SQL2k ... if I recall correctly, one
of the default Network Configurations includes NamedPipes as well as TCP/IP
... which in turn will lead to some issues with being able to use TCP/IP.
Try clearing NamedPipes.
This may also be a role/user access issue on the Win3 server.
"Big Mo" <jdecock@.gonzaga.nospam.edu> wrote in message
news:Pine.LNX.4.44.0406171221360.21793-100000@.barney.gonzaga.edu...
> Hi all,
> We're working on an ASP.Net Web Application that makes several calls to a
> SQL Server database. Everything was running correctly when the database
> and the web server were on the same computer, but we have sinced moved
> them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
> Serv 2003 Ent.
> The connection string in our web.config file originally looked like this:
> <add key="ConnectionString"
> value="server=localhost;Trusted_Connection=true;da tabase=Store;" />
> After moving the database (and changing the server in the connection
> string), we started to receive this error: "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection."
> We ended up changing the connection string to look like this:
> <add key="ConnectionString" value="Integrated Security=SSPI;Initial
> Catalog=Store;Data Source=192.168.0.12;" />
> This string only works if we add the following to the .config file:
> <authentication mode="Windows" />
> <identity impersonate="true" />
> Unfortunately, the web application was designed to use forms
> authentication, so we're still looking for a valid connection string.
> We've tried setting Trusted_Connection=false and providing a username and
> password, but we get the same error as before - only with the provided
> username listed instead of (null). We've tried setting the database to
> mixed mode, and Win Auth only and got the same results.
> Any help would be greatly appreciated.
>
> --
> Jason DeCock
> Elk River Systems, Inc.
> http://www.elkriversystems.com
>
|||One way out would be
- configure your iis asp.net worker process to run under a domain account
(need to modify your machine.config file)
- add this domain account as a valid login to your sql server.
hth
vikram
"Big Mo" <jdecock@.gonzaga.nospam.edu> wrote in message
news:Pine.LNX.4.44.0406171221360.21793-100000@.barney.gonzaga.edu...
> Hi all,
> We're working on an ASP.Net Web Application that makes several calls to a
> SQL Server database. Everything was running correctly when the database
> and the web server were on the same computer, but we have sinced moved
> them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
> Serv 2003 Ent.
> The connection string in our web.config file originally looked like this:
> <add key="ConnectionString"
> value="server=localhost;Trusted_Connection=true;da tabase=Store;" />
> After moving the database (and changing the server in the connection
> string), we started to receive this error: "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection."
> We ended up changing the connection string to look like this:
> <add key="ConnectionString" value="Integrated Security=SSPI;Initial
> Catalog=Store;Data Source=192.168.0.12;" />
> This string only works if we add the following to the .config file:
> <authentication mode="Windows" />
> <identity impersonate="true" />
> Unfortunately, the web application was designed to use forms
> authentication, so we're still looking for a valid connection string.
> We've tried setting Trusted_Connection=false and providing a username and
> password, but we get the same error as before - only with the provided
> username listed instead of (null). We've tried setting the database to
> mixed mode, and Win Auth only and got the same results.
> Any help would be greatly appreciated.
>
> --
> Jason DeCock
> Elk River Systems, Inc.
> http://www.elkriversystems.com
>
.NET and SQL Server on Separate Machines
Hi all,
We're working on an ASP.Net Web Application that makes several calls to a
SQL Server database. Everything was running correctly when the database
and the web server were on the same computer, but we have sinced moved
them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
Serv 2003 Ent.
The connection string in our web.config file originally looked like this:
<add key="ConnectionString"
value=" server=localhost;Trusted_Connection=true
;database=Store;" />
After moving the database (and changing the server in the connection
string), we started to receive this error: "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection."
We ended up changing the connection string to look like this:
<add key="ConnectionString" value="Integrated Security=SSPI;Initial
Catalog=Store;Data Source=192.168.0.12;" />
This string only works if we add the following to the .config file:
<authentication mode="Windows" />
<identity impersonate="true" />
Unfortunately, the web application was designed to use forms
authentication, so we're still looking for a valid connection string.
We've tried setting Trusted_Connection=false and providing a username and
password, but we get the same error as before - only with the provided
username listed instead of (null). We've tried setting the database to
mixed mode, and Win Auth only and got the same results.
Any help would be greatly appreciated.
Jason DeCock
Elk River Systems, Inc.
http://www.elkriversystems.comStandard SQL Authentication would not have Integrated Security in the
string. This implies we are requesting
NT authentication.
Your connection string should look something like this:
Provider=SQLOLEDB.1;Persist Security Info=False;User
ID=SQLUserNameHere;Initial Catalog=Northwind;Data
Source=SQLServerNameHere,1433;Network Library=DBMSSOCN;Use Encryption for
Data=False
There's also some good documentation here;
http://msdn.microsoft.com/library/d...-us/dnnetsec/ht
ml/SecNetHT03.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I'm guessing you did a new install of SQL2k ... if I recall correctly, one
of the default Network Configurations includes NamedPipes as well as TCP/IP
... which in turn will lead to some issues with being able to use TCP/IP.
Try clearing NamedPipes.
This may also be a role/user access issue on the Win3 server.
"Big Mo" <jdecock@.gonzaga.nospam.edu> wrote in message
news:Pine.LNX.4.44.0406171221360.21793-100000@.barney.gonzaga.edu...
> Hi all,
> We're working on an ASP.Net Web Application that makes several calls to a
> SQL Server database. Everything was running correctly when the database
> and the web server were on the same computer, but we have sinced moved
> them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
> Serv 2003 Ent.
> The connection string in our web.config file originally looked like this:
> <add key="ConnectionString"
> value=" server=localhost;Trusted_Connection=true
;database=Store;" />
> After moving the database (and changing the server in the connection
> string), we started to receive this error: "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection."
> We ended up changing the connection string to look like this:
> <add key="ConnectionString" value="Integrated Security=SSPI;Initial
> Catalog=Store;Data Source=192.168.0.12;" />
> This string only works if we add the following to the .config file:
> <authentication mode="Windows" />
> <identity impersonate="true" />
> Unfortunately, the web application was designed to use forms
> authentication, so we're still looking for a valid connection string.
> We've tried setting Trusted_Connection=false and providing a username and
> password, but we get the same error as before - only with the provided
> username listed instead of (null). We've tried setting the database to
> mixed mode, and Win Auth only and got the same results.
> Any help would be greatly appreciated.
>
> --
> Jason DeCock
> Elk River Systems, Inc.
> http://www.elkriversystems.com
>|||One way out would be
- configure your iis asp.net worker process to run under a domain account
(need to modify your machine.config file)
- add this domain account as a valid login to your sql server.
hth
vikram
"Big Mo" <jdecock@.gonzaga.nospam.edu> wrote in message
news:Pine.LNX.4.44.0406171221360.21793-100000@.barney.gonzaga.edu...
> Hi all,
> We're working on an ASP.Net Web Application that makes several calls to a
> SQL Server database. Everything was running correctly when the database
> and the web server were on the same computer, but we have sinced moved
> them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
> Serv 2003 Ent.
> The connection string in our web.config file originally looked like this:
> <add key="ConnectionString"
> value=" server=localhost;Trusted_Connection=true
;database=Store;" />
> After moving the database (and changing the server in the connection
> string), we started to receive this error: "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection."
> We ended up changing the connection string to look like this:
> <add key="ConnectionString" value="Integrated Security=SSPI;Initial
> Catalog=Store;Data Source=192.168.0.12;" />
> This string only works if we add the following to the .config file:
> <authentication mode="Windows" />
> <identity impersonate="true" />
> Unfortunately, the web application was designed to use forms
> authentication, so we're still looking for a valid connection string.
> We've tried setting Trusted_Connection=false and providing a username and
> password, but we get the same error as before - only with the provided
> username listed instead of (null). We've tried setting the database to
> mixed mode, and Win Auth only and got the same results.
> Any help would be greatly appreciated.
>
> --
> Jason DeCock
> Elk River Systems, Inc.
> http://www.elkriversystems.com
>
We're working on an ASP.Net Web Application that makes several calls to a
SQL Server database. Everything was running correctly when the database
and the web server were on the same computer, but we have sinced moved
them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
Serv 2003 Ent.
The connection string in our web.config file originally looked like this:
<add key="ConnectionString"
value=" server=localhost;Trusted_Connection=true
;database=Store;" />
After moving the database (and changing the server in the connection
string), we started to receive this error: "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection."
We ended up changing the connection string to look like this:
<add key="ConnectionString" value="Integrated Security=SSPI;Initial
Catalog=Store;Data Source=192.168.0.12;" />
This string only works if we add the following to the .config file:
<authentication mode="Windows" />
<identity impersonate="true" />
Unfortunately, the web application was designed to use forms
authentication, so we're still looking for a valid connection string.
We've tried setting Trusted_Connection=false and providing a username and
password, but we get the same error as before - only with the provided
username listed instead of (null). We've tried setting the database to
mixed mode, and Win Auth only and got the same results.
Any help would be greatly appreciated.
Jason DeCock
Elk River Systems, Inc.
http://www.elkriversystems.comStandard SQL Authentication would not have Integrated Security in the
string. This implies we are requesting
NT authentication.
Your connection string should look something like this:
Provider=SQLOLEDB.1;Persist Security Info=False;User
ID=SQLUserNameHere;Initial Catalog=Northwind;Data
Source=SQLServerNameHere,1433;Network Library=DBMSSOCN;Use Encryption for
Data=False
There's also some good documentation here;
http://msdn.microsoft.com/library/d...-us/dnnetsec/ht
ml/SecNetHT03.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I'm guessing you did a new install of SQL2k ... if I recall correctly, one
of the default Network Configurations includes NamedPipes as well as TCP/IP
... which in turn will lead to some issues with being able to use TCP/IP.
Try clearing NamedPipes.
This may also be a role/user access issue on the Win3 server.
"Big Mo" <jdecock@.gonzaga.nospam.edu> wrote in message
news:Pine.LNX.4.44.0406171221360.21793-100000@.barney.gonzaga.edu...
> Hi all,
> We're working on an ASP.Net Web Application that makes several calls to a
> SQL Server database. Everything was running correctly when the database
> and the web server were on the same computer, but we have sinced moved
> them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
> Serv 2003 Ent.
> The connection string in our web.config file originally looked like this:
> <add key="ConnectionString"
> value=" server=localhost;Trusted_Connection=true
;database=Store;" />
> After moving the database (and changing the server in the connection
> string), we started to receive this error: "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection."
> We ended up changing the connection string to look like this:
> <add key="ConnectionString" value="Integrated Security=SSPI;Initial
> Catalog=Store;Data Source=192.168.0.12;" />
> This string only works if we add the following to the .config file:
> <authentication mode="Windows" />
> <identity impersonate="true" />
> Unfortunately, the web application was designed to use forms
> authentication, so we're still looking for a valid connection string.
> We've tried setting Trusted_Connection=false and providing a username and
> password, but we get the same error as before - only with the provided
> username listed instead of (null). We've tried setting the database to
> mixed mode, and Win Auth only and got the same results.
> Any help would be greatly appreciated.
>
> --
> Jason DeCock
> Elk River Systems, Inc.
> http://www.elkriversystems.com
>|||One way out would be
- configure your iis asp.net worker process to run under a domain account
(need to modify your machine.config file)
- add this domain account as a valid login to your sql server.
hth
vikram
"Big Mo" <jdecock@.gonzaga.nospam.edu> wrote in message
news:Pine.LNX.4.44.0406171221360.21793-100000@.barney.gonzaga.edu...
> Hi all,
> We're working on an ASP.Net Web Application that makes several calls to a
> SQL Server database. Everything was running correctly when the database
> and the web server were on the same computer, but we have sinced moved
> them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
> Serv 2003 Ent.
> The connection string in our web.config file originally looked like this:
> <add key="ConnectionString"
> value=" server=localhost;Trusted_Connection=true
;database=Store;" />
> After moving the database (and changing the server in the connection
> string), we started to receive this error: "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection."
> We ended up changing the connection string to look like this:
> <add key="ConnectionString" value="Integrated Security=SSPI;Initial
> Catalog=Store;Data Source=192.168.0.12;" />
> This string only works if we add the following to the .config file:
> <authentication mode="Windows" />
> <identity impersonate="true" />
> Unfortunately, the web application was designed to use forms
> authentication, so we're still looking for a valid connection string.
> We've tried setting Trusted_Connection=false and providing a username and
> password, but we get the same error as before - only with the provided
> username listed instead of (null). We've tried setting the database to
> mixed mode, and Win Auth only and got the same results.
> Any help would be greatly appreciated.
>
> --
> Jason DeCock
> Elk River Systems, Inc.
> http://www.elkriversystems.com
>
Saturday, February 25, 2012
.mdf to .mdb
My web host only supports .mdb database files, so is there a way to convert .mdf to .mdb with a program? Or would I have to do it by hand?
Thank you.
I am not aware that such a program exists.
Maybe you can use SQL Server DTS or SQL Server Transformation Services to download your database into a .mdb format.
|||Try to use this.http://www.data-conversions.net/products.php?prod_num=1&&dest=MENU&&ID=100|||
I was having the same issue and followed these steps...
1. In your ODBC connections add a SQL server connection to your current SQL server and database.
2. Create a new Access Database
3. Import from ODBC source and select all tables.
The tables will import with a dbo_ prefix, but all of the structure and information will be there. It does not carry over the table relationships either.
Nick
.mdf to .mdb
My web host only supports .mdb database files, so is there a way to convert .mdf to .mdb with a program? Or would I have to do it by hand?
Thank you.
I am not aware that such a program exists.
Maybe you can use SQL Server DTS or SQL Server Transformation Services to download your database into a .mdb format.
|||Try to use this.http://www.data-conversions.net/products.php?prod_num=1&&dest=MENU&&ID=100|||
I was having the same issue and followed these steps...
1. In your ODBC connections add a SQL server connection to your current SQL server and database.
2. Create a new Access Database
3. Import from ODBC source and select all tables.
The tables will import with a dbo_ prefix, but all of the structure and information will be there. It does not carry over the table relationships either.
Nick
Saturday, February 11, 2012
(very) basic security questions
I'm almost ready to deploy my web application onto a shared server at my ISP, the application uses SQL Server 2000.
I am using paramaterised queries for all read operations and stored procs for all of the updates. While developing, I have been using a trusted connection to connect to SQL server.
Now that i'm about to deploy, what steps do I need to take to ensure that there is a single user which has basic read permissions plus execute permissions on the stored procs. The main things that i'm confused about are:-
1. What, typically do I need to set up? A new role? A new user group?
2. Trusted connections - I notice from my own connection string that I am not passing in a password. Why is that? If I continue to use a trusted connection to the server at the ISP, do I need to ask the ISP for any login information? Wil I need a password on the connection string (from what i've read so far, trusted connections are preferred becasue no password is transferred - how can that be?)
I know these are very basic questions, but all of the material i've read so far seems to assume some basic prior knowledge, (which as you can tell I don't have!)
Appreciate any help,
Thanks
BernieIn all the situations I have seen from remote hosting, you will need to change your connection string from trusted to one that has the uid=suppliedbyhost;pwd=suppliedbyhost;
If you look over your sp's check to see if dbo is the owner. This will limit the access on the remote host.
(ts Urgent) Connect to different databases
Hi
I have my database on four different database servers. I have a web appliction using asp.net 2.0. i want to add data to all four database servers. How can i do that with asp.net 2.0
Thanks in advance
Take care
Bye
In you web.config you can add all the connectionStrings to the section connectionStrings.
Then in your code, you can retrieve the relevant connectionString based on some condition to connect to the required database.
|||Hi
I really appreciate your response
Thanks for your reply
Take care
Bye
Thursday, February 9, 2012
(provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
I am getting the following error when i try to connect to the my web site using froma different server.
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
i am using sql express and i attach the database through the connection string in the web config.
Any ideas
The error indicates the connection was eatablished but then closed for some reason, this can happen if the SQL2005 instance is out of the available connections when the instance is configured to use a nonzero maximum number of concurrent connections. Check the SQL ERRORLOGs for detailed information, which you can get by executing xp_readerrorlog in Management Studio. If you find something like "Could not connect because the maximum number of '5' user connections has already been reached.", you can execute such command:
sp_configure 'user connections',0
Subscribe to:
Posts (Atom)