Cannot impersonate user for data source (rsErrorImpersonatingUser) error

An error has occurred during report processing. (rsProcessingAborted)
Cannot impersonate user for data source ‘SMSDB’

Usually this error is caused by user account that was used to install the Reporting Role password has been changed or it’s being disabled.

Solution:

  • Launch Reporting Services Configuration Manager
  • Click on Report Manager URL
  • Click Report URL
  • Drill into SMS_DB1 Reports

You should see a Database Source

db1

Click on the Database source & you will see the properties of your DB Source.

Go ahead and change/update the credentials. You should be able to do your reporting subscription now.

Diagnostic tool that helps troubleshoot Kerberos related connectivity issues with SQL Server, SQL Server Reporting Services, and SQL Server Analysis Services

There’s a tool to check Kerberos issue.

Kerberos authentication provides a highly secure method to authenticate client and server entities (security principals) on a network. To use Kerberos authentication with SQL Server, a Service Principal Name (SPN) must be registered with Active Directory, which plays the role of the Key Distribution Center in a Windows domain.
In addition, many customers also enable delegation for multi-tier applications using SQL Server. In such a setup, it may be difficult to troubleshoot the connectivity problems with SQL Server when Kerberos authentication fails.The Kerberos Configuration Manager for SQL Server is a diagnostic tool that helps troubleshoot Kerberos related connectivity issues with SQL Server, SQL Server Reporting Services, and SQL Server Analysis Services. It can perform the following functions:

  • Gather information on OS and Microsoft SQL Server instances installed on a server.
  • Report on all SPN and delegation configurations on the server.
  • Identify potential problems in SPNs and delegations.
  • Fix potential SPN problems.

You can download the tool at this link.

Windows 10 Activation Error Code 0xd0000272

Bump into this issue to activate Windows 10 with error code 0xd0000272.

Solution that helps my case;

  1. Go to Registry, HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
  2. Delete the Windows Update key
  3. Retry to Activate Windows 10 again

Hope it helps

ConfigMgr 2012: Error removing Component Server role

At some point you may encounter an error when removing Distribution Point role stated, The server xxx cannot be deleted because it contains the following site system roles:

Solution:
1. Ensure all roles other than Component Server and Site System are removed.

2. Go to Services.msc, Stop and Restart SMS_SITE_COMPONENT_MANAGER service.

3. Go back to ConfigMgr Console and hit f5 to refresh it.

You will notice Component Server is gone. Go ahead and delete the Server from the Console.

Hope it helps.

Deploying Skype for Business using SCCM

  1. Download Skype for Business Basic installer from https://www.microsoft.com/en-us/download/details.aspx?id=49439
  2. Extract the files by running the following command.

C:\lyncentry.exe /extract:C:\SkypeForBusiness /quiet

3. Browse to C:\SkypeForBusiness folder and you will see a lot of folders and files after extraction.

4. Launch command prompt and browse to the folder C:\SkypeForBusiness. Enter this command

setup /admin

5. Configure your desired settings. Most importantly, ensure Display level = None Suppress modal is checked

6. Once done configured, click File and then select Save.

7. Save it to Updates folder

C:\SkypeForBusiness\Updates

8. There you go, import the package to SCCM and ensure the command line = Setup.exe 

Hope this helps.

 

Update 1606 for SCCM 2012 is now Available

Those who are running SCCM 2012 1511 and 1602, an update is available to download now.

Please refer to this site.

Lots of great new features in this build!

Shrink SCCM 2012 SQL Server Reporting Services log database

After some time after you installed, configured SCCM 2012 with Reporting Services (SSRS), there’s a possibly a log file (ReportServer_log.ldf) where the size of it will use up all the free disk space on where the volume installed. We can shrink it by changing some values as below steps.

  1. Launch Microsoft SQL Management Studio
  2. Expand Databases
  3. Right click ReportServer database | Properties
  4. Change from Full Recovery to Simple Recovery
  5. Right click on ReportServerTasks | Shrink | Files
  6. Under File Type, select Log, then click OK
  7. ReportServer_log.ldf file should be decreased by a lot now.

Hope it helps.