Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts

Thursday, March 29, 2012

Can't connect from a vista client to SQL 2005 box,other machines work fine

Hey. I've a windows vista machine which can't connect to SQL 2005 box. Other machines which are lower than vista work fine. Also, vista box can connect to other SQL 2005 instances but can't connect to only one instance. But, I can connect to the instance fine from my XP box. Also, it's not a permissions issue. This user is an SA and can connect form some other machine. SQL 2005 box is at 2047 version right now. And, the user is able to connect to some other boxes which are also at 2047. Please help. Thank you

Add the account sepcifically to the SQL Server. When you connect from Vista (because of the UAC) it strips out your group SID from local admins, so SQL Server doesn't know who you are, and that's probably what is causing your issue. Add the user's account by name to the box.

If this post answers your question, make sure you mark it "answered" so others can find it quickly.

Thanks -

Buck Woody
http://www.buckwoody.com

Can't connect as SA through ODBC manager...why?

Hi All,
I can connect to my MSDE server by logging in as SA from the command line
but not through the ODBC manager utility in windows. I need to setup system
DSNs for a few applications but can't because they require I use SQL
authentication. When I reach that step in the ODBC manager I type in SA and
the password and hit next I get a 18456 "login failed for sa" error. My
server is in mixed mode (I checked the registry), the domain admins group has
login privilages to MSDE, I have no firewall active on any NICs, and none of
my passwords contain a semicolon. I have no clue what I'm missing here. Can
some one point me in the right direction or link me to a good article on how
to setup system dsns through the command line?
Thanks,
Prikly Pete Peterson
MSDE can only be used as the source of the data. It's not licensed to host
Reporting Services (as we discuss in our Reporting Services
book --www.sqlreportingservices.net). Chapter 2 (freely downloadable from
the site) explains why.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"ComfortablySAD" <ComfortablySAD@.discussions.microsoft.com> wrote in message
news:32E686BF-63A6-4DFF-9A7D-A00E8B6CAE09@.microsoft.com...
> Hi All,
> I can connect to my MSDE server by logging in as SA from the command line
> but not through the ODBC manager utility in windows. I need to setup
> system
> DSNs for a few applications but can't because they require I use SQL
> authentication. When I reach that step in the ODBC manager I type in SA
> and
> the password and hit next I get a 18456 "login failed for sa" error. My
> server is in mixed mode (I checked the registry), the domain admins group
> has
> login privilages to MSDE, I have no firewall active on any NICs, and none
> of
> my passwords contain a semicolon. I have no clue what I'm missing here.
> Can
> some one point me in the right direction or link me to a good article on
> how
> to setup system dsns through the command line?
> Thanks,
> Prikly Pete Peterson
sql

Can't connect after Windows XP SP2

Has i reviewed here after Windows XP SP2, MSDE has some problems conecctiong
over a network.
I installed SP3a for MSDE 2000 but the problem persists.
I put a permission to sqlserver.exe but my access to it over a network (and
internet) is blocked.
How can i solve this problem?
thanks,
Goncalo Boleo
hi,
"john raub" <john_raub@.ascendrms.com> ha scritto nel messaggio
news:20c601c4bdd8$f28b0840$a601280a@.phx.gbl
> problem with a customer that installed a 3rd party
> firewall software. He has since uninstalled, but we still
> can't connect to the machine containing the MSDE server.
please have a look at
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];884012
to see if they can help
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Can't connect after change the security setting

Hi, Experts! I very new to SQL server. I made a stupid movement by mistakenl
y
change the security of property of local(windows NT) from log in using this
account to system account. After the machine restarted, i can't no longer
start up SQL server. When I click local (window NT) in enterprise manager it
says "a connection could not be established to local. Reason, SQL serer
doesn't exist or access denied". I think it is the change of security that
the access was denied. How should I resolve this problem' Thanks so much.Thats weird, did the SQLServer service start up ? Look in the Service
manager. The service account can be switched in here. if you changed
the authentication method you can set it back via the registry entry as
mentioned in here:
---
http://support.microsoft.com/defaul...b;EN-US;q285097
---
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
---
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSq
lServer\LoginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
-URL---
HTH, Jens Suessmeyer.|||Jens,
Thank you so very much for your reply. I changed the registry loginmode from
2 to 1 and it did not work; I tried to change from 1 to 0, it did not work
either. In the service, I was not able to start up MSSQLSERVER. I got this
message "MSSQL SERVER service on local computer started and then stopped.
Some services stop automatically if they have no work to do ...".
Thanks.
"Jens" wrote:

> Thats weird, did the SQLServer service start up ? Look in the Service
> manager. The service account can be switched in here. if you changed
> the authentication method you can set it back via the registry entry as
> mentioned in here:
> ---
> http://support.microsoft.com/defaul...b;EN-US;q285097
> ---
> INF: How to Change the Default Login Authentication Mode to SQL While
> Installing SQL Server 2000 Desktop Engine by Using Windows Installer
> ---
> <snip>
> Another way to change the security mode after installation is to stop
> SQL Server and set the appropriate registry key for your installation:
>
> Default instance:
> HKLM\Software\Microsoft\MSSqlserver\MSSq
lServer\LoginMode
>
> Named instance:
> HKLM\Software\Microsoft\Microsoft SQL Server\Instance
> Name\MSSQLServer\LoginMode
>
> to 2 for mixed-mode or 1 for integrated. (Integrated is the default
> setup for the SQL Server 2000 Data Engine.)
> </snip>
>
> -URL---
>
> HTH, Jens Suessmeyer.
>|||Lokk in the event log to see why it failed, did you try to change the
service accoutn back to the original one in the service manager ?
Some error occured and you have to know which one, this information is
presented in the event log.
Jens Suessmeyer.|||Thank you Jens. You saved me. I was panic about it. It is the evaluation
period expired. We have license now. How can I update the license without
losing the data? If not doable it is ok too. Thanks. whew...
"Jens" wrote:

> Lokk in the event log to see why it failed, did you try to change the
> service accoutn back to the original one in the service manager ?
> Some error occured and you have to know which one, this information is
> presented in the event log.
> Jens Suessmeyer.
>|||http://support.microsoft.com/defaul...kb;en-us;281574
HTH, Jens Suessmeyer.|||Thank you so very much Jens. You are very helpful!!
"jsuessmeyer@.web.de" wrote:

> http://support.microsoft.com/defaul...kb;en-us;281574
> HTH, Jens Suessmeyer.
>

Can't connect after change the security setting

Hi, Experts! I very new to SQL server. I made a stupid movement by mistakenly
change the security of property of local(windows NT) from log in using this
account to system account. After the machine restarted, i can't no longer
start up SQL server. When I click local (window NT) in enterprise manager it
says "a connection could not be established to local. Reason, SQL serer
doesn't exist or access denied". I think it is the change of security that
the access was denied. How should I resolve this problem? Thanks so much.
Thats weird, did the SQLServer service start up ? Look in the Service
manager. The service account can be switched in here. if you changed
the authentication method you can set it back via the registry entry as
mentioned in here:
http://support.microsoft.com/default...;EN-US;q285097
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\Lo ginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
-URL---
HTH, Jens Suessmeyer.
|||Jens,
Thank you so very much for your reply. I changed the registry loginmode from
2 to 1 and it did not work; I tried to change from 1 to 0, it did not work
either. In the service, I was not able to start up MSSQLSERVER. I got this
message "MSSQL SERVER service on local computer started and then stopped.
Some services stop automatically if they have no work to do ...".
Thanks.
"Jens" wrote:

