failed to connect to SQL Server's database!

Hi,
I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
The only thing and the most important that should be working but not, is
application that uses SQL Server as it's main database. Before this, the
application used SQL Server 2000 and working fine.
Everytime users launch the application, there's this error message: "Error
in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
Although I've allowed Windows Authentication & SQL Server authentication in
SQL Server 2005 logins settings, that error message will still appears and
restrict any users to log-in to the application.
That application uses a "DataAccessLayer.config" file that has this
parameters:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="UseWebService" value="false"/>
<add key="DAL.DataService.DataService" value="http://companyweb"/>
<add key="DBCnnString" value="Persist Security Info=False;User
ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
<add key="server" value="ServerName"/>
<add key="database" value="INVENTORY"/>
<add key="uid" value="sa"/>
<add key="password" value=""/>
</appSettings>
</configuration>
What happened? Have anyone encountered the same symtomps/problem and know
how to work around it?
Please be noted, I attach this "INVENTORY" database into
ServerName\Database; I do not use instances for it.
Thank you, all help is appreciated.
ON the Security tab, change to [SQL Server and Windows Authentication].
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
|||And did you really install SQL 2005 without a password for the [sa] account?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
|||Dhow wrote:
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
You are trying to connect to the server using the "sa" login, with no
password!!! You have two problems here:
1. Never, ever, purposely allow an application to connect as "sa", you
need to tightly control the use of this login.
2. If you purposely installed SQL Server with a blank password for
"sa", change it, now. Your server is wide open to anybody who chooses
to login as "sa".
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:

> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:

> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:

> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:

> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:

> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Tracy,
I know I input blank password for [sa] user, but that was only for a tryout.
Later on after everything works fine, I'll input new password into it.
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other usefull sugesstions?
Thanks!
"Tracy McKibben" wrote:

> Dhow wrote:
> You are trying to connect to the server using the "sa" login, with no
> password!!! You have two problems here:
> 1. Never, ever, purposely allow an application to connect as "sa", you
> need to tightly control the use of this login.
> 2. If you purposely installed SQL Server with a blank password for
> "sa", change it, now. Your server is wide open to anybody who chooses
> to login as "sa".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>