Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
LourivalAre both named instances or is one for them default instance and if so, whic
h is the default
instance? Is the SQL Server browser service started?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegroups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival|||OK, I thought it might be the SQL Browser service not started, but that shou
ld mean you can connect
to the default but not named. You seem to have the other way around. One mor
e thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>sql

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
LourivalAre both named instances or is one for them default instance and if so, which is the default
instance? Is the SQL Server browser service started?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegroups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival|||OK, I thought it might be the SQL Browser service not started, but that should mean you can connect
to the default but not named. You seem to have the other way around. One more thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
Lourival
Are both named instances or is one for them default instance and if so, which is the default
instance? Is the SQL Server browser service started?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegr oups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>
|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor
|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegr oups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>
|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival
|||OK, I thought it might be the SQL Browser service not started, but that should mean you can connect
to the default but not named. You seem to have the other way around. One more thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegr oups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>

Problems with SQL 2000 and 2005 on same machine - Cant connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.

Any idea? Have i to reinstall 2000?

Tks,
Lourival(lourivalsjr@.gmail.com) writes:
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?

Exactly which service-pack level of SQL 2000 do you have? You can view
this on the first line of
C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG
(if this is the instance directory for SQL 2000.)

I believe you need at least SP3 (8.00.760 to run in parallel with SQL 2005.)

Another thing to try is to open the Server and Client Network Utilities of
SQL 2000, and make sure that both use TCP/IP. For local connections,
shared memory is the default, but if it for some reason does not work, you
can try TCP/IP.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Problems with creating SQL server accounts with SQL express edition

I installed Visual Web Developer on my laptop running on Windows XP Professional (SP2). With this SQL server express edition too got installed. Then I installed SQL server management studio express to manage the databases

I used "windows authentication" to login the SQL server for the first time. Then I found sa password is already there. I was never given the opportunity to set this sa password during the installation. I tired to change it to my own password but I found that it's not accepting any changes.

Then I tired to create a SQL server account and try to login. I was not allowed. Then through MSDN I got to know that Express Edition does not support mixed mode authentication by default but I have to select that during the installation. But the problem is I was never given the opportunity to select this authentication mode during the install ion.

I tired changing the registry values ( set LoginMode to '2") as instructed in the MSDN to allowe mixed mode. Even after that still I'm not allowed to create sql server accounts with my own passwords. I'm allowed to create accounts but it doesn't allow me to set the password; every time I check it had replace the password I set to some unknown password which I cannot see due to masking.

Can anyone offer me some advice to understand what's happening?

aththidiyavidana:

I'm allowed to create accounts but it doesn't allow me to set the password; every time I check it had replace the password I set to some unknown password which I cannot see due to masking.

Sounds Strange Make sure you've restarted the SQL Express instance after you modify the Authentication Mode.

Did you mean the password of new created account will be replaced by an unkown string?

How do you know (Did you get an error when try to login SQL Server with the account and password you just create, or you just find the length of the password seems to be changed)?

If yes, what's error message? Something like "Login failed for user 'test'. The user is not associated with a trusted SQL Server connection" or looks like "Login failed for user 'test'. (Microsoft SQL Server, Error: 18456"?

|||

Thanks for the reply.

I have found out the reason for not getting a chance to set 'sa' password during the installation; By default it avoids the advanced configuration options. We have to uncheck the option to get the extra dialog boxes to select authentication modes. I was able to reinstall SQL Serve express with this option uncheck and managed set my own sa password.

But I still don't know why I was not allowed to change the sa password set by the installation program during my first attempt. Each time I tired to reset this password it gave me the impression that changes are accepted because no error messages were thrown. But when I accessed the properties again after the changes I realized that 'sa' password I submit had not been accepted

I don't think this is an error or a bug. I think this is how it works…it won't let me access the server using SQL server accounts or set/reset my own SQL server account passwords if "mixed mode" is not selected during the installation

Thanks again for the reply