Showing posts with label provider. Show all posts
Showing posts with label provider. Show all posts

Monday, March 26, 2012

Microsoft OLEDB Provider Oracle

Hi,

Previously i was using oracle8i with ssis.ssis was working fine.later i have upgraded 8i to oracle 9i.now when ever i try to establish a new connection using Microsoft OLEDB Provider for Oracle.i am getting the following error "Oracle error occurred, but error message could not be retrieved from Oracle" .but i am able to access the oracle 9i database thru pl/sql and toad. what could be the problem?

Thanks

Jegan.T

We're running fine 9.2 on a development server (2005) along with SSIS packages.

What about tnsnames.ora?

|||

Hi Enric,

my tnsnames.ora is correct .bcoz i am able to login via toad/sqlplus.while upgradeing i have unistalled 8i and installed 9i . do we need to install any drivers?

Thanks

Jegan.T

Microsoft OLEDB provider for DB2 performance issue (Missing where clause on DB2 site)

Hi!

I have just installed Microsoft OLEDB provider for DB2 on a SQL server 2005. I created a Linked server against our DB2 V.8 Z/OS database. I tested the connection via execution of a simple select call, something like:

SELECT FIELD_A FROM DB2SRV.DB2DB.CREATOR_A.TABLE_A

WHERE FIELD_A='ABC'

I traced the call on the DB2 site. The SQL running on DB2 site was to my surprise without the “where clause”:

SELECT FIELD_A FROM DB2DB.CREATOR_A.TABLE_A

So, all rows are moved to SQL server before the where clause is executed, resulting in bad performance. The index on FIELD_A is not used and so on … !

If anyone out there has an idea of what could be wrong, please let me know!

NB. I know that by using OPENQUERY pass-through query, all execution is done on the DB2 site.

Moving to engine to resolve linked server specific issues. With regard to the driver, this blog is probably the place to go for experts on the driver itself:

http://blogs.msdn.com/dotnetinterop/archive/2006/01/19/514702.aspx

Hope this helps,

John

|||

Thanks !

The specific blog reference you gave me didn’t have any answers. But do you suggest that a raise my problem here ?

Brgds Henrik

|||If you are using WHERE clauses, you mihgt have to set the "Dervie Parameters", initialization property of the OLE DB data source to TRUE. It will instruct the provider to derive parameter info from the data source. I think you det it in the Advanced Options page of the Data Source Wizard, or maybe in the Data Links dialog. You might have to set it in the initialization string.|||

Fyi ! I have solved the problem myself. By setting option “collation compatible” to true, the where clause was executed on the DB2 site.

The option can be changed via Microsoft SQL Server Management Studio - linked servers “properties” and “server options” or by executing :

EXEC master.dbo.sp_serveroption @.server=N'DB2TSRV', @.optname=N'collation compatible', @.optvalue=N'true'

Henrik Garde

Microsoft OLEDB provider for DB2 performance issue (Missing where clause on DB2 site)

Hi!

I have just installed Microsoft OLEDB provider for DB2 on a SQL server 2005. I created a Linked server against our DB2 V.8 Z/OS database. I tested the connection via execution of a simple select call, something like:

SELECT FIELD_A FROM DB2SRV.DB2DB.CREATOR_A.TABLE_A

WHERE FIELD_A='ABC'

I traced the call on the DB2 site. The SQL running on DB2 site was to my surprise without the “where clause”:

SELECT FIELD_A FROM DB2DB.CREATOR_A.TABLE_A

So, all rows are moved to SQL server before the where clause is executed, resulting in bad performance. The index on FIELD_A is not used and so on … !

If anyone out there has an idea of what could be wrong, please let me know!

NB. I know that by using OPENQUERY pass-through query, all execution is done on the DB2 site.

Moving to engine to resolve linked server specific issues. With regard to the driver, this blog is probably the place to go for experts on the driver itself:

