Configuration for SQL 2000

Hi,

What configuration steps should I do to enable my .NET web application to access my SQL 2000 database? I have SQL Server 2000 SP3, SQL 2005 Express, SQL 2005 and VS 2005 installed on the same machine. Is it anything to do with the NT Authority\Network Service or ASPNET account that I need to allow access to or what? Kinda lost here... been banging my server for the past week.

Cheers!

There are several options. Do you want to run the SQL Server in Mixed Mode ? DO you want to use impersonation ? DO you want to impersoante the user at the SQL Server ?

-Jens Suessmeyer.

|||

That is also my next question. What I would like is for annonymous access to view the data taken from the database. Only authorized personnel can log in through Forms Authentication to Insert, Update or Delete the database.

I believe this is a simple implementation but I can't seem to get the configuration right. The database works if I put it as a local database but that defeats the purpose of the implementation.

I got this error which I believe is very common

What can I set in IIS 6.0, Compiter Management and SQL 2000?:

Server Error in '/' Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

|||

Anyway after some tweaking here and there, I managed to get it to work properly. Added NT Authority\Local Service account to SQL 2000 User Login, which will categorize it as the public grp. After that checking the tables this group can operate Select instruction on.

This is probably not the conventional way, so I would like to know what the generic workable implementation should be (otherwise called the industrial standard).

Cheers!

Config SQL Server 2000 mail with Outlook 2002

We have a SQL Advance server 2000 running SQL Server 2000 SP3 and has
Outlook 2002 installed. The SQL Agent runs under the account
ghs2000\sqlexec.
I logged into this machine as ghs2000\sqlexec and setup a POP3 account
on the machine. Tested sending emails and test mails from SQL Server
and they work fine.
Now we log into the machine as a different user, it's normally logged in
as ghs2000\madmin. And we leave Outlook running. But the emails from
SQL Server never get sent out. They won't get sent out unless we log
into the server as ghs2000\sqlexec and open Outlook 2002.
Any way to set this up so the messages are sent out regardless of who is
logged in? Is this a limitation in Outlook 2002 or would the same thing
happen in Outlook 2002?
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Hi
This may be happening!
From http://support.microsoft.com/default.aspx?scid=kb;pl;263556
WARNING: If you attempt to use SQL Mail to establish a connection to a
POP3/SMTP mail server you MUST be able to repeatedly connect and send mail
by using the following steps:
1.. Click the icon that starts the mail client.
2.. Send a message to the same e-mail address listed in the profile so
that you can test both the send and receive capability.
3.. Exit the mail client.
4.. Repeat steps 1 through 3 several times to simulate expected e-mail
traffic.
NOTE: If at any time during this process any dialog boxes appear that
require a response (such as clicking OK to log on) or you are prompted to
enter a password, it will not work with SQL Mail. For an Internet mail
connection to work with SQL Mail, you must have 100% connectivity or SQL
Mail is not usable and you might have to restart your server to clear up the
problem.
The reason for this is that SQL Mail does not provide for retries when
accessing a POP3 account. If SQL Mail cannot connect to the POP3 server on
the first attempt, the Internet Mail Connector normally opens a dialog box
that prompts you to click OK to retry. It that should occur, SQL Mail, which
is running as part of the MSSQLServer service, never sees the dialog box and
stops responding at this point. You might have to stop the Mapisp32.exe
application or even restart your Windows NT computer to clear the problem.
You may be better off using SMTP? http://www.sqldev.net/xp/xpsmtp.htm
John
"Colin Colin" <ccole@.ghs.guthrie.org> wrote in message
news:OJzDUx9lDHA.3024@.tk2msftngp13.phx.gbl...
> We have a SQL Advance server 2000 running SQL Server 2000 SP3 and has
> Outlook 2002 installed. The SQL Agent runs under the account
> ghs2000\sqlexec.
> I logged into this machine as ghs2000\sqlexec and setup a POP3 account
> on the machine. Tested sending emails and test mails from SQL Server
> and they work fine.
> Now we log into the machine as a different user, it's normally logged in
> as ghs2000\madmin. And we leave Outlook running. But the emails from
> SQL Server never get sent out. They won't get sent out unless we log
> into the server as ghs2000\sqlexec and open Outlook 2002.
> Any way to set this up so the messages are sent out regardless of who is
> logged in? Is this a limitation in Outlook 2002 or would the same thing
> happen in Outlook 2002?
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||I have Outlook 2K setup for a POP3 acct to work with SQL 2K. Honestly it is
painful to have it works. First thing it doesn't work well if I used
Terminal service, so I have to drive all the way at the midnight to the data
center where we keep our servers to logon physically. Then it never work as
expected. Why? Because emails stucked in the Out folder. I have to logon
as the domain acct that starts up SQL services then the mails are sent out.
I do every thing from MS KB. It works on this server but the others.
Finally it works on all servers but I will never know what made SQL mail
failed at the first time. I follow all steps, one by one, per MS KBs. If
it fails I will just start over, recreate the email profile, set up SQL mail
then it will work after second or third time.
>>Any way to set this up so the messages are sent out regardless of who is
>>logged in?
SQL mail is supposed to work that way. It is the way SQL mails is working
on my SQL boxes now.
"Colin Colin" <ccole@.ghs.guthrie.org> wrote in message
news:OJzDUx9lDHA.3024@.tk2msftngp13.phx.gbl...
> We have a SQL Advance server 2000 running SQL Server 2000 SP3 and has
> Outlook 2002 installed. The SQL Agent runs under the account
> ghs2000\sqlexec.
> I logged into this machine as ghs2000\sqlexec and setup a POP3 account
> on the machine. Tested sending emails and test mails from SQL Server
> and they work fine.
> Now we log into the machine as a different user, it's normally logged in
> as ghs2000\madmin. And we leave Outlook running. But the emails from
> SQL Server never get sent out. They won't get sent out unless we log
> into the server as ghs2000\sqlexec and open Outlook 2002.
> Any way to set this up so the messages are sent out regardless of who is
> logged in? Is this a limitation in Outlook 2002 or would the same thing
> happen in Outlook 2002?
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!sqlsql

Concurrent queries error

On my server running SQL Server 2000 (SP3). I frequently get this
informational message in the Event Viewer log.

17052 :
This SQL Server has been optimized for 8 concurrent queries. This limit has
been exceeded by 2 queries and performance may be adversely affected.

The application that I am running is a vendor application so I do not have
access to the code. I contacted the vendor, but they have never seen this
problem and cannot recreate it. I checked the Microsoft Knowledge Base for
help, but I came up empty. It seems like it should be a simple
configuration change.

Any advice?
Thanks,
JeffI found the answer many times by just searching this site. Should have
done that first.

Go ahead and remove this thread.

Jeff