Hi all,
When I am installing Commerce Server on my SQL Server 2005 machine I get
an error reported in the logs that that says "Login failed for user 'CSNET\t
aziegma'.
[CLIENT: 192.168.25.12] Error: 18456, Severity: 14, State: 16. I have lo
oked
on google for information. I have also posted in the Commerce Server groups.
I can run queries against the databases the remote system is trying to acces
s
no problem. But when Commerce Server tries to access it it errors out. Also,
when I view the Activity Monitor next to the processes kicked off by the
remote machine it says .net sqlserver client provider. Is there something
I need to set up for .net? I am stumped.
thanks,
tziegmannDoes Commerce Server never work or is it just an issue for this user?
depending on the configuration, this might be a "double hop" issue. If you
are not logged in directly to the to the commerce server machine but logged
in to another machine accessing Commerce Server, the Commerce Server would
require delegation permission to log into SQL Server with the client's
credentials. This only works if your networks supports Kerberos
authentication and delegation is allowed. Many networks don't allow this.
Note that this answer is based on a lot of assumptions about your
configuration and is basically a guess based on your mention of Commerce
Server.
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
"tziegmann" <tziegmann@.msn.com> wrote in message
news:428ac052327f8c80d356188011c@.news.microsoft.com...
> Hi all,
> When I am installing Commerce Server on my SQL Server 2005 machine I get
> an error reported in the logs that that says "Login failed for user
> 'CSNET\taziegma'. [CLIENT: 192.168.25.12] Error: 18456, Severity: 14,
> State: 16. I have looked on google for information. I have also posted in
> the Commerce Server groups. I can run queries against the databases the
> remote system is trying to access no problem. But when Commerce Server
> tries to access it it errors out. Also, when I view the Activity Monitor
> next to the processes kicked off by the remote machine it says .net
> sqlserver client provider. Is there something I need to set up for .net? I
> am stumped.
> thanks,
> tziegmann
>
Showing posts with label system. Show all posts
Showing posts with label system. Show all posts
Monday, March 19, 2012
Logon failed for user '(null)'. Not associated with trusted connec
Hi,
I have set up system dsn's with an sql server driver on Windows 2000 to use
SQL Server Authentication (NOT Windows Authentication) on a number of client
PC's. When I use these to connect to an sql server database (which allows
mixed mode authentication) via excel, I get the following message on some
(but not all) client PC's.
===============
Connection failed
SQLState 28000
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for
user
'(null)'.
Reason: Not associated with a trusted SQL Server connection.
================
When I click on OK, another SQL Server login pop-up box appears with the
"Use trusted connection" checkbox pre-checked. If I uncheck this then it
allows me to put in the correct user/password combination.
Why does this happen when the DSN was set up to use a User/password
combination in the first place?. It's as though it tries to connect with
Windows Authentication regardless of how it is originally set up.
Anybody have any ideas?.
Thanks,
AndyCheck for differences in MDAC versions on the PCs. There was
an issue with earlier MDAC versions where ODBC connections
would ignore the authentication mode and just use windows
authentication no matter what you selected. You can use the
component check to check mdac installations. It's available
at:
http://msdn.microsoft.com/data/mdac...ds/default.aspx
-Sue
On Wed, 4 May 2005 03:05:11 -0700, "Squirrel"
<Squirrel@.discussions.microsoft.com> wrote:
>Hi,
>I have set up system dsn's with an sql server driver on Windows 2000 to use
>SQL Server Authentication (NOT Windows Authentication) on a number of clien
t
>PC's. When I use these to connect to an sql server database (which allows
>mixed mode authentication) via excel, I get the following message on some
>(but not all) client PC's.
>===============
>Connection failed
>SQLState 28000
>SQL Server Error 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed fo
r user
>'(null)'.
>Reason: Not associated with a trusted SQL Server connection.
>================
>When I click on OK, another SQL Server login pop-up box appears with the
>"Use trusted connection" checkbox pre-checked. If I uncheck this then it
>allows me to put in the correct user/password combination.
>Why does this happen when the DSN was set up to use a User/password
>combination in the first place?. It's as though it tries to connect with
>Windows Authentication regardless of how it is originally set up.
>Anybody have any ideas?.
>Thanks,
>Andy
I have set up system dsn's with an sql server driver on Windows 2000 to use
SQL Server Authentication (NOT Windows Authentication) on a number of client
PC's. When I use these to connect to an sql server database (which allows
mixed mode authentication) via excel, I get the following message on some
(but not all) client PC's.
===============
Connection failed
SQLState 28000
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for
user
'(null)'.
Reason: Not associated with a trusted SQL Server connection.
================
When I click on OK, another SQL Server login pop-up box appears with the
"Use trusted connection" checkbox pre-checked. If I uncheck this then it
allows me to put in the correct user/password combination.
Why does this happen when the DSN was set up to use a User/password
combination in the first place?. It's as though it tries to connect with
Windows Authentication regardless of how it is originally set up.
Anybody have any ideas?.
Thanks,
AndyCheck for differences in MDAC versions on the PCs. There was
an issue with earlier MDAC versions where ODBC connections
would ignore the authentication mode and just use windows
authentication no matter what you selected. You can use the
component check to check mdac installations. It's available
at:
http://msdn.microsoft.com/data/mdac...ds/default.aspx
-Sue
On Wed, 4 May 2005 03:05:11 -0700, "Squirrel"
<Squirrel@.discussions.microsoft.com> wrote:
>Hi,
>I have set up system dsn's with an sql server driver on Windows 2000 to use
>SQL Server Authentication (NOT Windows Authentication) on a number of clien
t
>PC's. When I use these to connect to an sql server database (which allows
>mixed mode authentication) via excel, I get the following message on some
>(but not all) client PC's.
>===============
>Connection failed
>SQLState 28000
>SQL Server Error 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed fo
r user
>'(null)'.
>Reason: Not associated with a trusted SQL Server connection.
>================
>When I click on OK, another SQL Server login pop-up box appears with the
>"Use trusted connection" checkbox pre-checked. If I uncheck this then it
>allows me to put in the correct user/password combination.
>Why does this happen when the DSN was set up to use a User/password
>combination in the first place?. It's as though it tries to connect with
>Windows Authentication regardless of how it is originally set up.
>Anybody have any ideas?.
>Thanks,
>Andy
Logon failed for user '(null)'. Not associated with trusted connec
Hi,
I have set up system dsn's with an sql server driver on windows 2000 to use
SQL Server Authentication (NOT Windows Authentication) on a number of client
PC's. When I use these to connect to an sql server database (which allows
mixed mode authentication) via excel, I get the following message on some
(but not all) client PC's.
===============
Connection failed
SQLState 28000
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'(null)'.
Reason: Not associated with a trusted SQL Server connection.
================
When I click on OK, another SQL Server login pop-up box appears with the
"Use trusted connection" checkbox pre-checked. If I uncheck this then it
allows me to put in the correct user/password combination.
Why does this happen when the DSN was set up to use a User/password
combination in the first place?. It's as though it tries to connect with
Windows Authentication regardless of how it is originally set up.
Anybody have any ideas?.
Thanks,
Andy
Check for differences in MDAC versions on the PCs. There was
an issue with earlier MDAC versions where ODBC connections
would ignore the authentication mode and just use windows
authentication no matter what you selected. You can use the
component check to check mdac installations. It's available
at:
http://msdn.microsoft.com/data/mdac/...s/default.aspx
-Sue
On Wed, 4 May 2005 03:05:11 -0700, "Squirrel"
<Squirrel@.discussions.microsoft.com> wrote:
>Hi,
>I have set up system dsn's with an sql server driver on windows 2000 to use
>SQL Server Authentication (NOT Windows Authentication) on a number of client
>PC's. When I use these to connect to an sql server database (which allows
>mixed mode authentication) via excel, I get the following message on some
>(but not all) client PC's.
>===============
>Connection failed
>SQLState 28000
>SQL Server Error 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
>'(null)'.
>Reason: Not associated with a trusted SQL Server connection.
>================
>When I click on OK, another SQL Server login pop-up box appears with the
>"Use trusted connection" checkbox pre-checked. If I uncheck this then it
>allows me to put in the correct user/password combination.
>Why does this happen when the DSN was set up to use a User/password
>combination in the first place?. It's as though it tries to connect with
>Windows Authentication regardless of how it is originally set up.
>Anybody have any ideas?.
>Thanks,
>Andy
I have set up system dsn's with an sql server driver on windows 2000 to use
SQL Server Authentication (NOT Windows Authentication) on a number of client
PC's. When I use these to connect to an sql server database (which allows
mixed mode authentication) via excel, I get the following message on some
(but not all) client PC's.
===============
Connection failed
SQLState 28000
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'(null)'.
Reason: Not associated with a trusted SQL Server connection.
================
When I click on OK, another SQL Server login pop-up box appears with the
"Use trusted connection" checkbox pre-checked. If I uncheck this then it
allows me to put in the correct user/password combination.
Why does this happen when the DSN was set up to use a User/password
combination in the first place?. It's as though it tries to connect with
Windows Authentication regardless of how it is originally set up.
Anybody have any ideas?.
Thanks,
Andy
Check for differences in MDAC versions on the PCs. There was
an issue with earlier MDAC versions where ODBC connections
would ignore the authentication mode and just use windows
authentication no matter what you selected. You can use the
component check to check mdac installations. It's available
at:
http://msdn.microsoft.com/data/mdac/...s/default.aspx
-Sue
On Wed, 4 May 2005 03:05:11 -0700, "Squirrel"
<Squirrel@.discussions.microsoft.com> wrote:
>Hi,
>I have set up system dsn's with an sql server driver on windows 2000 to use
>SQL Server Authentication (NOT Windows Authentication) on a number of client
>PC's. When I use these to connect to an sql server database (which allows
>mixed mode authentication) via excel, I get the following message on some
>(but not all) client PC's.
>===============
>Connection failed
>SQLState 28000
>SQL Server Error 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
>'(null)'.
>Reason: Not associated with a trusted SQL Server connection.
>================
>When I click on OK, another SQL Server login pop-up box appears with the
>"Use trusted connection" checkbox pre-checked. If I uncheck this then it
>allows me to put in the correct user/password combination.
>Why does this happen when the DSN was set up to use a User/password
>combination in the first place?. It's as though it tries to connect with
>Windows Authentication regardless of how it is originally set up.
>Anybody have any ideas?.
>Thanks,
>Andy
Monday, March 12, 2012
Logins under Windows Group
Hi All,
I want to get all the Logins under Particular Windows Group by using Query
or System Stored Procedure.
For Eg: All Logins under BUILTIN\Administrators
Could anyone pls help me out?
Thanks in Advance...
Regards,
Herbert R.exec sp_helplogins
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:AC53F0BE-9938-4D4F-807B-833F00F5688E@.microsoft.com...
> Hi All,
> I want to get all the Logins under Particular Windows Group by using Query
> or System Stored Procedure.
> For Eg: All Logins under BUILTIN\Administrators
> Could anyone pls help me out?
> Thanks in Advance...
> Regards,
> Herbert R.
I want to get all the Logins under Particular Windows Group by using Query
or System Stored Procedure.
For Eg: All Logins under BUILTIN\Administrators
Could anyone pls help me out?
Thanks in Advance...
Regards,
Herbert R.exec sp_helplogins
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:AC53F0BE-9938-4D4F-807B-833F00F5688E@.microsoft.com...
> Hi All,
> I want to get all the Logins under Particular Windows Group by using Query
> or System Stored Procedure.
> For Eg: All Logins under BUILTIN\Administrators
> Could anyone pls help me out?
> Thanks in Advance...
> Regards,
> Herbert R.
Logins from 2000 to 2005
As from what i see there are different system files for logins.
Is there a way to transfer SQL 2000 logins to SQL 2005 i am used to the
sp_help_revlogin i think thats the script..in 2000
Is there a way to convert all logins from SQL 2000 to SQL 2005
Did you use the updated version of the procedure ?
http://blogs.msdn.com/lcris/archive/2006/04/03/567680.aspx
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||
No not seen that one...so just run on SQL 2000 and then run on SQL 2005.
Have you used it.
Thanks
|||You should use that one on your machine if you are using a SQL2k5.Jens K. Suessmeyer.
http://www.sqlserver2005.de
Wednesday, March 7, 2012
Login to a SQL Server 2000 database keeps failing
Hello,
On my system (XP professional),I have no problem logging to all of my
databases (SQL Server 2000) using "sa" or any of the other logins that I had
created and gave them database access.
However, on this other system (XP professional and SQL Server 2000) I keep
getting the following error:
Java.sql.SQLException: []Login failed for user â'saâ'. Reason: Not associatied
with a trusted SQL Server connection.
I will get the same error if I create and use new logins that were given
access to the databases. I had never seen this particular error message.
Please help!
Thanks,
--
MitraPerhaps this SQL Server is configured to allow only Windows authentication.
To connect with SQL logins, you need to change the server's authentication
mode to SQL Server and Windows and restart SQL Server. You can do this from
the Security tab under Enterprise Manager server properties.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:42CDF6EC-8DCD-46BE-96A3-CEE02C498284@.microsoft.com...
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I
> had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
> associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra|||Mitra,
How are you logging into your DBs -- it looks like from an application? Have
you tried creating a DSN entry using the same credentials? My guess is that
your application is trying to logon sa as a domain account not as a SQL
native account.
Tea C.
"mitra" wrote:
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user â'saâ'. Reason: Not associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra
On my system (XP professional),I have no problem logging to all of my
databases (SQL Server 2000) using "sa" or any of the other logins that I had
created and gave them database access.
However, on this other system (XP professional and SQL Server 2000) I keep
getting the following error:
Java.sql.SQLException: []Login failed for user â'saâ'. Reason: Not associatied
with a trusted SQL Server connection.
I will get the same error if I create and use new logins that were given
access to the databases. I had never seen this particular error message.
Please help!
Thanks,
--
MitraPerhaps this SQL Server is configured to allow only Windows authentication.
To connect with SQL logins, you need to change the server's authentication
mode to SQL Server and Windows and restart SQL Server. You can do this from
the Security tab under Enterprise Manager server properties.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:42CDF6EC-8DCD-46BE-96A3-CEE02C498284@.microsoft.com...
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I
> had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
> associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra|||Mitra,
How are you logging into your DBs -- it looks like from an application? Have
you tried creating a DSN entry using the same credentials? My guess is that
your application is trying to logon sa as a domain account not as a SQL
native account.
Tea C.
"mitra" wrote:
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user â'saâ'. Reason: Not associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra
Login to a SQL Server 2000 database keeps failing
Hello,
On my system (XP professional),I have no problem logging to all of my
databases (SQL Server 2000) using "sa" or any of the other logins that I had
created and gave them database access.
However, on this other system (XP professional and SQL Server 2000) I keep
getting the following error:
Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not associatied
with a trusted SQL Server connection.
I will get the same error if I create and use new logins that were given
access to the databases. I had never seen this particular error message.
Please help!
Thanks,
Mitra
Perhaps this SQL Server is configured to allow only Windows authentication.
To connect with SQL logins, you need to change the server's authentication
mode to SQL Server and Windows and restart SQL Server. You can do this from
the Security tab under Enterprise Manager server properties.
Hope this helps.
Dan Guzman
SQL Server MVP
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:42CDF6EC-8DCD-46BE-96A3-CEE02C498284@.microsoft.com...
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I
> had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
> associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra
|||Mitra,
How are you logging into your DBs -- it looks like from an application? Have
you tried creating a DSN entry using the same credentials? My guess is that
your application is trying to logon sa as a domain account not as a SQL
native account.
Tea C.
"mitra" wrote:
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra
On my system (XP professional),I have no problem logging to all of my
databases (SQL Server 2000) using "sa" or any of the other logins that I had
created and gave them database access.
However, on this other system (XP professional and SQL Server 2000) I keep
getting the following error:
Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not associatied
with a trusted SQL Server connection.
I will get the same error if I create and use new logins that were given
access to the databases. I had never seen this particular error message.
Please help!
Thanks,
Mitra
Perhaps this SQL Server is configured to allow only Windows authentication.
To connect with SQL logins, you need to change the server's authentication
mode to SQL Server and Windows and restart SQL Server. You can do this from
the Security tab under Enterprise Manager server properties.
Hope this helps.
Dan Guzman
SQL Server MVP
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:42CDF6EC-8DCD-46BE-96A3-CEE02C498284@.microsoft.com...
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I
> had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
> associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra
|||Mitra,
How are you logging into your DBs -- it looks like from an application? Have
you tried creating a DSN entry using the same credentials? My guess is that
your application is trying to logon sa as a domain account not as a SQL
native account.
Tea C.
"mitra" wrote:
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra
Login to a SQL Server 2000 database keeps failing
Hello,
On my system (XP professional),I have no problem logging to all of my
databases (SQL Server 2000) using "sa" or any of the other logins that I had
created and gave them database access.
However, on this other system (XP professional and SQL Server 2000) I keep
getting the following error:
Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not XXX
ociatied
with a trusted SQL Server connection.
I will get the same error if I create and use new logins that were given
access to the databases. I had never seen this particular error message.
Please help!
Thanks,
--
MitraPerhaps this SQL Server is configured to allow only Windows authentication.
To connect with SQL logins, you need to change the server's authentication
mode to SQL Server and Windows and restart SQL Server. You can do this from
the Security tab under Enterprise Manager server properties.
Hope this helps.
Dan Guzman
SQL Server MVP
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:42CDF6EC-8DCD-46BE-96A3-CEE02C498284@.microsoft.com...
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I
> had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
> associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra|||Mitra,
How are you logging into your DBs -- it looks like from an application? Have
you tried creating a DSN entry using the same credentials? My guess is that
your application is trying to logon sa as a domain account not as a SQL
native account.
Tea C.
"mitra" wrote:
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I h
ad
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not a
ssociatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra
On my system (XP professional),I have no problem logging to all of my
databases (SQL Server 2000) using "sa" or any of the other logins that I had
created and gave them database access.
However, on this other system (XP professional and SQL Server 2000) I keep
getting the following error:
Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not XXX
ociatied
with a trusted SQL Server connection.
I will get the same error if I create and use new logins that were given
access to the databases. I had never seen this particular error message.
Please help!
Thanks,
--
MitraPerhaps this SQL Server is configured to allow only Windows authentication.
To connect with SQL logins, you need to change the server's authentication
mode to SQL Server and Windows and restart SQL Server. You can do this from
the Security tab under Enterprise Manager server properties.
Hope this helps.
Dan Guzman
SQL Server MVP
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:42CDF6EC-8DCD-46BE-96A3-CEE02C498284@.microsoft.com...
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I
> had
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
> associatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra|||Mitra,
How are you logging into your DBs -- it looks like from an application? Have
you tried creating a DSN entry using the same credentials? My guess is that
your application is trying to logon sa as a domain account not as a SQL
native account.
Tea C.
"mitra" wrote:
> Hello,
> On my system (XP professional),I have no problem logging to all of my
> databases (SQL Server 2000) using "sa" or any of the other logins that I h
ad
> created and gave them database access.
> However, on this other system (XP professional and SQL Server 2000) I keep
> getting the following error:
> Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not a
ssociatied
> with a trusted SQL Server connection.
> I will get the same error if I create and use new logins that were given
> access to the databases. I had never seen this particular error message.
> Please help!
> Thanks,
> --
> Mitra
Friday, February 24, 2012
Login process error
Hi guys
Just setup a new system running Win2k3, SQL Server 2005, etc (all msdn).
I've got a web app (.net 2) which is running perfectly well, most of the
time, and then there's one page where I'm getting the following error...
Server Error in '/' Application.
A connection was successfully established with the server, but then an error
occured during the login process. (provider: Shared Memory Provider, error:
0
- No process is on the other end of the pipe.)
I guess the question is what does this message mean and how can I fix it?!
It's a website that's working fine apart from that page, and as far as I can
tell the code should be fine. Help!!
Cheers
Danmusosdev wrote:
> Hi guys
> Just setup a new system running Win2k3, SQL Server 2005, etc (all
> msdn). I've got a web app (.net 2) which is running perfectly well,
> most of the time, and then there's one page where I'm getting the
> following error...
> Server Error in '/' Application.
> A connection was successfully established with the server, but then
> an error occured during the login process. (provider: Shared Memory
> Provider, error: 0 - No process is on the other end of the pipe.)
> I guess the question is what does this message mean and how can I fix
> it?! It's a website that's working fine apart from that page, and as
> far as I can tell the code should be fine. Help!!
> Cheers
>
> Dan
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
http://blogs.msdn.com/sql_protocols.../22/483684.aspx (see
message 4)
David Gugick - SQL Server MVP
Quest Software
Just setup a new system running Win2k3, SQL Server 2005, etc (all msdn).
I've got a web app (.net 2) which is running perfectly well, most of the
time, and then there's one page where I'm getting the following error...
Server Error in '/' Application.
A connection was successfully established with the server, but then an error
occured during the login process. (provider: Shared Memory Provider, error:
0
- No process is on the other end of the pipe.)
I guess the question is what does this message mean and how can I fix it?!
It's a website that's working fine apart from that page, and as far as I can
tell the code should be fine. Help!!
Cheers
Danmusosdev wrote:
> Hi guys
> Just setup a new system running Win2k3, SQL Server 2005, etc (all
> msdn). I've got a web app (.net 2) which is running perfectly well,
> most of the time, and then there's one page where I'm getting the
> following error...
> Server Error in '/' Application.
> A connection was successfully established with the server, but then
> an error occured during the login process. (provider: Shared Memory
> Provider, error: 0 - No process is on the other end of the pipe.)
> I guess the question is what does this message mean and how can I fix
> it?! It's a website that's working fine apart from that page, and as
> far as I can tell the code should be fine. Help!!
> Cheers
>
> Dan
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
http://blogs.msdn.com/sql_protocols.../22/483684.aspx (see
message 4)
David Gugick - SQL Server MVP
Quest Software
Subscribe to:
Posts (Atom)