Re: SQL Server 2000 linked server problem

My guess is that if it were Kerberos delegation, that it would be happening
on other Linked servers to the same system.

We are in the process of moving databases off to a 2005 system.
So, I was looking to see if there was something that could be done to kick
this one linked server loose.


"Adams Qu [MSFT]" <v-adamqu@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:hYmJ424SIHA.5676@xxxxxxxxxxxxxxxxxxxxxxxxx
Dear Frank,

Thank you for posting here.

If the issue just occurs intermittently, the following factors may be the
possible causes:

1. Temporarily network connection problem has been experienced.
2. The delegated Kerberos authentication does not work stably.

To do the troubleshooting, we may need to collect some information to
identify which cause this temporary connection problem. Before collecting
this information, it is recommended that you apply the latest service pack
of SQL Server 2000 (SP4) to fix some known bugs on the SQL Server side.
Please refer to the following KB article:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
http://support.microsoft.com/?id=290211

IMPORTANT: Please ensure that you have done the Database Backup in avoid
any potential problem before upgrading to SP4,

Please help us to collect the following information:

I. SQL MPS Report
--------------------
When the issue occurs on the client side, please help create a MPSReport
on
the both two SQL Server instances (local and linked server), which will
collect ERRORLOG, Windows event log and other helpful information about
the
SQL Server. To create a MPSReport, please visit the following web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en

And look for MPSRPT_SQL.EXE. Download it and run it on the machine.
Dismiss
the prompted dialog boxes and the readme window (usually a Notepad) after
you read them. After the Command Prompt window closes itself, collect the
cab file the tool has generated and sent it to me at
v-adamqu@xxxxxxxxxxxxx

II.
--------------------
Please also let me know the extract time when the issue occurs so that we
can check the entries in the MPS Report accordingly.

Thank you for your cooperation.

Have a nice day!

