The publisher of this content does not allow it to be displayed in a frame

This will issue will come when SQL Server has been upgraded to any versions after 2016, SSRS reports that are used to display in iFrame will fail to display.

Solution:

Go to URL and change the URL to reportviwer, if the URL is using reports then it will not dispay in the iframe.

Example:

Change From:

https://Server/Reports/browse

Change To:

https://Server/ReportServer/Pages/ReportViewer.aspx?&rs:embed=true

or

 http://Servername/ReportServer/Pages/ReportViewer.aspx?%kjhkjs%khjkhkjhy%retre+uytts%2popiopoi+iuiuyiuy&rs:Command=Render&Rs:embed=true

Note:  this will be your report name -> %kjhkjs%khjkhkjhy%retre+uytts%2popiopoi+iuiuyiuy

SSRS Failed to Start - an error occurred when attempting to connect to the report server remote procedure call (RPC) end point.

ERROR: 

report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the operation.

 ---> System.Runtime.InteropServices.COMException: The RPC server is not listening. (Exception from HRESULT: 0x800706B3)

   --- End of inner exception stack trace ---

   at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.ThrowOnError(ManagementBaseObject mo)

   at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.GenerateDatabaseScript(String databaseName, Int32 lcid, Boolean isSharePointIntegrated, String& script)

   at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.GenerateDatabaseScript(String databaseName, Int32 lcid, Boolean isSharePointIntegrated, String& script)

Solution:

1. Switch the account to local service/local system

2. Start the reporting services and configure.

3. Now change the service account to domain account.

 

SQL Server Job - Failing - Error: 4014, Severity: 20, State: 8.

 There are many reasons to fail the SQL Server job with this error code like -

1. Permission issue for the Job owner
2. Permissions for the SQL Server Agent account
3. Permissions on MSDB and User Datbases
4. Issues with the sp_send_dbmail parameters 

If above are proper please follow the below steps to identify the issue -

Open profiler and choose the below events and then run the job.

In our case this was the culprit.

Now fix the code and run the job, which will succeed. 

Job Output file location

-- Script to find the JobOutPut Location.

select j.name,js.output_file_name,

  js.step_name,js.database_name "Executing On which DB?",

  last_run_outcome = case when js.last_run_outcome = 0 then 'Failed'

        when js.last_run_outcome = 1 then 'Succeeded'

        when js.last_run_outcome = 2 then 'Retry'

        when js.last_run_outcome = 3 then 'Canceled'

        else 'Unknown'

       end,

  last_run_datetime = msdb.dbo.agent_datetime(

       case when js.last_run_date = 0 then NULL else js.last_run_date end,

       case when js.last_run_time = 0 then NULL else js.last_run_time end)

from msdb.dbo.sysjobs j

  inner join msdb.dbo.sysjobsteps js

   on j.job_id = js.job_id

   WHERE js.output_file_name <> '[NULL]' 

  order by js.output_file_name

Thanks to : https://www.sqlservercentral.com/scripts/query-to-find-the-job-output-file-location-at-each-job-step

ORACLE- Contol File Missing – Recovery (ORA-00205: error in identifying control file)

 Good Recovery Tips, Thank you:

https://fatdba.com/2012/09/24/contol-file-missing-recovery-ora-00205-error-in-identifying-control-file/

Change Mode Of SSAS

Below are the details how we can change this mode, please note take a backup of existing CUBES before changing this option.

DeploymentModes :

DeploymentMode=2 for Tabular Mode

DeploymentMode=0 for Multidimensional Mode

DeploymentMode=1 is for PowerPivot for SharePoint instances.

Steps:

1. Backup any multidimensional databases on the server and either detach them or delete them.  Once mode is changed this may not work.
2. Copy the msmdsrv.ini file to safe location this can be found here - C:\Program Files\Microsoft SQL Server\MSAS15.MSSQLSERVER\OLAP\Config.
3. Open the config file in Notepad. Change the DeploymentMode property as required - 0 (multidimensional) to 2 (tabular) Save and close the file.
4. Copy the msmdsrv.ini file back to the OLAP\Config directory.
5. Restart the SQL Server Analysis Services instance.

SSRS 2019 Could Not Load Folder Contents - You are not allowed to view this folder

1. Add the user group / service account to the local admin
2. Refresh the URL