Cannot Login as sa

SQL 2000 on Windows2003
When we remote desktop to our SQL server we cannot login using the “sa”
user. We get a message saying the user name or password is in error.
The “sa” has permissions to do anything on the database (Not my idea).
The
password is correct as I can login to Query Analyzer from my desktop using
“sa” and password.
The only user we can login as is administrator.
This issue seems to have caused an application to fail, as it uses the “sa
”
account.
Interestingly, we can log on to the original SQL Server, on Windows 2000,
using the “sa” user. The app works fine there. We migrated everything
to
w2003 last November. We could never login as “sa” but the app was okay.
During some vender work on the app, the "sa” password was changed, that br
oke
the app. We changed the password back, app is still broke. Vendor says it
is because we can’t log on as “sa”.
CrystalJimYou shouldn't be logging in as 'sa' anyway - it's a mark of laziness of
the developer that created the app. Anyway, <stepping down off my
hobby-horse> is the server in Windows Authentication mode or mixed
mode? You should be able to tell by executing this statement:
SELECT SERVERPROPERTY('IsIntegratedSecurityOnly
')
*mike hodgson*
http://sqlnerd.blogspot.com
CrystalJim wrote:

>SQL 2000 on Windows2003
>When we remote desktop to our SQL server we cannot login using the “sa”
>user. We get a message saying the user name or password is in error.
>The “sa” has permissions to do anything on the database (Not my idea).
The
>password is correct as I can login to Query Analyzer from my desktop using
>“sa” and password.
>The only user we can login as is administrator.
>This issue seems to have caused an application to fail, as it uses the “s
a”
>account.
>Interestingly, we can log on to the original SQL Server, on Windows 2000,
>using the “sa” user. The app works fine there. We migrated everything
to
>w2003 last November. We could never login as “sa” but the app was okay
.
>During some vender work on the app, the "sa” password was changed, that b
roke
>the app. We changed the password back, app is still broke. Vendor says it
>is because we can’t log on as “sa”.
>
>|||You shouldn't be logging in as 'sa' anyway - it's a mark of laziness of
the developer that created the app. Anyway, <stepping down off my
hobby-horse> is the server in Windows Authentication mode or mixed
mode? You should be able to tell by executing this statement:
SELECT SERVERPROPERTY('IsIntegratedSecurityOnly
')
*mike hodgson*
http://sqlnerd.blogspot.com
CrystalJim wrote:

>SQL 2000 on Windows2003
>When we remote desktop to our SQL server we cannot login using the “sa”
>user. We get a message saying the user name or password is in error.
>The “sa” has permissions to do anything on the database (Not my idea).
The
>password is correct as I can login to Query Analyzer from my desktop using
>“sa” and password.
>The only user we can login as is administrator.
>This issue seems to have caused an application to fail, as it uses the “s
a”
>account.
>Interestingly, we can log on to the original SQL Server, on Windows 2000,
>using the “sa” user. The app works fine there. We migrated everything
to
>w2003 last November. We could never login as “sa” but the app was okay
.
>During some vender work on the app, the "sa” password was changed, that b
roke
>the app. We changed the password back, app is still broke. Vendor says it
>is because we can’t log on as “sa”.
>
>