Friday, March 30, 2012
Protect and invirible Database from each other
I'm using Windows 2000 Server + SQL Server 2000 + updated SP
This server is our Web Hosting services and we have many database in SQL Ser
ver.
Each databases are belonged to each customer domains in this Server.
All customers work with SQL Server by using SQL Enterprise Manage to connect
to the Server via TCP/IP.
My problem is that, after customers connect to the SQL Server, they can see
every Databases' name and table name although I'd set the right of each cust
omer to be able to see only their own database.
I'd ask many SQL Experts but they said that if I used SQL Enterprise manager
to remote connect to the SQL Server, this senario could not be protected an
d let me ask Microsoft.
Using SQL Enterprise Manager is the easiest way for my customer to manage th
eir database, so if I let them use the SQL command line to connect to the SQ
L Server, no customers will use my service.
Please help.
Regards,
NeungThere is no way currently to stop them from seeing the other databases. But
unless you give them specific permissions they can not access or view the
data in them.
Andrew J. Kelly SQL MVP
"Neung" <Neung@.discussions.microsoft.com> wrote in message
news:F5F3F38C-8F8B-499F-8C9C-7BE19D350C9A@.microsoft.com...
> Hi,
> I'm using Windows 2000 Server + SQL Server 2000 + updated SP
> This server is our Web Hosting services and we have many database in SQL
Server.
> Each databases are belonged to each customer domains in this Server.
> All customers work with SQL Server by using SQL Enterprise Manage to
connect to the Server via TCP/IP.
> My problem is that, after customers connect to the SQL Server, they can
see every Databases' name and table name although I'd set the right of each
customer to be able to see only their own database.
> I'd ask many SQL Experts but they said that if I used SQL Enterprise
manager to remote connect to the SQL Server, this senario could not be
protected and let me ask Microsoft.
> Using SQL Enterprise Manager is the easiest way for my customer to manage
their database, so if I let them use the SQL command line to connect to the
SQL Server, no customers will use my service.
> Please help.
> Regards,
> Neung|||Thanks and hope it will be solved in the next version.
Regards,
Neung
"Andrew J. Kelly" wrote:
> There is no way currently to stop them from seeing the other databases. B
ut
> unless you give them specific permissions they can not access or view the
> data in them.
> --
> Andrew J. Kelly SQL MVP
>
> "Neung" <Neung@.discussions.microsoft.com> wrote in message
> news:F5F3F38C-8F8B-499F-8C9C-7BE19D350C9A@.microsoft.com...
> Server.
> connect to the Server via TCP/IP.
> see every Databases' name and table name although I'd set the right of eac
h
> customer to be able to see only their own database.
> manager to remote connect to the SQL Server, this senario could not be
> protected and let me ask Microsoft.
> their database, so if I let them use the SQL command line to connect to th
e
> SQL Server, no customers will use my service.
>
>|||Yes, SQL 2005 has a lot of improvements in this area.
Andrew J. Kelly SQL MVP
"Neung" <Neung@.discussions.microsoft.com> wrote in message
news:032A5CFE-D0D9-4727-8032-707D90436D80@.microsoft.com...[vbcol=seagreen]
> Thanks and hope it will be solved in the next version.
> Regards,
> Neung
>
> "Andrew J. Kelly" wrote:
>
But[vbcol=seagreen]
the[vbcol=seagreen]
SQL[vbcol=seagreen]
can[vbcol=seagreen]
each[vbcol=seagreen]
manage[vbcol=seagreen]
the[vbcol=seagreen]|||> My problem is that, after customers connect to the SQL Server, they can
see every Databases' name and table name although I'd set the right of each
customer to be able to see only their own database.
Although database names are visible, I would not expect users to be able to
see other database contents unless they have explicitly been granted access
or the 'guest' user is enabled in the other databases.
Hope this helps.
Dan Guzman
SQL Server MVP
"Neung" <Neung@.discussions.microsoft.com> wrote in message
news:F5F3F38C-8F8B-499F-8C9C-7BE19D350C9A@.microsoft.com...
> Hi,
> I'm using Windows 2000 Server + SQL Server 2000 + updated SP
> This server is our Web Hosting services and we have many database in SQL
Server.
> Each databases are belonged to each customer domains in this Server.
> All customers work with SQL Server by using SQL Enterprise Manage to
connect to the Server via TCP/IP.
> My problem is that, after customers connect to the SQL Server, they can
see every Databases' name and table name although I'd set the right of each
customer to be able to see only their own database.
> I'd ask many SQL Experts but they said that if I used SQL Enterprise
manager to remote connect to the SQL Server, this senario could not be
protected and let me ask Microsoft.
> Using SQL Enterprise Manager is the easiest way for my customer to manage
their database, so if I let them use the SQL command line to connect to the
SQL Server, no customers will use my service.
> Please help.
> Regards,
> Neung
PROS and CONS of seperate databases for CACHING...
Also, we will be integrating Community Server into this Web site. Ofcourse you know CS adds its own database objects which crowd up ourmain database objects.
We were thinking of giving CS its own database also; bad practice, or...it doesn't matter much?
Thank youIf for ASPSTATE, then a separate server (now or in the future) would improve scalability.
If you mean multiple instances of SQL Server on the same server box (SQL Server 2000 and 2005 standard and up), then it is not a good idea as there is an overhead (plus licensing cost).
If you mean multiple databases within the same SQL instance, then that is the way to go.|||multiple databases within the same instance of sql server if its on the same machine...
sort of like this...
BOX1-SQL1 (all in same instance of sql server)
caching db
state db
auditing db
BOX2-SQL2 (all in same instance of sql server)
web site db
forum db
So THATS the way to go? Eh?
|||bumpsql
Wednesday, March 28, 2012
Proplem on configure sql 2005 web synchronization
I have a problem when configure the sql 2005 web sychronization. I went
through the configure web synchronization wizard. When it runs, it should do
the following things.
1. Create the virtual directory
2. copy the ISAPI DLL
3. Enable web service extensions
4. set the server agent permissions
5. set the sanpshot directory permissions
6. set the snapshot share permissions
7. modify the virture directory configuration file
It encoounters error on step6, so all the previous steps are rolled back.
The wizard did not provide any good erorr information other than saying
"Setting the snapshot share permissions (Error)"
Please help if you have any ideas or even guesses.
Thanks,
Yong
Yong,
it'd be worth posting up in
http://communities.microsoft.com/new...2005&slcid=us.
My guess is that the user is not correctly authenticated, but I'll try to
repro.
HTH,
Paul Ibison SQL Server MVP,
www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
property probelm
Services. My problem is that when I move reports from the development machine
to the server, they lose properties, like font and can grow setttings. Please
help me identify the problem.
--
Thanks,
CGWNever mind... I was just missing a font on the other machine.
"CGW" wrote:
> We have a development machine, and a web server, both running SQL Reporting
> Services. My problem is that when I move reports from the development machine
> to the server, they lose properties, like font and can grow setttings. Please
> help me identify the problem.
> --
> Thanks,
> CGW
Monday, March 26, 2012
Properly connecting to multiple instancesof SQL servers
I did some changes to my server and now having trouble with connections.
Took off SQL 2000 and replaced it with SQL2005 Standard.
Got one web site with the following connection via ASP:
<%
Set conn = Server.CreateObject("ADODB.Connection")
conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
%>
This produces "Login Failed" and kept doing it no matter what I have changed
in SQL 2005.
After trying to connect with numerous failing trys, I put SQL 2000 back on.
I gave it the new instance name of SQL2000.
I tried the above, and also chaned it to the follow connections:
(GLOBAL-7XQWMEEO\SQL2000)
&
(SQL2000)
These two produced the error - "Server does not exist or access denied" and
'local' still produces "login failed."
What is the correct method?
Thanks,
GBIt appears that your SQL Server was configured for Windows authentication
only. That's the default. Use the Surface Area Configuration app to change
the authentication to Mixed.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <allGeek@.hownerdy.com> wrote in message
news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
Hello.
I did some changes to my server and now having trouble with connections.
Took off SQL 2000 and replaced it with SQL2005 Standard.
Got one web site with the following connection via ASP:
<%
Set conn = Server.CreateObject("ADODB.Connection")
conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
%>
This produces "Login Failed" and kept doing it no matter what I have changed
in SQL 2005.
After trying to connect with numerous failing trys, I put SQL 2000 back on.
I gave it the new instance name of SQL2000.
I tried the above, and also chaned it to the follow connections:
(GLOBAL-7XQWMEEO\SQL2000)
&
(SQL2000)
These two produced the error - "Server does not exist or access denied" and
'local' still produces "login failed."
What is the correct method?
Thanks,
GB|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
> It appears that your SQL Server was configured for Windows authentication
> only. That's the default. Use the Surface Area Configuration app to
> change
> the authentication to Mixed.
>
First thing I did.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
> Hello.
> I did some changes to my server and now having trouble with connections.
> Took off SQL 2000 and replaced it with SQL2005 Standard.
> Got one web site with the following connection via ASP:
> <%
> Set conn = Server.CreateObject("ADODB.Connection")
> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
> %>
> This produces "Login Failed" and kept doing it no matter what I have
> changed
> in SQL 2005.
> After trying to connect with numerous failing trys, I put SQL 2000 back
> on.
> I gave it the new instance name of SQL2000.
> I tried the above, and also chaned it to the follow connections:
> (GLOBAL-7XQWMEEO\SQL2000)
> &
> (SQL2000)
> These two produced the error - "Server does not exist or access denied"
> and
> 'local' still produces "login failed."
> What is the correct method?
> Thanks,
> GB
>
>|||How about with the SQL client tools? Just want to be sure it isn't the
OLEDB stuff.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <allGeek@.hownerdy.com> wrote in message
news:46b919a4$0$4680$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
> It appears that your SQL Server was configured for Windows authentication
> only. That's the default. Use the Surface Area Configuration app to
> change
> the authentication to Mixed.
>
First thing I did.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
> Hello.
> I did some changes to my server and now having trouble with connections.
> Took off SQL 2000 and replaced it with SQL2005 Standard.
> Got one web site with the following connection via ASP:
> <%
> Set conn = Server.CreateObject("ADODB.Connection")
> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
> %>
> This produces "Login Failed" and kept doing it no matter what I have
> changed
> in SQL 2005.
> After trying to connect with numerous failing trys, I put SQL 2000 back
> on.
> I gave it the new instance name of SQL2000.
> I tried the above, and also chaned it to the follow connections:
> (GLOBAL-7XQWMEEO\SQL2000)
> &
> (SQL2000)
> These two produced the error - "Server does not exist or access denied"
> and
> 'local' still produces "login failed."
> What is the correct method?
> Thanks,
> GB
>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
> How about with the SQL client tools? Just want to be sure it isn't the
> OLEDB stuff.
>
Yes, I check under both 2000/2005.
Both seem to be set correctly.
I even tried to make user Windows user acount instead of using the SQL
login.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
> First thing I did.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000 back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>|||Try this...
"Provider=SQLOleDb; Data Source =(local); Database=Motorhome;
Trusted_Connection=yes;UID=xxxxxxxx;Password=xxxxxx"
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"GeekBoy" wrote:
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
> > How about with the SQL client tools? Just want to be sure it isn't the
> > OLEDB stuff.
> >
> >
> Yes, I check under both 2000/2005.
> Both seem to be set correctly.
> I even tried to make user Windows user acount instead of using the SQL
> login.
>
> > --
> > Tom
> >
> > ----
> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> > SQL Server MVP
> > Toronto, ON Canada
> > https://mvp.support.microsoft.com/profile/Tom.Moreau
> >
> >
> > "GeekBoy" <allGeek@.hownerdy.com> wrote in message
> > news:46b919a4$0$4680$4c368faf@.roadrunner.com...
> >
> > "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> > news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
> >> It appears that your SQL Server was configured for Windows authentication
> >> only. That's the default. Use the Surface Area Configuration app to
> >> change
> >> the authentication to Mixed.
> >>
> >
> > First thing I did.
> >
> >
> >> --
> >> Tom
> >>
> >> ----
> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> >> SQL Server MVP
> >> Toronto, ON Canada
> >> https://mvp.support.microsoft.com/profile/Tom.Moreau
> >>
> >>
> >> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
> >> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
> >> Hello.
> >>
> >> I did some changes to my server and now having trouble with connections.
> >>
> >> Took off SQL 2000 and replaced it with SQL2005 Standard.
> >>
> >> Got one web site with the following connection via ASP:
> >>
> >> <%
> >> Set conn = Server.CreateObject("ADODB.Connection")
> >>
> >> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
> >> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
> >> %>
> >>
> >> This produces "Login Failed" and kept doing it no matter what I have
> >> changed
> >> in SQL 2005.
> >>
> >> After trying to connect with numerous failing trys, I put SQL 2000 back
> >> on.
> >> I gave it the new instance name of SQL2000.
> >> I tried the above, and also chaned it to the follow connections:
> >>
> >> (GLOBAL-7XQWMEEO\SQL2000)
> >> &
> >> (SQL2000)
> >>
> >> These two produced the error - "Server does not exist or access denied"
> >> and
> >> 'local' still produces "login failed."
> >>
> >> What is the correct method?
> >>
> >> Thanks,
> >>
> >> GB
> >>
> >>
> >>
> >
> >
>
>|||"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2EB663D4-30BB-4353-B61E-EE574D883ED3@.microsoft.com...
> Try this...
> "Provider=SQLOleDb; Data Source =(local); Database=Motorhome;
> Trusted_Connection=yes;UID=xxxxxxxx;Password=xxxxxx"
Still not functioning,
I still need to know how to properly label the instance of "SQL2000," while
'local' is pointing to SQL 2005.
Though I did try to run another copy of the database in SQL 2005, still
getting same response.
Thanks
>
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread and
> time
> asking back if its 2000 or 2005]
>
> "GeekBoy" wrote:
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> > How about with the SQL client tools? Just want to be sure it isn't the
>> > OLEDB stuff.
>> >
>> >
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> > --
>> > Tom
>> >
>> > ----
>> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> > SQL Server MVP
>> > Toronto, ON Canada
>> > https://mvp.support.microsoft.com/profile/Tom.Moreau
>> >
>> >
>> > "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> > news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> >
>> > "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> > news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> >> It appears that your SQL Server was configured for Windows
>> >> authentication
>> >> only. That's the default. Use the Surface Area Configuration app to
>> >> change
>> >> the authentication to Mixed.
>> >>
>> >
>> > First thing I did.
>> >
>> >
>> >> --
>> >> Tom
>> >>
>> >> ----
>> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> >> SQL Server MVP
>> >> Toronto, ON Canada
>> >> https://mvp.support.microsoft.com/profile/Tom.Moreau
>> >>
>> >>
>> >> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> >> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> >> Hello.
>> >>
>> >> I did some changes to my server and now having trouble with
>> >> connections.
>> >>
>> >> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> >>
>> >> Got one web site with the following connection via ASP:
>> >>
>> >> <%
>> >> Set conn = Server.CreateObject("ADODB.Connection")
>> >>
>> >> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> >> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> >> %>
>> >>
>> >> This produces "Login Failed" and kept doing it no matter what I have
>> >> changed
>> >> in SQL 2005.
>> >>
>> >> After trying to connect with numerous failing trys, I put SQL 2000
>> >> back
>> >> on.
>> >> I gave it the new instance name of SQL2000.
>> >> I tried the above, and also chaned it to the follow connections:
>> >>
>> >> (GLOBAL-7XQWMEEO\SQL2000)
>> >> &
>> >> (SQL2000)
>> >>
>> >> These two produced the error - "Server does not exist or access
>> >> denied"
>> >> and
>> >> 'local' still produces "login failed."
>> >>
>> >> What is the correct method?
>> >>
>> >> Thanks,
>> >>
>> >> GB
>> >>
>> >>
>> >>
>> >
>> >
>>|||From a command prompt, could you run:
NET START
... and post the parts that mention SQL Server.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <allGeek@.hownerdy.com> wrote in message
news:46b921f0$0$8926$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
> How about with the SQL client tools? Just want to be sure it isn't the
> OLEDB stuff.
>
Yes, I check under both 2000/2005.
Both seem to be set correctly.
I even tried to make user Windows user acount instead of using the SQL
login.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
> First thing I did.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000 back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
> From a command prompt, could you run:
> NET START
> ... and post the parts that mention SQL Server.
Here is is:
SQL Server (MSSQLSERVER)
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server FullText Search (MSSQLSERVER)
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't the
>> OLEDB stuff.
>>
> Yes, I check under both 2000/2005.
> Both seem to be set correctly.
> I even tried to make user Windows user acount instead of using the SQL
> login.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows
>> authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
>>
>> First thing I did.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000 back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>>
>|||OK, that means that you are using a default instance. When you connect via
SSMS, while logged on directly at the box, what do you type into the Server
box? Have you tried just typing a dot:
.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46ba482f$0$3159$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
> From a command prompt, could you run:
> NET START
> ... and post the parts that mention SQL Server.
Here is is:
SQL Server (MSSQLSERVER)
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server FullText Search (MSSQLSERVER)
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't the
>> OLEDB stuff.
>>
> Yes, I check under both 2000/2005.
> Both seem to be set correctly.
> I even tried to make user Windows user acount instead of using the SQL
> login.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows
>> authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
>>
>> First thing I did.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000 back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
> OK, that means that you are using a default instance. When you connect
> via
> SSMS, while logged on directly at the box, what do you type into the
> Server
> box? Have you tried just typing a dot:
>
I don't type in anything. The boxes are already filled in and logg in using
a user account that has admin privleges.
never mind. Gosh how stupid.
The SQL2000 instance was not running in the services.
However, it still does not explain why I could not use 2005 to log in with
the the first error I received.
> .
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
> Here is is:
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Services (MSSQLSERVER)
> SQL Server Browser
> SQL Server FullText Search (MSSQLSERVER)
> SQL Server Integration Services
> SQL Server Reporting Services (MSSQLSERVER)
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't the
>> OLEDB stuff.
>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows
>> authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
>>
>> First thing I did.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with
>> connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000 back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>>
>>
>|||OK, I'm a bit lost now. You can connect now, right? You have only one
instance on the box now and it's SQL 2000, right? You're just asking what
the problem was when logging into a SQL 2005 instance with SSMS? I guess
since the instance is gone, we won't be able to troubleshoot that one.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
> OK, that means that you are using a default instance. When you connect
> via
> SSMS, while logged on directly at the box, what do you type into the
> Server
> box? Have you tried just typing a dot:
>
I don't type in anything. The boxes are already filled in and logg in using
a user account that has admin privleges.
never mind. Gosh how stupid.
The SQL2000 instance was not running in the services.
However, it still does not explain why I could not use 2005 to log in with
the the first error I received.
> .
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
> Here is is:
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Services (MSSQLSERVER)
> SQL Server Browser
> SQL Server FullText Search (MSSQLSERVER)
> SQL Server Integration Services
> SQL Server Reporting Services (MSSQLSERVER)
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't the
>> OLEDB stuff.
>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows
>> authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
>>
>> First thing I did.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with
>> connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000 back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>>
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
> OK, I'm a bit lost now. You can connect now, right? You have only one
> instance on the box now and it's SQL 2000, right? You're just asking what
> the problem was when logging into a SQL 2005 instance with SSMS? I guess
> since the instance is gone, we won't be able to troubleshoot that one.
I have 2 instances running.
The SQL2000 one was not running because in the services it was set to manual
start.
So now I have both of them running.
I have not had any problem with SSMS, it was with ASP logging in using an
SQL account.
Strange thing is I set up the database up using SSMS on version 9 (2005) SQL
server.
So now I don't know what is going on.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
> I don't type in anything. The boxes are already filled in and logg in
> using
> a user account that has admin privleges.
> never mind. Gosh how stupid.
> The SQL2000 instance was not running in the services.
> However, it still does not explain why I could not use 2005 to log in with
> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't the
>> OLEDB stuff.
>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows
>> authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
>>
>> First thing I did.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with
>> connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000
>> back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access
>> denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>>
>>
>>
>|||Was ASP running on the same box or a different one?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46ba688f$0$12176$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
> OK, I'm a bit lost now. You can connect now, right? You have only one
> instance on the box now and it's SQL 2000, right? You're just asking what
> the problem was when logging into a SQL 2005 instance with SSMS? I guess
> since the instance is gone, we won't be able to troubleshoot that one.
I have 2 instances running.
The SQL2000 one was not running because in the services it was set to manual
start.
So now I have both of them running.
I have not had any problem with SSMS, it was with ASP logging in using an
SQL account.
Strange thing is I set up the database up using SSMS on version 9 (2005) SQL
server.
So now I don't know what is going on.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
> I don't type in anything. The boxes are already filled in and logg in
> using
> a user account that has admin privleges.
> never mind. Gosh how stupid.
> The SQL2000 instance was not running in the services.
> However, it still does not explain why I could not use 2005 to log in with
> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't the
>> OLEDB stuff.
>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows
>> authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
>>
>> First thing I did.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with
>> connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000
>> back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access
>> denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>>
>>
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
> Was ASP running on the same box or a different one?
Same one.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I guess
>> since the instance is gone, we won't be able to troubleshoot that one.
> I have 2 instances running.
> The SQL2000 one was not running because in the services it was set to
> manual
> start.
> So now I have both of them running.
> I have not had any problem with SSMS, it was with ASP logging in using an
> SQL account.
> Strange thing is I set up the database up using SSMS on version 9 (2005)
> SQL
> server.
> So now I don't know what is going on.
>
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't
>> the
>> OLEDB stuff.
>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows
>> authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
>>
>> First thing I did.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with
>> connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000
>> back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access
>> denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>>
>>
>>
>>
>|||Dunno what to say. Can't troubleshoot without it being there. I guess you
could always add a 2005 instance and see if you can repro it.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <geek@.boy.com> wrote in message
news:46ba775e$0$28682$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
> Was ASP running on the same box or a different one?
Same one.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I guess
>> since the instance is gone, we won't be able to troubleshoot that one.
> I have 2 instances running.
> The SQL2000 one was not running because in the services it was set to
> manual
> start.
> So now I have both of them running.
> I have not had any problem with SSMS, it was with ASP logging in using an
> SQL account.
> Strange thing is I set up the database up using SSMS on version 9 (2005)
> SQL
> server.
> So now I don't know what is going on.
>
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't
>> the
>> OLEDB stuff.
>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> It appears that your SQL Server was configured for Windows
>> authentication
>> only. That's the default. Use the Surface Area Configuration app to
>> change
>> the authentication to Mixed.
>>
>> First thing I did.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>> Hello.
>> I did some changes to my server and now having trouble with
>> connections.
>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>> Got one web site with the following connection via ASP:
>> <%
>> Set conn = Server.CreateObject("ADODB.Connection")
>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>> %>
>> This produces "Login Failed" and kept doing it no matter what I have
>> changed
>> in SQL 2005.
>> After trying to connect with numerous failing trys, I put SQL 2000
>> back
>> on.
>> I gave it the new instance name of SQL2000.
>> I tried the above, and also chaned it to the follow connections:
>> (GLOBAL-7XQWMEEO\SQL2000)
>> &
>> (SQL2000)
>> These two produced the error - "Server does not exist or access
>> denied"
>> and
>> 'local' still produces "login failed."
>> What is the correct method?
>> Thanks,
>> GB
>>
>>
>>
>>
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
> Dunno what to say. Can't troubleshoot without it being there. I guess
> you
> could always add a 2005 instance and see if you can repro it.
>
The local is the 2005 instance while "SQL2000" is the 2000 SQL instance.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <geek@.boy.com> wrote in message
> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>
> Same one.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I
>> guess
>> since the instance is gone, we won't be able to troubleshoot that one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in using an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9 (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't
>> the
>> OLEDB stuff.
>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> It appears that your SQL Server was configured for Windows
>>> authentication
>>> only. That's the default. Use the Surface Area Configuration app
>>> to
>>> change
>>> the authentication to Mixed.
>>>
>> First thing I did.
>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>> Hello.
>>>
>>> I did some changes to my server and now having trouble with
>>> connections.
>>>
>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>
>>> Got one web site with the following connection via ASP:
>>>
>>> <%
>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>
>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>> %>
>>>
>>> This produces "Login Failed" and kept doing it no matter what I have
>>> changed
>>> in SQL 2005.
>>>
>>> After trying to connect with numerous failing trys, I put SQL 2000
>>> back
>>> on.
>>> I gave it the new instance name of SQL2000.
>>> I tried the above, and also chaned it to the follow connections:
>>>
>>> (GLOBAL-7XQWMEEO\SQL2000)
>>> &
>>> (SQL2000)
>>>
>>> These two produced the error - "Server does not exist or access
>>> denied"
>>> and
>>> 'local' still produces "login failed."
>>>
>>> What is the correct method?
>>>
>>> Thanks,
>>>
>>> GB
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Now I'm more confused. How many instances are on the box? If it's more
than one, which SQL Servers are they and what are the instance names?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <geek@.boy.com> wrote in message
news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
> Dunno what to say. Can't troubleshoot without it being there. I guess
> you
> could always add a 2005 instance and see if you can repro it.
>
The local is the 2005 instance while "SQL2000" is the 2000 SQL instance.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <geek@.boy.com> wrote in message
> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>
> Same one.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I
>> guess
>> since the instance is gone, we won't be able to troubleshoot that one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in using an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9 (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>> How about with the SQL client tools? Just want to be sure it isn't
>> the
>> OLEDB stuff.
>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the SQL
>> login.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> It appears that your SQL Server was configured for Windows
>>> authentication
>>> only. That's the default. Use the Surface Area Configuration app
>>> to
>>> change
>>> the authentication to Mixed.
>>>
>> First thing I did.
>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>> Hello.
>>>
>>> I did some changes to my server and now having trouble with
>>> connections.
>>>
>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>
>>> Got one web site with the following connection via ASP:
>>>
>>> <%
>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>
>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>> %>
>>>
>>> This produces "Login Failed" and kept doing it no matter what I have
>>> changed
>>> in SQL 2005.
>>>
>>> After trying to connect with numerous failing trys, I put SQL 2000
>>> back
>>> on.
>>> I gave it the new instance name of SQL2000.
>>> I tried the above, and also chaned it to the follow connections:
>>>
>>> (GLOBAL-7XQWMEEO\SQL2000)
>>> &
>>> (SQL2000)
>>>
>>> These two produced the error - "Server does not exist or access
>>> denied"
>>> and
>>> 'local' still produces "login failed."
>>>
>>> What is the correct method?
>>>
>>> Thanks,
>>>
>>> GB
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
> Now I'm more confused. How many instances are on the box? If it's more
> than one, which SQL Servers are they and what are the instance names?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <geek@.boy.com> wrote in message
> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>
> The local is the 2005 instance while "SQL2000" is the 2000 SQL instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I
>> guess
>> since the instance is gone, we won't be able to troubleshoot that one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in using
>> an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9 (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you
>> connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>> How about with the SQL client tools? Just want to be sure it isn't
>>> the
>>> OLEDB stuff.
>>>
>>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the
>> SQL
>> login.
>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> It appears that your SQL Server was configured for Windows
>>> authentication
>>> only. That's the default. Use the Surface Area Configuration app
>>> to
>>> change
>>> the authentication to Mixed.
>>>
>>>
>>> First thing I did.
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>> Hello.
>>>
>>> I did some changes to my server and now having trouble with
>>> connections.
>>>
>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>
>>> Got one web site with the following connection via ASP:
>>>
>>> <%
>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>
>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>> %>
>>>
>>> This produces "Login Failed" and kept doing it no matter what I
>>> have
>>> changed
>>> in SQL 2005.
>>>
>>> After trying to connect with numerous failing trys, I put SQL 2000
>>> back
>>> on.
>>> I gave it the new instance name of SQL2000.
>>> I tried the above, and also chaned it to the follow connections:
>>>
>>> (GLOBAL-7XQWMEEO\SQL2000)
>>> &
>>> (SQL2000)
>>>
>>> These two produced the error - "Server does not exist or access
>>> denied"
>>> and
>>> 'local' still produces "login failed."
>>>
>>> What is the correct method?
>>>
>>> Thanks,
>>>
>>> GB
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||Which is the default instance and which is the named instance?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
> Now I'm more confused. How many instances are on the box? If it's more
> than one, which SQL Servers are they and what are the instance names?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <geek@.boy.com> wrote in message
> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>
> The local is the 2005 instance while "SQL2000" is the 2000 SQL instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I
>> guess
>> since the instance is gone, we won't be able to troubleshoot that one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in using
>> an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9 (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you
>> connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> From a command prompt, could you run:
>> NET START
>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>> How about with the SQL client tools? Just want to be sure it isn't
>>> the
>>> OLEDB stuff.
>>>
>>>
>> Yes, I check under both 2000/2005.
>> Both seem to be set correctly.
>> I even tried to make user Windows user acount instead of using the
>> SQL
>> login.
>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> It appears that your SQL Server was configured for Windows
>>> authentication
>>> only. That's the default. Use the Surface Area Configuration app
>>> to
>>> change
>>> the authentication to Mixed.
>>>
>>>
>>> First thing I did.
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>> Hello.
>>>
>>> I did some changes to my server and now having trouble with
>>> connections.
>>>
>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>
>>> Got one web site with the following connection via ASP:
>>>
>>> <%
>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>
>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>> %>
>>>
>>> This produces "Login Failed" and kept doing it no matter what I
>>> have
>>> changed
>>> in SQL 2005.
>>>
>>> After trying to connect with numerous failing trys, I put SQL 2000
>>> back
>>> on.
>>> I gave it the new instance name of SQL2000.
>>> I tried the above, and also chaned it to the follow connections:
>>>
>>> (GLOBAL-7XQWMEEO\SQL2000)
>>> &
>>> (SQL2000)
>>>
>>> These two produced the error - "Server does not exist or access
>>> denied"
>>> and
>>> 'local' still produces "login failed."
>>>
>>> What is the correct method?
>>>
>>> Thanks,
>>>
>>> GB
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||2005 is default while "SQL2000" is the named.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
> Which is the default instance and which is the named instance?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only
>> one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I
>> guess
>> since the instance is gone, we won't be able to troubleshoot that one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in using
>> an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9
>> (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you
>> connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>> From a command prompt, could you run:
>>>
>>> NET START
>>>
>>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>> How about with the SQL client tools? Just want to be sure it isn't
>>> the
>>> OLEDB stuff.
>>>
>>>
>>> Yes, I check under both 2000/2005.
>>> Both seem to be set correctly.
>>>
>>> I even tried to make user Windows user acount instead of using the
>>> SQL
>>> login.
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> It appears that your SQL Server was configured for Windows
>>> authentication
>>> only. That's the default. Use the Surface Area Configuration app
>>> to
>>> change
>>> the authentication to Mixed.
>>>
>>>
>>> First thing I did.
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>> Hello.
>>>
>>> I did some changes to my server and now having trouble with
>>> connections.
>>>
>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>
>>> Got one web site with the following connection via ASP:
>>>
>>> <%
>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>
>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>> %>
>>>
>>> This produces "Login Failed" and kept doing it no matter what I
>>> have
>>> changed
>>> in SQL 2005.
>>>
>>> After trying to connect with numerous failing trys, I put SQL 2000
>>> back
>>> on.
>>> I gave it the new instance name of SQL2000.
>>> I tried the above, and also chaned it to the follow connections:
>>>
>>> (GLOBAL-7XQWMEEO\SQL2000)
>>> &
>>> (SQL2000)
>>>
>>> These two produced the error - "Server does not exist or access
>>> denied"
>>> and
>>> 'local' still produces "login failed."
>>>
>>> What is the correct method?
>>>
>>> Thanks,
>>>
>>> GB
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||OK, so you can connect to both of the following:
.
.\SQL2000
Correct?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46bb7068$0$30668$4c368faf@.roadrunner.com...
2005 is default while "SQL2000" is the named.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
> Which is the default instance and which is the named instance?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only
>> one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I
>> guess
>> since the instance is gone, we won't be able to troubleshoot that one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in using
>> an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9
>> (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>> OK, that means that you are using a default instance. When you
>> connect
>> via
>> SSMS, while logged on directly at the box, what do you type into the
>> Server
>> box? Have you tried just typing a dot:
>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>> .
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>> From a command prompt, could you run:
>>>
>>> NET START
>>>
>>> ... and post the parts that mention SQL Server.
>> Here is is:
>> SQL Server (MSSQLSERVER)
>> SQL Server Analysis Services (MSSQLSERVER)
>> SQL Server Browser
>> SQL Server FullText Search (MSSQLSERVER)
>> SQL Server Integration Services
>> SQL Server Reporting Services (MSSQLSERVER)
>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>> How about with the SQL client tools? Just want to be sure it isn't
>>> the
>>> OLEDB stuff.
>>>
>>>
>>> Yes, I check under both 2000/2005.
>>> Both seem to be set correctly.
>>>
>>> I even tried to make user Windows user acount instead of using the
>>> SQL
>>> login.
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> It appears that your SQL Server was configured for Windows
>>> authentication
>>> only. That's the default. Use the Surface Area Configuration app
>>> to
>>> change
>>> the authentication to Mixed.
>>>
>>>
>>> First thing I did.
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>> Hello.
>>>
>>> I did some changes to my server and now having trouble with
>>> connections.
>>>
>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>
>>> Got one web site with the following connection via ASP:
>>>
>>> <%
>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>
>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>> %>
>>>
>>> This produces "Login Failed" and kept doing it no matter what I
>>> have
>>> changed
>>> in SQL 2005.
>>>
>>> After trying to connect with numerous failing trys, I put SQL 2000
>>> back
>>> on.
>>> I gave it the new instance name of SQL2000.
>>> I tried the above, and also chaned it to the follow connections:
>>>
>>> (GLOBAL-7XQWMEEO\SQL2000)
>>> &
>>> (SQL2000)
>>>
>>> These two produced the error - "Server does not exist or access
>>> denied"
>>> and
>>> 'local' still produces "login failed."
>>>
>>> What is the correct method?
>>>
>>> Thanks,
>>>
>>> GB
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
> OK, so you can connect to both of the following:
> .
> .\SQL2000
> Correct?
>
I am familair with mySQL, but not MS SQL, so I do not know about the
reference you make concerning the way you are showing to connect.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
> 2005 is default while "SQL2000" is the named.
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only
>> one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I
>> guess
>> since the instance is gone, we won't be able to troubleshoot that
>> one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in using
>> an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9
>> (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>> OK, that means that you are using a default instance. When you
>>> connect
>>> via
>>> SSMS, while logged on directly at the box, what do you type into the
>>> Server
>>> box? Have you tried just typing a dot:
>>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>>> .
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>> From a command prompt, could you run:
>>>
>>> NET START
>>>
>>> ... and post the parts that mention SQL Server.
>>>
>>> Here is is:
>>>
>>> SQL Server (MSSQLSERVER)
>>> SQL Server Analysis Services (MSSQLSERVER)
>>> SQL Server Browser
>>> SQL Server FullText Search (MSSQLSERVER)
>>> SQL Server Integration Services
>>> SQL Server Reporting Services (MSSQLSERVER)
>>>
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>> How about with the SQL client tools? Just want to be sure it
>>> isn't
>>> the
>>> OLEDB stuff.
>>>
>>>
>>> Yes, I check under both 2000/2005.
>>> Both seem to be set correctly.
>>>
>>> I even tried to make user Windows user acount instead of using the
>>> SQL
>>> login.
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>> It appears that your SQL Server was configured for Windows
>>>> authentication
>>>> only. That's the default. Use the Surface Area Configuration
>>>> app
>>>> to
>>>> change
>>>> the authentication to Mixed.
>>>>
>>>
>>> First thing I did.
>>>
>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>> Hello.
>>>>
>>>> I did some changes to my server and now having trouble with
>>>> connections.
>>>>
>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>
>>>> Got one web site with the following connection via ASP:
>>>>
>>>> <%
>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>
>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>> %>
>>>>
>>>> This produces "Login Failed" and kept doing it no matter what I
>>>> have
>>>> changed
>>>> in SQL 2005.
>>>>
>>>> After trying to connect with numerous failing trys, I put SQL
>>>> 2000
>>>> back
>>>> on.
>>>> I gave it the new instance name of SQL2000.
>>>> I tried the above, and also chaned it to the follow connections:
>>>>
>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>> &
>>>> (SQL2000)
>>>>
>>>> These two produced the error - "Server does not exist or access
>>>> denied"
>>>> and
>>>> 'local' still produces "login failed."
>>>>
>>>> What is the correct method?
>>>>
>>>> Thanks,
>>>>
>>>> GB
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||When you use SSMS to connect to each of those instances while logged on
locally, what do you type into the Server text box? For the default (2005)
instance, it should be a dot. For the SQL 2000 instance, it should be
.\SQL2000. Have you tried that?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
> OK, so you can connect to both of the following:
> .
> .\SQL2000
> Correct?
>
I am familair with mySQL, but not MS SQL, so I do not know about the
reference you make concerning the way you are showing to connect.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
> 2005 is default while "SQL2000" is the named.
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> OK, I'm a bit lost now. You can connect now, right? You have only
>> one
>> instance on the box now and it's SQL 2000, right? You're just asking
>> what
>> the problem was when logging into a SQL 2005 instance with SSMS? I
>> guess
>> since the instance is gone, we won't be able to troubleshoot that
>> one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in using
>> an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9
>> (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>> OK, that means that you are using a default instance. When you
>>> connect
>>> via
>>> SSMS, while logged on directly at the box, what do you type into the
>>> Server
>>> box? Have you tried just typing a dot:
>>>
>> I don't type in anything. The boxes are already filled in and logg in
>> using
>> a user account that has admin privleges.
>> never mind. Gosh how stupid.
>> The SQL2000 instance was not running in the services.
>> However, it still does not explain why I could not use 2005 to log in
>> with
>> the the first error I received.
>>> .
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>> From a command prompt, could you run:
>>>
>>> NET START
>>>
>>> ... and post the parts that mention SQL Server.
>>>
>>> Here is is:
>>>
>>> SQL Server (MSSQLSERVER)
>>> SQL Server Analysis Services (MSSQLSERVER)
>>> SQL Server Browser
>>> SQL Server FullText Search (MSSQLSERVER)
>>> SQL Server Integration Services
>>> SQL Server Reporting Services (MSSQLSERVER)
>>>
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>> How about with the SQL client tools? Just want to be sure it
>>> isn't
>>> the
>>> OLEDB stuff.
>>>
>>>
>>> Yes, I check under both 2000/2005.
>>> Both seem to be set correctly.
>>>
>>> I even tried to make user Windows user acount instead of using the
>>> SQL
>>> login.
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>> It appears that your SQL Server was configured for Windows
>>>> authentication
>>>> only. That's the default. Use the Surface Area Configuration
>>>> app
>>>> to
>>>> change
>>>> the authentication to Mixed.
>>>>
>>>
>>> First thing I did.
>>>
>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>> Hello.
>>>>
>>>> I did some changes to my server and now having trouble with
>>>> connections.
>>>>
>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>
>>>> Got one web site with the following connection via ASP:
>>>>
>>>> <%
>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>
>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>> %>
>>>>
>>>> This produces "Login Failed" and kept doing it no matter what I
>>>> have
>>>> changed
>>>> in SQL 2005.
>>>>
>>>> After trying to connect with numerous failing trys, I put SQL
>>>> 2000
>>>> back
>>>> on.
>>>> I gave it the new instance name of SQL2000.
>>>> I tried the above, and also chaned it to the follow connections:
>>>>
>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>> &
>>>> (SQL2000)
>>>>
>>>> These two produced the error - "Server does not exist or access
>>>> denied"
>>>> and
>>>> 'local' still produces "login failed."
>>>>
>>>> What is the correct method?
>>>>
>>>> Thanks,
>>>>
>>>> GB
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
> When you use SSMS to connect to each of those instances while logged on
> locally, what do you type into the Server text box? For the default
> (2005)
> instance, it should be a dot. For the SQL 2000 instance, it should be
> .\SQL2000. Have you tried that?
>
I type in nothing. All the fields are already filled in.
Server Type: Database Engine
Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
Authentication: "my login user name"
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>
> I am familair with mySQL, but not MS SQL, so I do not know about the
> reference you make concerning the way you are showing to connect.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's
>> more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I
>> guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>> instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> OK, I'm a bit lost now. You can connect now, right? You have only
>>> one
>>> instance on the box now and it's SQL 2000, right? You're just
>>> asking
>>> what
>>> the problem was when logging into a SQL 2005 instance with SSMS? I
>>> guess
>>> since the instance is gone, we won't be able to troubleshoot that
>>> one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in
>> using
>> an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9
>> (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>> OK, that means that you are using a default instance. When you
>>> connect
>>> via
>>> SSMS, while logged on directly at the box, what do you type into
>>> the
>>> Server
>>> box? Have you tried just typing a dot:
>>>
>>>
>>> I don't type in anything. The boxes are already filled in and logg
>>> in
>>> using
>>> a user account that has admin privleges.
>>>
>>> never mind. Gosh how stupid.
>>> The SQL2000 instance was not running in the services.
>>>
>>> However, it still does not explain why I could not use 2005 to log
>>> in
>>> with
>>> the the first error I received.
>>>
>>> .
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>> From a command prompt, could you run:
>>>
>>> NET START
>>>
>>> ... and post the parts that mention SQL Server.
>>>
>>> Here is is:
>>>
>>> SQL Server (MSSQLSERVER)
>>> SQL Server Analysis Services (MSSQLSERVER)
>>> SQL Server Browser
>>> SQL Server FullText Search (MSSQLSERVER)
>>> SQL Server Integration Services
>>> SQL Server Reporting Services (MSSQLSERVER)
>>>
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>> How about with the SQL client tools? Just want to be sure it
>>>> isn't
>>>> the
>>>> OLEDB stuff.
>>>>
>>>>
>>> Yes, I check under both 2000/2005.
>>> Both seem to be set correctly.
>>>
>>> I even tried to make user Windows user acount instead of using the
>>> SQL
>>> login.
>>>
>>>
>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>> It appears that your SQL Server was configured for Windows
>>>> authentication
>>>> only. That's the default. Use the Surface Area Configuration
>>>> app
>>>> to
>>>> change
>>>> the authentication to Mixed.
>>>>
>>>>
>>>> First thing I did.
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>> Hello.
>>>>
>>>> I did some changes to my server and now having trouble with
>>>> connections.
>>>>
>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>
>>>> Got one web site with the following connection via ASP:
>>>>
>>>> <%
>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>
>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>> %>
>>>>
>>>> This produces "Login Failed" and kept doing it no matter what I
>>>> have
>>>> changed
>>>> in SQL 2005.
>>>>
>>>> After trying to connect with numerous failing trys, I put SQL
>>>> 2000
>>>> back
>>>> on.
>>>> I gave it the new instance name of SQL2000.
>>>> I tried the above, and also chaned it to the follow connections:
>>>>
>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>> &
>>>> (SQL2000)
>>>>
>>>> These two produced the error - "Server does not exist or access
>>>> denied"
>>>> and
>>>> 'local' still produces "login failed."
>>>>
>>>> What is the correct method?
>>>>
>>>> Thanks,
>>>>
>>>> GB
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||The second one should use a backslash, not a forward slash:
GLOBAL-7XQWMEEO\SQL2000
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
> When you use SSMS to connect to each of those instances while logged on
> locally, what do you type into the Server text box? For the default
> (2005)
> instance, it should be a dot. For the SQL 2000 instance, it should be
> .\SQL2000. Have you tried that?
>
I type in nothing. All the fields are already filled in.
Server Type: Database Engine
Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
Authentication: "my login user name"
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>
> I am familair with mySQL, but not MS SQL, so I do not know about the
> reference you make concerning the way you are showing to connect.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's
>> more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I
>> guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>> instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> OK, I'm a bit lost now. You can connect now, right? You have only
>>> one
>>> instance on the box now and it's SQL 2000, right? You're just
>>> asking
>>> what
>>> the problem was when logging into a SQL 2005 instance with SSMS? I
>>> guess
>>> since the instance is gone, we won't be able to troubleshoot that
>>> one.
>> I have 2 instances running.
>> The SQL2000 one was not running because in the services it was set to
>> manual
>> start.
>> So now I have both of them running.
>> I have not had any problem with SSMS, it was with ASP logging in
>> using
>> an
>> SQL account.
>> Strange thing is I set up the database up using SSMS on version 9
>> (2005)
>> SQL
>> server.
>> So now I don't know what is going on.
>>
>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>> OK, that means that you are using a default instance. When you
>>> connect
>>> via
>>> SSMS, while logged on directly at the box, what do you type into
>>> the
>>> Server
>>> box? Have you tried just typing a dot:
>>>
>>>
>>> I don't type in anything. The boxes are already filled in and logg
>>> in
>>> using
>>> a user account that has admin privleges.
>>>
>>> never mind. Gosh how stupid.
>>> The SQL2000 instance was not running in the services.
>>>
>>> However, it still does not explain why I could not use 2005 to log
>>> in
>>> with
>>> the the first error I received.
>>>
>>> .
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>> From a command prompt, could you run:
>>>
>>> NET START
>>>
>>> ... and post the parts that mention SQL Server.
>>>
>>> Here is is:
>>>
>>> SQL Server (MSSQLSERVER)
>>> SQL Server Analysis Services (MSSQLSERVER)
>>> SQL Server Browser
>>> SQL Server FullText Search (MSSQLSERVER)
>>> SQL Server Integration Services
>>> SQL Server Reporting Services (MSSQLSERVER)
>>>
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>> How about with the SQL client tools? Just want to be sure it
>>>> isn't
>>>> the
>>>> OLEDB stuff.
>>>>
>>>>
>>> Yes, I check under both 2000/2005.
>>> Both seem to be set correctly.
>>>
>>> I even tried to make user Windows user acount instead of using the
>>> SQL
>>> login.
>>>
>>>
>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>> It appears that your SQL Server was configured for Windows
>>>> authentication
>>>> only. That's the default. Use the Surface Area Configuration
>>>> app
>>>> to
>>>> change
>>>> the authentication to Mixed.
>>>>
>>>>
>>>> First thing I did.
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>> Hello.
>>>>
>>>> I did some changes to my server and now having trouble with
>>>> connections.
>>>>
>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>
>>>> Got one web site with the following connection via ASP:
>>>>
>>>> <%
>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>
>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>> %>
>>>>
>>>> This produces "Login Failed" and kept doing it no matter what I
>>>> have
>>>> changed
>>>> in SQL 2005.
>>>>
>>>> After trying to connect with numerous failing trys, I put SQL
>>>> 2000
>>>> back
>>>> on.
>>>> I gave it the new instance name of SQL2000.
>>>> I tried the above, and also chaned it to the follow connections:
>>>>
>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>> &
>>>> (SQL2000)
>>>>
>>>> These two produced the error - "Server does not exist or access
>>>> denied"
>>>> and
>>>> 'local' still produces "login failed."
>>>>
>>>> What is the correct method?
>>>>
>>>> Thanks,
>>>>
>>>> GB
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:el2J2hs2HHA.2064@.TK2MSFTNGP03.phx.gbl...
> The second one should use a backslash, not a forward slash:
> GLOBAL-7XQWMEEO\SQL2000
>
I did not put that in there, the system does and it works fine.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
>> When you use SSMS to connect to each of those instances while logged on
>> locally, what do you type into the Server text box? For the default
>> (2005)
>> instance, it should be a dot. For the SQL 2000 instance, it should be
>> .\SQL2000. Have you tried that?
>
> I type in nothing. All the fields are already filled in.
> Server Type: Database Engine
> Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
> Authentication: "my login user name"
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>>
>> I am familair with mySQL, but not MS SQL, so I do not know about the
>> reference you make concerning the way you are showing to connect.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's
>> more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I
>> guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>> instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> OK, I'm a bit lost now. You can connect now, right? You have only
>>> one
>>> instance on the box now and it's SQL 2000, right? You're just
>>> asking
>>> what
>>> the problem was when logging into a SQL 2005 instance with SSMS? I
>>> guess
>>> since the instance is gone, we won't be able to troubleshoot that
>>> one.
>>>
>>> I have 2 instances running.
>>> The SQL2000 one was not running because in the services it was set
>>> to
>>> manual
>>> start.
>>> So now I have both of them running.
>>>
>>> I have not had any problem with SSMS, it was with ASP logging in
>>> using
>>> an
>>> SQL account.
>>>
>>> Strange thing is I set up the database up using SSMS on version 9
>>> (2005)
>>> SQL
>>> server.
>>>
>>> So now I don't know what is going on.
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>> OK, that means that you are using a default instance. When you
>>> connect
>>> via
>>> SSMS, while logged on directly at the box, what do you type into
>>> the
>>> Server
>>> box? Have you tried just typing a dot:
>>>
>>>
>>> I don't type in anything. The boxes are already filled in and logg
>>> in
>>> using
>>> a user account that has admin privleges.
>>>
>>> never mind. Gosh how stupid.
>>> The SQL2000 instance was not running in the services.
>>>
>>> However, it still does not explain why I could not use 2005 to log
>>> in
>>> with
>>> the the first error I received.
>>>
>>> .
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>>> From a command prompt, could you run:
>>>>
>>>> NET START
>>>>
>>>> ... and post the parts that mention SQL Server.
>>>
>>> Here is is:
>>>
>>> SQL Server (MSSQLSERVER)
>>> SQL Server Analysis Services (MSSQLSERVER)
>>> SQL Server Browser
>>> SQL Server FullText Search (MSSQLSERVER)
>>> SQL Server Integration Services
>>> SQL Server Reporting Services (MSSQLSERVER)
>>>
>>>
>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>> How about with the SQL client tools? Just want to be sure it
>>>> isn't
>>>> the
>>>> OLEDB stuff.
>>>>
>>>>
>>>> Yes, I check under both 2000/2005.
>>>> Both seem to be set correctly.
>>>>
>>>> I even tried to make user Windows user acount instead of using
>>>> the
>>>> SQL
>>>> login.
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>> It appears that your SQL Server was configured for Windows
>>>> authentication
>>>> only. That's the default. Use the Surface Area Configuration
>>>> app
>>>> to
>>>> change
>>>> the authentication to Mixed.
>>>>
>>>>
>>>> First thing I did.
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>> Hello.
>>>>
>>>> I did some changes to my server and now having trouble with
>>>> connections.
>>>>
>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>
>>>> Got one web site with the following connection via ASP:
>>>>
>>>> <%
>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>
>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>> %>
>>>>
>>>> This produces "Login Failed" and kept doing it no matter what I
>>>> have
>>>> changed
>>>> in SQL 2005.
>>>>
>>>> After trying to connect with numerous failing trys, I put SQL
>>>> 2000
>>>> back
>>>> on.
>>>> I gave it the new instance name of SQL2000.
>>>> I tried the above, and also chaned it to the follow
>>>> connections:
>>>>
>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>> &
>>>> (SQL2000)
>>>>
>>>> These two produced the error - "Server does not exist or access
>>>> denied"
>>>> and
>>>> 'local' still produces "login failed."
>>>>
>>>> What is the correct method?
>>>>
>>>> Thanks,
>>>>
>>>> GB
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||So I take it that there is no longer a problem?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46bb8b06$0$29656$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:el2J2hs2HHA.2064@.TK2MSFTNGP03.phx.gbl...
> The second one should use a backslash, not a forward slash:
> GLOBAL-7XQWMEEO\SQL2000
>
I did not put that in there, the system does and it works fine.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
>> When you use SSMS to connect to each of those instances while logged on
>> locally, what do you type into the Server text box? For the default
>> (2005)
>> instance, it should be a dot. For the SQL 2000 instance, it should be
>> .\SQL2000. Have you tried that?
>
> I type in nothing. All the fields are already filled in.
> Server Type: Database Engine
> Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
> Authentication: "my login user name"
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>>
>> I am familair with mySQL, but not MS SQL, so I do not know about the
>> reference you make concerning the way you are showing to connect.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's
>> more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>> Dunno what to say. Can't troubleshoot without it being there. I
>> guess
>> you
>> could always add a 2005 instance and see if you can repro it.
>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>> instance.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> Was ASP running on the same box or a different one?
>>
>> Same one.
>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> OK, I'm a bit lost now. You can connect now, right? You have only
>>> one
>>> instance on the box now and it's SQL 2000, right? You're just
>>> asking
>>> what
>>> the problem was when logging into a SQL 2005 instance with SSMS? I
>>> guess
>>> since the instance is gone, we won't be able to troubleshoot that
>>> one.
>>>
>>> I have 2 instances running.
>>> The SQL2000 one was not running because in the services it was set
>>> to
>>> manual
>>> start.
>>> So now I have both of them running.
>>>
>>> I have not had any problem with SSMS, it was with ASP logging in
>>> using
>>> an
>>> SQL account.
>>>
>>> Strange thing is I set up the database up using SSMS on version 9
>>> (2005)
>>> SQL
>>> server.
>>>
>>> So now I don't know what is going on.
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>> OK, that means that you are using a default instance. When you
>>> connect
>>> via
>>> SSMS, while logged on directly at the box, what do you type into
>>> the
>>> Server
>>> box? Have you tried just typing a dot:
>>>
>>>
>>> I don't type in anything. The boxes are already filled in and logg
>>> in
>>> using
>>> a user account that has admin privleges.
>>>
>>> never mind. Gosh how stupid.
>>> The SQL2000 instance was not running in the services.
>>>
>>> However, it still does not explain why I could not use 2005 to log
>>> in
>>> with
>>> the the first error I received.
>>>
>>> .
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>>> From a command prompt, could you run:
>>>>
>>>> NET START
>>>>
>>>> ... and post the parts that mention SQL Server.
>>>
>>> Here is is:
>>>
>>> SQL Server (MSSQLSERVER)
>>> SQL Server Analysis Services (MSSQLSERVER)
>>> SQL Server Browser
>>> SQL Server FullText Search (MSSQLSERVER)
>>> SQL Server Integration Services
>>> SQL Server Reporting Services (MSSQLSERVER)
>>>
>>>
>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>> How about with the SQL client tools? Just want to be sure it
>>>> isn't
>>>> the
>>>> OLEDB stuff.
>>>>
>>>>
>>>> Yes, I check under both 2000/2005.
>>>> Both seem to be set correctly.
>>>>
>>>> I even tried to make user Windows user acount instead of using
>>>> the
>>>> SQL
>>>> login.
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>> It appears that your SQL Server was configured for Windows
>>>> authentication
>>>> only. That's the default. Use the Surface Area Configuration
>>>> app
>>>> to
>>>> change
>>>> the authentication to Mixed.
>>>>
>>>>
>>>> First thing I did.
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>> Hello.
>>>>
>>>> I did some changes to my server and now having trouble with
>>>> connections.
>>>>
>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>
>>>> Got one web site with the following connection via ASP:
>>>>
>>>> <%
>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>
>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>> %>
>>>>
>>>> This produces "Login Failed" and kept doing it no matter what I
>>>> have
>>>> changed
>>>> in SQL 2005.
>>>>
>>>> After trying to connect with numerous failing trys, I put SQL
>>>> 2000
>>>> back
>>>> on.
>>>> I gave it the new instance name of SQL2000.
>>>> I tried the above, and also chaned it to the follow
>>>> connections:
>>>>
>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>> &
>>>> (SQL2000)
>>>>
>>>> These two produced the error - "Server does not exist or access
>>>> denied"
>>>> and
>>>> 'local' still produces "login failed."
>>>>
>>>> What is the correct method?
>>>>
>>>> Thanks,
>>>>
>>>> GB
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||Not since I started the SQL2000 instance in the server in "services."
Hence Why I ask why the databse is functioning now, when the SQL2000
instance was not running, but the database is setup in the SQL 2005
instance.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:O6IL4Bt2HHA.4880@.TK2MSFTNGP03.phx.gbl...
> So I take it that there is no longer a problem?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb8b06$0$29656$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:el2J2hs2HHA.2064@.TK2MSFTNGP03.phx.gbl...
>> The second one should use a backslash, not a forward slash:
>> GLOBAL-7XQWMEEO\SQL2000
> I did not put that in there, the system does and it works fine.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
>> When you use SSMS to connect to each of those instances while logged on
>> locally, what do you type into the Server text box? For the default
>> (2005)
>> instance, it should be a dot. For the SQL 2000 instance, it should be
>> .\SQL2000. Have you tried that?
>>
>>
>> I type in nothing. All the fields are already filled in.
>> Server Type: Database Engine
>> Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
>> Authentication: "my login user name"
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>>
>> I am familair with mySQL, but not MS SQL, so I do not know about the
>> reference you make concerning the way you are showing to connect.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's
>> more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>>> Dunno what to say. Can't troubleshoot without it being there. I
>>> guess
>>> you
>>> could always add a 2005 instance and see if you can repro it.
>>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>> instance.
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> Was ASP running on the same box or a different one?
>>>
>>>
>>> Same one.
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> OK, I'm a bit lost now. You can connect now, right? You have
>>> only
>>> one
>>> instance on the box now and it's SQL 2000, right? You're just
>>> asking
>>> what
>>> the problem was when logging into a SQL 2005 instance with SSMS?
>>> I
>>> guess
>>> since the instance is gone, we won't be able to troubleshoot that
>>> one.
>>>
>>> I have 2 instances running.
>>> The SQL2000 one was not running because in the services it was set
>>> to
>>> manual
>>> start.
>>> So now I have both of them running.
>>>
>>> I have not had any problem with SSMS, it was with ASP logging in
>>> using
>>> an
>>> SQL account.
>>>
>>> Strange thing is I set up the database up using SSMS on version 9
>>> (2005)
>>> SQL
>>> server.
>>>
>>> So now I don't know what is going on.
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>>> OK, that means that you are using a default instance. When you
>>>> connect
>>>> via
>>>> SSMS, while logged on directly at the box, what do you type into
>>>> the
>>>> Server
>>>> box? Have you tried just typing a dot:
>>>>
>>>
>>> I don't type in anything. The boxes are already filled in and logg
>>> in
>>> using
>>> a user account that has admin privleges.
>>>
>>> never mind. Gosh how stupid.
>>> The SQL2000 instance was not running in the services.
>>>
>>> However, it still does not explain why I could not use 2005 to log
>>> in
>>> with
>>> the the first error I received.
>>>
>>>> .
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>>> From a command prompt, could you run:
>>>>
>>>> NET START
>>>>
>>>> ... and post the parts that mention SQL Server.
>>>>
>>>> Here is is:
>>>>
>>>> SQL Server (MSSQLSERVER)
>>>> SQL Server Analysis Services (MSSQLSERVER)
>>>> SQL Server Browser
>>>> SQL Server FullText Search (MSSQLSERVER)
>>>> SQL Server Integration Services
>>>> SQL Server Reporting Services (MSSQLSERVER)
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>> How about with the SQL client tools? Just want to be sure it
>>>> isn't
>>>> the
>>>> OLEDB stuff.
>>>>
>>>>
>>>> Yes, I check under both 2000/2005.
>>>> Both seem to be set correctly.
>>>>
>>>> I even tried to make user Windows user acount instead of using
>>>> the
>>>> SQL
>>>> login.
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>> It appears that your SQL Server was configured for Windows
>>>> authentication
>>>> only. That's the default. Use the Surface Area Configuration
>>>> app
>>>> to
>>>> change
>>>> the authentication to Mixed.
>>>>
>>>>
>>>> First thing I did.
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>> Hello.
>>>>
>>>> I did some changes to my server and now having trouble with
>>>> connections.
>>>>
>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>
>>>> Got one web site with the following connection via ASP:
>>>>
>>>> <%
>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>
>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>> %>
>>>>
>>>> This produces "Login Failed" and kept doing it no matter what
>>>> I
>>>> have
>>>> changed
>>>> in SQL 2005.
>>>>
>>>> After trying to connect with numerous failing trys, I put SQL
>>>> 2000
>>>> back
>>>> on.
>>>> I gave it the new instance name of SQL2000.
>>>> I tried the above, and also chaned it to the follow
>>>> connections:
>>>>
>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>> &
>>>> (SQL2000)
>>>>
>>>> These two produced the error - "Server does not exist or
>>>> access
>>>> denied"
>>>> and
>>>> 'local' still produces "login failed."
>>>>
>>>> What is the correct method?
>>>>
>>>> Thanks,
>>>>
>>>> GB
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||I'm confused again. You say that the DB is functioning "when the SQL2000
instance was not running". That's not really possible.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46bb929f$0$4684$4c368faf@.roadrunner.com...
Not since I started the SQL2000 instance in the server in "services."
Hence Why I ask why the databse is functioning now, when the SQL2000
instance was not running, but the database is setup in the SQL 2005
instance.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:O6IL4Bt2HHA.4880@.TK2MSFTNGP03.phx.gbl...
> So I take it that there is no longer a problem?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb8b06$0$29656$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:el2J2hs2HHA.2064@.TK2MSFTNGP03.phx.gbl...
>> The second one should use a backslash, not a forward slash:
>> GLOBAL-7XQWMEEO\SQL2000
> I did not put that in there, the system does and it works fine.
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
>> When you use SSMS to connect to each of those instances while logged on
>> locally, what do you type into the Server text box? For the default
>> (2005)
>> instance, it should be a dot. For the SQL 2000 instance, it should be
>> .\SQL2000. Have you tried that?
>>
>>
>> I type in nothing. All the fields are already filled in.
>> Server Type: Database Engine
>> Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
>> Authentication: "my login user name"
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>>
>> I am familair with mySQL, but not MS SQL, so I do not know about the
>> reference you make concerning the way you are showing to connect.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> Now I'm more confused. How many instances are on the box? If it's
>> more
>> than one, which SQL Servers are they and what are the instance names?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <geek@.boy.com> wrote in message
>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>>> Dunno what to say. Can't troubleshoot without it being there. I
>>> guess
>>> you
>>> could always add a 2005 instance and see if you can repro it.
>>>
>>
>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>> instance.
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> Was ASP running on the same box or a different one?
>>>
>>>
>>> Same one.
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> OK, I'm a bit lost now. You can connect now, right? You have
>>> only
>>> one
>>> instance on the box now and it's SQL 2000, right? You're just
>>> asking
>>> what
>>> the problem was when logging into a SQL 2005 instance with SSMS?
>>> I
>>> guess
>>> since the instance is gone, we won't be able to troubleshoot that
>>> one.
>>>
>>> I have 2 instances running.
>>> The SQL2000 one was not running because in the services it was set
>>> to
>>> manual
>>> start.
>>> So now I have both of them running.
>>>
>>> I have not had any problem with SSMS, it was with ASP logging in
>>> using
>>> an
>>> SQL account.
>>>
>>> Strange thing is I set up the database up using SSMS on version 9
>>> (2005)
>>> SQL
>>> server.
>>>
>>> So now I don't know what is going on.
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>>> OK, that means that you are using a default instance. When you
>>>> connect
>>>> via
>>>> SSMS, while logged on directly at the box, what do you type into
>>>> the
>>>> Server
>>>> box? Have you tried just typing a dot:
>>>>
>>>
>>> I don't type in anything. The boxes are already filled in and logg
>>> in
>>> using
>>> a user account that has admin privleges.
>>>
>>> never mind. Gosh how stupid.
>>> The SQL2000 instance was not running in the services.
>>>
>>> However, it still does not explain why I could not use 2005 to log
>>> in
>>> with
>>> the the first error I received.
>>>
>>>> .
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>>> From a command prompt, could you run:
>>>>
>>>> NET START
>>>>
>>>> ... and post the parts that mention SQL Server.
>>>>
>>>> Here is is:
>>>>
>>>> SQL Server (MSSQLSERVER)
>>>> SQL Server Analysis Services (MSSQLSERVER)
>>>> SQL Server Browser
>>>> SQL Server FullText Search (MSSQLSERVER)
>>>> SQL Server Integration Services
>>>> SQL Server Reporting Services (MSSQLSERVER)
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>> How about with the SQL client tools? Just want to be sure it
>>>> isn't
>>>> the
>>>> OLEDB stuff.
>>>>
>>>>
>>>> Yes, I check under both 2000/2005.
>>>> Both seem to be set correctly.
>>>>
>>>> I even tried to make user Windows user acount instead of using
>>>> the
>>>> SQL
>>>> login.
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>> It appears that your SQL Server was configured for Windows
>>>> authentication
>>>> only. That's the default. Use the Surface Area Configuration
>>>> app
>>>> to
>>>> change
>>>> the authentication to Mixed.
>>>>
>>>>
>>>> First thing I did.
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>> Hello.
>>>>
>>>> I did some changes to my server and now having trouble with
>>>> connections.
>>>>
>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>
>>>> Got one web site with the following connection via ASP:
>>>>
>>>> <%
>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>
>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>> %>
>>>>
>>>> This produces "Login Failed" and kept doing it no matter what
>>>> I
>>>> have
>>>> changed
>>>> in SQL 2005.
>>>>
>>>> After trying to connect with numerous failing trys, I put SQL
>>>> 2000
>>>> back
>>>> on.
>>>> I gave it the new instance name of SQL2000.
>>>> I tried the above, and also chaned it to the follow
>>>> connections:
>>>>
>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>> &
>>>> (SQL2000)
>>>>
>>>> These two produced the error - "Server does not exist or
>>>> access
>>>> denied"
>>>> and
>>>> 'local' still produces "login failed."
>>>>
>>>> What is the correct method?
>>>>
>>>> Thanks,
>>>>
>>>> GB
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23p3emHu2HHA.484@.TK2MSFTNGP06.phx.gbl...
> I'm confused again. You say that the DB is functioning "when the SQL2000
> instance was not running". That's not really possible.
>
No..you have that switched around.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb929f$0$4684$4c368faf@.roadrunner.com...
> Not since I started the SQL2000 instance in the server in "services."
> Hence Why I ask why the databse is functioning now, when the SQL2000
> instance was not running, but the database is setup in the SQL 2005
> instance.
>
>
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:O6IL4Bt2HHA.4880@.TK2MSFTNGP03.phx.gbl...
>> So I take it that there is no longer a problem?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb8b06$0$29656$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:el2J2hs2HHA.2064@.TK2MSFTNGP03.phx.gbl...
>> The second one should use a backslash, not a forward slash:
>> GLOBAL-7XQWMEEO\SQL2000
>>
>> I did not put that in there, the system does and it works fine.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
>> When you use SSMS to connect to each of those instances while logged on
>> locally, what do you type into the Server text box? For the default
>> (2005)
>> instance, it should be a dot. For the SQL 2000 instance, it should be
>> .\SQL2000. Have you tried that?
>>
>>
>> I type in nothing. All the fields are already filled in.
>> Server Type: Database Engine
>> Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
>> Authentication: "my login user name"
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>>
>> I am familair with mySQL, but not MS SQL, so I do not know about the
>> reference you make concerning the way you are showing to connect.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> Now I'm more confused. How many instances are on the box? If it's
>>> more
>>> than one, which SQL Servers are they and what are the instance
>>> names?
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>>> Dunno what to say. Can't troubleshoot without it being there. I
>>> guess
>>> you
>>> could always add a 2005 instance and see if you can repro it.
>>>
>>>
>>>
>>>
>>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>>> instance.
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> Was ASP running on the same box or a different one?
>>>
>>>
>>> Same one.
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>>> OK, I'm a bit lost now. You can connect now, right? You have
>>>> only
>>>> one
>>>> instance on the box now and it's SQL 2000, right? You're just
>>>> asking
>>>> what
>>>> the problem was when logging into a SQL 2005 instance with SSMS?
>>>> I
>>>> guess
>>>> since the instance is gone, we won't be able to troubleshoot that
>>>> one.
>>>
>>> I have 2 instances running.
>>> The SQL2000 one was not running because in the services it was set
>>> to
>>> manual
>>> start.
>>> So now I have both of them running.
>>>
>>> I have not had any problem with SSMS, it was with ASP logging in
>>> using
>>> an
>>> SQL account.
>>>
>>> Strange thing is I set up the database up using SSMS on version 9
>>> (2005)
>>> SQL
>>> server.
>>>
>>> So now I don't know what is going on.
>>>
>>>
>>>
>>>
>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>>> OK, that means that you are using a default instance. When you
>>>> connect
>>>> via
>>>> SSMS, while logged on directly at the box, what do you type into
>>>> the
>>>> Server
>>>> box? Have you tried just typing a dot:
>>>>
>>>>
>>>> I don't type in anything. The boxes are already filled in and
>>>> logg
>>>> in
>>>> using
>>>> a user account that has admin privleges.
>>>>
>>>> never mind. Gosh how stupid.
>>>> The SQL2000 instance was not running in the services.
>>>>
>>>> However, it still does not explain why I could not use 2005 to
>>>> log
>>>> in
>>>> with
>>>> the the first error I received.
>>>>
>>>> .
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>>> From a command prompt, could you run:
>>>>
>>>> NET START
>>>>
>>>> ... and post the parts that mention SQL Server.
>>>>
>>>> Here is is:
>>>>
>>>> SQL Server (MSSQLSERVER)
>>>> SQL Server Analysis Services (MSSQLSERVER)
>>>> SQL Server Browser
>>>> SQL Server FullText Search (MSSQLSERVER)
>>>> SQL Server Integration Services
>>>> SQL Server Reporting Services (MSSQLSERVER)
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>> How about with the SQL client tools? Just want to be sure it
>>>> isn't
>>>> the
>>>> OLEDB stuff.
>>>>
>>>>
>>>> Yes, I check under both 2000/2005.
>>>> Both seem to be set correctly.
>>>>
>>>> I even tried to make user Windows user acount instead of using
>>>> the
>>>> SQL
>>>> login.
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>>> It appears that your SQL Server was configured for Windows
>>>>> authentication
>>>>> only. That's the default. Use the Surface Area
>>>>> Configuration
>>>>> app
>>>>> to
>>>>> change
>>>>> the authentication to Mixed.
>>>>>
>>>>
>>>> First thing I did.
>>>>
>>>>
>>>>> --
>>>>> Tom
>>>>>
>>>>> ----
>>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>>> SQL Server MVP
>>>>> Toronto, ON Canada
>>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>>
>>>>>
>>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>>> Hello.
>>>>>
>>>>> I did some changes to my server and now having trouble with
>>>>> connections.
>>>>>
>>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>>
>>>>> Got one web site with the following connection via ASP:
>>>>>
>>>>> <%
>>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>>
>>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>>> %>
>>>>>
>>>>> This produces "Login Failed" and kept doing it no matter what
>>>>> I
>>>>> have
>>>>> changed
>>>>> in SQL 2005.
>>>>>
>>>>> After trying to connect with numerous failing trys, I put SQL
>>>>> 2000
>>>>> back
>>>>> on.
>>>>> I gave it the new instance name of SQL2000.
>>>>> I tried the above, and also chaned it to the follow
>>>>> connections:
>>>>>
>>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>>> &
>>>>> (SQL2000)
>>>>>
>>>>> These two produced the error - "Server does not exist or
>>>>> access
>>>>> denied"
>>>>> and
>>>>> 'local' still produces "login failed."
>>>>>
>>>>> What is the correct method?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> GB
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||You've lost me now...
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46bbb43a$0$4919$4c368faf@.roadrunner.com...
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23p3emHu2HHA.484@.TK2MSFTNGP06.phx.gbl...
> I'm confused again. You say that the DB is functioning "when the SQL2000
> instance was not running". That's not really possible.
>
No..you have that switched around.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bb929f$0$4684$4c368faf@.roadrunner.com...
> Not since I started the SQL2000 instance in the server in "services."
> Hence Why I ask why the databse is functioning now, when the SQL2000
> instance was not running, but the database is setup in the SQL 2005
> instance.
>
>
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:O6IL4Bt2HHA.4880@.TK2MSFTNGP03.phx.gbl...
>> So I take it that there is no longer a problem?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb8b06$0$29656$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:el2J2hs2HHA.2064@.TK2MSFTNGP03.phx.gbl...
>> The second one should use a backslash, not a forward slash:
>> GLOBAL-7XQWMEEO\SQL2000
>>
>> I did not put that in there, the system does and it works fine.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
>> When you use SSMS to connect to each of those instances while logged on
>> locally, what do you type into the Server text box? For the default
>> (2005)
>> instance, it should be a dot. For the SQL 2000 instance, it should be
>> .\SQL2000. Have you tried that?
>>
>>
>> I type in nothing. All the fields are already filled in.
>> Server Type: Database Engine
>> Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
>> Authentication: "my login user name"
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>>
>> I am familair with mySQL, but not MS SQL, so I do not know about the
>> reference you make concerning the way you are showing to connect.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Which is the default instance and which is the named instance?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> Now I'm more confused. How many instances are on the box? If it's
>>> more
>>> than one, which SQL Servers are they and what are the instance
>>> names?
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>>> Dunno what to say. Can't troubleshoot without it being there. I
>>> guess
>>> you
>>> could always add a 2005 instance and see if you can repro it.
>>>
>>>
>>>
>>>
>>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>>> instance.
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>> Was ASP running on the same box or a different one?
>>>
>>>
>>> Same one.
>>>
>>>
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>>> OK, I'm a bit lost now. You can connect now, right? You have
>>>> only
>>>> one
>>>> instance on the box now and it's SQL 2000, right? You're just
>>>> asking
>>>> what
>>>> the problem was when logging into a SQL 2005 instance with SSMS?
>>>> I
>>>> guess
>>>> since the instance is gone, we won't be able to troubleshoot that
>>>> one.
>>>
>>> I have 2 instances running.
>>> The SQL2000 one was not running because in the services it was set
>>> to
>>> manual
>>> start.
>>> So now I have both of them running.
>>>
>>> I have not had any problem with SSMS, it was with ASP logging in
>>> using
>>> an
>>> SQL account.
>>>
>>> Strange thing is I set up the database up using SSMS on version 9
>>> (2005)
>>> SQL
>>> server.
>>>
>>> So now I don't know what is going on.
>>>
>>>
>>>
>>>
>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>>> OK, that means that you are using a default instance. When you
>>>> connect
>>>> via
>>>> SSMS, while logged on directly at the box, what do you type into
>>>> the
>>>> Server
>>>> box? Have you tried just typing a dot:
>>>>
>>>>
>>>> I don't type in anything. The boxes are already filled in and
>>>> logg
>>>> in
>>>> using
>>>> a user account that has admin privleges.
>>>>
>>>> never mind. Gosh how stupid.
>>>> The SQL2000 instance was not running in the services.
>>>>
>>>> However, it still does not explain why I could not use 2005 to
>>>> log
>>>> in
>>>> with
>>>> the the first error I received.
>>>>
>>>> .
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>>> From a command prompt, could you run:
>>>>
>>>> NET START
>>>>
>>>> ... and post the parts that mention SQL Server.
>>>>
>>>> Here is is:
>>>>
>>>> SQL Server (MSSQLSERVER)
>>>> SQL Server Analysis Services (MSSQLSERVER)
>>>> SQL Server Browser
>>>> SQL Server FullText Search (MSSQLSERVER)
>>>> SQL Server Integration Services
>>>> SQL Server Reporting Services (MSSQLSERVER)
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>> How about with the SQL client tools? Just want to be sure it
>>>> isn't
>>>> the
>>>> OLEDB stuff.
>>>>
>>>>
>>>> Yes, I check under both 2000/2005.
>>>> Both seem to be set correctly.
>>>>
>>>> I even tried to make user Windows user acount instead of using
>>>> the
>>>> SQL
>>>> login.
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>>> It appears that your SQL Server was configured for Windows
>>>>> authentication
>>>>> only. That's the default. Use the Surface Area
>>>>> Configuration
>>>>> app
>>>>> to
>>>>> change
>>>>> the authentication to Mixed.
>>>>>
>>>>
>>>> First thing I did.
>>>>
>>>>
>>>>> --
>>>>> Tom
>>>>>
>>>>> ----
>>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>>> SQL Server MVP
>>>>> Toronto, ON Canada
>>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>>
>>>>>
>>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>>> Hello.
>>>>>
>>>>> I did some changes to my server and now having trouble with
>>>>> connections.
>>>>>
>>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>>
>>>>> Got one web site with the following connection via ASP:
>>>>>
>>>>> <%
>>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>>
>>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>>> %>
>>>>>
>>>>> This produces "Login Failed" and kept doing it no matter what
>>>>> I
>>>>> have
>>>>> changed
>>>>> in SQL 2005.
>>>>>
>>>>> After trying to connect with numerous failing trys, I put SQL
>>>>> 2000
>>>>> back
>>>>> on.
>>>>> I gave it the new instance name of SQL2000.
>>>>> I tried the above, and also chaned it to the follow
>>>>> connections:
>>>>>
>>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>>> &
>>>>> (SQL2000)
>>>>>
>>>>> These two produced the error - "Server does not exist or
>>>>> access
>>>>> denied"
>>>>> and
>>>>> 'local' still produces "login failed."
>>>>>
>>>>> What is the correct method?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> GB
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||The database did not function until I started the SQL 2000 instance in the
"services."
The issue is, how can it start to function again if the SQL 2000 server was
started while it is setup to run on the SQL 2005 instance?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OeJ1rfu2HHA.1208@.TK2MSFTNGP03.phx.gbl...
> You've lost me now...
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bbb43a$0$4919$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23p3emHu2HHA.484@.TK2MSFTNGP06.phx.gbl...
>> I'm confused again. You say that the DB is functioning "when the SQL2000
>> instance was not running". That's not really possible.
>
> No..you have that switched around.
>
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb929f$0$4684$4c368faf@.roadrunner.com...
>> Not since I started the SQL2000 instance in the server in "services."
>> Hence Why I ask why the databse is functioning now, when the SQL2000
>> instance was not running, but the database is setup in the SQL 2005
>> instance.
>>
>>
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:O6IL4Bt2HHA.4880@.TK2MSFTNGP03.phx.gbl...
>> So I take it that there is no longer a problem?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb8b06$0$29656$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:el2J2hs2HHA.2064@.TK2MSFTNGP03.phx.gbl...
>> The second one should use a backslash, not a forward slash:
>> GLOBAL-7XQWMEEO\SQL2000
>>
>> I did not put that in there, the system does and it works fine.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
>> When you use SSMS to connect to each of those instances while logged
>> on
>> locally, what do you type into the Server text box? For the default
>> (2005)
>> instance, it should be a dot. For the SQL 2000 instance, it should be
>> .\SQL2000. Have you tried that?
>>
>>
>> I type in nothing. All the fields are already filled in.
>> Server Type: Database Engine
>> Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
>> Authentication: "my login user name"
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>>
>> I am familair with mySQL, but not MS SQL, so I do not know about the
>> reference you make concerning the way you are showing to connect.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>>> Which is the default instance and which is the named instance?
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>>
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> Now I'm more confused. How many instances are on the box? If it's
>>> more
>>> than one, which SQL Servers are they and what are the instance
>>> names?
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>>> Dunno what to say. Can't troubleshoot without it being there. I
>>> guess
>>> you
>>> could always add a 2005 instance and see if you can repro it.
>>>
>>>
>>>
>>>
>>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>>> instance.
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>>> Was ASP running on the same box or a different one?
>>>
>>>
>>> Same one.
>>>
>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>>> OK, I'm a bit lost now. You can connect now, right? You have
>>>> only
>>>> one
>>>> instance on the box now and it's SQL 2000, right? You're just
>>>> asking
>>>> what
>>>> the problem was when logging into a SQL 2005 instance with SSMS?
>>>> I
>>>> guess
>>>> since the instance is gone, we won't be able to troubleshoot
>>>> that
>>>> one.
>>>>
>>>> I have 2 instances running.
>>>> The SQL2000 one was not running because in the services it was
>>>> set
>>>> to
>>>> manual
>>>> start.
>>>> So now I have both of them running.
>>>>
>>>> I have not had any problem with SSMS, it was with ASP logging in
>>>> using
>>>> an
>>>> SQL account.
>>>>
>>>> Strange thing is I set up the database up using SSMS on version 9
>>>> (2005)
>>>> SQL
>>>> server.
>>>>
>>>> So now I don't know what is going on.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>>> OK, that means that you are using a default instance. When you
>>>> connect
>>>> via
>>>> SSMS, while logged on directly at the box, what do you type
>>>> into
>>>> the
>>>> Server
>>>> box? Have you tried just typing a dot:
>>>>
>>>>
>>>> I don't type in anything. The boxes are already filled in and
>>>> logg
>>>> in
>>>> using
>>>> a user account that has admin privleges.
>>>>
>>>> never mind. Gosh how stupid.
>>>> The SQL2000 instance was not running in the services.
>>>>
>>>> However, it still does not explain why I could not use 2005 to
>>>> log
>>>> in
>>>> with
>>>> the the first error I received.
>>>>
>>>> .
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>>> From a command prompt, could you run:
>>>>
>>>> NET START
>>>>
>>>> ... and post the parts that mention SQL Server.
>>>>
>>>> Here is is:
>>>>
>>>> SQL Server (MSSQLSERVER)
>>>> SQL Server Analysis Services (MSSQLSERVER)
>>>> SQL Server Browser
>>>> SQL Server FullText Search (MSSQLSERVER)
>>>> SQL Server Integration Services
>>>> SQL Server Reporting Services (MSSQLSERVER)
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>>> How about with the SQL client tools? Just want to be sure it
>>>>> isn't
>>>>> the
>>>>> OLEDB stuff.
>>>>>
>>>>>
>>>> Yes, I check under both 2000/2005.
>>>> Both seem to be set correctly.
>>>>
>>>> I even tried to make user Windows user acount instead of using
>>>> the
>>>> SQL
>>>> login.
>>>>
>>>>
>>>>
>>>>> --
>>>>> Tom
>>>>>
>>>>> ----
>>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>>> SQL Server MVP
>>>>> Toronto, ON Canada
>>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>>
>>>>>
>>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>>
>>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>>> It appears that your SQL Server was configured for Windows
>>>>> authentication
>>>>> only. That's the default. Use the Surface Area
>>>>> Configuration
>>>>> app
>>>>> to
>>>>> change
>>>>> the authentication to Mixed.
>>>>>
>>>>>
>>>>> First thing I did.
>>>>>
>>>>>
>>>>> --
>>>>> Tom
>>>>>
>>>>> ----
>>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>>> SQL Server MVP
>>>>> Toronto, ON Canada
>>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>>
>>>>>
>>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>>> Hello.
>>>>>
>>>>> I did some changes to my server and now having trouble with
>>>>> connections.
>>>>>
>>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>>
>>>>> Got one web site with the following connection via ASP:
>>>>>
>>>>> <%
>>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>>
>>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>>> %>
>>>>>
>>>>> This produces "Login Failed" and kept doing it no matter
>>>>> what
>>>>> I
>>>>> have
>>>>> changed
>>>>> in SQL 2005.
>>>>>
>>>>> After trying to connect with numerous failing trys, I put
>>>>> SQL
>>>>> 2000
>>>>> back
>>>>> on.
>>>>> I gave it the new instance name of SQL2000.
>>>>> I tried the above, and also chaned it to the follow
>>>>> connections:
>>>>>
>>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>>> &
>>>>> (SQL2000)
>>>>>
>>>>> These two produced the error - "Server does not exist or
>>>>> access
>>>>> denied"
>>>>> and
>>>>> 'local' still produces "login failed."
>>>>>
>>>>> What is the correct method?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> GB
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Looks like your app is pointing to the SQL 2000 instance and not the SQL
2005 instance. Perhaps you can try:
conn.Open "Data Source=.;Provider=SQLOLEDB.1;Initial
Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
conn.Open "Data Source=.\SQL2000;Provider=SQLOLEDB.1;Initial
Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
Do these connect? Failing that, the following link may be useful:
http://www.connectionstrings.com/
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"GeekBoy" <nobody@.spamcop.net> wrote in message
news:46bbbdd5$0$28669$4c368faf@.roadrunner.com...
The database did not function until I started the SQL 2000 instance in the
"services."
The issue is, how can it start to function again if the SQL 2000 server was
started while it is setup to run on the SQL 2005 instance?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OeJ1rfu2HHA.1208@.TK2MSFTNGP03.phx.gbl...
> You've lost me now...
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "GeekBoy" <nobody@.spamcop.net> wrote in message
> news:46bbb43a$0$4919$4c368faf@.roadrunner.com...
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23p3emHu2HHA.484@.TK2MSFTNGP06.phx.gbl...
>> I'm confused again. You say that the DB is functioning "when the SQL2000
>> instance was not running". That's not really possible.
>
> No..you have that switched around.
>
>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb929f$0$4684$4c368faf@.roadrunner.com...
>> Not since I started the SQL2000 instance in the server in "services."
>> Hence Why I ask why the databse is functioning now, when the SQL2000
>> instance was not running, but the database is setup in the SQL 2005
>> instance.
>>
>>
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:O6IL4Bt2HHA.4880@.TK2MSFTNGP03.phx.gbl...
>> So I take it that there is no longer a problem?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb8b06$0$29656$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:el2J2hs2HHA.2064@.TK2MSFTNGP03.phx.gbl...
>> The second one should use a backslash, not a forward slash:
>> GLOBAL-7XQWMEEO\SQL2000
>>
>> I did not put that in there, the system does and it works fine.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7fab$0$20612$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%233QlHYs2HHA.5360@.TK2MSFTNGP03.phx.gbl...
>> When you use SSMS to connect to each of those instances while logged
>> on
>> locally, what do you type into the Server text box? For the default
>> (2005)
>> instance, it should be a dot. For the SQL 2000 instance, it should be
>> .\SQL2000. Have you tried that?
>>
>>
>> I type in nothing. All the fields are already filled in.
>> Server Type: Database Engine
>> Server name: GLOBAL-7XQWMEEO or GLOBAL-7XQWMEEO/SQL2000
>> Authentication: "my login user name"
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb79ce$0$20536$4c368faf@.roadrunner.com...
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%230Pwo%23r2HHA.2752@.TK2MSFTNGP06.phx.gbl...
>> OK, so you can connect to both of the following:
>> .
>> .\SQL2000
>> Correct?
>>
>> I am familair with mySQL, but not MS SQL, so I do not know about the
>> reference you make concerning the way you are showing to connect.
>>
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>> news:46bb7068$0$30668$4c368faf@.roadrunner.com...
>> 2005 is default while "SQL2000" is the named.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23qJopKr2HHA.4184@.TK2MSFTNGP06.phx.gbl...
>>> Which is the default instance and which is the named instance?
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>> news:46bb27ce$0$8961$4c368faf@.roadrunner.com...
>>> Two. local (SQL 2005 Std) and SQL2000 (SQL 2000)
>>>
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23pE5YXn2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>> Now I'm more confused. How many instances are on the box? If it's
>>> more
>>> than one, which SQL Servers are they and what are the instance
>>> names?
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba8b75$0$20593$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:eZI09Ej2HHA.5164@.TK2MSFTNGP05.phx.gbl...
>>> Dunno what to say. Can't troubleshoot without it being there. I
>>> guess
>>> you
>>> could always add a 2005 instance and see if you can repro it.
>>>
>>>
>>>
>>>
>>> The local is the 2005 instance while "SQL2000" is the 2000 SQL
>>> instance.
>>>
>>> --
>>> Tom
>>>
>>> ----
>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>> SQL Server MVP
>>> Toronto, ON Canada
>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>
>>>
>>> "GeekBoy" <geek@.boy.com> wrote in message
>>> news:46ba775e$0$28682$4c368faf@.roadrunner.com...
>>>
>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>> news:%23WZyzRi2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>>> Was ASP running on the same box or a different one?
>>>
>>>
>>> Same one.
>>>
>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba688f$0$12176$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:erV3U6h2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>>>> OK, I'm a bit lost now. You can connect now, right? You have
>>>> only
>>>> one
>>>> instance on the box now and it's SQL 2000, right? You're just
>>>> asking
>>>> what
>>>> the problem was when logging into a SQL 2005 instance with SSMS?
>>>> I
>>>> guess
>>>> since the instance is gone, we won't be able to troubleshoot
>>>> that
>>>> one.
>>>>
>>>> I have 2 instances running.
>>>> The SQL2000 one was not running because in the services it was
>>>> set
>>>> to
>>>> manual
>>>> start.
>>>> So now I have both of them running.
>>>>
>>>> I have not had any problem with SSMS, it was with ASP logging in
>>>> using
>>>> an
>>>> SQL account.
>>>>
>>>> Strange thing is I set up the database up using SSMS on version 9
>>>> (2005)
>>>> SQL
>>>> server.
>>>>
>>>> So now I don't know what is going on.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba5ae7$0$30652$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:%23yDpFEh2HHA.1184@.TK2MSFTNGP04.phx.gbl...
>>>> OK, that means that you are using a default instance. When you
>>>> connect
>>>> via
>>>> SSMS, while logged on directly at the box, what do you type
>>>> into
>>>> the
>>>> Server
>>>> box? Have you tried just typing a dot:
>>>>
>>>>
>>>> I don't type in anything. The boxes are already filled in and
>>>> logg
>>>> in
>>>> using
>>>> a user account that has admin privleges.
>>>>
>>>> never mind. Gosh how stupid.
>>>> The SQL2000 instance was not running in the services.
>>>>
>>>> However, it still does not explain why I could not use 2005 to
>>>> log
>>>> in
>>>> with
>>>> the the first error I received.
>>>>
>>>> .
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <nobody@.spamcop.net> wrote in message
>>>> news:46ba482f$0$3159$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:OdHSGng2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>>>> From a command prompt, could you run:
>>>>
>>>> NET START
>>>>
>>>> ... and post the parts that mention SQL Server.
>>>>
>>>> Here is is:
>>>>
>>>> SQL Server (MSSQLSERVER)
>>>> SQL Server Analysis Services (MSSQLSERVER)
>>>> SQL Server Browser
>>>> SQL Server FullText Search (MSSQLSERVER)
>>>> SQL Server Integration Services
>>>> SQL Server Reporting Services (MSSQLSERVER)
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Tom
>>>>
>>>> ----
>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>> SQL Server MVP
>>>> Toronto, ON Canada
>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>
>>>>
>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>> news:46b921f0$0$8926$4c368faf@.roadrunner.com...
>>>>
>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>> news:e0cIpqV2HHA.748@.TK2MSFTNGP04.phx.gbl...
>>>>> How about with the SQL client tools? Just want to be sure it
>>>>> isn't
>>>>> the
>>>>> OLEDB stuff.
>>>>>
>>>>>
>>>> Yes, I check under both 2000/2005.
>>>> Both seem to be set correctly.
>>>>
>>>> I even tried to make user Windows user acount instead of using
>>>> the
>>>> SQL
>>>> login.
>>>>
>>>>
>>>>
>>>>> --
>>>>> Tom
>>>>>
>>>>> ----
>>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>>> SQL Server MVP
>>>>> Toronto, ON Canada
>>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>>
>>>>>
>>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>>> news:46b919a4$0$4680$4c368faf@.roadrunner.com...
>>>>>
>>>>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>>>>> news:OJ7XmMV2HHA.1164@.TK2MSFTNGP02.phx.gbl...
>>>>> It appears that your SQL Server was configured for Windows
>>>>> authentication
>>>>> only. That's the default. Use the Surface Area
>>>>> Configuration
>>>>> app
>>>>> to
>>>>> change
>>>>> the authentication to Mixed.
>>>>>
>>>>>
>>>>> First thing I did.
>>>>>
>>>>>
>>>>> --
>>>>> Tom
>>>>>
>>>>> ----
>>>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>>>>> SQL Server MVP
>>>>> Toronto, ON Canada
>>>>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>>>>
>>>>>
>>>>> "GeekBoy" <allGeek@.hownerdy.com> wrote in message
>>>>> news:46b8ffe0$0$31256$4c368faf@.roadrunner.com...
>>>>> Hello.
>>>>>
>>>>> I did some changes to my server and now having trouble with
>>>>> connections.
>>>>>
>>>>> Took off SQL 2000 and replaced it with SQL2005 Standard.
>>>>>
>>>>> Got one web site with the following connection via ASP:
>>>>>
>>>>> <%
>>>>> Set conn = Server.CreateObject("ADODB.Connection")
>>>>>
>>>>> conn.Open "Data Source=(local);Provider=SQLOLEDB.1;Initial
>>>>> Catalog=Motorhome;UID=xxxxxxxx;Password=xxxxxx"
>>>>> %>
>>>>>
>>>>> This produces "Login Failed" and kept doing it no matter
>>>>> what
>>>>> I
>>>>> have
>>>>> changed
>>>>> in SQL 2005.
>>>>>
>>>>> After trying to connect with numerous failing trys, I put
>>>>> SQL
>>>>> 2000
>>>>> back
>>>>> on.
>>>>> I gave it the new instance name of SQL2000.
>>>>> I tried the above, and also chaned it to the follow
>>>>> connections:
>>>>>
>>>>> (GLOBAL-7XQWMEEO\SQL2000)
>>>>> &
>>>>> (SQL2000)
>>>>>
>>>>> These two produced the error - "Server does not exist or
>>>>> access
>>>>> denied"
>>>>> and
>>>>> 'local' still produces "login failed."
>>>>>
>>>>> What is the correct method?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> GB
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>