Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Sun Foster
Aged Yak Warrior
515 Posts |
 Posted - 2006-04-12 : 08:42:34
|
| I program ASP.NET with SQL server 2000 using mixed authentication mode. If I use sa in connection string, there is no problem. If I create another account in SQL server (e.g. ASPNET)and replaced "sa" with "ASPNET", I got a prompt in Crystal report aking to input network login name and password. What is wrong? |
|
|
Srinika
Master Smack Fu Yak Hacker
1378 Posts |
Posted - 2006-04-12 : 08:50:34
|
| -- U MUST use a different user name - even if u can use sa (sa is the super admin - if some unauthorized person knowing that would be disastrous)-- U should not try to (U cannot) replace sa User Name, Instead create a different user name as ASPNET-- In crystal Report, the DB connection may have made with sa / pswd, u may need to change itSrinika |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-04-12 : 09:05:31
|
| i may be wrong but is aspnet reserved?try to use a different loginame and see if this is the case...HTH--------------------keeping it simple... |
|
|
|
Sun Foster
Aged Yak Warrior
515 Posts |
Posted - 2006-04-12 : 09:59:20
|
| Thank for help. I'll try to use another account. We use windows 2003 and IIS 6, is aspnet still reserved? |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-04-12 : 10:11:19
|
| check your local users under computer management, usersit's only an assumption since aspnet is a user created for asp.net--------------------keeping it simple... |
|
|
|
Norwich
Posting Yak Master
158 Posts |
Posted - 2006-04-12 : 10:24:40
|
| You should stay away from using SA in your connection strings or your day to day activities.Rather create a user with all the sysadmin rights for your day to day stuff.RegardsNThe revolution won't be televised! |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-04-12 : 11:46:38
|
| If you want to avoid the login stuff consider using a Windows (Trusted) Login, instead of a SQL Server oneKristen |
|
|
|
|
|
|
Use sa or create another account?