> Thats weird, did the SQLServer service start up ? Look in the Service
> manager. The service account can be switched in here. if you changed
> the authentication method you can set it back via the registry entry as
> mentioned in here:
> http://support.microsoft.com/default...;EN-US;q285097
> INF: How to Change the Default Login Authentication Mode to SQL While
> Installing SQL Server 2000 Desktop Engine by Using Windows Installer
> <snip>
> Another way to change the security mode after installation is to stop
> SQL Server and set the appropriate registry key for your installation:
>
> Default instance:
> HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\Lo ginMode
>
> Named instance:
> HKLM\Software\Microsoft\Microsoft SQL Server\Instance
> Name\MSSQLServer\LoginMode
>
> to 2 for mixed-mode or 1 for integrated. (Integrated is the default
> setup for the SQL Server 2000 Data Engine.)
> </snip>
>
> -URL---
>
> HTH, Jens Suessmeyer.
>
|||Lokk in the event log to see why it failed, did you try to change the
service accoutn back to the original one in the service manager ?
Some error occured and you have to know which one, this information is
presented in the event log.
Jens Suessmeyer.
|||Thank you Jens. You saved me. I was panic about it. It is the evaluation
period expired. We have license now. How can I update the license without
losing the data? If not doable it is ok too. Thanks. whew...
"Jens" wrote:

> Lokk in the event log to see why it failed, did you try to change the
> service accoutn back to the original one in the service manager ?
> Some error occured and you have to know which one, this information is
> presented in the event log.
> Jens Suessmeyer.
>
|||http://support.microsoft.com/default...b;en-us;281574
HTH, Jens Suessmeyer.
|||Thank you so very much Jens. You are very helpful!!
"jsuessmeyer@.web.de" wrote:

> http://support.microsoft.com/default...b;en-us;281574
> HTH, Jens Suessmeyer.
>
sql

Cant Connect - SQL Server does not exist