Best regards,

Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
| From: "frankm" <frankm@xxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.sqlserver.connect
| References: <%jRcj.1769$pr6.1313@xxxxxxxxxxxxxxxxxxxx>
<#v9K5rLSIHA.3532@xxxxxxxxxxxxxxxxxxxx>
<v0Tcj.1219$se5.545@xxxxxxxxxxxxxxxxxxxx>
<OXddsaMSIHA.5288@xxxxxxxxxxxxxxxxxxxx>
<0jUcj.1202$6%.1061@xxxxxxxxxxxxxxxxxxxx>
<YbX87eSSIHA.5204@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: SQL Server 2000 linked server problem
| Lines: 257
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| Message-ID: <Wj7dj.35070$Pv2.17450@xxxxxxxxxxxxxxxxxxxxxxxxxx>
| NNTP-Posting-Host: 165.152.63.227
| X-Complaints-To: abuse@xxxxxxxxxxx
| X-Trace: newssvr23.news.prodigy.net 1198850422 ST000 165.152.63.227
(Fri,
28 Dec 2007 09:00:22 EST)
| NNTP-Posting-Date: Fri, 28 Dec 2007 09:00:22 EST
| Organization: AT&T http://yahoo.sbc.com
| X-UserInfo1:
OHZQB_WEZZWSP_@YMZJ\_Q\@TJ_ZTB\MV@BJ]Q]KEYUNDQUCCNSUAACY@L[ZX__HGFD]JBJNSFXT
OOGA_VWY^_HG@FW_HUTHOH]TBPGCO\P^PLP^@[GLHUK@WLECKFVL^TYG[@RMWQXIWM[SDDYWNLG_
G[_BWUCHFY_Y@AS@Q[B\APPF@DCZM_PG_VSCPQZM
| Date: Fri, 28 Dec 2007 08:00:21 -0600
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!tornado.f
astwebnet.it!tiscali!newsfeed1.ip.tiscali.net!newshub.sdsu.edu!newscon04.new
s.prodigy.net!prodigy.net!newsdst01.news.prodigy.net!prodigy.com!postmaster.
news.prodigy.com!newssvr23.news.prodigy.net.POSTED!e51d285f!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.connect:1951
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| 1. Can your client or application connect to linked SQL Server instance
| directly via the required authentication method?
| Yes
|
| 2. If Windows Firewall or other third party firewall is used, please
also
| make sure that your Remote Procedure Call (RPC) port (135) and MSDTC
| "C:\Windows\System32\Msdtc.exe" has been added into the exception list.
| Yes
|
|
| An an FYI - this happenes intermittantly and a reboot fixes it.
|
|
|
|
| "Adams Qu [MSFT]" <v-adamqu@xxxxxxxxxxxxxxxxxxxx> wrote in message
| news:YbX87eSSIHA.5204@xxxxxxxxxxxxxxxxxxxxxxxxx
| > Dear Frank,
| >
| > Thank you for posting here.
| >
| > Based on our experience, if we are able to connect the linked server
| > successfully on the SQL Server itself but fails to connect from the
remote
| > client, the most common cause of this behavior is the delegation
problem.
| >
| > Before going further, I recommend that you refer to this article and
check
| > if the requirements for your client, the first SQL Server (most
important)
| > and the second SQL Server (linked server) are satisfied:
| >
| > Configuring Linked Servers for Delegation
| > http://msdn2.microsoft.com/en-us/library/ms189580.aspx
| >
| > Apart from checking the delegation configuration, we also recommend
that
| > you check and let me know the following conditions for further
research:
| >
| > 1. Can your client or application connect to linked SQL Server
instance
| > directly via the required authentication method?
| > 2. If Windows Firewall or other third party firewall is used, please
also
| > make sure that your Remote Procedure Call (RPC) port (135) and MSDTC
| > "C:\Windows\System32\Msdtc.exe" has been added into the exception
list.
| >
| > You may also want to apply the latest service pack of SQL Server 2000.
| > Please refer to the following articles.
| >
| > 290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
| > http://support.microsoft.com/?id=290211
| >
| > If the issue persists, please help us to collect the following
| > information:
| >
| > SQL MPS Report
| > ========================================
| > Please help create a MPSReport on the both two SQL Server instances
(local
| > and linked server), which will collect ERRORLOG, Windows event log and
| > other helpful information about the SQL Server. To create a MPSReport,
| > please visit the following web site:
| >
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
| > 88B7-F9C79B7306C0&displaylang=en
| >
| > And look for MPSRPT_SQL.EXE. Download it and run it on the machine.
| > Dismiss
| > the prompted dialog boxes and the readme window (usually a Notepad)
after
| > you read them. After the Command Prompt window closes itself, collect
the
| > cab file the tool has generated and sent it to me at
| > v-adamqu@xxxxxxxxxxxxx
| >
| > Reference
| > ----------------------------------
| > For your information, the error message "SQL Server does not exist or
| > access denied" can be commonly caused by one of the following factors:
| >
| > o That the logon process to SQL Server failed.
| > o That SQL Server does not have the correct permissions to process the
| > query.
| > o That you cannot use SQL Server authentication because only Windows
| > authentication is permitted
| >
| > Below is related KB article
| >
| > Potential causes of the "SQL Server does not exist or access denied"
error
| > message
| > http://support.microsoft.com/kb/328306/
| >
| > NOTE: If the issue is urgent to your business, it is recommended that
you
| > contact Microsoft Customer Service and Support (CSS) via telephone so
that
| > a dedicated Support Professional can assist you in resolving the issue
in
| > a
| > more efficient manner. Please be advised that contacting phone support
| > will
| > be a charged call.
| >
| > To obtain the phone numbers for specific technology request please
take
a
| > look at the web site listed below.
| > http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu
| > MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > =====================================================
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > =====================================================
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| > --------------------
| > | From: "frankm" <frankm@xxxxxxxxxxxxxxxx>
| > | Newsgroups: microsoft.public.sqlserver.connect
| > | References: <%jRcj.1769$pr6.1313@xxxxxxxxxxxxxxxxxxxx>
| > <#v9K5rLSIHA.3532@xxxxxxxxxxxxxxxxxxxx>
| > <v0Tcj.1219$se5.545@xxxxxxxxxxxxxxxxxxxx>
| > <OXddsaMSIHA.5288@xxxxxxxxxxxxxxxxxxxx>
| > | Subject: Re: SQL Server 2000 linked server problem
| > | Lines: 88
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| > | X-RFC2646: Format=Flowed; Response
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| > | Message-ID: <0jUcj.1202$6%.1061@xxxxxxxxxxxxxxxxxxxx>
| > | NNTP-Posting-Host: 165.152.63.227
| > | X-Complaints-To: abuse@xxxxxxxxxxx
| > | X-Trace: nlpi061.nbdc.sbc.com 1198788924 ST000 165.152.63.227 (Thu,
27
| > Dec 2007 15:55:24 EST)
| > | NNTP-Posting-Date: Thu, 27 Dec 2007 15:55:24 EST
| > | Organization: AT&T http://yahoo.sbc.com
| > | X-UserInfo1:
| >
TSU[@IONYJVWBTTXIBCBNWX@RJ_XPDLMN@GZ_GYO^JWTEPIB_NVUAH_[BL[\IRKIANGGJBFNJF_D
| >
OLSCENSY^U@FRFUEXR@KFXYDBPWBCDQJA@X_DCBHXR[C@\EOKCJLED_SZ@RMWYXYWE_P@\\GOIW^
| > @SYFFSWHFIXMADO@^[ADPRPETLBJ]RDGENSKQQZN
| > | Date: Thu, 27 Dec 2007 14:55:25 -0600
| > | Path:
| >
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed0
| >
0.sul.t-online.de!t-online.de!news.glorb.com!newscon02.news.prodigy.net!prod
| >
igy.net!newsdst02.news.prodigy.net!prodigy.com!postmaster.news.prodigy.com!n
| > lpi061.nbdc.sbc.com.POSTED!e51d285f!not-for-mail
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.connect:1949
| > | X-Tomcat-NG: microsoft.public.sqlserver.connect
| > |
| > | It is most likely a RPC service or something like that on the
Windows
| > side.
| > | This isn't a login issue, the Linked Server simply cannot connect.
It's
| > not
| > | authentication based.
| > |
| > | I'm kinda hoping that someone can tell me which service to recycle
as
| > this
| > | is a business critical system and getting downtime to rebott is
rather
| > | dicey.
| > |
| > | I think I've seen this before, but for the life of me I can remember
if
| > | there was a resolution.
| > |
| > |
| > |
| > |
| > | "Russell Fields" <russellfields@xxxxxxxxxx> wrote in message
| > | news:OXddsaMSIHA.5288@xxxxxxxxxxxxxxxxxxxxxxx
| > | > frankm,
| > | >
| > | > Could you describe the security settings on the linked server's
| > security
| > | > tab?
| > | >
| > | > If it is "Be made using the login's current security context" then
it
| > | > might imply that something broke the delegation chain for the
| > double-hop
| > | > needed to pass a user's credentials to the next server. When you
are
| > | > logged onto the server there is no double-hop since the linked
server
| > is
| > | > only one hop away.
| > | >
| > | > Does that make sense? In that case, it is not a SQL Server
problem,
| > but a
| > | > Windows or a domain problem. The SQL Server is simply victimized.
| > Since I
| > | > am not a domain/network administrator I don't have good insight
into
| > what
| > | > could be wrong, but I am pretty sure that is where the problem
lies.
| > | >
| > | > RLF
| > | >
| > | >
| > | > "frankm" <frankm@xxxxxxxxxxxxxxxx> wrote in message
| > | > news:v0Tcj.1219$se5.545@xxxxxxxxxxxxxxxxxxxxxxx
| > | >> The error is "SQL Server does not exist or access denied" which
means
| > it
| > | >> cannot connect.
| > | >> I know all of it works - it works from EM on the server itself
and
| > | >> doesn't from any remote client.
| > | >> I have tried RPC settings and that does not work.
| > | >>
| > | >> Apparently this happens "once in a while", and it takes a reboot
to
| > fix
| > | >> it.
| > | >>
| > | >>
| > | >>
| > | >>
| > | >>
| > | >> "Russell Fields" <russellfields@xxxxxxxxxx> wrote in message
| > | >> news:%23v9K5rLSIHA.3532@xxxxxxxxxxxxxxxxxxxxxxx
| > | >>> frankm,
| > | >>>
| > | >>> What error are you getting? That might reveal what the problem
is.
| > In
| > | >>> general: Check the security tab of the linked server properties
if
| > it
| > is
| > | >>> security context error. You might also check the Server Options
for
| > how
| > | >>> RPC and RPC OUT are set.
| > | >>>
| > | >>> Out of curiousily, have their been any changes to your network
| > | >>> infrastructure for the purpose of making the network more
secure?
| > | >>>
| > | >>> RLF
| > | >>>
| > | >>> "frankm" <frankm@xxxxxxxxxxxxxxxx> wrote in message
| > | >>> news:%jRcj.1769$pr6.1313@xxxxxxxxxxxxxxxxxxxxxxx
| > | >>>> This is SQL Server 2000 sp3a.
| > | >>>>
| > | >>>> I have linked servers that have been working for a fairly long
| > time.
| > | >>>>
| > | >>>> If I am on the server (TermSvc), I cann connect and test
through
| > the
| > | >>>> linked server successfully.
| > | >>>>
| > | >>>> If I am initiating this from any workstation or application off
the
| > SQL
| > | >>>> Server itself, the linked server connection fails.
| > | >>>>
| > | >>>> Any ideas???
| > | >>>>
| > | >>>> frankm
| > | >>>>
| > | >>>
| > | >>>
| > | >>
| > | >>
| > | >
| > | >
| > |
| > |
| > |
| >
|
|
|



.

Relevant Pages

  • Re: SQL Server 2005 Login Problem
    ... There are two authentication method in SQL Server. ... 1- Windows Authentication ... 2- Mixed Authentication (through SQL Server logins and Windows accounts) ...
    (microsoft.public.sqlserver.clients)
  • RE: My Documents Redirection error
    ... We can upgrade the instance SharePoint ... >> is no need to manually migrate data from MSDE to SQL server and all dada ... >> How to back up and restore http://companyweb data in Windows Small ...
    (microsoft.public.windows.server.sbs)
  • Re: server authentication & ASP authentication
    ... on to the client workstation with an authorized Windows account. ... SQL Server with Windows authentication. ...
    (microsoft.public.sqlserver.security)
  • RE: My Documents Redirection error
    ... > is no need to manually migrate data from MSDE to SQL server and all dada is ... > How to back up and restore http://companyweb data in Windows Small Business ... Insert the Microsoft Windows Small Business Server 2003 Premium ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall SQL Server; ... Reinstall Monitoring and Sharepoint and make sure they work; ... On the Windows Configuration page, ...
    (microsoft.public.windows.server.sbs)