http://blogs.msdn.com/dotnetinterop/archive/2006/01/19/514702.aspx

Hope this helps,

John

|||

Thanks !

The specific blog reference you gave me didn’t have any answers. But do you suggest that a raise my problem here ?

Brgds Henrik

|||If you are using WHERE clauses, you mihgt have to set the "Dervie Parameters", initialization property of the OLE DB data source to TRUE. It will instruct the provider to derive parameter info from the data source. I think you det it in the Advanced Options page of the Data Source Wizard, or maybe in the Data Links dialog. You might have to set it in the initialization string.|||

Fyi ! I have solved the problem myself. By setting option “collation compatible” to true, the where clause was executed on the DB2 site.

The option can be changed via Microsoft SQL Server Management Studio - linked servers “properties” and “server options” or by executing :

EXEC master.dbo.sp_serveroption @.server=N'DB2TSRV', @.optname=N'collation compatible', @.optvalue=N'true'

Henrik Garde

Microsoft OLEDB provider for DB2 performance issue (Missing where clause on DB2 site)

Hi!

I have just installed Microsoft OLEDB provider for DB2 on a SQL server 2005. I created a Linked server against our DB2 V.8 Z/OS database. I tested the connection via execution of a simple select call, something like:

SELECT FIELD_A FROM DB2SRV.DB2DB.CREATOR_A.TABLE_A

WHERE FIELD_A='ABC'

I traced the call on the DB2 site. The SQL running on DB2 site was to my surprise without the “where clause”:

SELECT FIELD_A FROM DB2DB.CREATOR_A.TABLE_A

So, all rows are moved to SQL server before the where clause is executed, resulting in bad performance. The index on FIELD_A is not used and so on … !

If anyone out there has an idea of what could be wrong, please let me know!

NB. I know that by using OPENQUERY pass-through query, all execution is done on the DB2 site.

Moving to engine to resolve linked server specific issues. With regard to the driver, this blog is probably the place to go for experts on the driver itself:

http://blogs.msdn.com/dotnetinterop/archive/2006/01/19/514702.aspx

Hope this helps,

John

|||

Thanks !

The specific blog reference you gave me didn’t have any answers. But do you suggest that a raise my problem here ?

Brgds Henrik

|||If you are using WHERE clauses, you mihgt have to set the "Dervie Parameters", initialization property of the OLE DB data source to TRUE. It will instruct the provider to derive parameter info from the data source. I think you det it in the Advanced Options page of the Data Source Wizard, or maybe in the Data Links dialog. You might have to set it in the initialization string.|||

Fyi ! I have solved the problem myself. By setting option “collation compatible” to true, the where clause was executed on the DB2 site.

The option can be changed via Microsoft SQL Server Management Studio - linked servers “properties” and “server options” or by executing :

EXEC master.dbo.sp_serveroption @.server=N'DB2TSRV', @.optname=N'collation compatible', @.optvalue=N'true'

Henrik Garde

Microsoft OLEDB Provider Error (with SQL server and ASP)

Dear all,

Still i am having problem with connecting sql server with ASP (Intranet).

Following is the code which i am using for the connection now,

Set conn=Server.CreateObject("ADODB.Connection")
conn.open "DSN=aspfirst;Uid=;PWD=;"

The error mesage , generated by this code is attached with this mail. Please check the attachment and hel me in the same

Gracesonhttp://support.microsoft.com/default.aspx?scid=kb;en-us;q306518 To resolve.

HTH|||Thank you so much.

I could resolve the problem.

It was just add user IUSR_mechinename fromuser list.

Good finishing for a marathon...

bye

Thank you

gracesonsql

Microsoft OLE DB Provider for Visual FoxPro 9.0

Im quite interested to see if any one is using Microsoft OLE DB Provider for Visual FoxPro 9.0 in an SSIS package. Is it possible to use this for free table directory like you can with the ODBC driver. ?

thanks kindly

