How do I add an avatar to the public avatar library?
Classic ASP connectionstring to SQL Server 2005
Hello Guest
  
  • Login
• Register…
• Start blog
  • Who, Where, When
• What can I do?
• What to Read?
  • Polls
• Avatars
• Interests
  • Cities and Countries
• Random blog
• Users search
  • Search
• Games
• Tests
• QAIX
  • Сообщества
• Talxy Chat
• Horoscope
• Online
 
Зарегистрируйся!

QAIX > ASP web-programming > Classic ASP connectionstring to SQL Server 2005 30 June 2008 15:01:10

  Recent blog posts: 
  They have birthday today: 
  Forums:   
  Discuss: 
  Recent forum topics: 
  Recent forum comments:
  Moderators:

Classic ASP connectionstring to SQL Server 2005

Guy 30 June 2008 15:01:10
 Hi

I am supporting a classic ASP application that uses SQL Server 2000 on the
backend. I now need to contect to a SQL Server 2K5 database. I currently use
conntectionstring: Provider= sqloledb.1;Persist Security Info=False;User
ID='XXX';Password= 'XXXX';Initial Catalog= 'XXXXX';Data Source='XXXX';Conne­ct
Timeout='25' which does not work. Is there another connectionstring I should
use?


Thanks
Guy
Add comment
Bob Barrows 13 March 2008 20:06:12 permanent link ]
 Guy wrote:
Hi
I am supporting a classic ASP application that uses SQL Server 2000
on the backend. I now need to contect to a SQL Server 2K5 database. I
currently use conntectionstring: Provider= sqloledb.1;Persist
Security Info=False;User ID='XXX';Password= 'XXXX';Initial Catalog=
'XXXXX';Data Source='XXXX';Conne­ct Timeout='25' which does not work.
Is there another connectionstring I should use?
That's pretty much what I use. You can also use the SQLNCLI provider
instead of the SQLOLEDB one, but if SQLOLEDB isn't working, then neither
should SQLNCLI. (btw - always endeavor to describe your symptoms without
using the words "not work" or "not working" or similar non-descriptive
verbiage - error messages are always helpful).

Is TCP/IP enabled on your sql server? I think you have to use the SQL
Server Surface Area Configuration tool (Start>SQL Server
2005>Configuration Tools) to enable it ... yes, it's accessed by
clicking the Services and Connections link. Look for the Remote
Connections option in the Database Engine node.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.


Add comment
Guy 14 March 2008 18:55:02 permanent link ]
 Thanks for the information. I tried using ‘SQLNCLI’ but when I did I received
an error message:

ADODB.Connection error '800a0e7a'

Provider cannot be found. It may not be properly installed.

I also checked to see if TCP/IP is enabled and it is. I noticed that there
is an option to enable both TCP/IP and name pipes. Is that an option I should
enable instead? Did I mention that I am accessing the database from an ASP to
VB6 DLL to SQL Server 2K5? I’m not sure if that matters but I thought I
should mention it. Any other suggestions would be greatly appreciated.

Thanks
Guy
"Bob Barrows [MVP]" wrote:

Guy wrote:
Hi
I am supporting a classic ASP application that uses SQL Server 2000
on the backend. I now need to contect to a SQL Server 2K5 database. I
currently use conntectionstring: Provider= sqloledb.1;Persist
Security Info=False;User ID='XXX';Password= 'XXXX';Initial Catalog=
'XXXXX';Data Source='XXXX';Conne­ct Timeout='25' which does not work.
Is there another connectionstring I should use?
That's pretty much what I use. You can also use the SQLNCLI provider
instead of the SQLOLEDB one, but if SQLOLEDB isn't working, then neither
should SQLNCLI. (btw - always endeavor to describe your symptoms without
using the words "not work" or "not working" or similar non-descriptive
verbiage - error messages are always helpful).
Is TCP/IP enabled on your sql server? I think you have to use the SQL
Server Surface Area Configuration tool (Start>SQL Server
2005>Configuration Tools) to enable it ... yes, it's accessed by
clicking the Services and Connections link. Look for the Remote
Connections option in the Database Engine node.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
Add comment
Bob Barrows 14 March 2008 19:05:05 permanent link ]
 Both libraries should no be needed.
So this connection string is in the VB6 dll? No, it makes no difference.
I'm still in the dark as to the failure mode when using SQLOLEDB. What
is the error message?
Do you have physical access to the machine running the web server? If
so, can you ping the sql server?

