 |
|
|
|
Next: Redirected Restore using Veritas NetBackup
|
| Author |
Message |
External
Since: Jul 02, 2004
Posts: 27
|
(Msg. 1) Posted: Thu Dec 27, 2007 11:31 am
Post subject: SQL Server 2000 linked server problem
Archived from groups: microsoft>public>sqlserver>connect (more info?)
|
|
|
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 |
|
| Back to top |
|
 | |
External
Since: Feb 21, 2007
Posts: 457
|
(Msg. 2) Posted: Thu Dec 27, 2007 2:02 pm
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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" wrote in message
> 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
> |
|
| Back to top |
|
| |
External
Since: Jul 02, 2004
Posts: 27
|
(Msg. 3) Posted: Thu Dec 27, 2007 2:02 pm
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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" wrote in message
> 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" wrote in message
>
>> 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
>>
>
> >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
External
Since: Feb 21, 2007
Posts: 457
|
(Msg. 4) Posted: Thu Dec 27, 2007 3:25 pm
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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" wrote in message
> 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" wrote in message
>
>> 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" wrote in message
>>
>>> 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
>>>
>>
>>
>
> >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
External
Since: Jul 02, 2004
Posts: 27
|
(Msg. 5) Posted: Thu Dec 27, 2007 3:25 pm
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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" wrote in message
> 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" wrote in message
>
>> 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" wrote in message
>>
>>> 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" wrote in message
>>>
>>>> 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
>>>>
>>>
>>>
>>
>>
>
> >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
External
Since: Apr 25, 2007
Posts: 61
|
(Msg. 6) Posted: Fri Dec 28, 2007 3:59 am
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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.RemoveThis@microsoft.com
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"
| Newsgroups: microsoft.public.sqlserver.connect
| References:
| 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:
| NNTP-Posting-Host: 165.152.63.227
| X-Complaints-To: abuse.RemoveThis@prodigy.net
| 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" wrote in message
|
| > 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" wrote in message
| >
| >> 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" wrote in message
| >>
| >>> 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" wrote in message
| >>>
| >>>> 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
| >>>>
| >>>
| >>>
| >>
| >>
| >
| >
|
|
| >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
External
Since: Jul 02, 2004
Posts: 27
|
(Msg. 7) Posted: Fri Dec 28, 2007 8:00 am
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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]" wrote in message
> 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.RemoveThis@microsoft.com
>
> 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"
> | Newsgroups: microsoft.public.sqlserver.connect
> | References:
>
>
>
> | 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:
> | NNTP-Posting-Host: 165.152.63.227
> | X-Complaints-To: abuse.RemoveThis@prodigy.net
> | 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" wrote in message
> |
> | > 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" wrote in message
> | >
> | >> 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" wrote in message
> | >>
> | >>> 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" wrote in message
> | >>>
> | >>>> 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
> | >>>>
> | >>>
> | >>>
> | >>
> | >>
> | >
> | >
> |
> |
> |
> >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
External
Since: Apr 25, 2007
Posts: 61
|
(Msg. 8) Posted: Mon Dec 31, 2007 5:21 am
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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.DeleteThis@microsoft.com
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"
| Newsgroups: microsoft.public.sqlserver.connect
| References:
| 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:
| NNTP-Posting-Host: 165.152.63.227
| X-Complaints-To: abuse.DeleteThis@prodigy.net
| 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]" wrote in message
|
| > 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.DeleteThis@microsoft.com
| >
| > 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"
| > | Newsgroups: microsoft.public.sqlserver.connect
| > | References:
| >
| >
| >
| > | 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:
| > | NNTP-Posting-Host: 165.152.63.227
| > | X-Complaints-To: abuse.DeleteThis@prodigy.net
| > | 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" wrote in message
| > |
| > | > 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" wrote in message
| > | >
| > | >> 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" wrote in message
| > | >>
| > | >>> 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" wrote in message
| > | >>>
| > | >>>> 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
| > | >>>>
| > | >>>
| > | >>>
| > | >>
| > | >>
| > | >
| > | >
| > |
| > |
| > |
| >
|
|
| >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
External
Since: Jul 02, 2004
Posts: 27
|
(Msg. 9) Posted: Wed Jan 02, 2008 7:39 am
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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]" wrote in message
> 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.TakeThisOut@microsoft.com
>
> 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"
> | Newsgroups: microsoft.public.sqlserver.connect
> | References:
>
>
>
>
>
> | 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:
> | NNTP-Posting-Host: 165.152.63.227
> | X-Complaints-To: abuse.TakeThisOut@prodigy.net
> | 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]" wrote in message
> |
> | > 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.TakeThisOut@microsoft.com
> | >
> | > 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"
> | > | Newsgroups: microsoft.public.sqlserver.connect
> | > | References:
> | >
> | >
> | >
> | > | 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:
> | > | NNTP-Posting-Host: 165.152.63.227
> | > | X-Complaints-To: abuse.TakeThisOut@prodigy.net
> | > | 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" wrote in message
> | > |
> | > | > 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" wrote in message
> | > | >
> | > | >> 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" wrote in message
> | > | >>
> | > | >>> 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" wrote in message
> | > | >>>
> | > | >>>> 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
> | > | >>>>
> | > | >>>
> | > | >>>
> | > | >>
> | > | >>
> | > | >
> | > | >
> | > |
> | > |
> | > |
> | >
> |
> |
> |
> >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
External
Since: Apr 25, 2007
Posts: 61
|
(Msg. 10) Posted: Thu Jan 03, 2008 8:03 am
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Dear Frank,
Thank you for your update.
Yes. If the Kerberos delegation does not work properly, other linked
servers should also be affected. If my understanding is right, your last
reply indicates that there are multi-linked servers created in your
environment but the issue only occurs when involving one specific link
server. If I have any misunderstanding, feel free to let me know.
I understand that you are in the process of moving databases off to a SQL
Server 2005 system. After completing the migration, please check if the
issue can still be reproduced. If you need further assistance, please feel
free to post back and also collect the requested information (MPS report).
I will do more research for you and try to find the root cause for this
problem.
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"
| Newsgroups: microsoft.public.sqlserver.connect
| References:
| Subject: Re: SQL Server 2000 linked server problem
| Lines: 423
| 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:
| NNTP-Posting-Host: 165.152.63.227
| X-Complaints-To: abuse.RemoveThis@prodigy.net
| X-Trace: nlpi069.nbdc.sbc.com 1199281170 ST000 165.152.63.227 (Wed, 02
Jan 2008 08:39:30 EST)
| NNTP-Posting-Date: Wed, 02 Jan 2008 08:39:30 EST
| Organization: AT&T http://yahoo.sbc.com
| X-UserInfo1:
[[PA@SVDTRV[RQTYN[O@_WH@YR_B@EXLLBWLOOAF@YUDUWYAKVUOPCW[ML\JXUCKVFDYZKBMSFX^
OMSAFNTINTDDMVW[X\THOPXZRVOCJTUTPC\_JSBVX\KAOTBAJBVMZTYAKMNLDI_MFDSSOLXINH__
FS^\WQGHGI^C@E[A_CF\AQLDQ\BTMPLDFNVUQ_VM
| Date: Wed, 2 Jan 2008 07:39:29 -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!newsdst01.news.prodigy.net!prodigy.com!postmaster.news.prodigy.com!n
lpi069.nbdc.sbc.com.POSTED!e51d285f!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.connect:1976
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| 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]" wrote in message
|
| > 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.RemoveThis@microsoft.com
| >
| > 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"
| > | Newsgroups: microsoft.public.sqlserver.connect
| > | References:
| >
| >
| >
| >
| >
| > | 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:
| > | NNTP-Posting-Host: 165.152.63.227
| > | X-Complaints-To: abuse.RemoveThis@prodigy.net
| > | 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]" wrote in message
| > |
| > | > 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.RemoveThis@microsoft.com
| > | >
| > | > 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"
| > | > | Newsgroups: microsoft.public.sqlserver.connect
| > | > | References:
| > | >
| > | >
| > | >
| > | > | 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:
| > | > | NNTP-Posting-Host: 165.152.63.227
| > | > | X-Complaints-To: abuse.RemoveThis@prodigy.net
| > | > | 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" wrote in message
| > | > |
| > | > | > 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" wrote in message
| > | > | >
| > | > | >> 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" wrote in message
| > | > | >>
| > | > | >>> 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" wrote in message
| > | > | >>>
| > | > | >>>> 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
| > | > | >>>>
| > | > | >>>
| > | > | >>>
| > | > | >>
| > | > | >>
| > | > | >
| > | > | >
| > | > |
| > | > |
| > | > |
| > | >
| > |
| > |
| > |
| >
|
|
| >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
External
Since: Apr 25, 2007
Posts: 61
|
(Msg. 11) Posted: Mon Jan 14, 2008 1:56 am
Post subject: Re: SQL Server 2000 linked server problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Dear Frank,
How are things going? I have not heard back from you in a few days and
wanted to check on the status of the problem. Please let me know how the
troubleshooting steps turned out.
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.
--------------------
| X-Tomcat-ID: 87415216
| References:
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu DeleteThis @online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Thu, 03 Jan 2008 10:03:04 GMT
| Subject: Re: SQL Server 2000 linked server problem
| X-Tomcat-NG: microsoft.public.sqlserver.connect
| Message-ID:
| Newsgroups: microsoft.public.sqlserver.connect
| Lines: 481
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.connect:1979
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Frank,
|
| Thank you for your update.
|
| Yes. If the Kerberos delegation does not work properly, other linked
| servers should also be affected. If my understanding is right, your last
| reply indicates that there are multi-linked servers created in your
| environment but the issue only occurs when involving one specific link
| server. If I have any misunderstanding, feel free to let me know.
|
| I understand that you are in the process of moving databases off to a SQL
| Server 2005 system. After completing the migration, please check if the
| issue can still be reproduced. If you need further assistance, please
feel
| free to post back and also collect the requested information (MPS
report).
| I will do more research for you and try to find the root cause for this
| problem.
|
| 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"
| | Newsgroups: microsoft.public.sqlserver.connect
| | References:
|
|
|
|
|
|
|
| | Subject: Re: SQL Server 2000 linked server problem
| | Lines: 423
| | 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:
| | NNTP-Posting-Host: 165.152.63.227
| | X-Complaints-To: abuse DeleteThis @prodigy.net
| | X-Trace: nlpi069.nbdc.sbc.com 1199281170 ST000 165.152.63.227 (Wed, 02
| Jan 2008 08:39:30 EST)
| | NNTP-Posting-Date: Wed, 02 Jan 2008 08:39:30 EST
| | Organization: AT&T http://yahoo.sbc.com
| | X-UserInfo1:
|
[[PA@SVDTRV[RQTYN[O@_WH@YR_B@EXLLBWLOOAF@YUDUWYAKVUOPCW[ML\JXUCKVFDYZKBMSFX^
|
OMSAFNTINTDDMVW[X\THOPXZRVOCJTUTPC\_JSBVX\KAOTBAJBVMZTYAKMNLDI_MFDSSOLXINH__
| FS^\WQGHGI^C@E[A_CF\AQLDQ\BTMPLDFNVUQ_VM
| | Date: Wed, 2 Jan 2008 07:39:29 -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!newsdst01.news.prodigy.net!prodigy.com!postmaster.news.prodigy.com!n
| lpi069.nbdc.sbc.com.POSTED!e51d285f!not-for-mail
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.connect:1976
| | X-Tomcat-NG: microsoft.public.sqlserver.connect
| |
| | 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]" wrote in message
| |
| | > 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 DeleteThis @microsoft.com
| | >
| | > 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"
| | > | Newsgroups: microsoft.public.sqlserver.connect
| | > | References:
| | >
| | >
| | >
| | >
| | >
| | > | 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:
| | > | NNTP-Posting-Host: 165.152.63.227
| | > | X-Complaints-To: abuse DeleteThis @prodigy.net
| | > | 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]" wrote in message
| | > |
| | > | > 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 DeleteThis @microsoft.com
| | > | >
| | > | > 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"
| | > | > | Newsgroups: microsoft.public.sqlserver.connect
| | > | > | References:
| | > | >
| | > | >
| | > | >
| | > | > | 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:
| | > | > | NNTP-Posting-Host: 165.152.63.227
| | > | > | X-Complaints-To: abuse DeleteThis @prodigy.net
| | > | > | 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" wrote in message
| | > | > |
| | > | > | > 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" wrote in message
| | > | > | >
| | > | > | >> 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" wrote in message
| | > | > | >>
| | > | > | >>> 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" wrote in message
| | > | > | >>>
| | > | > | >>>> 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
| | > | > | >>>>
| | > | > | >>>
| | > | > | >>>
| | > | > | >>
| | > | > | >>
| | > | > | >
| | > | > | >
| | > | > |
| | > | > |
| | > | > |
| | > | >
| | > |
| | > |
| | > |
| | >
| |
| |
| |
|
| >> Stay informed about: SQL Server 2000 linked server problem |
|
| Back to top |
|
| |
| Related Topics: | Authentification problem with SQL Server 2000 - Hello ! We use SQL Server 2000 (standard edition) under Windows 2003 Server. Due to a hardware failure, we have fully set up the server after having formating the hard drives. After having installed Windows Server 2003, we have installed SQL Server..
SQLSERVER2005 64 bit linked server problem - Hello, I am having a hard time finding any information on an error I am receiving from attempting to connect 2 SQL Server 2005 servers linked server. I am setting the linked server to use the credentials of a SQL Server login. In searching the web,..
Sql Server 2000 & Vb.net Connection Problem - Hi, I am new for VB.net and I have defined the connectionstrings in web.config. <appSettings> <add key="constring" value="Data Source=Localhost;Initial Catalog=nexus;user id=nexusdb;password=nexus123;Integrated Security...
SQL Server 2000 SP4 client connection problem - Description: I have a server and two clients (ClientA and ClientB). All are on static IP, on the same LAN segment. Server ------ W2K3 Enterprise SP2 SQL Server 2000 SP4 Clients ------- WinXP SP2 Attempts to connect from ClientB result in the..
SQL Server 2005 - VFPOLEDB Linked Server Provider - Hello, I'm having a problem getting the VFPOLEDB provider to work with SQL Server 2005. I have installed the VFP 9.0 OLE DB provider from Microsoft, but the VFPOLEDB entry does not show up under Server Objects > Linked Servers > Providers. I w... |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Search
Profile
Private Messages
Log in