My basic proccess is as follows: The source foxpro database has hundreds of dbf files the SSIS procress is as follows

1: Copy only required dbf files and/or matching .fpt files over to local drive on SSIS box(we only need 10 files)

use MS Visual Foxpro ODBC driver (free table option) and set up a system DSN--dataflow tabdatareader source--and away you go

Hi! Yes, you can use the free table option with the VFP OLE DB data provider. A typical connection string for the OLE DB data provider is "Provider=VFPOLEDB.1;Data Source=C:\Temp\" -- Cindy Winegarden cindy@.cindywinegarden.com VFP OLE DB: http://msdn2.microsoft.com/en-us/vfoxpro/bb190232.aspx VFP ODBC: http://msdn2.microsoft.com/en-us/vfoxpro/bb190233.aspx ""Mr Pro Tools"@.discussions.microsoft.com" <"=?UTF-8?B?TXIgUHJvIFRvb2xz?="@.discussions.microsoft.com> wrote in message news:64e94200-765c-4209-afa1-a2d8bb82af1f@.discussions.microsoft.com... Im quite interested to see if any one is using Microsoft OLE DB Provider for Visual FoxPro 9.0 in an SSIS package. Is it possible to use this for free table directory like you can with the ODBC driver. ? ...

Microsoft OLE DB Provider for Visual FoxPro 9.0

Im quite interested to see if any one is using Microsoft OLE DB Provider for Visual FoxPro 9.0 in an SSIS package. Is it possible to use this for free table directory like you can with the ODBC driver. ?

thanks kindly

My basic proccess is as follows: The source foxpro database has hundreds of dbf files the SSIS procress is as follows

1: Copy only required dbf files and/or matching .fpt files over to local drive on SSIS box(we only need 10 files)

use MS Visual Foxpro ODBC driver (free table option) and set up a system DSN--dataflow tabdatareader source--and away you go

Hi!

Yes, you can use the free table option with the VFP OLE DB data provider. A

typical connection string for the OLE DB data provider is

"Provider=VFPOLEDB.1;Data Source=C:\Temp\"

--

Cindy Winegarden

cindy@.cindywinegarden.com

VFP OLE DB: http://msdn2.microsoft.com/en-us/vfoxpro/bb190232.aspx

VFP ODBC: http://msdn2.microsoft.com/en-us/vfoxpro/bb190233.aspx

""Mr Pro Tools"@.discussions.microsoft.com"

<"=?UTF-8?B?TXIgUHJvIFRvb2xz?="@.discussions.microsoft.com> wrote in message

news:64e94200-765c-4209-afa1-a2d8bb82af1f@.discussions.microsoft.com...

Im quite interested to see if any one is using Microsoft OLE DB Provider for

Visual FoxPro 9.0 in an SSIS package. Is it possible to use this for free

table directory like you can with the ODBC driver. ? ...

Microsoft OLE DB Provider for SQL Server"

I receive a "Cannot generate SSPI context" error message when you try to
connect to a SQL Server 2000 SP3 server computer.
According microsoft's article ID 843248 there is a hot fix. I do not want to
install SP2 just the hot fix.
Does anybody know the actual ID name of the hotfix. I am trying to connect
from XP SP1 Thank you
According to the article you referenced you could either download XP SP2 or
contact Product Support to get the fix.
In that article you can also find a workaround if you can not install either
SP2 or the fix.
I would recommend that you consider to install XP SP2 since it contains a
lot of security enhancements.
Simon
This posting is provided "as is" with no warranties and confers no rights.
"Yianni" <Yianni@.discussions.microsoft.com> wrote in message
news:B89BD7C7-E80B-48EE-943A-6832804665B5@.microsoft.com...
>I receive a "Cannot generate SSPI context" error message when you try to
> connect to a SQL Server 2000 SP3 server computer.
> According microsoft's article ID 843248 there is a hot fix. I do not want
> to
> install SP2 just the hot fix.
> Does anybody know the actual ID name of the hotfix. I am trying to connect
> from XP SP1 Thank you
>