Guy wrote:
Thanks for the information. I tried using 'SQLNCLI' but when I did I
received an error message:
ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.
I also checked to see if TCP/IP is enabled and it is. I noticed that
there is an option to enable both TCP/IP and name pipes. Is that an
option I should enable instead? Did I mention that I am accessing the
database from an ASP to VB6 DLL to SQL Server 2K5? I'm not sure if
that matters but I thought I should mention it. Any other suggestions
would be greatly appreciated.
Thanks
Guy
"Bob Barrows [MVP]" wrote:
Guy wrote:
Hi
I am supporting a classic ASP application that uses SQL Server 2000
on the backend. I now need to contect to a SQL Server 2K5 database.
I currently use conntectionstring: Provider= sqloledb.1;Persist
Security Info=False;User ID='XXX';Password= 'XXXX';Initial Catalog=
'XXXXX';Data Source='XXXX';Conne­ct Timeout='25' which does not work.
Is there another connectionstring I should use?
That's pretty much what I use. You can also use the SQLNCLI provider
instead of the SQLOLEDB one, but if SQLOLEDB isn't working, then
neither should SQLNCLI. (btw - always endeavor to describe your
symptoms without using the words "not work" or "not working" or
similar non-descriptive verbiage - error messages are always
helpful).
Is TCP/IP enabled on your sql server? I think you have to use the SQL
Server Surface Area Configuration tool (Start>SQL Server
2005>Configuration Tools) to enable it ... yes, it's accessed by
clicking the Services and Connections link. Look for the Remote
Connections option in the Database Engine node.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get
a quicker response by posting to the newsgroup.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.


Add comment
Guy 14 March 2008 19:50:01 permanent link ]
 So this connection string is in the VB6 dll? Yes

What is the error message? Provider cannot be found. It may not be properly
installed.

Do you have physical access to the machine running the web server? Yes

If so, can you ping the sql server? Yes


"Bob Barrows [MVP]" wrote:

Both libraries should no be needed.
So this connection string is in the VB6 dll? No, it makes no difference.
I'm still in the dark as to the failure mode when using SQLOLEDB. What
is the error message?
Do you have physical access to the machine running the web server? If
so, can you ping the sql server?
Guy wrote:
Thanks for the information. I tried using 'SQLNCLI' but when I did I
received an error message:
ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.
I also checked to see if TCP/IP is enabled and it is. I noticed that
there is an option to enable both TCP/IP and name pipes. Is that an
option I should enable instead? Did I mention that I am accessing the
database from an ASP to VB6 DLL to SQL Server 2K5? I'm not sure if
that matters but I thought I should mention it. Any other suggestions
would be greatly appreciated.
Thanks
Guy
"Bob Barrows [MVP]" wrote:
Guy wrote:
Hi
I am supporting a classic ASP application that uses SQL Server 2000
on the backend. I now need to contect to a SQL Server 2K5 database.
I currently use conntectionstring: Provider= sqloledb.1;Persist
Security Info=False;User ID='XXX';Password= 'XXXX';Initial Catalog=
'XXXXX';Data Source='XXXX';Conne­ct Timeout='25' which does not work.
Is there another connectionstring I should use?
That's pretty much what I use. You can also use the SQLNCLI provider
instead of the SQLOLEDB one, but if SQLOLEDB isn't working, then
neither should SQLNCLI. (btw - always endeavor to describe your
symptoms without using the words "not work" or "not working" or
similar non-descriptive verbiage - error messages are always
helpful).
Is TCP/IP enabled on your sql server? I think you have to use the SQL
Server Surface Area Configuration tool (Start>SQL Server
2005>Configuration Tools) to enable it ... yes, it's accessed by
clicking the Services and Connections link. Look for the Remote
Connections option in the Database Engine node.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get
a quicker response by posting to the newsgroup.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
Add comment
Bob Barrows 14 March 2008 20:10:31 permanent link ]
 Guy wrote:
So this connection string is in the VB6 dll? Yes
What is the error message? Provider cannot be found. It may not be
properly installed.

I thought that was the error you received when using SQLNCLI? You are
also getting it when using SQLOLEDB? If so, you need to reinstall or
upgrade MDAC on that server.

Do you have physical access to the machine running the web server? Yes
If so, can you ping the sql server? Yes

So it's probbly not a network issue.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.


Add comment
Guest 30 June 2008 15:01:10 permanent link ]
 Hi...

Not sure if you fixed your problem but when I moved to SQLServer 2005 I had problems connecting and was recieving a range of different messages. When 2005 is installed it is defaulted to 'local' connections only...

Navigate to the following Start Menu Item:
Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration.

In the Server 2005 Surface Area Configuration page, select Surface Area Configuration for Services and Connections. Expand Database Engine, select Remote Connections, select Local and remote connections and select the appropriate protocol to enable for your environment, and then click Apply.

Hope this helps... :-)­


Bono
Add comment
 

Add new comment

As:
Login:  Password:  
 
 
  
 
Пожалуйста, относитесь к собеседникам уважительно, не используйте нецензурные слова, не злоупотребляйте заглавными буквами, не публикуйте рекламу и объявления о купле/продаже, а также материалы нарушающие сетевой этикет или УК РФ.


QAIX > ASP web-programming > Classic ASP connectionstring to SQL Server 2005 30 June 2008 15:01:10

see also:
Complete Navigation Tree
Logo-Form like the ZMS-Demo on…
Re: empty workspace - solved
пройди тесты:
see also:
Hello everybody!Here i want to shar...
voipswitch on unbelievable low…
I know 3xp10i73r

  Copyright © 2001—2008 QAIX
Idea: Miсhael Monashev
Помощь и задать вопросы можно в сообществе support.qaix.com.
Сообщения об ошибках оставляем в сообществе bugs.qaix.com.
Предложения и комментарии пишем в сообществе suggest.qaix.com.
Информация для родителей.
Write us at:
If you would like to report an abuse of our service, such as a spam message, please .