So lately i have been working with FEP 2010 and integrating it with SCCM 2007 R3. After a successful deployment and integration, i had some issues with getting my reports to show accurately. The issue in summary was that the FEP dashboard was reporting the correct analysis of the client deployment but when i checked the computer list report, it listed just about 22 instead of over 100 deployed systems.
And so the troubleshooting began, I posted the question on my favorite TechNet forums but did not get a response so after a week of no resolution, i decided to take the risk and re-install the FEP reporting role.
THE RE-INSTALL…… :) (All actions carried out on the SCCM/FEP 2010 server)
1. From control panel locate program features and click to uninstall a program or better still in a run box type appwiz.cpl and select the FEP 2010 reporting and choose to uninstall
2. After a successful uninstallation, insert the DVD/ navigate to the FEP installation folder select the FEP en.us and select 64 bit folder. Double click on the server setup
3. Follow through the installation wizard, when u get to the installation options page, choose advanced installation
4. Select the FEP 2010 Reporting role and click next
5. On the reporting configuration page, ensure the reporting url is entered just as it appears on the SSRS configuration page (In my case the NETBIOS name was used http://servername/reportserver).
6. Follow through the wizard till the perquisites check.
Note that a warning would be given for the SSRS perquisite check; click next to continue the installation.
7. Complete your installation and check through your reports again…
Viola all pops up!
Taking a risk is worth it sometimes.
I hope this helps someone else.
Feel free to drop your comments or questions. :)
Enabling Firewall Exceptions For SQL Server Named Instances
For over 3 weeks I had issues connecting to my sharepoint configuation database which resides on a remote SQL server 2008 R2 with windows firewall enabled on it. Here is my scenario
WFE Server (Windows server 2008 SP2, Moss 2010)
Backend/ database ( Windows server 2008 R2, SQL Server 2008 R2)
I had created exceptions for the TCP port 1433 and UDP port 1434 and also allowed the SQL Browser program through the firewall. Also I ensure the named pipes and TCP/IP were enabled and properly configured with regards to dynamic ports (I enabled the correct ip and entered the port 1433 as the dynamic port for communication in the network configuration console for the SQL server). Inspite of all these I still had transient issues with communication between the WFE and Backend server.
After weeks of checking I finally set up a similar scenario on a test server and the same issue showed up (Unable to connect to configuration database server, the database server does not exist or the user does not have sufficient permissions to connect). The only difference was that my test SQL 2008 R2 Server was residing on a windows server 2008 R2 server, I decided to use the diagnose and repair option (available in windows server 2008 R2) in the advanced firewall actions pane; here’s what I did;
1. After opening the advanced firewall window (On the SQL Server); select the diagnose and repair option as depicted below
2. Select the incoming connections on the troubleshooting problems page and click next
3. Select next on the incoming connections page
4. On the what are you trying to do page; select “Allow other computers to connect to SQL server….” and click next
After the process it detected that the firewall was blocking incoming SQL connections and offered to fix it automatically. I selected yes and after it was fixed I tried to connect my SharePoint again and voila! It worked like a charm.
This in turn helped me to fix the production SQL server 2008 R2 on Windows Server 2008 SP2 by creating a firewall exception for SQL service program sqlservr .exe for the named instance located at C:\Program Files\Microsoft SQL Server\MSSQL10_50.”Instance name”\MSSQL\Binn
Hope this helps someone too! :)
Recently I was saddled with the task of upgrading our SQL 2008 SP1 server to SQL 2008 R2. Here is what I did;
1. Install and run SQL Server 2008 R2 upgrade advisor on the server
2. Based on the analysis report from the upgrade advisor, make corrections and re-run the upgrade advisor.
Issues Encountered and Resolution
1. Custom security and authentication extensions were detected; the effect of this was that the upgrade would be blocked. In order to resolve this, the security and authentication entries in the report services configuration file were removed and placed in a text file.
2. Custom data processing and report items extensions were discovered; the effect of this is that the upgrade can be done but the custom extensions would have to be manually moved from the old installation file to the new installation file
1. Run the setup file from the disk or shared directory and on the installation center page, select planning menu and select system configuration checker (this helps to ensure that the system requirements are adequate)
2. Select Installation menu and select upgrade from SQL 2000, 2005, 2008
3. After the support files are installed a restart is required though the upgrade can continue and the server can be restarted after the upgrade is complete.
1. Update the reporting server configuration file with the security and authentication entries copied out before the upgrade. This enables the Operations manager reporting server function again.
2. Move all extensions present in the old bin folder of the old report server installation to the bin folder of the new reporting server.
Ensure to run the upgrade advisor first in order to help plan your upgrade. :)
Finally I get the chance to fiddle around one of my favorites..I Got it stored upSystems Centre Data Protection Manager 2010 a welcome relief to manage your Infrastructures’ backup and disaster recovery. You can get the RTM here http://technet.microsoft.com/en-us/evalcenter/bb727240.aspxBelow is a step by step guide on How to Install the Product Using a remote/existing Instance of SQL 2008 w/SP1Before I begin, I would like to mention some important notes1. The Account you plan to use on the remote SQL should be a member of the Local Administrator on Both Servers (DPM and Remote SQL), this is just for the installation purpose especially on the remote instance so it can be removed from the remote sql after installation.2. The Installation Account must be a member of the sysadmin role on the SQL instance you plan to use.3. The SQL Instance (Either default or named) must have an un-allocated SRSS attched to it (by un-allocated that infers not in use by another application such as share-point) and the reporting services mode should be in native mode not share point integrated mode.PS: when using a named instance, ensure the following protocols are enabled (for the instance) Named Pipes, TCP/IP and Shared Memory .PS: Well in my case to avoid issues and for proper troubleshooting i just installed a new named instance and dedicated it to DPM (that’s the best i could do for my favorite!)4. Finally do ensure your SQL 2008 is patched at least SP1….with regards to using R2 i am yet to test on that and maybe i’ll update when i get more info or do an actual test.5. For system requirements for DPM server you could have a quick scheme through technet’s guide http://technet.microsoft.com/en-us/library/ff399554.aspx6. If you plan to to use the DPM console on your desktop then follow this step before you install DPM http://www.scdpmonline.org/dpm-console-on-your-desktop.aspxSo lets get down to the Business of the day!Pre-Installation StepsOn Remote SQL Server1. Insert your dvd/ point to the installation folder (from a share or local system), locate the SQLPreinstaller folder2. Double click on the SQLPreinstaller package with the correct version of your SQL (x64/x86)3.Wait for the installation to complete and click close.On DPM Server1. Insert your dvd/ point to the installation folder (from a share or local system), locate the setup.msi and double click on it2. on the Splash screen select install Data Protection Manager3. Accept the agreement and click next4.Click next on the welcome page5.On the prequisites check page, ensure evrything is green before moving on else the installation will not continue*Not much worry as DPM contains the package or link to the prequisite needed just incase any one is missing!6.On the product registration page enter your details and move on7.On Installation settings page ensure to select an existing instance of SQL in the SQL server settings path, also you may choose to cahnge the default installation path or accept the default and move on.8.On the SQL settings page, specify the name and instance of the remote SQL and also a valid account (with priviledges listed above) and move on to the next page9.On security settings page, enter the password for the restricted local user accounts that DPM will create and move on10. Select you Microsoft update opt-in and CEIP settings on the next two pages and move on11.Examine the Installation Summary and click install12. Wait and ensure no errors are encounterd and yeah u are half way to the finish line.Update (march 3rd/2011) : I just tried the dpm 2010 with a remote SQL 2008R2 and ..no luck, there is no direct support as at today :(. However if you install dpm 2010 and then upgrade your sql to R2 from 2008 Sp1 it works very well. :)Hope you find this helpful!
Filed under: Computers and Internet