Microsoft OLE DB Provider for SQL Server error '80040e37'

I get Microsoft OLE DB Provider for SQL Server error '80040e37'

Invalid object name '#t_testTemp484883646'.
when I run the following ASP code:

Code is below

<!#Include File="../includes/adovbs.inc" -->

<HTML>
<HEAD>
<META NAME="GENERATOR" Content="Microsoft Visual Studio 6.0">
<TITLE></TITLE>
</HEAD>
<BODY>

<%
'-- Setup database connection
Set DataCmd = Server.CreateObject("ADODB.Connection")
Set rsData = Server.CreateObject("ADODB.RecordSet")
Dim varTempTableName
DataCmd.Open Application("DB")
'-- Use a Temp Table so that it gets destroyed automatically in case the page times out
'-- Use a Global Temp Table so that it is available across scopes when I open the record set below
'-- Append a semi unique number to the end because its global it could conflict with another browser running the same report
'varTempTableName = "##t_TestTemp" & Minute(Now()) & Second(Now())
varTempTableName = "#t_TestTemp" & Session.SessionID

strSQL = "Create Table " & varTempTableName & "(TestColumn2 int)"
DataCmd.Execute strSQL

strSQL = "select * from t_Test"
rsData.Open strSQL, DataCmd, adOpenForwardOnly,adLockReadOnly


Do While Not rsData.EOF
varTestColumn2 = rsData("TestColumn2")

'Error occurs when I place the following insert statement. Code works with the global variable

strSQL = "Insert into " & varTempTableName & " (TestColumn2) values (" & varTestColumn2 & ")"
DataCmd.Execute strSQL

rsData.MoveNext
Loop
rsData.Close

strSQL = "Drop Table " & varTempTableName
DataCmd.Execute strSQL

Set rsData = Nothing
Set DataCmd = Nothing
%>
</BODY>
</HTML>