Hi
We recently had a SQL Server 2K, Win2K box crash on us, and we had to
reinstall Windows.
Sql Server was also damaged (I think the registry got corrupted), and
so I reinstalled that too (couldnt start the Services). The server is
now up and running, but from any other computers (such as my desktop)
I can't connect to the server. If I open QA, for example, I can locate
the server name using the ... button (so it's there), but when I put
in a UID & PWD I get the "SQL Server does not exist or access denied"
error.
If I start QA on the server itself, though, and connect using the same
UID & PWD, there's no problem.
any ideas?
Thanks
SeanEnsure that both the server and client share a network protocol in common.
Try to ping the server name and IP from the client to ensure connectivity.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sean" <plugwalsh@.yahoo.com> wrote in message
news:3698af3c.0408100316.2596d560@.posting.google.com...
> Hi
> We recently had a SQL Server 2K, Win2K box crash on us, and we had to
> reinstall Windows.
> Sql Server was also damaged (I think the registry got corrupted), and
> so I reinstalled that too (couldnt start the Services). The server is
> now up and running, but from any other computers (such as my desktop)
> I can't connect to the server. If I open QA, for example, I can locate
> the server name using the ... button (so it's there), but when I put
> in a UID & PWD I get the "SQL Server does not exist or access denied"
> error.
> If I start QA on the server itself, though, and connect using the same
> UID & PWD, there's no problem.
> any ideas?
> Thanks
> Sean|||Sorry - had the wrong IP in the hosts file... doh!
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<uIsqD7sfEHA.396@.
TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Ensure that both the server and client share a network protocol in common.
> Try to ping the server name and IP from the client to ensure connectivity.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Sean" <plugwalsh@.yahoo.com> wrote in message
> news:3698af3c.0408100316.2596d560@.posting.google.com...

Cant Connect - SQL Server does not exist

Hi
We recently had a SQL Server 2K, Win2K box crash on us, and we had to
reinstall Windows.
Sql Server was also damaged (I think the registry got corrupted), and
so I reinstalled that too (couldnt start the Services). The server is
now up and running, but from any other computers (such as my desktop)
I can't connect to the server. If I open QA, for example, I can locate
the server name using the ... button (so it's there), but when I put
in a UID & PWD I get the "SQL Server does not exist or access denied"
error.
If I start QA on the server itself, though, and connect using the same
UID & PWD, there's no problem.
any ideas?
Thanks
Sean
Ensure that both the server and client share a network protocol in common.
Try to ping the server name and IP from the client to ensure connectivity.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sean" <plugwalsh@.yahoo.com> wrote in message
news:3698af3c.0408100316.2596d560@.posting.google.c om...
> Hi
> We recently had a SQL Server 2K, Win2K box crash on us, and we had to
> reinstall Windows.
> Sql Server was also damaged (I think the registry got corrupted), and
> so I reinstalled that too (couldnt start the Services). The server is
> now up and running, but from any other computers (such as my desktop)
> I can't connect to the server. If I open QA, for example, I can locate
> the server name using the ... button (so it's there), but when I put
> in a UID & PWD I get the "SQL Server does not exist or access denied"
> error.
> If I start QA on the server itself, though, and connect using the same
> UID & PWD, there's no problem.
> any ideas?
> Thanks
> Sean
|||Sorry - had the wrong IP in the hosts file... doh!
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<uIsqD7sfEHA.396@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Ensure that both the server and client share a network protocol in common.
> Try to ping the server name and IP from the client to ensure connectivity.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Sean" <plugwalsh@.yahoo.com> wrote in message
> news:3698af3c.0408100316.2596d560@.posting.google.c om...

Cant Connect - SQL Server does not exist

Hi
We recently had a SQL Server 2K, Win2K box crash on us, and we had to
reinstall Windows.
Sql Server was also damaged (I think the registry got corrupted), and
so I reinstalled that too (couldnt start the Services). The server is
now up and running, but from any other computers (such as my desktop)
I can't connect to the server. If I open QA, for example, I can locate
the server name using the ... button (so it's there), but when I put
in a UID & PWD I get the "SQL Server does not exist or access denied"
error.
If I start QA on the server itself, though, and connect using the same
UID & PWD, there's no problem.
any ideas?
Thanks
SeanEnsure that both the server and client share a network protocol in common.
Try to ping the server name and IP from the client to ensure connectivity.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sean" <plugwalsh@.yahoo.com> wrote in message
news:3698af3c.0408100316.2596d560@.posting.google.com...
> Hi
> We recently had a SQL Server 2K, Win2K box crash on us, and we had to
> reinstall Windows.
> Sql Server was also damaged (I think the registry got corrupted), and
> so I reinstalled that too (couldnt start the Services). The server is
> now up and running, but from any other computers (such as my desktop)
> I can't connect to the server. If I open QA, for example, I can locate
> the server name using the ... button (so it's there), but when I put
> in a UID & PWD I get the "SQL Server does not exist or access denied"
> error.
> If I start QA on the server itself, though, and connect using the same
> UID & PWD, there's no problem.
> any ideas?
> Thanks
> Sean|||Sorry - had the wrong IP in the hosts file... doh!
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<uIsqD7sfEHA.396@.TK2MSFTNGP12.phx.gbl>...
> Ensure that both the server and client share a network protocol in common.
> Try to ping the server name and IP from the client to ensure connectivity.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Sean" <plugwalsh@.yahoo.com> wrote in message
> news:3698af3c.0408100316.2596d560@.posting.google.com...
> > Hi
> >
> > We recently had a SQL Server 2K, Win2K box crash on us, and we had to
> > reinstall Windows.
> >
> > Sql Server was also damaged (I think the registry got corrupted), and
> > so I reinstalled that too (couldnt start the Services). The server is
> > now up and running, but from any other computers (such as my desktop)
> > I can't connect to the server. If I open QA, for example, I can locate
> > the server name using the ... button (so it's there), but when I put
> > in a UID & PWD I get the "SQL Server does not exist or access denied"
> > error.
> >
> > If I start QA on the server itself, though, and connect using the same
> > UID & PWD, there's no problem.
> >
> > any ideas?
> > Thanks
> > Sean

Can't Connect

Win 2000, sqlServer 2000 Personal edition
Trying ot connect using .asp Vb Script
1. Sql server set to use Windows Authentication
2. Log onto Windows 2000 as Jim Bunton {no password)
3 Server 'Study' running ok
4. sql query analyser
i. "SELECT User_Name > dbo
ii. [using database NorthWind]
"SELECT * FROM Customers" > gives expected result
5. VB script
** BEGIN CODE connect.asp ***
<%
@. LANGUAGE="VBSCRIPT"
%>
<%
Option explicit
response.expires = 0
%>
<!-- #include file="adovbs.inc" -->
<html>
<head>
<title></title>
</head>
<body>
<%
dim Cn, CnStr
Set Cn = Server.CreateObject("ADODB.Connection")
Cn.ConnectionTimeOut = 1
Cn.provider="sqloledb"
response.write "Conn Provider is " & Cn.provider
CnStr="Data Source=Study;Initial Catalog=Norhwind;User
Id=sa;Password=;"
' Tried all sorts of user id's and paswords
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id = 'Jim
Bunton';Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
=dbo;Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
JimBunton;Password=;"
'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
='Study\Jim Bunton';Password=;"
%>
<p>--</p>
<%
response.write "Cnstr = " & CnStr
'ERROR ALWAYS OCCURS ON NEXT LINEon the next line
Cn.open CnStr
%>
<p>--</p>
<%
response.write "The End - ran ok"
%>
</body>
</html>
**** END CODE *****
? what to do?
? am I missing something 'obvious' out ?
Jim Bunton
If you are using windows authentication (also known as a
trusted connection) to connect, you don't supply a user
name, password in the connection string. Instead, you
indicate this by using Integrated Security=SSPI
in your connection string.
You also want to make sure the database is correct. In your
examples, you want to make sure you use Northwind (you have
Norwind listed).
You can find sample connection strings using the SQL Server
OLE DB provider at:
http://www.carlprothman.net/Default...erForSQLServer
-Sue
On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton"
<jBunton@.BlueYonder.co.uk> wrote:

>Win 2000, sqlServer 2000 Personal edition
>Trying ot connect using .asp Vb Script
>1. Sql server set to use Windows Authentication
>2. Log onto Windows 2000 as Jim Bunton {no password)
>3 Server 'Study' running ok
>4. sql query analyser
> i. "SELECT User_Name > dbo
> ii. [using database NorthWind]
> "SELECT * FROM Customers" > gives expected result
>5. VB script
>** BEGIN CODE connect.asp ***
><%
> @. LANGUAGE="VBSCRIPT"
>%>
><%
> Option explicit
> response.expires = 0
>%>
><!-- #include file="adovbs.inc" -->
><html>
><head>
><title></title>
></head>
><body>
><%
> dim Cn, CnStr
> Set Cn = Server.CreateObject("ADODB.Connection")
> Cn.ConnectionTimeOut = 1
> Cn.provider="sqloledb"
> response.write "Conn Provider is " & Cn.provider
> CnStr="Data Source=Study;Initial Catalog=Norhwind;User
>Id=sa;Password=;"
> ' Tried all sorts of user id's and paswords
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id = 'Jim
>Bunton';Password=;"
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
>=dbo;Password=;"
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
>JimBunton;Password=;"
> 'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
>='Study\Jim Bunton';Password=;"
>%>
><p>--</p>
><%
> response.write "Cnstr = " & CnStr
> 'ERROR ALWAYS OCCURS ON NEXT LINEon the next line
> Cn.open CnStr
>%>
><p>--</p>
><%
> response.write "The End - ran ok"
>%>
></body>
></html>
>**** END CODE *****
>? what to do?
>? am I missing something 'obvious' out ?
|||Thanks for your clear response Sue.
Unfortunately I still have a problem:
The following works:-
<%
dim Cn, SqlStr,rsCustomers
Set Cn=Server.CreateObject("ADODB.Connection")
Cn.Provider = "sqloledb"
Cn.Properties("Data Source") = "Study\StudySQLServer"
Cn.Properties("Initial Catalog") = "NorthWind"
Cn.Properties("Connect Timeout") = "3"
Cn.Properties("User ID") = "sa"
Cn.Properties("Password") = "mypassword"
Cn.open
. . . code which displays Customer info
The folowing does NOT:-
<%
dim Cn, CnStr, SqlStr,rsCustomers
Set Cn=Server.CreateObject("ADODB.Connection")
CnStr="Provider=sqloledb;" & _
"Data Source=Study\StudySqlServer;" & _
"Initial Catalog=NorthWind;" & _
"Integrated Security=SSPI"
response.write "cnStr = " & cnStr
' response.end
Cn.open CnStr
It fails at Cn.open CnStr
Error Type:
(0x80040E4D)
/MyWebs/Connect_wAuth.asp, line 15
response.write "cnStr = " & cnStr gives:-
cnStr = Provider=sqloledb;Data Source=Study\StudySqlServer;Initial Catalog=NorthWind;Integrated Security=SSPI
In Query Analyser (login using Windows Authentification)
select user_Name() >> dbo
select * from Customers >> a list of customers
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message news:5tuui1l8ku9a5fl6r704knccn7jfun1kf4@.4ax.com...
> If you are using windows authentication (also known as a
> trusted connection) to connect, you don't supply a user
> name, password in the connection string. Instead, you
> indicate this by using Integrated Security=SSPI
> in your connection string.
> You also want to make sure the database is correct. In your
> examples, you want to make sure you use Northwind (you have
> Norwind listed).
> You can find sample connection strings using the SQL Server
> OLE DB provider at:
> http://www.carlprothman.net/Default...erForSQLServer
> -Sue
> On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton"
> <jBunton@.BlueYonder.co.uk> wrote:
>
|||Then it's likely the authentication settings on the IIS side
of it. Try adding the IUSR account as a login in SQL Server
with the appropriate permissions as needed for your code.
Also, turned on failed login audits in SQL Server and
restart the instance. That will help you track down what
login is failing.
-Sue
On Tue, 20 Sep 2005 10:17:50 GMT, "Jim Bunton"
<jBunton@.BlueYonder.co.uk> wrote:
[vbcol=seagreen]
>Thanks for your clear response Sue.
>Unfortunately I still have a problem:
>The following works:-
><%
>dim Cn, SqlStr,rsCustomers
> Set Cn=Server.CreateObject("ADODB.Connection")
> Cn.Provider = "sqloledb"
> Cn.Properties("Data Source") = "Study\StudySQLServer"
> Cn.Properties("Initial Catalog") = "NorthWind"
> Cn.Properties("Connect Timeout") = "3"
> Cn.Properties("User ID") = "sa"
> Cn.Properties("Password") = "mypassword"
> Cn.open
> . . . code which displays Customer info
>The folowing does NOT:-
><%
>dim Cn, CnStr, SqlStr,rsCustomers
> Set Cn=Server.CreateObject("ADODB.Connection")
> CnStr="Provider=sqloledb;" & _
> "Data Source=Study\StudySqlServer;" & _
> "Initial Catalog=NorthWind;" & _
> "Integrated Security=SSPI"
> response.write "cnStr = " & cnStr
> ' response.end
> Cn.open CnStr
>It fails at Cn.open CnStr
>Error Type:
>(0x80040E4D)
>/MyWebs/Connect_wAuth.asp, line 15
>response.write "cnStr = " & cnStr gives:-
>cnStr = Provider=sqloledb;Data Source=Study\StudySqlServer;Initial Catalog=NorthWind;Integrated Security=SSPI
>In Query Analyser (login using Windows Authentification)
>select user_Name() >> dbo
>select * from Customers >> a list of customers
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message news:5tuui1l8ku9a5fl6r704knccn7jfun1kf4@.4ax.com...

Can't Connect

Win 2000, sqlServer 2000 Personal edition
Trying ot connect using .asp Vb Script
1. Sql server set to use Windows Authentication
2. Log onto Windows 2000 as Jim Bunton {no password)
3 Server 'Study' running ok
4. sql query analyser
i. "SELECT User_Name > dbo
ii. [using database NorthWind]
"SELECT * FROM Customers" > gives expected result
5. VB script
** BEGIN CODE connect.asp ***
<%
@. LANGUAGE="VBSCRIPT"
%>
<%
Option explicit
response.expires = 0
%>
<!-- #include file="adovbs.inc" -->
<html>
<head>
<title></title>
</head>
<body>
<%
dim Cn, CnStr
Set Cn = Server.CreateObject("ADODB.Connection")
Cn.ConnectionTimeOut = 1
Cn.provider="sqloledb"
response.write "Conn Provider is " & Cn.provider
CnStr="Data Source=Study;Initial Catalog=Norhwind;User
Id=sa;Password=;"
' Tried all sorts of user id's and paswords
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id = 'Jim
Bunton';Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
=dbo;Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
JimBunton;Password=;"
'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
='Study\Jim Bunton';Password=;"
%>
<p>--</p>
<%
response.write "Cnstr = " & CnStr
'ERROR ALWAYS OCCURS ON NEXT LINEon the next line
Cn.open CnStr
%>
<p>--</p>
<%
response.write "The End - ran ok"
%>
</body>
</html>
**** END CODE *****
? what to do'
' am I missing something 'obvious' out ?
Jim BuntonIf you are using windows authentication (also known as a
trusted connection) to connect, you don't supply a user
name, password in the connection string. Instead, you
indicate this by using Integrated Security=SSPI
in your connection string.
You also want to make sure the database is correct. In your
examples, you want to make sure you use Northwind (you have
Norwind listed).
You can find sample connection strings using the SQL Server
OLE DB provider at:
http://www.carlprothman.net/Default...derForSQLServer
-Sue
On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton"
<jBunton@.BlueYonder.co.uk> wrote:

>Win 2000, sqlServer 2000 Personal edition
>Trying ot connect using .asp Vb Script
>1. Sql server set to use Windows Authentication
>2. Log onto Windows 2000 as Jim Bunton {no password)
>3 Server 'Study' running ok
>4. sql query analyser
> i. "SELECT User_Name > dbo
> ii. [using database NorthWind]
> "SELECT * FROM Customers" > gives expected result
>5. VB script
>** BEGIN CODE connect.asp ***
><%
> @. LANGUAGE="VBSCRIPT"
>%>
><%
> Option explicit
> response.expires = 0
>%>
><!-- #include file="adovbs.inc" -->
><html>
><head>
><title></title>
></head>
><body>
><%
> dim Cn, CnStr
> Set Cn = Server.CreateObject("ADODB.Connection")
> Cn.ConnectionTimeOut = 1
> Cn.provider="sqloledb"
> response.write "Conn Provider is " & Cn.provider
> CnStr="Data Source=Study;Initial Catalog=Norhwind;User
>Id=sa;Password=;"
> ' Tried all sorts of user id's and paswords
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id = 'Jim
>Bunton';Password=;"
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
>=dbo;Password=;"
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
>JimBunton;Password=;"
> 'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
>='Study\Jim Bunton';Password=;"
>%>
><p>--</p>
><%
> response.write "Cnstr = " & CnStr
> 'ERROR ALWAYS OCCURS ON NEXT LINEon the next line
> Cn.open CnStr
>%>
><p>--</p>
><%
> response.write "The End - ran ok"
>%>
></body>
></html>
>**** END CODE *****
>? what to do'
>' am I missing something 'obvious' out ?|||Thanks for your clear response Sue.
Unfortunately I still have a problem:
The following works:-
<%
dim Cn, SqlStr,rsCustomers
Set Cn=Server.CreateObject("ADODB.Connection")
Cn.Provider = "sqloledb"
Cn.Properties("Data Source") = "Study\StudySQLServer"
Cn.Properties("Initial Catalog") = "NorthWind"
Cn.Properties("Connect Timeout") = "3"
Cn.Properties("User ID") = "sa"
Cn.Properties("Password") = "mypassword"
Cn.open
. . . code which displays Customer info
The folowing does NOT:-
<%
dim Cn, CnStr, SqlStr,rsCustomers
Set Cn=Server.CreateObject("ADODB.Connection")
CnStr="Provider=sqloledb;" & _
"Data Source=Study\StudySqlServer;" & _
"Initial Catalog=NorthWind;" & _
"Integrated Security=SSPI"
response.write "cnStr = " & cnStr
' response.end
Cn.open CnStr
It fails at Cn.open CnStr
Error Type:
(0x80040E4D)
/MyWebs/Connect_wAuth.asp, line 15
response.write "cnStr = " & cnStr gives:-
cnStr = Provider=sqloledb;Data Source=Study\StudySqlServer;Initial Catalog=N
orthWind;Integrated Security=SSPI
In Query Analyser (login using Windows Authentification)
select user_Name() >> dbo
select * from Customers >> a list of customers
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message news:5tuui1l8ku9a5fl6r704knccn7jfun1
kf4@.4ax.com...
> If you are using windows authentication (also known as a
> trusted connection) to connect, you don't supply a user
> name, password in the connection string. Instead, you
> indicate this by using Integrated Security=SSPI
> in your connection string.
> You also want to make sure the database is correct. In your
> examples, you want to make sure you use Northwind (you have
> Norwind listed).
> You can find sample connection strings using the SQL Server
> OLE DB provider at:
> [url]http://www.carlprothman.net/Default.aspx?tabid=87#OLEDBProviderForSQLServer[/url
]
>
> -Sue
>
> On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton"
> <jBunton@.BlueYonder.co.uk> wrote:
>
>|||Then it's likely the authentication settings on the IIS side
of it. Try adding the IUSR account as a login in SQL Server
with the appropriate permissions as needed for your code.
Also, turned on failed login audits in SQL Server and
restart the instance. That will help you track down what
login is failing.
-Sue
On Tue, 20 Sep 2005 10:17:50 GMT, "Jim Bunton"
<jBunton@.BlueYonder.co.uk> wrote:
[vbcol=seagreen]
>Thanks for your clear response Sue.
>Unfortunately I still have a problem:
>The following works:-
><%
>dim Cn, SqlStr,rsCustomers
> Set Cn=Server.CreateObject("ADODB.Connection")
> Cn.Provider = "sqloledb"
> Cn.Properties("Data Source") = "Study\StudySQLServer"
> Cn.Properties("Initial Catalog") = "NorthWind"
> Cn.Properties("Connect Timeout") = "3"
> Cn.Properties("User ID") = "sa"
> Cn.Properties("Password") = "mypassword"
> Cn.open
> . . . code which displays Customer info
>The folowing does NOT:-
><%
>dim Cn, CnStr, SqlStr,rsCustomers
> Set Cn=Server.CreateObject("ADODB.Connection")
> CnStr="Provider=sqloledb;" & _
> "Data Source=Study\StudySqlServer;" & _
> "Initial Catalog=NorthWind;" & _
> "Integrated Security=SSPI"
> response.write "cnStr = " & cnStr
> ' response.end
> Cn.open CnStr
>It fails at Cn.open CnStr
>Error Type:
>(0x80040E4D)
>/MyWebs/Connect_wAuth.asp, line 15
>response.write "cnStr = " & cnStr gives:-
>cnStr = Provider=sqloledb;Data Source=Study\StudySqlServer;Initial Catalog=
NorthWind;Integrated Security=SSPI
>In Query Analyser (login using Windows Authentification)
>select user_Name() >> dbo
>select * from Customers >> a list of customers
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message news:5tuui1l8ku9a5f
l6r704knccn7jfun1kf4@.4ax.com...sql

Cant connect

Win 2000, sqlServer 2000 Personal edition

Trying ot connect using .asp Vb Script

1. Sql server set to use Windows Authentication
2. Log onto Windows 2000 as Jim Bunton {no password)
3 Server 'Study' running ok
4. sql query analyser
i. "SELECT User_Name > dbo
ii. [using database NorthWind]
"SELECT * FROM Customers" > gives expected result

5. VB script
** BEGIN CODE connect.asp ***
<%
@. LANGUAGE="VBSCRIPT"
%
<%
Option explicit
response.expires = 0
%
<!-- #include file="adovbs.inc" --
<html>
<head>
<title></title>
</head>
<body>
<%
dim Cn, CnStr
Set Cn = Server.CreateObject("ADODB.Connection")
Cn.ConnectionTimeOut = 1
Cn.provider="sqloledb"
response.write "Conn Provider is " & Cn.provider
CnStr="Data Source=Study;Initial Catalog=Norhwind;User
Id=sa;Password=;"
' Tried all sorts of user id's and paswords
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
'Jim Bunton';Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
=dbo;Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
JimBunton;Password=;"
'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
='Study\Jim Bunton';Password=;"
%>
<p>----</p>
<%
response.write "Cnstr = " & CnStr
'ERROR ALWAYS OCCURS ON NEXT LINE
Cn.open CnStr
'Error Type:
'(0x80004005)
'Unspecified error
'/myweb/mywebs/connect.asp, line 35
%>
<p>----</p>
<%
response.write "The End - ran ok"
%
</body
</html
**** END CODE *****

? what to do??
?? am I missing something 'obvious' out ?

--

Jim BuntonJim Bunton (jBunton@.BlueYonder.co.uk) writes:
> Win 2000, sqlServer 2000 Personal edition
> Trying ot connect using .asp Vb Script
> 1. Sql server set to use Windows Authentication
> 2. Log onto Windows 2000 as Jim Bunton {no password)

You're a brave man!

> 'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
>='Study\Jim Bunton';Password=;"

That is not likely to be correct. User Id and Password is for SQL
authentication, and SQL logins usually don't have \ in them. To login
with Windows authentication, specify "Integrated Security=SSPI", or
Trusted_connect=Yes.

And spell Northwind correctly. :-)

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Tuesday, March 27, 2012

Can't Change Registry keys in Failover Clustering

Plat form: Windows 2003 enterprise ed,
SQL Server 2000 Failover Clustering SP3A enterprise ed.
Action: Change some registry keys after bring SQL resources offline.
I am trying to change the following registry keys to point to new location
on registry at
Master node, member node and virtual server. However, Sytem didn't allow me
to change. The Keys changed themself back after I brought SQL resources back
online or reboot nodes:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer
FullTextDefaultPath
E:\DATA\MSSQL\FTDATA
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Replication
WorkingDirectory
E:\DATA\MSSQL\REPLDATA
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Setup
SQLDataRoot
E:\DATA\MSSQL
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ SQLServerAgent
WorkingDirectory
E:\DATA\MSSQL\JOBS
There must be somewhere hidden in the registry to override those keys I did
change. Can anyone help me figure out how to change those keys in failover
clustering? Is there anyone with such expience? how do you fix that?
Thank you.
Maggie
Hello Maggie,
This is the expected behavior for a clustered SQL Server 2000 instance. The behavior that you saw is due to the fact the registry entries are stored in the Quorum and are over written when you get the SQL Server
resource online. Changing the registry entries is NOT Supported (although there are ways to do it) and I do not recommend it.
Are you trying the registry changes on a production server or a test server?
What exactly are you trying to achieve?
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||For SQL Server default installation, we have default the locations for the
following subdirectories:
BACKUP - default backup location
FTDATA - default FT Catalog location and FTS system config files
JOBS - SQL Agent working area
REPLDATA - Replication working area
However, we need to move them from default installation location to other
cluster disck drives in order apply our capacity planning, such as:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\
Backup from E:\data\mssql\backup to F:\backup
FullTextDefaultPath from E:\DATA\MSSQL\FTDATA to E:\FTDATA
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Replication\WorkingDirectory
E:\DATA\MSSQL\REPLDATA to R:\REPLDATA
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Setup
SQLDataRoot from E:\DATA\MSSQL to E:\DATA
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ SQLServerAgent
WorkingDirectory from E:\DATA\MSSQL\JOBS to J:\JOBS
Plus, we even could not change any
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0 for applications, gathering
manager and indexer to redirect our full text indexes.
We are in middle of building SQL Server Failover Clustering . We are able
to change registry keys on other non-clustering regulger SQL Server to apply
our disk/file allocation design. But we can't change on the same registry
keys on Clustering as we always did on non-cluster. I hope that Microsoft
can work with us to solve this issue, and make failover clustering for SQL
Server configuable same as on reguler Window 2003 server enterprise ed.
Thank you.
Maggie
|||Maggie,
Even though you can change the registry entries for a regular SQL Server instance, it is not the recommended/supported method (infact it is the worst case scenario and done only with the assistance of a SQL Server
support engineer). SQL Server clustered instances are slightly different and the registry entries are replicated to all cluster nodes and are stored in the quorum. It is not supported to change the registry. That does not
mean one cannot change the registry keys for clustered SQL instances but then what is the guarantee that something may not break. So why go the unsupported path. Not worth it for a production server.
But this doesn't mean that one cannot change the location of the data files, log files, backups etc to other shared disk on the cluster. Supported steps that could be used on regular instances can still be used on
clustered SQL Server. For example, to move the log files on a seperate drive, one could used attach/detach method or Restore with Move.
KB "http://support.microsoft.com/?kbid=314546" has some ideas and links to related articles that you may find helpful.
You can also open up a case with Microsoft Customer Support Services for additional support. Call Support Customer Care: 1-800-936-3500 (U.S. and Canada Only)
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Actually, I already know these articles about moving databases around. And
also I always applied these procedures when each time I built new SQL Server.
However, There are not appliable to move default BACKUP, FTDATA ,JOBS and
REPLDATA folders to other disk drives instead of default E:\data\mssql\ on
failover clustering, such as,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\
Backup from E:\data\mssql\backup to F:\backup
FullTextDefaultPath from E:\DATA\MSSQL\FTDATA to E:\FTDATA
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Replication\WorkingDirectory E:\DATA\MSSQL\REPLDATA to R:\REPLDATA
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Setup
SQLDataRoot from E:\DATA\MSSQL to E:\DATA
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ SQLServerAgent
WorkingDirectory from E:\DATA\MSSQL\JOBS to J:\JOBS
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0 for applications, gathering
manger, indexer
We do not want to point Backup, jobs, replication and FTDATA to same disk
drives. We need spread out files across the physical drives in order to
allocate resources efficiently. That's best way to implement enterprise
level database servers.
Oracle provide OFA(Optimal Flexible Architecture) to allow us to implement
very large database as part of software without additonal support call.
Microsoft should do the same feature if you have a big vision to support
enterprise databases.
Thanks.
"Uttam Parui[MS]" wrote:

> Maggie,
> Even though you can change the registry entries for a regular SQL Server instance, it is not the recommended/supported method (infact it is the worst case scenario and done only with the assistance of a SQL Server
> support engineer). SQL Server clustered instances are slightly different and the registry entries are replicated to all cluster nodes and are stored in the quorum. It is not supported to change the registry. That does not
> mean one cannot change the registry keys for clustered SQL instances but then what is the guarantee that something may not break. So why go the unsupported path. Not worth it for a production server.
> But this doesn't mean that one cannot change the location of the data files, log files, backups etc to other shared disk on the cluster. Supported steps that could be used on regular instances can still be used on
> clustered SQL Server. For example, to move the log files on a seperate drive, one could used attach/detach method or Restore with Move.
> KB "http://support.microsoft.com/?kbid=314546" has some ideas and links to related articles that you may find helpful.
> You can also open up a case with Microsoft Customer Support Services for additional support. Call Support Customer Care: 1-800-936-3500 (U.S. and Canada Only)
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||You are correct that one should spread out files across the physical drives in order to allocate resources efficiently. And this is how most of our customers do for their GB and TB dbs.
But can't we do the same thing without touching the registry. For example, if I want to use drive V: for Backup, W: for jobs, X: for Replication then we can make these drives dependencies for SQL Server and then use
them. For example, for the backup one will just have to point the new drive (in this case V. Similary for the jobs, the job definition will point to the appropriate drive. Same will be true for Replication (using TSQL). I am
not an expert on Fulltext and cannot speak for that though. Somebody in the Fulltext newsgroup may be able to answer how to change the default location using TSQL/SEM.
Please note that changing registry (for any SQL instance whether default or virtual) is not supported and may give you undesired results. It is always best to use TSQL or SEM to make the changes. There may be
certain things that cannot be done (as of now) -- for example changing the virtual server name (other than uninstalling/reinstalling) and we have filed a Design Change Request to the SQL development team.
If you feel a particular feature or change should be made, please feel free to write to sqlwish@.microsoft.com decribing the feature you want and its business impact. You may not get a reply back but the SQL
Developers are monitoring it and they will consider it for next versions/service pack changes.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thank you for your advice. I still have some questions:
1. Can you tell me how to change default location for V: for Backup, W: for
jobs, X: for Replication with TSQL/SEM ?
2. Can you ask your Fulltext team on how to change the default location
using TSQL/SEM on failover clusterng environment?
3. You may request Microsoft SQL Team to offer OFA(Optimal Flexible
Architecture) to the customers on Failover Clustering environment with
formal documents on implementation.
Best Regards,
Maggie
"Uttam Parui[MS]" wrote:

> You are correct that one should spread out files across the physical drives in order to allocate resources efficiently. And this is how most of our customers do for their GB and TB dbs.
> But can't we do the same thing without touching the registry. For example, if I want to use drive V: for Backup, W: for jobs, X: for Replication then we can make these drives dependencies for SQL Server and then use
> them. For example, for the backup one will just have to point the new drive (in this case V. Similary for the jobs, the job definition will point to the appropriate drive. Same will be true for Replication (using TSQL). I am
> not an expert on Fulltext and cannot speak for that though. Somebody in the Fulltext newsgroup may be able to answer how to change the default location using TSQL/SEM.
> Please note that changing registry (for any SQL instance whether default or virtual) is not supported and may give you undesired results. It is always best to use TSQL or SEM to make the changes. There may be
> certain things that cannot be done (as of now) -- for example changing the virtual server name (other than uninstalling/reinstalling) and we have filed a Design Change Request to the SQL development team.
> If you feel a particular feature or change should be made, please feel free to write to sqlwish@.microsoft.com decribing the feature you want and its business impact. You may not get a reply back but the SQL
> Developers are monitoring it and they will consider it for next versions/service pack changes.
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||See inline.
HTH,
Wish you a very happy and prosperous New Year.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
From: =?Utf-8?B?TWFnZ2ll?= <Maggie@.discussions.microsoft.com>
Subject: RE: Can't Change Registry keys in Failover Clustering
Date: Thu, 30 Dec 2004 09:13:06 -0800
Newsgroups: microsoft.public.sqlserver.clustering
Thank you for your advice. I still have some questions:
1. Can you tell me how to change default location for V: for Backup, W: for
jobs, X: for Replication with TSQL/SEM ?
<uttam>
- Assuming SQL Server resource is dependent on V:, W: and X:
- For Backup, if it is a TSQL backup job then I will basically change the TSQL statement to point to V:
For ex, If the backup job is as
BACKUP DATABASE TestDB
TO DISK = 'c:\Testdb.bak'
I will change it to
BACKUP DATABASE TestDB
TO DISK = 'V:\Testdb.bak'
Or if you are using database maintenance plan wizard to create the backup job, you will be able to use V: as the backup location.
- Same idea for jobs.
- For Replication, one method would be to use the TSQL command sp_changedistpublisher. See SQL Server Books Online for syntax.
</uttam>
2. Can you ask your Fulltext team on how to change the default location
using TSQL/SEM on failover clusterng environment?
<uttam> As experts in SQL Clustering are monitoring this newsgroup, experts in SQL fulltext are monitoring the fulltext newsgroup.
Please post your qs in the sql fulltext newsgroup.
http://www.microsoft.com/sql/communi...ver.fulltex t
For all SQL Server newsgroups, see
http://www.microsoft.com/sql/communi...s/default.mspx
</uttam>
3. You may request Microsoft SQL Team to offer OFA(Optimal Flexible
Architecture) to the customers on Failover Clustering environment with
formal documents on implementation.
<uttam> I can do that. But I would suggest that you directly email sqlwish@.microsoft.com. Its better for the development team to hear directly from our customers. It does makes a difference. Do write the business
impact (i.e. how this will benefit your business and/how you are hurting without it, etc) . All emails are monitored and are considered for next versions/service packs.
</uttam>
Best Regards,
Maggie

Cant Auto-Start Agent

I have a SQL Server 2000 that failed to start after a Windows reboot.
Agent properties are checked to auto start if stopped. Under the Agent
Error Log, I have the following data:

Information:
SQL Agent stopping because of Windows shutdown.
SQL Agent terminated normally.

Error:
SQL Server Error: 1115, cannot generate SSPI context SQLState HY000.
Logon to server(local) failed.

Help apprecaited. Thanks
Frank

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Frank Py <fpy@.proactnet.com> wrote in message news:<3f843998$0$202$75868355@.news.frii.net>...
> I have a SQL Server 2000 that failed to start after a Windows reboot.
> Agent properties are checked to auto start if stopped. Under the Agent
> Error Log, I have the following data:
> Information:
> SQL Agent stopping because of Windows shutdown.
> SQL Agent terminated normally.
> Error:
> SQL Server Error: 1115, cannot generate SSPI context SQLState HY000.
> Logon to server(local) failed.
> Help apprecaited. Thanks
> Frank
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

You might find these KB articles helpful:

http://support.microsoft.com/defaul...9&Product=sql2k
http://support.microsoft.com/defaul...4&Product=sql2k

Simon|||I am having this problem, too. Have you found a solution?

Sunday, March 25, 2012

Can't attach a database during an install

I have a Wise for Windows Installer package that will install SQL Express 2005 and then attach a database. In order to keep consistent I am placing the new .MDF file in C:\Program Files\Microsoft SQL Server\MSSQL$INSTANCE\data. If the folders don't exists I create them. Well, on one test machine I create the folder and copy the MDF to the directory and then use 'osql' to attach the database but I am getting this error:

Msg 5173, Level 16, State 1, Server SREXROAT2\FHMOBILE, Line 1 One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup. Msg 1813, Level 16, State 2, Server [COMPUTERNAME], Line 1 Could not open new database '[DATABASE NAME]'. CREATE DATABASE is aborted. Log file '[LOG FILE NAME]' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.

Does anyone know how to get around this? It works on our other test machines with the same database.

hi,

a dumb question of mines... did you try with another copy of the installer package? is it corrupt?

regards

|||

You should be installing both the .MDF and the .LDF.

|||The problem, besides not attaching correctly, was that the MDF file was attached to a different location and a different name so that when I would attach it during the install it would try and create the log file in the wrong spot and this case it already existed.

Thursday, March 22, 2012

can't add current login as user (more)

That's SQL Server 2000 (sorry!) and Windows (Server)
2000... it's almost like SQL isn't reading from or
synchronizing with Active Directory properly, but we can
find no other indicator that there is a problem.
Again, any help is greatly appreciated!

>--Original Message--
>Hi all. I'm having problems trying to add a current
login
>as a user to any databases. The logins are there, but
>when I try to give one access to another db, or even if I
>try to add user from within the db itself, I get error
>15401 (Windows NT user or group not found). I looked in
>KB but could only find this error in reference to adding
a
>new login. As stated, the logins are already setup and
>have been for about two years now, the system just won't
>let me add them as users.
>What really gets me is how SQL Server will let me use the
>necessary tool to pick the login from the list, but then
>it says it's not found. (?)
>Thanks in advance for any help!
>Sandy Mach
>.
>Check the article I just posted for you in the first message
on this (you can keep all these in the same thread...just
reply to the original to follow up and add additional info).
The only time I've run into something similar was with
accounts that were renamed.
-Sue
On Thu, 25 Mar 2004 11:32:05 -0800, "Sandy Mach"
<anonymous@.discussions.microsoft.com> wrote:
>That's SQL Server 2000 (sorry!) and Windows (Server)
>2000... it's almost like SQL isn't reading from or
>synchronizing with Active Directory properly, but we can
>find no other indicator that there is a problem.
>Again, any help is greatly appreciated!
>
>login
>a|||Right, and that's happened here before too, but we
reconciled those long ago. This is something new because
these accounts haven't been renamed since then, and I've
added them as users since then.

>--Original Message--
>Check the article I just posted for you in the first
message
>on this (you can keep all these in the same thread...just
>reply to the original to follow up and add additional
info).
>The only time I've run into something similar was with
>accounts that were renamed.
>-Sue
>On Thu, 25 Mar 2004 11:32:05 -0800, "Sandy Mach"
><anonymous@.discussions.microsoft.com> wrote:
>
I
in
adding
won't
the
then
>.
>sql

Can't access SqlServer 2005 using JDBC

Hi;

I can access SqlServer 2000 fine, but not SqlServer 2005. My client is on Windows XP and SqlServer 2005 (dev version) is on Windows 2003. When I run I get:

Error: net.windward.datasource.DataSourceException: JdbcDataSource could not ope
n jdbc:sqlserver://T1-Databases;databaseName=AdventureWorks;integratedSecurity=t
rue;
net.windward.datasource.DataSourceException: net.windward.datasource.DataSourceE
xception: JdbcDataSource could not open jdbc:sqlserver://T1-Databases;databaseNa
me=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more
Exception in thread "main" net.windward.datasource.DataSourceException: net.wind
ward.datasource.DataSourceException: JdbcDataSource could not open jdbc:sqlserve
r://T1-Databases;databaseName=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more

Any ideas?

thanks - dave

Are you using Microsoft SQL Server 2005 JDBC Driver version 1.1?

What platform (OS and version) does your JDBC client run on?

|||

I have similar error:

java.lang.NoClassDefFoundError
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)

I do have the JDBC driver version 1.1.

Cocoon 2.0

Tomcat 4.x

|||

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true

It appears as though it has something to do with integratedSecurity. I think the connection string is case sensitive, you did spell it IntegratedSecurity="True" right? The exception thrown seems to be targetted to integratedSecurity specifically. Also, are you authenticating in mixed mode or windows only? Did you configure the server on install correctly to be able to authenticate the kind of connection you are trying to make?

Hope we can figure this one out together,

John

|||

Have you tried enabling the TCP/IP Protocol through the SQL Server Configuration Manager? I seem to recall it being turned off by default in SQL 2005. Enable it and restart the SQL Service.

Good luck,

-Tom

|||You can run SQL Profiler to check if your application is indeed trying to establish a connection or not.|||It looks like you are using the 1.0 dirver which did not support integrated auth property.sql

Can't access SqlServer 2005 using JDBC

Hi;

I can access SqlServer 2000 fine, but not SqlServer 2005. My client is on Windows XP and SqlServer 2005 (dev version) is on Windows 2003. When I run I get:

Error: net.windward.datasource.DataSourceException: JdbcDataSource could not ope
n jdbc:sqlserver://T1-Databases;databaseName=AdventureWorks;integratedSecurity=t
rue;
net.windward.datasource.DataSourceException: net.windward.datasource.DataSourceE
xception: JdbcDataSource could not open jdbc:sqlserver://T1-Databases;databaseNa
me=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more
Exception in thread "main" net.windward.datasource.DataSourceException: net.wind
ward.datasource.DataSourceException: JdbcDataSource could not open jdbc:sqlserve
r://T1-Databases;databaseName=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more

Any ideas?

thanks - dave

Are you using Microsoft SQL Server 2005 JDBC Driver version 1.1?

What platform (OS and version) does your JDBC client run on?

|||

I have similar error:

java.lang.NoClassDefFoundError
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)

I do have the JDBC driver version 1.1.

Cocoon 2.0

Tomcat 4.x

|||

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true

It appears as though it has something to do with integratedSecurity. I think the connection string is case sensitive, you did spell it IntegratedSecurity="True" right? The exception thrown seems to be targetted to integratedSecurity specifically. Also, are you authenticating in mixed mode or windows only? Did you configure the server on install correctly to be able to authenticate the kind of connection you are trying to make?

Hope we can figure this one out together,

John

|||

Have you tried enabling the TCP/IP Protocol through the SQL Server Configuration Manager? I seem to recall it being turned off by default in SQL 2005. Enable it and restart the SQL Service.

Good luck,

-Tom

|||You can run SQL Profiler to check if your application is indeed trying to establish a connection or not.|||It looks like you are using the 1.0 dirver which did not support integrated auth property.

Can't access SqlServer 2005 using JDBC

Hi;

I can access SqlServer 2000 fine, but not SqlServer 2005. My client is on Windows XP and SqlServer 2005 (dev version) is on Windows 2003. When I run I get:

Error: net.windward.datasource.DataSourceException: JdbcDataSource could not ope
n jdbc:sqlserver://T1-Databases;databaseName=AdventureWorks;integratedSecurity=t
rue;
net.windward.datasource.DataSourceException: net.windward.datasource.DataSourceE
xception: JdbcDataSource could not open jdbc:sqlserver://T1-Databases;databaseNa
me=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more
Exception in thread "main" net.windward.datasource.DataSourceException: net.wind
ward.datasource.DataSourceException: JdbcDataSource could not open jdbc:sqlserve
r://T1-Databases;databaseName=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more

Any ideas?

thanks - dave

Are you using Microsoft SQL Server 2005 JDBC Driver version 1.1?

What platform (OS and version) does your JDBC client run on?

|||

I have similar error:

java.lang.NoClassDefFoundError
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)

I do have the JDBC driver version 1.1.

Cocoon 2.0

Tomcat 4.x

|||

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true

It appears as though it has something to do with integratedSecurity. I think the connection string is case sensitive, you did spell it IntegratedSecurity="True" right? The exception thrown seems to be targetted to integratedSecurity specifically. Also, are you authenticating in mixed mode or windows only? Did you configure the server on install correctly to be able to authenticate the kind of connection you are trying to make?

Hope we can figure this one out together,

John

|||

Have you tried enabling the TCP/IP Protocol through the SQL Server Configuration Manager? I seem to recall it being turned off by default in SQL 2005. Enable it and restart the SQL Service.

Good luck,

-Tom

|||You can run SQL Profiler to check if your application is indeed trying to establish a connection or not.|||It looks like you are using the 1.0 dirver which did not support integrated auth property.

Can't access SQL Server Reporting Services URL anymore

Hi all,
We've had a Reporting Services installation for nearly 6 months now with no
problems. Reporting Services is installed on a Windows 2003 machine which is
connecting to SQL Server 2000 databases.
This morning, it was reporting that the URL to access the report server
(http://server/reports) is returning the following error message:
The report server cannot open a connection to the report server database. A
connection to the database is required for all requests and processing.
(rsReportServerDatabaseUnavailable) Get Online Help Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
Not sure where to go from here. Nothing has changed as far as we can tell.
Thanks,
JasonThere's also an error in the event log of the Reporting Services machine that
states:
Report Server cannot connect to the report server database.
How do I re-establish this connection? The database still resides on the
same server, same name as before. I am not sure how this happened.
"Jason" wrote:
> Hi all,
> We've had a Reporting Services installation for nearly 6 months now with no
> problems. Reporting Services is installed on a Windows 2003 machine which is
> connecting to SQL Server 2000 databases.
> This morning, it was reporting that the URL to access the report server
> (http://server/reports) is returning the following error message:
>
> The report server cannot open a connection to the report server database. A
> connection to the database is required for all requests and processing.
> (rsReportServerDatabaseUnavailable) Get Online Help Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
>
> Not sure where to go from here. Nothing has changed as far as we can tell.
> Thanks,
> Jason
>

Tuesday, March 20, 2012

can't access server - lost sa password

We have what we think is msde running on a box. No one knows the sa password.
I am in the domain admin group on Windows and the Windows admin group but
when I right click on BUILTIN\administrator, I don't get the "properties"
menu selection. I also can't create a new login.
A few weeks ago I was able to create a new login and a new database. I'm not
sure what happened. My windows login is not there anymore but I would have
thought I could use the BUILTIN\administrator login to admin the server.
Any ideas on how I can get control of the server?
Thanks,
Dan D.
Although I hate tools like these but try this tool if it works for you ...
http://www.nextgenss.com/sqlcrack.htm
Harman Sahni
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:E449D233-29E8-4ED0-AC95-2B4BF0FDC6D3@.microsoft.com...
> We have what we think is msde running on a box. No one knows the sa
password.
> I am in the domain admin group on Windows and the Windows admin group but
> when I right click on BUILTIN\administrator, I don't get the "properties"
> menu selection. I also can't create a new login.
> A few weeks ago I was able to create a new login and a new database. I'm
not
> sure what happened. My windows login is not there anymore but I would have
> thought I could use the BUILTIN\administrator login to admin the server.
> Any ideas on how I can get control of the server?
> Thanks,
> --
> Dan D.
|||Thanks but I figured out the sa password. I'll keep this for future reference.
"Harman Sahni" wrote:

> Although I hate tools like these but try this tool if it works for you ...
> http://www.nextgenss.com/sqlcrack.htm
> Harman Sahni
>
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:E449D233-29E8-4ED0-AC95-2B4BF0FDC6D3@.microsoft.com...
> password.
> not
>
>
|||Dan
Log in SQL Server with Windows Authentication and run EXEC sp_password NULL,
'NewPass', 'MyUser
'
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:2264F204-A7B6-422A-95AC-0517B560C27C@.microsoft.com...
> Thanks but I figured out the sa password. I'll keep this for future
reference.[vbcol=seagreen]
> "Harman Sahni" wrote:
...[vbcol=seagreen]
but[vbcol=seagreen]
"properties"[vbcol=seagreen]
I'm[vbcol=seagreen]
have[vbcol=seagreen]
server.[vbcol=seagreen]