Go to KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList there is a list of SIDs here.
These security IDs are what links the user account to the profile. Each user account has a SID. Click on the SIDs and you will see a ProfileImagePath key in the right hand key. Use this to figure out the effected profile.
It will say something like %SystemDrive%\Users\username write this down you will need it later. Once you know which user account the SID is for.
Delete the SID from the profile list hive (just right click on it and hit delete). Now restart and log on as the user you couldn't log in as. It will create a new profile all your settings will be gone. Log off and log back on as a local admin.
Go back to regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList again.
This was repopulated when you logged back on. Now select profile image path and set it back to what it was originally. See if you can log back in as the user."
We encountered problem with Timer Service on one of the servers in SP 2010 Farm. The System log was filled with error events [Event Id 7024 - The SharePoint 2010 Timer service terminated with service-specific error %%-2147467259] and [Event Id 7031 - The SharePoint 2010 Timer service terminated unexpectedly. It has done this 20 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service] every 2 minutes causing the Timer service and jobs to fail.
Not sure, but assuming that this issue might be caused after recent Windows and SP security patches/updates. We tried with Microsoft Support ticket for $499. They couldn't resolve and we got refund. Also tried solutions from different blogs and local MSFT certified vendors (charged $200 per hour). But, nothing worked. In SP 2007, we don't see any CONFIG files in the BIN folder. [C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN]
But, from SP 2010 onward, we see new additional CONFIG files in the BIN folder. [C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN]
Luckily, the Timer service is working fine on one of the SP 2010 Farm servers. [As part of Rollback plan for the activity Change Request, we took snapshots for both the servers, DB backups and also copied the original config files as backup into another folder].
Copied both the OWSTIMER.EXE.CONFIG and PSCONFIG.EXE.CONFIG files from the working server and pasted into the folder of the problematic server.
Ran the below PSConfig command successfully on both the servers.
MSFT keeps on updating the features/options very frequently. Licenses and Apps is bit confusing now a days. There are many related licenses & applications. For Ex: OneDrive, Microsoft Teams Site Collections, SharePoint Online apps under Office Enterprise E3 License. Below are the TEST cases with licenses & applications combination. TEST 1: Enable Microsoft Teams app only. Created a new user (Teams Test) with user (no administrator access) role (as shown below).
Login into https://www.office.com , you will see Only Teams icon. (Add-in appeared for enabling of Office Store).
Click on Teams, you will notice the below message for first time. By Clicking on "Get the Windows app", you can install Teams Windows app for Windows 7/10. If already installed, it will be initiated for login. By clicking on "Use the web app instead", will open the Teams in browser.
Was able to login thru Teams Windows app and Teams web app. Created a new Team (TeamsTest) with below selected options.
Microsoft Teams login thru Teams Windows app.
Microsoft Teams login thru Teams web app.
Click on Files tab in the Teams window. You will see options as shown below.
Click on "Open in SharePoint"
Teams is opened as SharePoint Online Site (as shown below).
(Note: When new Team is created, a SharePoint Site collection get created in the back-end).
Conclusion 1: Enabling Office 365 Enterprise E3 (Developer) License and Microsoft Teams App, user was able to login into SharePoint Online Site related to specific Teams without any issues.
TEST 2: Without changing any Licences and Apps (continuing as above), added the above test user to OneDrive access. SPac >> User profiles >> Manage User Permissions.
Login into https://www.office.com , you will see Only Teams icon. (Add-in appeared for enabling of Office Store). We don't see OneDrive icon.
Made up the OneDrive URL and tried, but failed.
Conclusion 2: Enabling Office 365 Enterprise E3 (Developer) License and Microsoft Teams App, user cannot login into OneDrive app. _______________________________________________________________ TEST 3: Without changing any Licences and Apps (continuing as above), added the users to Team Site Visitors group with Read access to SharePoint Online site (as shown below).
User was able to access the SharePoint Site (as shown below).
Conclusion 3: Enabling Office 365 Enterprise E3 (Developer) License and Microsoft Teams App, user was able to login into SharePoint Online site with providing permissions. _______________________________________________________________ Continuing with second part.....SPO - O365 - Licenses and Apps - Post2