If you have connection pooling enabled you will get *one* of the connection which *could* be actually not the same connection as this which created the temp table. So either use global temp tables (## instead of #) or disable connection pooling.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Microsoft OLE DB Provider for SQL Server error '80040e31'

Hi
Till now the website was ok. But now I am getting
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
My connection in Config.inc is
<%Set MyConn=Server.CreateObject("ADODB.Connection")
MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
ID=eventsadmin;Password=adminevents;Init
ial Catalog=Events1;Data
Source=SERVER-NAME"
%>Try to connect with the ip address instead of the server name.
"Nachi" wrote:

> Hi
> Till now the website was ok. But now I am getting
> Microsoft OLE DB Provider for SQL Server error '80040e31'
> Timeout expired
>
> My connection in Config.inc is
> <%Set MyConn=Server.CreateObject("ADODB.Connection")
> MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
> ID=eventsadmin;Password=adminevents;Init
ial Catalog=Events1;Data
> Source=SERVER-NAME"
> %>
>|||Hi Nachi,
Is the problemi resloved.... if not i have few queires for this...
how are you connecting to the server,
1. Using OLEDB or using...
2. was any time out was set at the cleint side of ODBC.
Shiva Naidu Jai
"steve wojciechowski" wrote:
[vbcol=seagreen]
> Try to connect with the ip address instead of the server name.
> "Nachi" wrote:
>sql

Microsoft OLE DB Provider for SQL Server error '80040e31'

Hi
Till now the website was ok. But now I am getting
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
My connection in Config.inc is
<%Set MyConn=Server.CreateObject("ADODB.Connection")
MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
ID=eventsadmin;Password=adminevents;Initial Catalog=Events1;Data
Source=SERVER-NAME"
%>Try to connect with the ip address instead of the server name.
"Nachi" wrote:
> Hi
> Till now the website was ok. But now I am getting
> Microsoft OLE DB Provider for SQL Server error '80040e31'
> Timeout expired
>
> My connection in Config.inc is
> <%Set MyConn=Server.CreateObject("ADODB.Connection")
> MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
> ID=eventsadmin;Password=adminevents;Initial Catalog=Events1;Data
> Source=SERVER-NAME"
> %>
>|||Hi Nachi,
Is the problemi resloved.... if not i have few queires for this...
how are you connecting to the server,
1. Using OLEDB or using...
2. was any time out was set at the cleint side of ODBC.
Shiva Naidu Jai
"steve wojciechowski" wrote:
> Try to connect with the ip address instead of the server name.
> "Nachi" wrote:
> > Hi
> >
> > Till now the website was ok. But now I am getting
> > Microsoft OLE DB Provider for SQL Server error '80040e31'
> > Timeout expired
> >
> >
> >
> > My connection in Config.inc is
> > <%Set MyConn=Server.CreateObject("ADODB.Connection")
> > MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
> > ID=eventsadmin;Password=adminevents;Initial Catalog=Events1;Data
> > Source=SERVER-NAME"
> > %>
> >
> >

Microsoft OLE DB Provider for SQL Server error '80040e31'

Hi
Let me share the Possibilities & fix of the following error:
The error appeares only peak hrs. (when more request comes)
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
/News/Home.asp, line 121
Thanks in Advance
Dil
From Dil :
> Hi
> Let me share the Possibilities & fix of the following error:
> The error appeares only peak hrs. (when more request comes)
>
> Microsoft OLE DB Provider for SQL Server error '80040e31'
> Timeout expired
> /News/Home.asp, line 121
> Thanks in Advance
> Dil
Well, since you're not sharing, how about
http://www.aspfaq.com/show.asp?id=2287

Microsoft OLE DB Provider for SQL Server error '80040e14'

I am trying to add data from a form with 8 text boxes.
Each text box needs to allow atleast 2000 characters to be
entered. When trying to save this data to a record in my
database I get the following error: Microsoft OLE DB
Provider for SQL Server error '80040e14' Cannot create a
row of size 8858 which is greater than the allowable
maximum of 8060.
Is there a way around this?
Thanks."Chris" <christopherhebrard@.hotmail.com> wrote in message
news:046e01c39f45$63a6a010$a401280a@.phx.gbl...
> I am trying to add data from a form with 8 text boxes.
> Each text box needs to allow atleast 2000 characters to be
> entered. When trying to save this data to a record in my
> database I get the following error: Microsoft OLE DB
> Provider for SQL Server error '80040e14' Cannot create a
> row of size 8858 which is greater than the allowable
> maximum of 8060.
>
8060 is the maximum row size for any table in SQLServer. You can
-use TEXT instead of VARCHAR columns (TEXT data is not stored on the row).
-break your table into multiple tables and spread out your varchar columns.
David|||Thanks for your help, very much apreciated. Its funny that
I spent about an hour researching this problem, and all I
had to do was try the text type. :)
>--Original Message--
>"Chris" <christopherhebrard@.hotmail.com> wrote in message
>news:046e01c39f45$63a6a010$a401280a@.phx.gbl...
>> I am trying to add data from a form with 8 text boxes.
>> Each text box needs to allow atleast 2000 characters to
be
>> entered. When trying to save this data to a record in
my
>> database I get the following error: Microsoft OLE DB
>> Provider for SQL Server error '80040e14' Cannot create a
>> row of size 8858 which is greater than the allowable
>> maximum of 8060.
>8060 is the maximum row size for any table in SQLServer.
You can
>-use TEXT instead of VARCHAR columns (TEXT data is not
stored on the row).
>-break your table into multiple tables and spread out
your varchar columns.
>David
>
>.
>

Microsoft OLE DB Provider for SQL Server error '80004005' on Load Balancing

I have posted this also in one forum. Somebody might have idea here.

