RE: 0x80004005 - you need permission to view its data
From: Sophie Guo [MSFT] (v-sguo_at_online.microsoft.com)
Date: 09/22/05
- Previous message: Joe Yong: "Re: Impact of Changing Authentication Mode"
- Maybe in reply to: Jeff Grundy: "0x80004005 - you need permission to view its data"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 22 Sep 2005 02:30:24 GMT
Hello Jeff,
It is MSSQLsvc. I have tested the issue on my side and it works fine.
When creating the Access linked server, make sure the data source using UNC
path instead of mapped drive. On my side, the UNC path like this:
\\envm-w2k3entsp1.test.com\sophie\northwind.mdb
Error 7399 is a general error and many factors can cause the issue. I
suggest that you perform the following steps to narrow down the issue:
1. Make sure you can query data on the Access linked server locally on the
the SQL server( Both SQL authentication and Windows Authentication work).
2. Use SQL authentication to connect to the SQL server, then run select
statement to query data on the Access linked server to make sure it works
under SQL authentication. Please let me know the detailed results.
When using Windows Authentication, client security will be impersonated.
Does not matter the login is a sysadmin or not. OLEDB provider is created
with security context of client user.
When using SQL Authentication, no impersonation is done. OLEDB provider is
created with security context of SQL Server.
If SQL authentication doesn't work, skip the remainning steps and post
here the exact error message. We need to make sure SQL authentication
works before performing further troubleshooting.
3. Define a new SQL linked server in SQL server 2000 on machine B. The
linked server is installed on machine C. Make sure you can query data on
the SQL linked server locally on the the SQL server(Both SQL authentication
and Windows Authentication work).
(User A)Machine A -----------> Machine B --------------> Machine C
(SQL server
2000, (data source in shared folder, New SQL server
instance)
linked
server)
Use Windows authentication to connect to the SQL server, then run select
statement to query data on the SQL linked server. If it works fine,
Kerberos works fine.
If Kerberos doesn't work, refer to the following articles to troubleshoot
the issue:
a.
262177 How to enable Kerberos event logging
(http://support.microsoft.com/kb/262177/)
Enable Kerberos event log. Reproduce the issue and check the system log.
b. Download the Kerbtray and verify Kerberos tickets from any of the
associated computers that are being used.
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/kerbtray
-o.asp
4. Ping DNS from both the client machine and the SQL machine to make sure
DNS settings and other networks settings are correct.
I look forward to hearing from you.
Sophie Guo
Microsoft Online Partner Support
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.
- Previous message: Joe Yong: "Re: Impact of Changing Authentication Mode"
- Maybe in reply to: Jeff Grundy: "0x80004005 - you need permission to view its data"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
