| Groups | Blog | Home |
sql server connect : 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.aspx?tabid=87#OLEDBProviderForSQLServer -Sue On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton" [quoted text, click to view] <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=3DServer.CreateObject("ADODB.Connection") Cn.Provider =3D "sqloledb" Cn.Properties("Data Source") =3D "Study\StudySQLServer" Cn.Properties("Initial Catalog") =3D "NorthWind" Cn.Properties("Connect Timeout") =3D "3" Cn.Properties("User ID") =3D "sa" Cn.Properties("Password") =3D "mypassword" Cn.open=20 . . . code which displays Customer info The folowing does NOT:- <% dim Cn, CnStr, SqlStr,rsCustomers Set Cn=3DServer.CreateObject("ADODB.Connection") CnStr=3D"Provider=3Dsqloledb;" & _ "Data Source=3DStudy\StudySqlServer;" & _ "Initial Catalog=3DNorthWind;" & _ "Integrated Security=3DSSPI" response.write "cnStr =3D " & cnStr ' response.end Cn.open CnStr It fails at Cn.open CnStr Error Type: (0x80040E4D) /MyWebs/Connect_wAuth.asp, line 15 response.write "cnStr =3D " & cnStr gives:- cnStr =3D Provider=3Dsqloledb;Data Source=3DStudy\StudySqlServer;Initial = Catalog=3DNorthWind;Integrated Security=3DSSPI In Query Analyser (login using Windows Authentification) select user_Name() >> dbo select * from Customers >> a list of customers [quoted text, click to view] "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message = http://www.carlprothman.net/Default.aspx?tabid=3D87#OLEDBProviderForSQLSe=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=3DSSPI > 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: > = rver [quoted text, click to view] >=20
> -Sue >=20 > On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton" > <jBunton@BlueYonder.co.uk> wrote: >=20 > >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=3D"VBSCRIPT" > >%> > > > ><% > > Option explicit > > response.expires =3D 0 > >%> > > > ><!-- #include file=3D"adovbs.inc" --> > > > ><html> > ><head> > ><title></title> > ></head> > ><body> > ><% > > dim Cn, CnStr > > Set Cn =3D Server.CreateObject("ADODB.Connection") > > Cn.ConnectionTimeOut =3D 1 > > Cn.provider=3D"sqloledb" > > response.write "Conn Provider is " & Cn.provider > > CnStr=3D"Data Source=3DStudy;Initial Catalog=3DNorhwind;User > >Id=3Dsa;Password=3D;" > > ' Tried all sorts of user id's and paswords > > > > 'CnStr=3D"Data Source=3DStudy;Initial Catalog=3DNorhwind;User Id = =3D 'Jim > >Bunton';Password=3D;" > > 'CnStr=3D"Data Source=3DStudy;Initial Catalog=3DNorhwind;User = Id > >=3Ddbo;Password=3D;" > > 'CnStr=3D"Data Source=3DStudy;Initial Catalog=3DNorhwind;User = Id =3D > >JimBunton;Password=3D;" > > 'CnStr=3D"Data Source=3D'Study';Initial = Catalogue=3D'Norhwind';User Id > >=3D'Study\Jim Bunton';Password=3D;" > >%> > ><p>----------</p> > ><% > > response.write "Cnstr =3D " & 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 ???
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" [quoted text, click to view] <jBunton@BlueYonder.co.uk> wrote:
>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.aspx?tabid=87#OLEDBProviderForSQLServer >> >> -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 ??? >>
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
August 2008
| home · blog · groups | Questions? Comments? Contact the dn |