Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts

Monday, March 19, 2012

servers "Client unable to establish connection"

We have several linked SQL servers running both SQL 7 (sp4) and SQL 2000 (sp3). Recently, when we run the following command from SQL 7 query analyzer to a SQL 2000 database, select * from remoteserver.database.dbo.tablename, we get this message:

[OLE/DB provider returned message: Client unable to establish connection]
[DBNMPNTW]ConnectionOpen (CreateFile()).

The databases are linked with specific remote login and password. The same command works the opposite direction, in other words from the SQL 2000 database to SQL 7 database. This was working last week but all of a sudden stopped. Of course, no one admits to changing anything on either of the servers. The SQL 2000 is on Windows 2003 server.

Thanks.

LccTom,

It is possible that some of the recent w2k3 patches disabled the file sharing and remote network connectivity on your w2k3 machine. Can you try if you can remote access to the w2k3 machine, such as file sharing? If you can't, you need to enable the file sharing because the namepipe provider[DBNMPNTW] depends on it.

Also, if you want TCP connection, you need to make firewall exception for the SQL tcp listening port, default to 1433 for a default instance.

|||We have no OS service packs installed but for some reason, it started working again Wednesday morning. Thanks for the reply and I'll make sure to look at the file sharing if it happens again. I reported it to my network people also.

servers

After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
2003 we get this message when trying to use a linked server...
Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
Any thoughts?
Questar,
See these threads:
http://groups.google.com/groups?q=jczypinski+oledb32r
http://groups.google.com/groups?q=ko...b32.dll+solved
A wrong version of oledb32.dll might be the issue.
Steve Kass
Drew University
Questar wrote:

>After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
>2003 we get this message when trying to use a linked server...
>Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].
>Any thoughts?
>
>
|||Good call. Problem solved. Thank you!
"Steve Kass" wrote:

> Questar,
> See these threads:
> http://groups.google.com/groups?q=jczypinski+oledb32r
> http://groups.google.com/groups?q=ko...b32.dll+solved
> A wrong version of oledb32.dll might be the issue.
> Steve Kass
> Drew University
> Questar wrote:
>

servers

I have two servers running SQL Server 2000 SP3 and SP4. The one running SP4
was created recently by restoring all the system and user databases from
another server which has now been retired. Now I have both the servers linked
from the other server and they both show up in the Enterprise Manager.
However, I can only access the server running SP4 from the server running
SP3, not vice versa. It gives an error:
Server: Msg 17, Level 16, State 1, Line 2
SQL Server does not exist or access denied.
Any insight will be greatly appreciated. Thanks.Are you able to ping old server from the new one?
Manu
"sharman" wrote:
> I have two servers running SQL Server 2000 SP3 and SP4. The one running SP4
> was created recently by restoring all the system and user databases from
> another server which has now been retired. Now I have both the servers linked
> from the other server and they both show up in the Enterprise Manager.
> However, I can only access the server running SP4 from the server running
> SP3, not vice versa. It gives an error:
> Server: Msg 17, Level 16, State 1, Line 2
> SQL Server does not exist or access denied.
> Any insight will be greatly appreciated. Thanks.

servers

After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
2003 we get this message when trying to use a linked server...
Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
Any thoughts?Questar,
See these threads:
http://groups.google.com/groups?q=jczypinski+oledb32r
http://groups.google.com/groups?q=kotuby+oledb32.dll+solved
A wrong version of oledb32.dll might be the issue.
Steve Kass
Drew University
Questar wrote:
>After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
>2003 we get this message when trying to use a linked server...
>Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].
>Any thoughts?
>
>|||Good call. Problem solved. Thank you!
"Steve Kass" wrote:
> Questar,
> See these threads:
> http://groups.google.com/groups?q=jczypinski+oledb32r
> http://groups.google.com/groups?q=kotuby+oledb32.dll+solved
> A wrong version of oledb32.dll might be the issue.
> Steve Kass
> Drew University
> Questar wrote:
> >After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
> >2003 we get this message when trying to use a linked server...
> >
> >Could not create an instance of OLE DB provider 'SQLOLEDB'.
> >OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
> >returned 0x8007007f].
> >
> >Any thoughts?
> >
> >
> >
>

Monday, March 12, 2012

servers

After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
2003 we get this message when trying to use a linked server...
Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
Any thoughts?Questar,
See these threads:
http://groups.google.com/groups?q=jczypinski+oledb32r
http://groups.google.com/groups?q=k...db32.dll+solved
A wrong version of oledb32.dll might be the issue.
Steve Kass
Drew University
Questar wrote:

>After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
>2003 we get this message when trying to use a linked server...
>Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].
>Any thoughts?
>
>|||Good call. Problem solved. Thank you!
"Steve Kass" wrote:

> Questar,
> See these threads:
> http://groups.google.com/groups?q=jczypinski+oledb32r
> http://groups.google.com/groups?q=k...db32.dll+solved
> A wrong version of oledb32.dll might be the issue.
> Steve Kass
> Drew University
> Questar wrote:
>
>