We have four Windows 2003 advance servers with SP 3 configured on NLB.
Each of them has one NIC.
Recently we started to get frequent time-out error messages from web applications on those servers when they try to establish the connection with the SQL 2005. If you run web pages application to connect to sql server 10 times, 9 times you will get good connection results and 1 time you will get time-out.

Microsoft OLE DB Provider for SQL Server error '80004005'
Timeout expired
/common/mypage.asp, line 20

Connection to sql server is established with the connection string. Any idea how to solve this problem? Is there a connectionproblem? from NLB to Web to SQL?

We have tried doing some suggestions (e.g. LMHOST, IP, domain account for WEb to SQL connection, the Query Wait in SQL advance property.), but seems this timeout expired still exist Sad

Thanks in advance...

We thought it was only in IIS and Firewall pooling connections. There were open connection threads on IIS, where in fact the firewall already disconnect it. When a new request from IIS is set, sometimes it uses the aged out connections. This was one of the cause. What we did is modify the timeout connection from firewall 1 minute more than the IIS timeout expiration. Though we still encounter timeout expired once in a while. Any idea?

|||

Another thing that might help to analyze this issue:

I tried to check the Profiler for the timeout expiration. On the Profiler, SQL grants login (AuditLogin) but kicked it out right away (AuditLogut) for that specific timeout connection. No duration cost.

Friday, March 23, 2012

Microsoft OLE DB Provider for SQL Server error ''80004005'' on Load Balancing

I have posted this also in one forum. Somebody might have idea here.

We have four Windows 2003 advance servers with SP 3 configured on NLB.
Each of them has one NIC.
Recently we started to get frequent time-out error messages from web applications on those servers when they try to establish the connection with the SQL 2005. If you run web pages application to connect to sql server 10 times, 9 times you will get good connection results and 1 time you will get time-out.

Microsoft OLE DB Provider for SQL Server error '80004005'
Timeout expired
/common/mypage.asp, line 20

Connection to sql server is established with the connection string. Any idea how to solve this problem? Is there a connectionproblem? from NLB to Web to SQL?

We have tried doing some suggestions (e.g. LMHOST, IP, domain account for WEb to SQL connection, the Query Wait in SQL advance property.), but seems this timeout expired still exist Sad

Thanks in advance...

We thought it was only in IIS and Firewall pooling connections. There were open connection threads on IIS, where in fact the firewall already disconnect it. When a new request from IIS is set, sometimes it uses the aged out connections. This was one of the cause. What we did is modify the timeout connection from firewall 1 minute more than the IIS timeout expiration. Though we still encounter timeout expired once in a while. Any idea?

|||

Another thing that might help to analyze this issue:

I tried to check the Profiler for the timeout expiration. On the Profiler, SQL grants login (AuditLogin) but kicked it out right away (AuditLogut) for that specific timeout connection. No duration cost.

sql

Microsoft OLE DB Provider for SQL Server error '80004005' - Unspecified error

