My IT Experiences - Microsoft 365, SharePoint & Azure

Setting up Reporting Services for a SharePoint 2010 in integrated mode can be done in less than 30 minutes if you have the infrastructure ready. However there are a few things to take care of if we are in a SharePoint farm environment with different servers handling different roles. To get Reporting Services to work in SharePoint Integrated mode requires SharePoint object model. Either we install SharePoint object model on our database server running Reporting Service or install SQL Server Reporting Service on a SharePoint application server. Here are a few things to take care of: 1. Use a domain account in the Reporting Services Configuration Manager 2. In the Reporting Services Configuration Manager wizard, click on Apply in different screens before navigating away. 3. Reporting Services Add-in is required on SharePoint Servers; it is part of the SharePoint 2010 pre-requisite installer. It can also be downloaded and installed separately on SharePoint Servers. ...

While checking the Surface Area settings in our SQL Server 2005 cluster environment, I received this error: You cannot configure surface area of clusted services by connecting to a computer name. connect to the virtual server to configure clustered services The reason was I had logged in remotely using the cluster name and tried to open the SQL Surface Area Configuration window; therefore it was assuming local settings. This is how I fixed the issue: In SQL Surface Area Configuration Windows, click Change Computer and select the cluster instance under the option Remote Computer

I was trying to install MOSS 2007 64 bit on a Windows Server 2008 R2 (Virtual Server) and I encountered this error while running Sharepoint Products and Technologies Wizard on my first server in the farm: Failed to connect to the database server or the database name does not exist. Ensure the database server exists, is a Sql server, and that you have the appropriate permissions to access the database server. It seems certain ports needs to be open in the Windows Server where SQL Server 2008 was installed, this batch file solved the problem: @echo ========= SQL Server Ports =================== @echo Enabling SQLServer default instance port 1433 netsh firewall set portopening TCP 1433 "SQLServer" @echo Enabling Dedicated Admin Connection port 1434 netsh firewall set portopening TCP 1434 "SQL Admin Connection" @echo Enabling conventional SQL Server Service Broker port 4022 netsh firewall set portopening TCP 4022 "SQL Service Broker" @echo Enabling Transact...