|
|
You're in the
sql server connect
group:More on that login problem - found the logs -
sql server connect:
2005-11-18 12:50:36.85 logon Login succeeded for user 'NT AUTHORITY\SYSTEM'. Connection: Trusted. and some more that might be useful - 2005-11-18 12:50:40.92 logon Login succeeded for user 'NT AUTHORITY\SYSTEM'. Connection: Trusted. 2005-11-18 12:51:01.35 logon Login succeeded for user 'NT AUTHORITY\SYSTEM'. Connection: Trusted. 2005-11-18 12:51:53.71 logon Login failed for user 'sa'. 2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'. Connection: Trusted. 2005-11-18 12:58:01.80 logon Login failed for user 'sa'. 2005-11-18 12:58:07.73 logon Login failed for user 'a'. 2005-11-18 12:58:16.75 logon Login failed for user 'a'. 2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'. Connection: Trusted. 2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'. Connection: Trusted. 2005-11-18 12:58:37.46 spid9 Starting up database 'test'. 2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf. 2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf. 2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'. Connection: Trusted. 2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'. Connection: Trusted. 2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'. Connection: Trusted. 2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w tilman'. Connection: Trusted. 2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w tilman'. Connection: Trusted. 2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version '1998.11.13' to execute extended stored procedure 'xp_msver'. Can connect with Windows NT authentication, but not with SQL server auth. So all my code has stopped working ... When I try to make a new SQL Server registration I get server does not exist or access denied...
Hi, Verify that you are using both SQL Server and Windows authentication using server Properties and look in the Security tab (I believe that you are really using both SQL Server and Windows authentication since log messages for Windows only authentication would show "Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection"). Which account are you using to connect to the database? Has the password for this account been changed? Ben Nevarez [quoted text, click to view] "Barrett Bonden" <arthur@networks-cc.com> wrote in message news:sIJff.13085$ha2.13022@fe08.lga... > 2005-11-18 12:50:12.09 logon Login failed for user 'sa'. > 2005-11-18 12:50:36.85 logon Login succeeded for user 'NT > AUTHORITY\SYSTEM'. Connection: Trusted. > > and some more that might be useful - > > 2005-11-18 12:50:40.92 logon Login succeeded for user 'NT > AUTHORITY\SYSTEM'. Connection: Trusted. > 2005-11-18 12:51:01.35 logon Login succeeded for user 'NT > AUTHORITY\SYSTEM'. Connection: Trusted. > 2005-11-18 12:51:53.71 logon Login failed for user 'sa'. > 2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'. > Connection: Trusted. > 2005-11-18 12:58:01.80 logon Login failed for user 'sa'. > 2005-11-18 12:58:07.73 logon Login failed for user 'a'. > 2005-11-18 12:58:16.75 logon Login failed for user 'a'. > 2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'. > Connection: Trusted. > 2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'. > Connection: Trusted. > 2005-11-18 12:58:37.46 spid9 Starting up database 'test'. > 2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf. > 2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf. > 2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'. > Connection: Trusted. > 2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'. > Connection: Trusted. > 2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'. > Connection: Trusted. > 2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w tilman'. > Connection: Trusted. > 2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w tilman'. > Connection: Trusted. > 2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version '1998.11.13' > to > execute extended stored procedure 'xp_msver'. > > > Can connect with Windows NT authentication, but not with SQL server auth. > So > all my > code has stopped working ... > When I try to make a new SQL Server registration > I get server does not exist or access denied... > > >
Ben:
I see that I'm using both SQL Server and Windows authentication; I see too that under "Startup service account" (also in the security tab) startup runs the System Account. WHen I choose "This account" it defaults to "LocalSystem" and a password I don't now - I'm scared to try this - Under "registered SQL server properties" "Use windows NT authentication" is checked. WHen I try to use SQL authenticaton nothing works - no matter what combo of login name and password I try .... Should I try to make a new SQL server registration ? All this is clear as mud - if anyone from MS reads this; boys, why do you have to make it so hard, so confusing , so badly documented ? It's hard enough using it productivly when you can get it in in the first place ... [quoted text, click to view] "Ben Nevarez" <bnevarez@sjm.com> wrote in message news:#cQs$CX7FHA.3684@TK2MSFTNGP12.phx.gbl... > > Hi, > > Verify that you are using both SQL Server and Windows authentication using > server Properties and look in the Security tab (I believe that you are > really using both SQL Server and Windows authentication since log messages > for Windows only authentication would show "Login failed for user 'sa'. > Reason: Not associated with a trusted SQL Server connection"). > > Which account are you using to connect to the database? Has the password for > this account been changed? > > Ben Nevarez > > > "Barrett Bonden" <arthur@networks-cc.com> wrote in message > news:sIJff.13085$ha2.13022@fe08.lga... > > 2005-11-18 12:50:12.09 logon Login failed for user 'sa'. > > 2005-11-18 12:50:36.85 logon Login succeeded for user 'NT > > AUTHORITY\SYSTEM'. Connection: Trusted. > > > > and some more that might be useful - > > > > 2005-11-18 12:50:40.92 logon Login succeeded for user 'NT > > AUTHORITY\SYSTEM'. Connection: Trusted. > > 2005-11-18 12:51:01.35 logon Login succeeded for user 'NT > > AUTHORITY\SYSTEM'. Connection: Trusted. > > 2005-11-18 12:51:53.71 logon Login failed for user 'sa'. > > 2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'. > > Connection: Trusted. > > 2005-11-18 12:58:01.80 logon Login failed for user 'sa'. > > 2005-11-18 12:58:07.73 logon Login failed for user 'a'. > > 2005-11-18 12:58:16.75 logon Login failed for user 'a'. > > 2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'. > > Connection: Trusted. > > 2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'. > > Connection: Trusted. > > 2005-11-18 12:58:37.46 spid9 Starting up database 'test'. > > 2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf. > > 2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf. > > 2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'. > > Connection: Trusted. > > 2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'. > > Connection: Trusted. > > 2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'. > > Connection: Trusted. > > 2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w tilman'. > > Connection: Trusted. > > 2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w tilman'. > > Connection: Trusted. > > 2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version '1998.11.13' > > to > > execute extended stored procedure 'xp_msver'. > > > > > > Can connect with Windows NT authentication, but not with SQL server auth. > > So > > all my > > code has stopped working ... > > When I try to make a new SQL Server registration > > I get server does not exist or access denied... > > > > > > > >
If your server registration is using Windows authentication and also you can see the server properties that means that you are a member of the system administrators groups. Do not change the registration properties. Also, your server is running as the system account (Security tab). Do not change that either. Which account is not working? sa? Is it possible that the password was changed? Can you create, for testing purposes, another SQL Server login and connect with Query Analyzer using that login? Ben Nevarez [quoted text, click to view] "Barrett Bonden" <arthur@networks-cc.com> wrote in message news:jCQff.26341$rc7.2259@fe12.lga... > Ben: > > I see that I'm using both SQL Server and Windows authentication; I see > too > that under > "Startup service account" (also in the security tab) startup runs the > System Account. WHen I choose "This account" it defaults to "LocalSystem" > and a password I don't now - I'm scared to try this - > Under "registered SQL server properties" "Use windows NT authentication" > is checked. WHen I try to use SQL authenticaton nothing works - no matter > what > combo of login name and password I try .... > Should I try to make a new SQL server registration ? > > All this is clear as mud - if anyone from MS reads this; boys, why do you > have > to make it so hard, so confusing , so badly documented ? It's hard enough > using it > productivly when you can get it in in the first place ... > > > > > > > "Ben Nevarez" <bnevarez@sjm.com> wrote in message > news:#cQs$CX7FHA.3684@TK2MSFTNGP12.phx.gbl... >> >> Hi, >> >> Verify that you are using both SQL Server and Windows authentication >> using >> server Properties and look in the Security tab (I believe that you are >> really using both SQL Server and Windows authentication since log >> messages >> for Windows only authentication would show "Login failed for user 'sa'. >> Reason: Not associated with a trusted SQL Server connection"). >> >> Which account are you using to connect to the database? Has the password > for >> this account been changed? >> >> Ben Nevarez >> >> >> "Barrett Bonden" <arthur@networks-cc.com> wrote in message >> news:sIJff.13085$ha2.13022@fe08.lga... >> > 2005-11-18 12:50:12.09 logon Login failed for user 'sa'. >> > 2005-11-18 12:50:36.85 logon Login succeeded for user 'NT >> > AUTHORITY\SYSTEM'. Connection: Trusted. >> > >> > and some more that might be useful - >> > >> > 2005-11-18 12:50:40.92 logon Login succeeded for user 'NT >> > AUTHORITY\SYSTEM'. Connection: Trusted. >> > 2005-11-18 12:51:01.35 logon Login succeeded for user 'NT >> > AUTHORITY\SYSTEM'. Connection: Trusted. >> > 2005-11-18 12:51:53.71 logon Login failed for user 'sa'. >> > 2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'. >> > Connection: Trusted. >> > 2005-11-18 12:58:01.80 logon Login failed for user 'sa'. >> > 2005-11-18 12:58:07.73 logon Login failed for user 'a'. >> > 2005-11-18 12:58:16.75 logon Login failed for user 'a'. >> > 2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'. >> > Connection: Trusted. >> > 2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'. >> > Connection: Trusted. >> > 2005-11-18 12:58:37.46 spid9 Starting up database 'test'. >> > 2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf. >> > 2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf. >> > 2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'. >> > Connection: Trusted. >> > 2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'. >> > Connection: Trusted. >> > 2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'. >> > Connection: Trusted. >> > 2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w >> > tilman'. >> > Connection: Trusted. >> > 2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w >> > tilman'. >> > Connection: Trusted. >> > 2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version >> > '1998.11.13' >> > to >> > execute extended stored procedure 'xp_msver'. >> > >> > >> > Can connect with Windows NT authentication, but not with SQL server > auth. >> > So >> > all my >> > code has stopped working ... >> > When I try to make a new SQL Server registration >> > I get server does not exist or access denied... >> > >> > >> > >> >> > >
Many thanks for your help; I changed the password on the sa account, and it
now works , along, strangely , with the the other accounts I had set up. Clearly I need to learn more about this part of the program; so far I;ve just experimented with making it a backend for Access - [quoted text, click to view] "Ben Nevarez" <bnevarez@sjm.com> wrote in message news:OGo3LKa7FHA.1020@TK2MSFTNGP15.phx.gbl... > > If your server registration is using Windows authentication and also you can > see the server properties that means that you are a member of the system > administrators groups. Do not change the registration properties. > > Also, your server is running as the system account (Security tab). Do not > change that either. > > Which account is not working? sa? Is it possible that the password was > changed? > > Can you create, for testing purposes, another SQL Server login and connect > with Query Analyzer using that login? > > Ben Nevarez > > > > "Barrett Bonden" <arthur@networks-cc.com> wrote in message > news:jCQff.26341$rc7.2259@fe12.lga... > > Ben: > > > > I see that I'm using both SQL Server and Windows authentication; I see > > too > > that under > > "Startup service account" (also in the security tab) startup runs the > > System Account. WHen I choose "This account" it defaults to "LocalSystem" > > and a password I don't now - I'm scared to try this - > > Under "registered SQL server properties" "Use windows NT authentication" > > is checked. WHen I try to use SQL authenticaton nothing works - no matter > > what > > combo of login name and password I try .... > > Should I try to make a new SQL server registration ? > > > > All this is clear as mud - if anyone from MS reads this; boys, why do you > > have > > to make it so hard, so confusing , so badly documented ? It's hard enough > > using it > > productivly when you can get it in in the first place ... > > > > > > > > > > > > > > "Ben Nevarez" <bnevarez@sjm.com> wrote in message > > news:#cQs$CX7FHA.3684@TK2MSFTNGP12.phx.gbl... > >> > >> Hi, > >> > >> Verify that you are using both SQL Server and Windows authentication > >> using > >> server Properties and look in the Security tab (I believe that you are > >> really using both SQL Server and Windows authentication since log > >> messages > >> for Windows only authentication would show "Login failed for user 'sa'. > >> Reason: Not associated with a trusted SQL Server connection"). > >> > >> Which account are you using to connect to the database? Has the password > > for > >> this account been changed? > >> > >> Ben Nevarez > >> > >> > >> "Barrett Bonden" <arthur@networks-cc.com> wrote in message > >> news:sIJff.13085$ha2.13022@fe08.lga... > >> > 2005-11-18 12:50:12.09 logon Login failed for user 'sa'. > >> > 2005-11-18 12:50:36.85 logon Login succeeded for user 'NT > >> > AUTHORITY\SYSTEM'. Connection: Trusted. > >> > > >> > and some more that might be useful - > >> > > >> > 2005-11-18 12:50:40.92 logon Login succeeded for user 'NT > >> > AUTHORITY\SYSTEM'. Connection: Trusted. > >> > 2005-11-18 12:51:01.35 logon Login succeeded for user 'NT > >> > AUTHORITY\SYSTEM'. Connection: Trusted. > >> > 2005-11-18 12:51:53.71 logon Login failed for user 'sa'. > >> > 2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'. > >> > Connection: Trusted. > >> > 2005-11-18 12:58:01.80 logon Login failed for user 'sa'. > >> > 2005-11-18 12:58:07.73 logon Login failed for user 'a'. > >> > 2005-11-18 12:58:16.75 logon Login failed for user 'a'. > >> > 2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'. > >> > Connection: Trusted. > >> > 2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'. > >> > Connection: Trusted. > >> > 2005-11-18 12:58:37.46 spid9 Starting up database 'test'. > >> > 2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf. > >> > 2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf. > >> > 2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'. > >> > Connection: Trusted. > >> > 2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'. > >> > Connection: Trusted. > >> > 2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'. > >> > Connection: Trusted. > >> > 2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w > >> > tilman'. > >> > Connection: Trusted. > >> > 2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w > >> > tilman'. > >> > Connection: Trusted. > >> > 2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version > >> > '1998.11.13' > >> > to > >> > execute extended stored procedure 'xp_msver'. > >> > > >> > > >> > Can connect with Windows NT authentication, but not with SQL server > > auth. > >> > So > >> > all my > >> > code has stopped working ... > >> > When I try to make a new SQL Server registration > >> > I get server does not exist or access denied... > >> > > >> > > >> > > >> > >> > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
August 2008
| home · blog · groups | Questions? Comments? Contact the dn |