Hot answers tagged

21

Here is Microsoft solution: http://support.microsoft.com/kb/2752600 Basically, start the browser as a different user. Another solution (but dirty) is to edit the Welcome.aspx file and add a control: <SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser" Text="<%$Resources:wss,personalactions_loginasdifferentuser%>" ...


11

'John Smith' should be the 'Display Name' in the AD. This will then be synchronized with user-profile service. Please make sure that your 'user profile synchronization service' is working without errors.


10

RIGHT click on IE hold SHIFT and then RIGHT click again on IE LEFT click "Run as different user" login Repeat 1.- 4. for other users :)


8

There is a free tool from Pointbird that will give you this functionality, or you could just add a custom action that adds a link to "/_layouts/closeConnection.aspx?loginasanotheruser=true" http://pointbird.com/products/pointbird-sign-in-as-different-user/ http://www.cwheeler76.com/Lists/Posts/Post.aspx?ID=2


8

Your issue is related to access to Configuration Database. Please follow the link for details - http://blog.falchionconsulting.com/index.php/2009/07/custom-sharepoint-2007-site-collection-creation-page/. It describes the same issues with creation of site collection and possible solutions and also touches Timer Job.


7

If the user had two accounts, you should check which account the user should be using and then use Move-SPUser PowerShell command for SharePoint 2010 to migrate the old user to the new one. Move-SPUser –Identity "DOMAIN\JaneDoe" –NewAlias "Domain\JaneSmith" More information on the PowerShell command is available here: ...


6

User profile service was not running correctly, but some accounts were stuck in companyDomain\jsmith. the following fixes that: Set-SPUser –Identity "domain\jsmith" –DisplayName "John Smith" –Web http://companyDomain.com


6

You can try this if I understand you correct? Microsoft.SharePoint.SPContext.Current.Web.CurrentUser.LoginName; or HttpContext.Current.User.Identity.Name and Microsoft.SharePoint.SPContext.Current.Web.CurrentUser.ID; hope this helps :)


5

Check your web application user policy and see if builtin\administrators have full control.


5

Take a look at http://spcurrentusers.codeplex.com which may serve as a starting point. It's my solution, in case you're wondering :-) .b


5

In case any other internet wayfarers come by this problem; it's highly likely that this is due to the app-pool user being given the "Act as system" privilege in the Central Admin User Policy for the webapplication.


4

You can use SPContext within a "RunWithElevatedPrivileges" block, but objects you get from "SPContext" such as: SPUser, SPWeb, etc. are not running in elevated privilege, they just take the current user security context. So why not just use "scweb" to get to the "Group". Since "scweb" object is initialized within the "RunWithElevatedPrivileges" block just ...


4

Create a bookmarklet that points to : URL=javascript:window.location = _spPageContextInfo.webServerRelativeUrl.replace(/\/$/, "") + "/_layouts/closeConnection.aspx?loginasanotheruser=true" As something you deploy to your browser, rather than your site, it approaches the problem from the other direction. But honestly, most of your users won't need this ...


4

Use chrome and create multiple users In settings you can shift to a different user using top right menu every user opens in a seperate window. Each window uses its own cache, saved passwords, bookmarks etc.


4

Users are stored on User Profile Service(UPS) and in User Information List. Users get stored on the User Profile Service when you do a UPS sync which imports user profiles from Active Directory. Normally, this is how it's setup. You can add, update, or delete the user profiles manually. Users get stored on the User Information List only when they access ...


4

I believe I've seen this when the first name and last name properties in Active Directory were blank.


4

Here is an article I wrote a while back to pull together resources for supporting multiple domains. http://www.mikeoryszak.com/sharepoint/supporting-multiple-active-directory-domains


4

The users are stored per SiteCollection, so there will no other way as to iterate through all of them.


3

No. Removing a user will not remove their files they created on SharePoint sites that are not their OneDrive. Eventually, after 30 days, their person site , which contains their OneDrive, will be purged. In addition to the article mentioned earlier, see also this article: https://support.microsoft.com/en-us/kb/2619308


3

You can use the current user object to get the name: SPContext.Current.Web.CurrentUser.Name


3

Copying the original poster's answer so we can mark this answered: Installing latest MOSS 2007 CU did the trick and all are well. Thanks for your answers


3

Check your IIS logs for the SharePoint site. By default, IIS logs that information, so if the web server knows the data, it will be in there.


3

I recommend you to read this and this blog posts. I am not sure about SP 2007, but in SP 2010 there is a property RemoteAdministratorAccessDenied (msdn page is not full of information, it's a pity). If this property setup to true, you can only update service from Central Admin pages, and if account, under code running has appropriate permissions. As blog ...


3

Even though users are from active directory, SharePoint stores these information seperately in a list called User Information List which will be available in the site.


3

I would change the password of the site collection admin account and give the developers full control access to the site collection and/or list them as site collection administrators. That will nip the sharing in the bud and more than likely resolve this issue. As to why it's happening, I'm not entirely sure. Do any network tools give you any insight like ...


3

This is not something that's possible OOTB. Even with FBA, you'll need additional code (codeplex has a great one) to create the accounts in the FBA store. You could build a request page for which would allow anonymous users access to request a login, specifying their user name.


3

Log Parsing or web analytics in general will give you good historical info, but generally not good real-time information. Querying the content database should absolutely not be done. Microsoft says that doing so will void any warranty or support. Anyone that has poked around with SharePoint enough will know that trying it absolutely does create problems ...


3

if you ask for the best practice then: Create the SQL_Admin: The SQL Server service account is used to run SQL Server. It is the service account for the following SQL Server services: MSSQLSERVER SQLSERVERAGENT. SQL Admin on the SQL Server. it should be domain user with Local Administrator on the SQL Server. read more about the best practice: SharePoint ...


3

You can use a try/catch block like this: $siteCollUrl = "http://my-sharepoint-site" $spSourceWeb = Get-SPWeb $siteCollUrl; $test_user = "CONTOSO\Administrator" try { $userx = $spSourceWeb.EnsureUser($test_user) echo $userx.UserLogin } catch { echo "default user" }


3

I think you can face problem as sometimes the profile synchronization timer job does not correctly synchronize the changes in the User name and Account name information. You need to execute the following Move-SPUser command (an equivalent of the STSADM MigrateUser command) for the user account in order to update the account name in SharePoint: Move-SPUser ...



Only top voted, non community-wiki answers of a minimum length are eligible