View Complete Post
Edited by Nancy Michell
MSDN Magazine January 2004
I am attempting to use the 64-bit OLEDB Provider for Access found in the "Microsoft Access Database Engine 2010 Redistributable" to connect to and query an Access 2003 database that is on another server separate from my SharePoint server. I have not had
any success making the connection. My SharePoint server is Windows Server 2008 SP2 and I am running MOSS 2007 (patched up to the April 2010 CU)
Here is the connection info in my Application Definition XML:
<Property Name="AuthenticationMode" Type="Microsoft.Office.Server.ApplicationRegistry.SystemSpecific.Db.DbAuthenticationMode">RevertToSelf</Property>
<Property Name="DatabaseAccessProvider" Type="Microsoft.Office.Server.ApplicationRegistry.SystemSpecific.Db.DbAccessProvider">OleDb</Property>
<Property Name="rdbconnectionData Source" Type="System.String">\\server1\share1\Lessons.mdb</Property>
<Property Name="rdbconnectionProvider" Type="System.String&qu
I am able to access reports from my computer that has the SQL Server (2008) installed, but can't seem to access from other computers in the network. All I get is
"The permissions granted to user 'MyComputerName\Guest' are insufficient for performing this operation. (rsAccessDenied)"
Can someone please help?
I tried creating user "MyComputerName\Guest" and assign permission to view reports, but still cannot get it to work. Am I doing something wrong?
Here are some details from my Report Services Configuration Manager
Service Account is set up to Use built-in account : Network Service
Current Report Server Database
SQL Server Name : MyComputerName\ServerName
Database Name : ReportServer$ServerName
Report Server Mode : Native
Current Report Server Database Credential
Credential : SQL Account
Login : sa
Password : **********
I'm new to Analysis Server. How will i connect the Remote Analysis Server across Network using ADOMD Connection.
Please Help me!
We have setup a test SharePoint environment on a single box. If we create a new classic authentication web application using NTLM the site works fine, and recognizes AD users correctly. Users can then login successfully. If we create a new claims based authentication
web application using NTLM all users receive an Access Denied error when trying to view the site. The application will recognize AD users when applying permissions in Central Admin's User Policy section, but none of those users are able to access the site.
If I turn on Fiddler Capture, the sites will work fine. Once I turn it off the sites no longer work and we are again presented with an Access Denied exception (or sometimes 403 Forbidden in Firefox and Chrome). I know that Fiddler create a local proxy so
I'm curious what that proxy is doing that allows claims based to work correctly.
Has anyone seen this before? Does this sound Firewall/Antivirus related? Client or server?
I was able to install and configure SP 2010 Foundation on a Windows 7 Home Premium Edition as a Development Environment. But I am facing following issues:
a)cannot export lists from Access DB (Reason not able to connect to the local site on my machine)
b) for a list on SP site can't "Open with Access" - Access application is triggered, but the list doesn't show-up.
c) open a Page or List for edit with Sharepoint Designer ( SharePoint Designer application gets triggered but it get message "Unable to open Web site, Possible Causes: ..."
d) Also "Open Site" for local site on my machine gives the same error as in point c) above.
These 4 unsuccessful operations happen only for the local development site (created on my laptop), all the above operations are successful though when I do them on a web hosted SP 2010 site. I have given "Full Control"
permission for my login on the Central Administration. So what is wrong with the local site which prevents SharePoint Designer and Access DB connectivity?
I've been checking previous postings. We are opening up a sharepoint site for partner companies. Once they get to their site we don't want them on any other servers on the network.
I followed the info in previous postings and created a group called Computer_Deny, created a user and added them to that group. I created a GPO and linked it to the default domain with the user right deny access to this computer from the network enabled
and the Computer_Deny group added. Removed authenticated users from the filtering and added the Computer_Deny group.
did gpupdate /force
restarted an internal machine for testing. Logged on as the user I created, the user can't get to any server except the domain controller. What I'm not sure about....they need to authenticate with the DC, I believe, once they finish their HTTPS
entry and then need to get to the sharepoint server. If that is true, the authentication process has to happen on the DC. I would think the authentication process is different that a user trying to access a computer from the network. Am I
correct? Am I least moving in the right direction?
The user can still access the DC various ways i.e. run command, entire network but NOT via RDP since that right has not been granted. Some further research indicates that if
I have an application that has both a server and client... the client can exist on any computer.
I have a need to allow a client to export a set of files.ÃÂ The server process that will be exporting the job runs as the Local System account.
When I want to export resources to a remote UNC such as \\servername\share that I don't have permission on I would like to prompt my user for credentials.
How do I then use these new credentials to authenticate and thenÃÂ System.IO.File.Copy(src,dst)?
I've found several articles on impersonation and I can impersonate a local user, but not a remote user it seems...ÃÂ
I'm programming in C#.