View Complete Post
I have installed a named instance of SQL Server 2008 R2 Enterprise 64 bit on Windows Server 2008 R2 Enterprise 64 bit. The os is running as a VM ware virtual machine.
I have created an AD security group for database engine sys admins on that machine. I added my user to that group.So for example;
domainname\machinename_SQL_DBE_SysADmins is a user with SysAdmin server role permissions. User domainname\MichaelEFF is a member of this group.
When I log onto the machine as this user and run the management studio with run as administrator I cannot log into the database engine. The log shows the error:
Login failed for user: Reason:Token-based server access validation failed with an infrastructure error
I've read many posts where the MVP says that the UAC is not passing the group membership. Is this the case? If so then how will role based access ever be possible with windows authentication? How can this be resolved?
I would appreciate help with the following issue:
I have created a local group in our SQL 2008 server and added two Windows user accounts "DOMAIN\UserName"
I then added the local group to the database and granted read only access.
The users are trying to link tables using MS Access using and ODBC connection and getting the following error.
Users are not system administrators.
Date 6/30/2010 1:01:54 PM
I have MS Accounting Professional 2009 installed on Windows Small Business Server 2008 with the accounting database in SQL Server 2005
I can access the database on the server using my client installation of MS Accounting and use it as expected
When I add another user I am unable to restrict the access rights of that user by selecting a role for them and restricting their access by denying them access to certain areas or providing read-only access to certain areas
What happens when we select a user and select a role and un-tick the Administrator rights box and click ok is that the user rights are not saved without administrator rights. When the user's rights are opened again, the Administrator box has a tick
in it again.
The sequence of events is exactly as described - untick the Administrator box, click ok, then select the user in the "Manage Users" list again, click "Edit" and there's a tick in the "Administrator" box.
In every other respect, MS Accounting appears to work ok, i.e. no error messages, no crashes.
We believe that we should be able to work around this issue by manually setting user access rights directly in the SQL database, but so far we have not been able to do that.
Has anyone ever experienced anything like this, can anyone provide any help or suggestions?
Is there any way we can restrict a particular sys admin sql user from accessing database on the production enviornment?
There are couple of people who knew the password and keep accessing via this user in the manageemnt studio.
Is it possible to achieve thru policy management?
I'm trying to determine the minimal amount of access I can give my developers to be able to run create stored procedure scripts with an inclusion of the grant execute to the application user group.
We have been developing some interesting work arounds, but I think there must be an easier way to grant the access.
Grant Create Stored Procedure to user1 on a specific database
Grant Permission to Grant Execute permission for Stored Procedures on a specific Database to user1 for any user.
Can I restrict the number of times a user can access the sql server?
For example, userA is using the database, if another person tries to access the database using the userA account while userA is still logged in.. SQL server denies that access or disconnects the former user.
Can I implement that when I use it as a connection string to my windows application in c#.
Any resource that I can dig in? ;)
thanks a lot.
I have been looking everywhere online regarding this, but have not found a clear answer.
I have an ASP.Net app running on Windows Server 2008, it's basically a reporting app using Crystal Reports. I have encountered a roadblock in regards to rendering some pages. When I run the app in Visual Studio(on the same 2008 machine) everything works perfectly. Yet when I publish it and run it live the reports will not display correctly, I get a message saying Failed to render page.
I looked this error up in the Crystal Reports website and the fixes they have there refer to giving the windows "aspnet" user full access rights to certain folders on the machine. I would be happy to do this, however there is no aspnet user in Windows Server 2008.
I installed the server and set its role to be Web Server. I also checked all the options regarding ASP.Net and IIS 6 compatibility. Yet there is no ASPNET username anywhere.
Did I set the server up wrong? or do I have to do something within ASP.Net to create this user and then give it rights?
SQL Server 2000 Reporting Services--a server-based reporting platform built on the .NET Framework and integrated with SQL Server 2000--lets you easily add reporting from diverse data sources. Using Visual Studio and Reporting Services you can integrate reports from any data source that has an OLE DB, ODBC, or ADO.NET provider into your Web applications. This article explains how it's done.
John C. Hancock
MSDN Magazine August 2004
MSDN Magazine November 2003
The knowledge worker is greatly empowered if she is able to access information across the enterprise from a central access point. With the SharePoint Portal Server 2001 Search Service you can catalogue information stored in Exchange public folders, on the Web, in the file system, and even in Lotus Notes databases. This article discusses the use of ActiveX Data Objects and the Web-based Distributed Authoring and Versioning protocol for creating search solutions based on SharePoint Portal Server 2001.
MSDN Magazine April 2002
What if you need to convert an existing Microsoft Access 97 database application into a true client-server application that is based on a SQL Server back end? If you know a little about Visual Basic and SQL Server, it's easy to make your app take advantage of the power and scalability provided by SQL Server 7.0. Using some concrete code examples, this article takes you step by step through converting the native Jet queries in your Access application into stored procedures and pass-through queries that SQL Server can use. You'll also learn how to pass on parameters when your client-server app calls these SQL Server stored procedures and queries.
MSDN Magazine June 2000