Hi,
I have an ASP code that calls a stored procedure. I use a Command
object to execute the stored procedure. The Stored procedure returns
data when executed in Query analyser. But it takes around 1 minute for
this. The stored procedure involves querying a huge amount of data.
When I try to open the ASP page, I get the following error :
Microsoft OLE DB Provider for SQL Server error '80004005'
Unspecified error
Any suggestions?
TIA,
AnishyaHi
Have you checked with SQL Profiler that the procedure is being called? Check
that the login/user you are using has the correct permissions. If this has
timed out then I would expect that a TIMEOUT error message. You may also want
to check http://www.aspfaq.com/show.asp?id=2009
John
"Ani" wrote:
> Hi,
> I have an ASP code that calls a stored procedure. I use a Command
> object to execute the stored procedure. The Stored procedure returns
> data when executed in Query analyser. But it takes around 1 minute for
> this. The stored procedure involves querying a huge amount of data.
> When I try to open the ASP page, I get the following error :
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Unspecified error
> Any suggestions?
> TIA,
> Anishya
>|||Hi,
The procedure is being called in the Profiler. I tried executing the
same stored procedure call in query analyser and saw that it works
fine. The only problem is that it takes around 1 minute. So I am sure
this is why the ASP page gives the error. The stored proc makes the use
of a temporary table. I tried executing the stored proc by using a
permanent table instead of the temporary table. It doesnt take much
time. But doesn't permanent tables involve more performance overheads
than temporary tables? I am trying to find another alternative. Is
there any way that I could increase the timeout period for ASP pages?
Thanks,
Anishya|||Hi
You could be seeing contention on tempdb if a lot of people are
simulataneously creating temporary tables, see
http://support.microsoft.com/kb/328551. You should see if the temporary table
is really necessary or possibly use a table variable as an alternative.
You may also want to change the timeout on your command object
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdprocommandtimeout.asp
John
"Ani" wrote:
> Hi,
> The procedure is being called in the Profiler. I tried executing the
> same stored procedure call in query analyser and saw that it works
> fine. The only problem is that it takes around 1 minute. So I am sure
> this is why the ASP page gives the error. The stored proc makes the use
> of a temporary table. I tried executing the stored proc by using a
> permanent table instead of the temporary table. It doesnt take much
> time. But doesn't permanent tables involve more performance overheads
> than temporary tables? I am trying to find another alternative. Is
> there any way that I could increase the timeout period for ASP pages?
> Thanks,
> Anishya
>

Microsoft OLE DB Provider for SQL Server error '80004005'

Hello Group,

I need some help in the worst way. I had a program/database I was working on a particular machine. I took all the data from there and placed it on a another machine. Now I'm unable to navigate through the web pages on the new machine. I am getting the error...

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

......asp, line 19

Can you please help!!

Quote:

Originally Posted by ConfusedDeuce

Hello Group,

I need some help in the worst way. I had a program/database I was working on a particular machine. I took all the data from there and placed it on a another machine. Now I'm unable to navigate through the web pages on the new machine. I am getting the error...

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

......asp, line 19

Can you please help!!


On line 19, your connection to the database is failing. Are you on the same network segment/subnet as you previously were? What is the physical difference between the computers?|||

Quote:

Originally Posted by ConfusedDeuce

Hello Group,

I need some help in the worst way. I had a program/database I was working on a particular machine. I took all the data from there and placed it on a another machine. Now I'm unable to navigate through the web pages on the new machine. I am getting the error...

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

......asp, line 19

Can you please help!!


How are you now specifying the server name when connecting to this machine?
You'll need to allow the server port on that new machine if it's running a firewall.|||

Quote:

Originally Posted by Motoma

On line 19, your connection to the database is failing. Are you on the same network segment/subnet as you previously were? What is the physical difference between the computers?


