After migrating SQL Server 2000 from NT to 2003, I have a login failure for
one user when trying to access a database.When I go to the user's login
properties, Database Access, I check the Permit box for the database for the
user and click OK.
I get an Microsoft SQL-DMO error message:
Error 21002:[SQL-DMO]User 'MW_DBA' already exists.
How can I fix this?
AntoninAntonin
It sounds like your logins and User ID's have got out of synch. Try running
the following on the master database
EXEC sp_change_users_login 'Auto_Fix', 'MW_DBA'
Hope this helps
John|||Hi John,
Thanks for your reply. I tried it and got this:
The number of orphaned users fixed by updating users was 0.
The number of orphaned users fixed by adding new logins and then updating
users was 0.
Antonin
"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:D9637F5C-58DF-4940-8E0F-9E4D2A507B51@.microsoft.com...
> Antonin
> It sounds like your logins and User ID's have got out of synch. Try
> running
> the following on the master database
> EXEC sp_change_users_login 'Auto_Fix', 'MW_DBA'
> Hope this helps
> John
Friday, February 24, 2012
Login problem: MSDE database from ASP.Net
I have created an MSDE database and successfully used it with an VB.Net
program on my desktop. Works great.
I have just begun learning ASP.Net. I created another MSDE database. But I
can't get past the login problems. "Predict" is the name of the database.
"GARY" is the Windows user account name. The error message is as follows:
Cannot open database requested in login 'Predict'. Login fails. Login failed
for user 'GARY\ASPNET'.
I used the following 2 connection strings. Neither works.
data source=(local)\VSdotNET;database=Predict;integrate d security=true
workstation id=GARY;packet size=4096;integrated security=SSPI;data
source="GARY\VSDOTNET";persist security info=False;initial catalog=Predict
Does anyone know what MSDE might be looking for here?
hi Gary,
Gary Frank wrote:
> I have created an MSDE database and successfully used it with an
> VB.Net program on my desktop. Works great.
> I have just begun learning ASP.Net. I created another MSDE database.
> But I can't get past the login problems. "Predict" is the name of
> the database. "GARY" is the Windows user account name. The error
> message is as follows:
> Cannot open database requested in login 'Predict'. Login fails. Login
> failed for user 'GARY\ASPNET'.
> I used the following 2 connection strings. Neither works.
> data source=(local)\VSdotNET;database=Predict;integrate d security=true
> workstation id=GARY;packet size=4096;integrated security=SSPI;data
> source="GARY\VSDOTNET";persist security info=False;initial
> catalog=Predict
> Does anyone know what MSDE might be looking for here?
you have to grant the account trying to log in (GARY\ASPNET) login
privileges as long as granting hin db access to the required databases..
as you can see from the raised error, using WinNT trusted authentication via
asp, you are not using the account you are logged in with, but the account
IIS is running on..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3jdk15Fp8sp6U1@.individual.net...
> hi Gary,
> Gary Frank wrote:
> you have to grant the account trying to log in (GARY\ASPNET) login
> privileges as long as granting hin db access to the required databases..
> as you can see from the raised error, using WinNT trusted authentication
> via asp, you are not using the account you are logged in with, but the
> account IIS is running on..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
Thanks Andrea. I am using MSDE and not SQL Server. As I understand it,
MSDE does not come with comprehensive administration tools. I can't figure
out how to grant access using MSDE. Are you aware of any tools I can
download or pay for without buying SQL Server, in order to grant database
access to a Windows user account?
|||hi Gary,
Gary Frank wrote:
> Thanks Andrea. I am using MSDE and not SQL Server. As I understand
> it, MSDE does not come with comprehensive administration tools. I
> can't figure out how to grant access using MSDE. Are you aware of
> any tools I can download or pay for without buying SQL Server, in
> order to grant database access to a Windows user account?
you can use the command line tool, oSql.exe, provided with MSDE, like
described in
http://support.microsoft.com/default...EN-US;q325003, or you can
have a look at a free prj of mine, available at the link following my
sign... other tools,, both free and commercial, are listed at
http://www.microsoft.com/sql/msde/partners/ and/or
http://www.aspfaq.com/show.asp?id=2442..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
program on my desktop. Works great.
I have just begun learning ASP.Net. I created another MSDE database. But I
can't get past the login problems. "Predict" is the name of the database.
"GARY" is the Windows user account name. The error message is as follows:
Cannot open database requested in login 'Predict'. Login fails. Login failed
for user 'GARY\ASPNET'.
I used the following 2 connection strings. Neither works.
data source=(local)\VSdotNET;database=Predict;integrate d security=true
workstation id=GARY;packet size=4096;integrated security=SSPI;data
source="GARY\VSDOTNET";persist security info=False;initial catalog=Predict
Does anyone know what MSDE might be looking for here?
hi Gary,
Gary Frank wrote:
> I have created an MSDE database and successfully used it with an
> VB.Net program on my desktop. Works great.
> I have just begun learning ASP.Net. I created another MSDE database.
> But I can't get past the login problems. "Predict" is the name of
> the database. "GARY" is the Windows user account name. The error
> message is as follows:
> Cannot open database requested in login 'Predict'. Login fails. Login
> failed for user 'GARY\ASPNET'.
> I used the following 2 connection strings. Neither works.
> data source=(local)\VSdotNET;database=Predict;integrate d security=true
> workstation id=GARY;packet size=4096;integrated security=SSPI;data
> source="GARY\VSDOTNET";persist security info=False;initial
> catalog=Predict
> Does anyone know what MSDE might be looking for here?
you have to grant the account trying to log in (GARY\ASPNET) login
privileges as long as granting hin db access to the required databases..
as you can see from the raised error, using WinNT trusted authentication via
asp, you are not using the account you are logged in with, but the account
IIS is running on..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3jdk15Fp8sp6U1@.individual.net...
> hi Gary,
> Gary Frank wrote:
> you have to grant the account trying to log in (GARY\ASPNET) login
> privileges as long as granting hin db access to the required databases..
> as you can see from the raised error, using WinNT trusted authentication
> via asp, you are not using the account you are logged in with, but the
> account IIS is running on..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
Thanks Andrea. I am using MSDE and not SQL Server. As I understand it,
MSDE does not come with comprehensive administration tools. I can't figure
out how to grant access using MSDE. Are you aware of any tools I can
download or pay for without buying SQL Server, in order to grant database
access to a Windows user account?
|||hi Gary,
Gary Frank wrote:
> Thanks Andrea. I am using MSDE and not SQL Server. As I understand
> it, MSDE does not come with comprehensive administration tools. I
> can't figure out how to grant access using MSDE. Are you aware of
> any tools I can download or pay for without buying SQL Server, in
> order to grant database access to a Windows user account?
you can use the command line tool, oSql.exe, provided with MSDE, like
described in
http://support.microsoft.com/default...EN-US;q325003, or you can
have a look at a free prj of mine, available at the link following my
sign... other tools,, both free and commercial, are listed at
http://www.microsoft.com/sql/msde/partners/ and/or
http://www.aspfaq.com/show.asp?id=2442..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Login problem. Please help
Ok, I know this question has been asked dozen of time. I did do some research but I encountered some difficulties. Please help me and I promise all the reward points that I have.
Below is my procedure :
1) I created a stored procedure with the following source from http://www.mssqlcity.com/Articles/KnowHow/Textcopy.htm
CREATE PROCEDURE sp_textcopy (
@.srvname varchar (30),
@.login varchar (30),
@.password varchar (30),
@.dbname varchar (30),
@.tbname varchar (30),
@.colname varchar (30),
@.filename varchar (30),
@.whereclause varchar (40),
@.direction char(1))
AS
DECLARE @.exec_str varchar (255)
SELECT @.exec_str =
'textcopy /S ' + @.srvname +
' /U ' + @.login +
' /P ' + @.password +
' /D ' + @.dbname +
' /T ' + @.tbname +
' /C ' + @.colname +
' /W "' + @.whereclause +
'" /F ' + @.filename +
' /' + @.direction
EXEC master..xp_cmdshell @.exec_str
2) Then I go to SQL Query Analyser, where I am using Windows Authenitication and select the database where my tables and the stored procedure located.
3) My database is called "paramount", table is 'movie' and has a field called "image" and its type is "image".
4) I issued this command :
sp_textcopy @.srvname = 'local',
@.login = 'test', @.password = '',
@.dbname = 'paramountSilver', @.tbname = 'movie',
@.colname = 'image',
@.filename = 'd:\paramount\antz.jpg',
@.whereclause = "title = 'antz'",
@.direction = 'I'
5) I got this message from the output panel
SQL Server Message 18452: Login failed for user 'test'. Reason: Not associated with a trusted SQL Server connection.
DB-Library Error 10003: Login incorrect.
I already created a login user from Enterprise Manager->Security->Login and set it to my database.
Please tell me what is wrong and how to rectify the error.
Thank you very much.Use one of the following workarounds:
Use trusted connections over named pipes where appropriate.
Disable multiprotocol for SQL Server using the Server Network Utility.|||Originally posted by Satya
Use one of the following workarounds:
Use trusted connections over named pipes where appropriate.
Hello boss,
Thanks for the reply. I am a total dummy in MSSQL. Could you please elaborate further on how to Use trusted connections over named pipes where appropriate?
Where should I get to or set the trusted connection?
Please enlighten me.
Thanks|||First of all read thru books online for Trusted connections information, which gives you information required.
Here is the extract from BOL:
How to set up Windows Authentication Mode security (Enterprise Manager)
New Information - SQL Server 2000 SP3.
To set up Windows Authentication Mode security
Expand a server group.
Right-click a server, and then click Properties.
On the Security tab, under Authentication, click Windows only.
Under Audit level, select the level at which user accesses to Microsoft SQL Server are recorded in the SQL Server error log:
None causes no auditing to be performed.
Success causes only successful login attempts to be audited.
Failure causes only failed login attempts to be audited.
All causes successful and failed login attempts to be audited.
Security Note Microsoft recommends auditing, at minimum, failed login attempts. Auditing failed login attempts helps determine if unauthorized users are attempting to access the system.
See Also
Authentication Modes
:cool:|||sp_textcopy @.srvname = 'DIABLO', @.login = 'sa', @.password = 'sa',
@.dbname = 'paramountSilver', @.tbname = 'movie',
@.colname = 'image',
@.filename = 'd:\paramount\antz.jpg',
@.whereclause = "title = 'antz'",
@.direction = 'I'
It looks like I have solved the login problem but now I got another message:
SQL Server 'DIABLO'Message 170: Line 1: Incorrect syntax near '='. (Concerning line 1)
DB-Library Error 10007: General SQL Server error: Check messages from the SQL Server.
Do you have any idea?|||OK. I know what's wrong. Thanks|||It would help others if you can post the your assumption to workaround this issue.
Originally posted by mpls2000
OK. I know what's wrong. Thanks|||i forgot "where".
Below is my procedure :
1) I created a stored procedure with the following source from http://www.mssqlcity.com/Articles/KnowHow/Textcopy.htm
CREATE PROCEDURE sp_textcopy (
@.srvname varchar (30),
@.login varchar (30),
@.password varchar (30),
@.dbname varchar (30),
@.tbname varchar (30),
@.colname varchar (30),
@.filename varchar (30),
@.whereclause varchar (40),
@.direction char(1))
AS
DECLARE @.exec_str varchar (255)
SELECT @.exec_str =
'textcopy /S ' + @.srvname +
' /U ' + @.login +
' /P ' + @.password +
' /D ' + @.dbname +
' /T ' + @.tbname +
' /C ' + @.colname +
' /W "' + @.whereclause +
'" /F ' + @.filename +
' /' + @.direction
EXEC master..xp_cmdshell @.exec_str
2) Then I go to SQL Query Analyser, where I am using Windows Authenitication and select the database where my tables and the stored procedure located.
3) My database is called "paramount", table is 'movie' and has a field called "image" and its type is "image".
4) I issued this command :
sp_textcopy @.srvname = 'local',
@.login = 'test', @.password = '',
@.dbname = 'paramountSilver', @.tbname = 'movie',
@.colname = 'image',
@.filename = 'd:\paramount\antz.jpg',
@.whereclause = "title = 'antz'",
@.direction = 'I'
5) I got this message from the output panel
SQL Server Message 18452: Login failed for user 'test'. Reason: Not associated with a trusted SQL Server connection.
DB-Library Error 10003: Login incorrect.
I already created a login user from Enterprise Manager->Security->Login and set it to my database.
Please tell me what is wrong and how to rectify the error.
Thank you very much.Use one of the following workarounds:
Use trusted connections over named pipes where appropriate.
Disable multiprotocol for SQL Server using the Server Network Utility.|||Originally posted by Satya
Use one of the following workarounds:
Use trusted connections over named pipes where appropriate.
Hello boss,
Thanks for the reply. I am a total dummy in MSSQL. Could you please elaborate further on how to Use trusted connections over named pipes where appropriate?
Where should I get to or set the trusted connection?
Please enlighten me.
Thanks|||First of all read thru books online for Trusted connections information, which gives you information required.
Here is the extract from BOL:
How to set up Windows Authentication Mode security (Enterprise Manager)
New Information - SQL Server 2000 SP3.
To set up Windows Authentication Mode security
Expand a server group.
Right-click a server, and then click Properties.
On the Security tab, under Authentication, click Windows only.
Under Audit level, select the level at which user accesses to Microsoft SQL Server are recorded in the SQL Server error log:
None causes no auditing to be performed.
Success causes only successful login attempts to be audited.
Failure causes only failed login attempts to be audited.
All causes successful and failed login attempts to be audited.
Security Note Microsoft recommends auditing, at minimum, failed login attempts. Auditing failed login attempts helps determine if unauthorized users are attempting to access the system.
See Also
Authentication Modes
:cool:|||sp_textcopy @.srvname = 'DIABLO', @.login = 'sa', @.password = 'sa',
@.dbname = 'paramountSilver', @.tbname = 'movie',
@.colname = 'image',
@.filename = 'd:\paramount\antz.jpg',
@.whereclause = "title = 'antz'",
@.direction = 'I'
It looks like I have solved the login problem but now I got another message:
SQL Server 'DIABLO'Message 170: Line 1: Incorrect syntax near '='. (Concerning line 1)
DB-Library Error 10007: General SQL Server error: Check messages from the SQL Server.
Do you have any idea?|||OK. I know what's wrong. Thanks|||It would help others if you can post the your assumption to workaround this issue.
Originally posted by mpls2000
OK. I know what's wrong. Thanks|||i forgot "where".
Login problem, mystery
Hi
I have installed MSDE ver 8.00.760.03 from the package sql2desksp03 located
at go.microsoft.com/fwlink/?linkid=13962
My intention is to develop an asp.net application with Microsoft Visual
Basic.Net Standard. Already installed. Because I can't create a database
with the
standard edition I want to use MS Access 2000 project to create the tables,
but when I try to create the project using the Microsoft SQL Server database
wizard and enter my SQL Server details as follows
name=svrname
user=sa
password=correctpassword
I get the following message.
Connection failed:
SQLState:'28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
If I leave the Microsoft SQL Server database wizard user and password boxes
empty I am able to create my project but unable to create tables.
I'm on WinXP SP2 with Administrative rights. MSDE is running and my password
is definately correct - Please help :-)
hi,
SimonW wrote:
> Hi
> I have installed MSDE ver 8.00.760.03 from the package sql2desksp03
> located at go.microsoft.com/fwlink/?linkid=13962
> My intention is to develop an asp.net application with Microsoft
> Visual Basic.Net Standard. Already installed. Because I can't create
> a database with the
> standard edition I want to use MS Access 2000 project to create the
> tables, but when I try to create the project using the Microsoft SQL
> Server database
> wizard and enter my SQL Server details as follows
> name=svrname
> user=sa
> password=correctpassword
> I get the following message.
> Connection failed:
> SQLState:'28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> If I leave the Microsoft SQL Server database wizard user and password
> boxes empty I am able to create my project but unable to create
> tables.
> I'm on WinXP SP2 with Administrative rights. MSDE is running and my
> password is definately correct - Please help :-)
MSDE installs by default only allowing trusted conections... you can modify
this behavior bot at install time, providing the
SECURITYMODE=SQL
parameter to the setup.exe boostrap installer or later, at runtime, hacking
the Windows registry as described in
http://support.microsoft.com/default...n-us;285097... stop and
restart the server..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you very much Andrea :-)
"Andrea Montanari" wrote:
> hi,
> SimonW wrote:
> MSDE installs by default only allowing trusted conections... you can modify
> this behavior bot at install time, providing the
> SECURITYMODE=SQL
> parameter to the setup.exe boostrap installer or later, at runtime, hacking
> the Windows registry as described in
> http://support.microsoft.com/default...n-us;285097... stop and
> restart the server..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
I have installed MSDE ver 8.00.760.03 from the package sql2desksp03 located
at go.microsoft.com/fwlink/?linkid=13962
My intention is to develop an asp.net application with Microsoft Visual
Basic.Net Standard. Already installed. Because I can't create a database
with the
standard edition I want to use MS Access 2000 project to create the tables,
but when I try to create the project using the Microsoft SQL Server database
wizard and enter my SQL Server details as follows
name=svrname
user=sa
password=correctpassword
I get the following message.
Connection failed:
SQLState:'28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
If I leave the Microsoft SQL Server database wizard user and password boxes
empty I am able to create my project but unable to create tables.
I'm on WinXP SP2 with Administrative rights. MSDE is running and my password
is definately correct - Please help :-)
hi,
SimonW wrote:
> Hi
> I have installed MSDE ver 8.00.760.03 from the package sql2desksp03
> located at go.microsoft.com/fwlink/?linkid=13962
> My intention is to develop an asp.net application with Microsoft
> Visual Basic.Net Standard. Already installed. Because I can't create
> a database with the
> standard edition I want to use MS Access 2000 project to create the
> tables, but when I try to create the project using the Microsoft SQL
> Server database
> wizard and enter my SQL Server details as follows
> name=svrname
> user=sa
> password=correctpassword
> I get the following message.
> Connection failed:
> SQLState:'28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> If I leave the Microsoft SQL Server database wizard user and password
> boxes empty I am able to create my project but unable to create
> tables.
> I'm on WinXP SP2 with Administrative rights. MSDE is running and my
> password is definately correct - Please help :-)
MSDE installs by default only allowing trusted conections... you can modify
this behavior bot at install time, providing the
SECURITYMODE=SQL
parameter to the setup.exe boostrap installer or later, at runtime, hacking
the Windows registry as described in
http://support.microsoft.com/default...n-us;285097... stop and
restart the server..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you very much Andrea :-)
"Andrea Montanari" wrote:
> hi,
> SimonW wrote:
> MSDE installs by default only allowing trusted conections... you can modify
> this behavior bot at install time, providing the
> SECURITYMODE=SQL
> parameter to the setup.exe boostrap installer or later, at runtime, hacking
> the Windows registry as described in
> http://support.microsoft.com/default...n-us;285097... stop and
> restart the server..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
Login problem with Windows Authentication
I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
BillFor Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegroups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
BillFor Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegroups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>
Login problem with Windows Authentication
I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
Bill
For Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegr oups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
Bill
For Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegr oups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>
Login problem with Windows Authentication
I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
BillFor Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegroups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
BillFor Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegroups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>
Subscribe to:
Posts (Atom)