I have linked an oracle remote database from MS SQL server 2000, connecting
an Oracle 8.1.7 database. The linked worked fine for a few days but fails
now with a message 'Error 7399:OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE DB Provider 'MSDAORA' DBInitialize::Initialized
returned 0x80004005. ]. The version of MSDAORA.DLL being used is 4.71. Any
ideas where the problem might be? I can connect to Oracle database from SQL
server via sql+.That's a generic error. Try turning on trace flag 7300 or
us SQL Profiler to capture the OLEDB Errors event. This
should give you to get more information about the error.
Additionally, you'll want to check the following article:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Sun, 18 Jul 2004 21:59:55 GMT, "Javed"
<purdaysee@.hotmail.com> wrote:
>I have linked an oracle remote database from MS SQL server 2000, connecting
>an Oracle 8.1.7 database. The linked worked fine for a few days but fails
>now with a message 'Error 7399:OLE DB provider 'MSDAORA' reported an error.
>OLE DB error trace [OLE DB Provider 'MSDAORA' DBInitialize::Initialized
>returned 0x80004005. ]. The version of MSDAORA.DLL being used is 4.71. Any
>ideas where the problem might be? I can connect to Oracle database from SQL
>server via sql+.
>|||I have the same setup. Friday 07/30/2004 the linked server started to fail w
ith the same message you are getting. We are looking into some OS security p
atches that were installed as the possible problem. Specifically MS04-020 an
d MS04-024. No resolution y
et.
Have you found the problem?
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...
Showing posts with label linked. Show all posts
Showing posts with label linked. Show all posts
Thursday, March 22, 2012
Connectivity fails to remote Oracle linked server
I have linked an oracle remote database from MS SQL server 2000, connecting
an Oracle 8.1.7 database. The linked worked fine for a few days but fails
now with a message 'Error 7399:OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE DB Provider 'MSDAORA' DBInitialize::Initialized
returned 0x80004005. ]. The version of MSDAORA.DLL being used is 4.71. Any
ideas where the problem might be? I can connect to Oracle database from SQL
server via sql+.
That's a generic error. Try turning on trace flag 7300 or
us SQL Profiler to capture the OLEDB Errors event. This
should give you to get more information about the error.
Additionally, you'll want to check the following article:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Sun, 18 Jul 2004 21:59:55 GMT, "Javed"
<purdaysee@.hotmail.com> wrote:
>I have linked an oracle remote database from MS SQL server 2000, connecting
>an Oracle 8.1.7 database. The linked worked fine for a few days but fails
>now with a message 'Error 7399:OLE DB provider 'MSDAORA' reported an error.
>OLE DB error trace [OLE DB Provider 'MSDAORA' DBInitialize::Initialized
>returned 0x80004005. ]. The version of MSDAORA.DLL being used is 4.71. Any
>ideas where the problem might be? I can connect to Oracle database from SQL
>server via sql+.
>
|||I have the same setup. Friday 07/30/2004 the linked server started to fail with the same message you are getting. We are looking into some OS security patches that were installed as the possible problem. Specifically MS04-020 and MS04-024. No resolution y
et.
Have you found the problem?
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
an Oracle 8.1.7 database. The linked worked fine for a few days but fails
now with a message 'Error 7399:OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE DB Provider 'MSDAORA' DBInitialize::Initialized
returned 0x80004005. ]. The version of MSDAORA.DLL being used is 4.71. Any
ideas where the problem might be? I can connect to Oracle database from SQL
server via sql+.
That's a generic error. Try turning on trace flag 7300 or
us SQL Profiler to capture the OLEDB Errors event. This
should give you to get more information about the error.
Additionally, you'll want to check the following article:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Sun, 18 Jul 2004 21:59:55 GMT, "Javed"
<purdaysee@.hotmail.com> wrote:
>I have linked an oracle remote database from MS SQL server 2000, connecting
>an Oracle 8.1.7 database. The linked worked fine for a few days but fails
>now with a message 'Error 7399:OLE DB provider 'MSDAORA' reported an error.
>OLE DB error trace [OLE DB Provider 'MSDAORA' DBInitialize::Initialized
>returned 0x80004005. ]. The version of MSDAORA.DLL being used is 4.71. Any
>ideas where the problem might be? I can connect to Oracle database from SQL
>server via sql+.
>
|||I have the same setup. Friday 07/30/2004 the linked server started to fail with the same message you are getting. We are looking into some OS security patches that were installed as the possible problem. Specifically MS04-020 and MS04-024. No resolution y
et.
Have you found the problem?
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
Connectivity across Domains.
Can you create linked SQL servers across domains ? If so do you need to do
something different from a normal linked server ?
Thanks
Si
Hi
Unless you have a trust relationship between the 2 domains, you need to use
a SQL Server login for the linked server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
> Can you create linked SQL servers across domains ? If so do you need to do
> something different from a normal linked server ?
> Thanks
> Si
|||The two domains do not trust each other and the Network guys have no
intention of changing this. However when i try and link the server with
username and password I still can`t connect to run a query on the linked
server.
Si
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Unless you have a trust relationship between the 2 domains, you need to use
> a SQL Server login for the linked server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
>
>
|||Make sure the request is going over TCP rather than named pipes. The latter
tries to enforce a network login even though you're using SQL
authentication.
Cheers,
'(' Jeff A. Stucker
\
Senior Consultant
www.rapidigm.com
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:D01D0AB4-7741-4BE2-8DEF-A24AA303F1B7@.microsoft.com...[vbcol=seagreen]
> The two domains do not trust each other and the Network guys have no
> intention of changing this. However when i try and link the server with
> username and password I still can`t connect to run a query on the linked
> server.
> Si
> "Mike Epprecht (SQL MVP)" wrote:
|||And use an IP address for the server name.
-Sue
On Tue, 13 Dec 2005 05:17:07 -0800, "Simon"
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The two domains do not trust each other and the Network guys have no
>intention of changing this. However when i try and link the server with
>username and password I still can`t connect to run a query on the linked
>server.
>Si
>"Mike Epprecht (SQL MVP)" wrote:
something different from a normal linked server ?
Thanks
Si
Hi
Unless you have a trust relationship between the 2 domains, you need to use
a SQL Server login for the linked server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
> Can you create linked SQL servers across domains ? If so do you need to do
> something different from a normal linked server ?
> Thanks
> Si
|||The two domains do not trust each other and the Network guys have no
intention of changing this. However when i try and link the server with
username and password I still can`t connect to run a query on the linked
server.
Si
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Unless you have a trust relationship between the 2 domains, you need to use
> a SQL Server login for the linked server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
>
>
|||Make sure the request is going over TCP rather than named pipes. The latter
tries to enforce a network login even though you're using SQL
authentication.
Cheers,
'(' Jeff A. Stucker
\
Senior Consultant
www.rapidigm.com
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:D01D0AB4-7741-4BE2-8DEF-A24AA303F1B7@.microsoft.com...[vbcol=seagreen]
> The two domains do not trust each other and the Network guys have no
> intention of changing this. However when i try and link the server with
> username and password I still can`t connect to run a query on the linked
> server.
> Si
> "Mike Epprecht (SQL MVP)" wrote:
|||And use an IP address for the server name.
-Sue
On Tue, 13 Dec 2005 05:17:07 -0800, "Simon"
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The two domains do not trust each other and the Network guys have no
>intention of changing this. However when i try and link the server with
>username and password I still can`t connect to run a query on the linked
>server.
>Si
>"Mike Epprecht (SQL MVP)" wrote:
Connectivity across Domains.
Can you create linked SQL servers across domains ? If so do you need to do
something different from a normal linked server ?
Thanks
SiHi
Unless you have a trust relationship between the 2 domains, you need to use
a SQL Server login for the linked server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
> Can you create linked SQL servers across domains ? If so do you need to do
> something different from a normal linked server ?
> Thanks
> Si|||The two domains do not trust each other and the Network guys have no
intention of changing this. However when i try and link the server with
username and password I still can`t connect to run a query on the linked
server.
Si
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Unless you have a trust relationship between the 2 domains, you need to us
e
> a SQL Server login for the linked server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
>
>|||Make sure the request is going over TCP rather than named pipes. The latter
tries to enforce a network login even though you're using SQL
authentication.
Cheers,
'(' Jeff A. Stucker
\
Senior Consultant
www.rapidigm.com
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:D01D0AB4-7741-4BE2-8DEF-A24AA303F1B7@.microsoft.com...[vbcol=seagreen]
> The two domains do not trust each other and the Network guys have no
> intention of changing this. However when i try and link the server with
> username and password I still can`t connect to run a query on the linked
> server.
> Si
> "Mike Epprecht (SQL MVP)" wrote:
>|||And use an IP address for the server name.
-Sue
On Tue, 13 Dec 2005 05:17:07 -0800, "Simon"
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The two domains do not trust each other and the Network guys have no
>intention of changing this. However when i try and link the server with
>username and password I still can`t connect to run a query on the linked
>server.
>Si
>"Mike Epprecht (SQL MVP)" wrote:
>
something different from a normal linked server ?
Thanks
SiHi
Unless you have a trust relationship between the 2 domains, you need to use
a SQL Server login for the linked server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
> Can you create linked SQL servers across domains ? If so do you need to do
> something different from a normal linked server ?
> Thanks
> Si|||The two domains do not trust each other and the Network guys have no
intention of changing this. However when i try and link the server with
username and password I still can`t connect to run a query on the linked
server.
Si
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Unless you have a trust relationship between the 2 domains, you need to us
e
> a SQL Server login for the linked server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
>
>|||Make sure the request is going over TCP rather than named pipes. The latter
tries to enforce a network login even though you're using SQL
authentication.
Cheers,
'(' Jeff A. Stucker
\
Senior Consultant
www.rapidigm.com
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:D01D0AB4-7741-4BE2-8DEF-A24AA303F1B7@.microsoft.com...[vbcol=seagreen]
> The two domains do not trust each other and the Network guys have no
> intention of changing this. However when i try and link the server with
> username and password I still can`t connect to run a query on the linked
> server.
> Si
> "Mike Epprecht (SQL MVP)" wrote:
>|||And use an IP address for the server name.
-Sue
On Tue, 13 Dec 2005 05:17:07 -0800, "Simon"
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The two domains do not trust each other and the Network guys have no
>intention of changing this. However when i try and link the server with
>username and password I still can`t connect to run a query on the linked
>server.
>Si
>"Mike Epprecht (SQL MVP)" wrote:
>
Monday, March 19, 2012
ConnectionCheckForData((null)())?
Hi all,
I have 2 servers - Financial and Trilogy. Trilogy is a linked server on the Financial Database. It uses MSDASQL to link it. Now I have a insert trigger on one of the tables on the financial Database that inserts data to a table that resides on the trilogy database. A few days ago it was working fine. Any inserts into the financial table would insert data into the trilogy table, however now I get the following error when I try to an insert into the financial table....
Changed Language setting to Us_English
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData((null)()).
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General Network Error. Check your Network Documentation.
The only thing that has been done within these few days was a reboot of the trilogy server.
Also when I remove this trigger and do an insert into the financial table it works fine, so I unsure whether this error occurs due to ODBC or MSDTC?? Can anyone help with this?? And what causes this error and how do I go about fixing it??
Thanks
AnthonyThis sounds like a known issue. Please see article for info.
http://support.microsoft.com/?id=317852
I have 2 servers - Financial and Trilogy. Trilogy is a linked server on the Financial Database. It uses MSDASQL to link it. Now I have a insert trigger on one of the tables on the financial Database that inserts data to a table that resides on the trilogy database. A few days ago it was working fine. Any inserts into the financial table would insert data into the trilogy table, however now I get the following error when I try to an insert into the financial table....
Changed Language setting to Us_English
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData((null)()).
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General Network Error. Check your Network Documentation.
The only thing that has been done within these few days was a reboot of the trilogy server.
Also when I remove this trigger and do an insert into the financial table it works fine, so I unsure whether this error occurs due to ODBC or MSDTC?? Can anyone help with this?? And what causes this error and how do I go about fixing it??
Thanks
AnthonyThis sounds like a known issue. Please see article for info.
http://support.microsoft.com/?id=317852
Subscribe to:
Posts (Atom)