The thing is that I'm not completely sure what the other machine had on it because they data was copied over from that machine and the machine was immediately taken away. Now I am using VMWare and virtually connected to new machine (which shouldnt be the problem). I'm not sure of any of the specs of the last machine : (|||

Quote:

Originally Posted by r035198x

How are you now specifying the server name when connecting to this machine?
You'll need to allow the server port on that new machine if it's running a firewall.


I'm not connecting to the old machine anymore. That machine is out of the office and no longer in physical reach.|||

Quote:

Originally Posted by ConfusedDeuce

The thing is that I'm not completely sure what the other machine had on it because they data was copied over from that machine and the machine was immediately taken away. Now I am using VMWare and virtually connected to new machine (which shouldnt be the problem). I'm not sure of any of the specs of the last machine : (


Do you have the SQL Server database up and running on the new machine? Have you added the appropriate accounts and permissions for the users?|||

Quote:

Originally Posted by Motoma

Do you have the SQL Server database up and running on the new machine? Have you added the appropriate accounts and permissions for the users?


Yes it is up and running. How do i add the accounts and permissions?|||

Quote:

Originally Posted by ConfusedDeuce

Yes it is up and running. How do i add the accounts and permissions?


Enterprise Manager -> Server -> Security -> Logins
Enterprise Manager -> Server -> Databases -> Database -> Users
Enterprise Manager -> Server -> Databases -> Database -> Roles|||

Quote:

Originally Posted by ConfusedDeuce

I'm not connecting to the old machine anymore. That machine is out of the office and no longer in physical reach.


Actually I was refering to that new machine. That error means that the connection to the database server was not done correctly. The reasons could be
wrong hostname being specified
firewall blocking connections
change of IP
wrong port being used or break in TCP/IP conection while accessing the database server
e.t.c

Microsoft OLE DB Provider for SQL Server error 80004005

Hi friends,

Can anyone help me in connecting sql server and asp.
Wheneever try to do the connection, I am getting following error. All the connection string which i am using are correct.

can you help me.

Following are the error line

--------------------

Microsoft OLE DB Provider for SQL Server error '80004005'

Invalid connection string attribute

/MAsteringASP/global.asa, line 17

Microsoft OLE DB Provider for SQL Server error '80004005'

Invalid connection string attribute

/MAsteringASP/test2.asp, line 21
----------------

Please ckeck my code which I am using for connection

Thank you

Graceson MAthew

--------------------
<%@. Language =VBScript %>
<% option explicit %>

<Html>
<head>
<title> Database Connection </title>
</head>
<body>
<%

<!-- #INCLUDE FILE="adovbs.inc" -->

dim conn
dim sql
dim r
dim aConnectionString

Set conn=Server.CreateObject("ADODB.Connection")

conn.Mode=adModeReadWrite
conn.Open="Provider=SQLOLEDB;UID=Administrator;Password=passw d;Initial Catalog=nrth;Datasource=server ip;Port Number= 80"

Response.Write (" Database Connectivity")

%>
</body>
</html>try this type of connection string

driver={SQL Server};server=Server ip\DontForgetTheInstanceName;uid=Administrator;pwd =password;Database=nrth|||Also KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q169/3/77.asp&NoWebContent=1) to detail the connection between ASP & SQL Server.

HTH|||I don't recall Port NMumber being used in a connection string. Maybe if you took that part out?|||Ensure SQL uses that port and enabled on server or that port is not used by any other application.|||oh gosh, can't believe nobody saw this one!

replace uid with user id

:D :D :D :D :D|||Hehe. I guess that would be a problem for SQLOLEDB. Was UID phased out with the previous driver? Can't even remember what it was called. MSQL something-or-other.|||MSDASQL|||Dear karolyn,

Thank you for your reply, i attended the problem i the way you suggested .But now i am getting some other error, which is also could not rectify me,

now error is in following way
------
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

//global.asa, line 17

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

/test2.asp, line 21

----------------------

Will you please help me .

graceson


Originally posted by Karolyn
try this type of connection string

driver={SQL Server};server=Server ip\DontForgetTheInstanceName;uid=Administrator;pwd =password;Database=nrth|||http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328306 to deal the issue.|||i think you're trying to use windows authentication. in this case you need to try this:

conn.Open="Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=nrth;Datasource=server ip;Port Number= 80"

also, i noticed that if this is your "exact" connection string, you need to know the ip address of the server, as well as the actual port it's listening on. confirm it's port 80, otherwise the default is 1433 (port 80 is the default for http)

Microsoft OLE DB Provider for SQL Server

Why do I get the following error each time I am trying to create a new datasource view " SQL server does not exist"......

Could you please provide more information?

Thank you

|||

Hi

thanx but i have managed to resolve the problem. Instead of typing local sever name i typed localhost.....

Microsoft OLE DB Provider for SQL Server

Why do I get the following error each time I am trying to create a new datasource view " SQL server does not exist"......

Could you please provide more information?

Thank you

|||

Hi

thanx but i have managed to resolve the problem. Instead of typing local sever name i typed localhost.....

sql