I have an installation program that during install was able to authenticate
to SQL 2000 and validate "sa" and password. But it won't do that on SQL
2005. The program installs directly on the same box as that the SQL runs. Is
there any reason why authentication should fail?
Comments Please,
Michael ValeCruzAre you getting an error back? Did you set an SA password when you
installed SQL2k5?|||No error other than invalid user name and password.
Yes the password is valid, I use it to connect with the SQL Server
Management Studio using SQL Server Authentication and the SA is set with
server role "sysadmin"
I am just wondering if there is something in SQL 2000 that is automatically
on that is not turned on in SQL 2005 for this authentication to take place.
"PSPDBA" <williambr@.state.pa.us> wrote in message
news:1147285864.526093.215500@.v46g2000cwv.googlegroups.com...
> Are you getting an error back? Did you set an SA password when you
> installed SQL2k5?
>|||You might want to check that the program isn't sending MachineName\sa
instead of sa. When connecting from the same machine, I can't think of
anything that needs to be turned on. Look through the Surface Area
Configuration Tool and see if theres something that stands out..|||I met install experience when I intalled first SQL Server 2005 and second
SQL Server 2000.
In this situation I think that SA direct to S2K5 by default
"PSPDBA"?? ??? ??:
> You might want to check that the program isn't sending MachineName\sa
> instead of sa. When connecting from the same machine, I can't think of
> anything that needs to be turned on. Look through the Surface Area
> Configuration Tool and see if theres something that stands out..
>
Thursday, March 22, 2012
authentication on SQL 2005
Labels:
authenticateto,
authentication,
database,
install,
installation,
microsoft,
mysql,
oracle,
password,
program,
server,
sql,
validate
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment