Wednesday, June 25, 2008
no report servers were found on the specified machine. Details: Invalid namespace
First step to do is to make sure IIS and ASP.NET is running/installed. If those are installed and working well, now the easy way is to run sql setup.exe file to reinstall reporting service by checking that option then prompt to install all the components.
How to install SQL Server 2005 Reporting Services a Windows Vista-based computer
After you install the original release version of SQL Server 2005, you must apply SQL Server 2005 Service Pack 2 (SP2) or a later service pack to obtain support from Microsoft. Additionally, SQL Server 2005 Express Edition with Advanced Services SP2 is already at the SQL Server 2005 SP2 level. For more information, visit the following Microsoft Web site:http://go.microsoft.com/fwlink/?LinkID=63922 (http://go.microsoft.com/fwlink/?LinkID=63922)
Before you install SQL Server 2005 Reporting Services, you must enable Microsoft ASP.NET and Microsoft Internet Information Services (IIS).
To enable ASP.NET and IIS, follow these steps:
1. In Control Panel, click Programs, and then double-click Programs and Features.
2. In the User Account Control dialog box, click Continue.
3. Click Turn Windows features on or off.
4. In the Windows Features dialog box, expand Internet Information Services, expand Web Management Tools, expand IIS6 Management Compatibility, and then click to select the following check boxes:
• IIS 6 WMI Compatibility
• IIS Metabase and IIS 6 configuration compatibility
5. Expand World Wide Web Services, expand Application Development Features, and then click to select the following check boxes:
• ASP.NET
• ISAPI Extensions
• ISAPI Filters
6. Expand Common HTTP Features, and then click to select the following check boxes:
• Default Document
• Directory Browsing
• HTTP Errors
• HTTP Redirection
• Static Content
7. Expand Security, and then click to select the Windows Authentication check box.
Install SQL Server 2005 Reporting Services
To install SQL Server 2005 Reporting Services, follow these steps:
1. Log on to Windows Vista, and enable ASP.NET and IIS. For more information, see the "Prerequisites" section.
2. Verify that the World Wide Web Publishing service is started. If the World Wide Web Publishing service is not started, configure the service to start automatically. To do this, follow these steps:
a. In Control Panel, click System and Maintenance.
b. Click Administrative Tools.
c. Double-click Services.
d. In the User Account Control dialog box, click Continue.
e. Right-click World Wide Web Publishing Service, and then click Properties.
f. In the World Wide Web Publishing Service Properties dialog box, click Automatic in the Startup Type list. g. Click Apply, click Start, and then click OK.
3. Start to install SQL Server 2005 or SQL Server 2005 Express Edition with Advanced Services SP2.
Notes
• When you install the original release version of SQL Server 2005, you receive a warning message that explains that this program has known compatibility issues. Click Run program to continue the installation.
• In the Feature Selection dialog box, make sure that Reporting Services is selected.
• In the Report Server Installation Options dialog box, select either of the following options:
• Install the default configuration
• Install but do not configure the server
4. Install SQL Server 2005 SP2.
Notes
• For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 913089 (http://support.microsoft.com/kb/913089/) How to obtain the latest service pack for SQL Server 2005
• If you install SQL Server 2005 Express Edition with Advanced Services SP2, skip step 4 because SQL Server 2005 SP2 is already installed.
• You must make sure that the SQL Server service is started before you install SQL Server 2005 SP2. The SQL Server service must be running to perform an authentication check in the Authentication Mode dialog box of the Setup program.
• After you leave the Authentication Mode dialog box, you can stop the SQL Server service to avoid a system restart. To stop the SQL Server service, click Administrative Tools in Control Panel, double-click Services, right-click the SQL Server service, and then click Stop.
• If the SQL Server 2005 User Provisioning Tool for Vista starts, start the SQL Server service before you grant administrative rights to a user. You can use the SQL Server 2005 User Provisioning Tool for Vista to add Windows user accounts to the SYSADMIN fixed server role easily.
5. Start the SQL Server service if the service is not started. If you install SQL Server Express Edition with Advanced Services SP2, reset IIS.
To reset IIS, follow these steps:
1. Open a command prompt by using the Run as administrator option.
2. Type IISRESET, and then press Enter.
6. If you selected the Install but do not configure the server option in the Report Server Installation Options dialog box, configure the report server. To do this, follow these steps:
a. Start the Reporting Services Configuration tool. To start the tool, click Start, point to All Programs, point to SQL Server 2005, point to Configuration Tools, and then click Reporting Services Configuration.
b. In the User Account Control dialog box, click Continue.
c. In the Report Server Installation Instance Selection dialog box, type the name of the computer in the Machine Name box.
d. Click the instance of SQL Server 2005 Reporting Services in the Instance Name list, and then click Connect. e. Configure the server for operation. Note Reporting Services runs as a legacy application on IIS 7.0. If you configure the application pool for the Report Server virtual directory on a new Reporting Services installation, one of the following methods:
• Select Classic .NET AppPool for the report server.
• Create a new application pool. Then, set the Managed Pipeline Mode option to Classic.
If you installed Reporting Services by using the default configuration, the report server runs in its own application pool under the NetworkService account. If you use the default configuration, the report server is fully operational on Windows Vista. However, you should avoid running the report server in the default application pool on IIS 7.0. The default application pool has the Managed Pipeline Mode option set to Integrated. You will receive an "HTTP 500" error message if you run the report server in the default application pool.
7. Configure the report server for local administration. To access the report server and Report Manager locally, follow these steps:
a. Start Windows Internet Explorer.
b. On the Tools menu, click Internet Options.
c. Click Security.
d. Click Trusted Sites.
e. Click Sites.
f. Under Add this Web site to the zone, type http://ServerName. If you are not using HTTPS for the default site, click to clear the Require server certification (https:) for all sites in this zone check box.
g. Click Add. h. Repeat step 7f and step 7g to add the http://localhost URL, and then click Close. Note This step enables you to start Internet Explorer and open either the localhost or the network computer name of the server for both the Report Server application and the Report Manager application.
8. Create role assignments that explicitly grant you access together with full permissions. To do this, follow these steps:
a. Start Internet Explorer together with the Run as administrator option. To do this, click Start, click All Programs, right-click Internet Explorer, and then click Run as administrator.
b. Open Report Manager. By default, the Report Manager URL is http://ServerName/reports.
If you use SQL Server Express with Advanced Services SP2, the Report Manager URL is http://ServerName/reports$sqlexpress. If you use a named instance of Reporting Services, the Report Manager URL is http://ServerName/reports$InstanceName
c. In the Home dialog box, click Properties.
d. Click New Role Assignment.
e. Type a Windows user account name by using the following format:Domain\User
f. Click to select the Content Manager check box.
g. Click OK.
h. In the Home dialog box, click Site Settings.
i. Click Configure site-wide security.
j. Click New Role Assignment.
k. Type a Windows user account by using the following format:Domain\User
l. Click System Administrator.
m. Click OK.
n. Close Report Manager.
9. Use Internet Explorer without the Run as administrator option to reopen Report Manager.
http://support.microsoft.com/kb/934164
http://www.microsoft.com/downloads/details.aspx?familyid=4C6BA9FD-319A-4887-BC75-3B02B5E48A40&displaylang=en
http://msdn.microsoft.com/en-us/library/ms143718.aspx
SCOM_ClientMonitoring
How to Configure Clients for Client Monitoring in Operations Manager 2007
follow the following link to do initial setup of client monitoring from OpsMgr http://technet.microsoft.com/en-us/library/bb381453.aspx
Run the Group Policy Object Editor (gpedit.msc) for the domain or local computer. NoteFor information about Group Policy, see http://go.microsoft.com/fwlink/?LinkId=70168.
You can find the GP under Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings. Also you can configure as per your requirement to turn on/off Windows Error Reporting policy.
On Group Policy administrative template or local computer policy, you can add Agentless Exception Monitoring to the domain . Run Client Monitoring Configuration Wizard to create Group Policy administrative template file .
NOTE: Use the same procedure to Disable the Group Policy settings, thereby disabling Client Monitoring on the clients.
follow the following link to do initial setup of client monitoring from OpsMgr http://technet.microsoft.com/en-us/library/bb381453.aspx
Run the Group Policy Object Editor (gpedit.msc) for the domain or local computer. NoteFor information about Group Policy, see http://go.microsoft.com/fwlink/?LinkId=70168.
You can find the GP under Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings. Also you can configure as per your requirement to turn on/off Windows Error Reporting policy.
On Group Policy administrative template or local computer policy, you can add Agentless Exception Monitoring to the domain . Run Client Monitoring Configuration Wizard to create Group Policy administrative template file .
NOTE: Use the same procedure to Disable the Group Policy settings, thereby disabling Client Monitoring on the clients.
Monday, June 23, 2008
Config SCOM 2007 Notification setup
SMTP Notification
In this example we will use Microsoft Exchange 2007, which will use Windows integrated SMTP
authentication when sending e-mails. However, Exchange is not required. You can use just about any SMTP server for sending e-mail notification in Operations Manager 2007, including a local instance of IIS SMTP installed on your Management Server.
NOTE: How to test SMTP services manually in Windows server 2003
http://support.microsoft.com/kb/323350
Setup Notification Channel
In this part we will setup channels SCOM 2007 can use to send IM and SMTP.
1. From the Start Menu, select the SCOM Operations Console
2. In the Navigation pane (left), Click Administration
3. In the Administration pane, click Settings
4. In the Action pane, right click Notification and select Properties from the context menu.
5. On the E-mail tab, select the "Enable e-mail notification" checkbox.
6. Next, we’ll add the SMTP Server. Click the Add button. Enter the FQDN of the target SMTP
Server, port number (In most cases you can leave default port 25), and the authentication
method for the SMTP Server. In this example, the SMTP Server requires Windows Integrated
authentication. Consult your e-mail administrator for the appropriate authentication setting for
your SMTP Server.
NOTE: You can add additional SMTP servers for failover to provide redundancy in the event of
failure of the primary SMTP Server.
7. Next, input the Return address; this address will be shown as sender when notifications are sent to notification recipients. Note that this e-mail needs to be the e-mail address of the Notification Action Account. Accept the default values in the remaining fields.
8. Next, select the Instant Messaging tab. Select the “Enable instant messaging notifications"
checkbox. In the IM Server field, enter the FQDN of your LCS server. In the Return address field, enter the sip address of the Notification Action Account.
NOTE: You must add sip: in front of the return address, for example
sip:scom-notification@scomresources.local.
9. If you have installed a Microsoft Office Live Communication 2005 Server with default settings, you will have to change IM port to 5060. It is important that you use your Notification Action Account instant messaging address; otherwise instant message notifications may fail due to lack of permissions. Accept the remaining default values by clicking OK.
Setup Notification Action Account
In this part we will create an account that will be used to send SMTP and IM notification, the notification action account. Note that this account should have the e-mail and SIP URI that you have filled in as return addresses under notification channels. I have created a domain user account named SCOMNOTIFICATION that will be used to both send SMTP and IM.
1. From the Start Menu, launch the SCOM Operations Console
2. In the Navigation pane (left), Click Administration
3. In the Administration pane, right-click Run As Accounts and choose Create Run As Account from the context menu to launch the Create Run As Account Wizard.
4. On the Introduction screen, click Next
5. On the General screen, choose Windows from the Run as account type drop-down box, input
display name and a short description. Click Next
6. On the Account screen, input user name, password and domain, then click Create. The wizard
will close when done.
Configure Run As Profile for Notification Action Account
We will now configure SCOM to use that account when sending notifications from your Management Server.
1. In the Administration pane click Run As Profiles. In the Action pane, right-click the Notification Account node and choose Properties
2. Select the Run As Accounts tab, then click New
3. On the Alternative Run As Account screen, choose the Run As Account created in previous
section, and then select your Management Server in the matching computer list. Then click OK.
Click OK again to finish.
Create a Notification Recipient to Receive SMTP and IM Notifications
First we will create a recipient and fill in all information about that account. Then we will create a
subscription and setup what notifications will be sent to that recipient. Finally, we will add notification devices to allow the notification recipient to receive notifications via both e-mail and instant message. In this example, we have created a domain account named John Conner that will receive all alerts at all times, both IM and SMTP.
1. From the Start Menu, launch the SCOM Operations Console
2. In the Navigation pane (left), Click Administration
3. In the Administration pane, right-click Recipients and choose New Notification Recipient
4. On the General tab click the button to the right of the textbox to select your notification
recipients’ domain account and click OK.
5. On the Notification Devices tab, click Add to launch the Create Notification Device Wizard.
6. Choose E-mail from the Notification channel dropdown. Verify that the recipient e-mail address is correct in the “Delivery address for the selected channel" textbox. Click Next.
7. On the Schedule screen, leave the default settings and this recipient will receive e-mails 24/7.
Click Next
8. On the General screen, enter a device name, for example John Conner E-Mail. Click Finish
9. On the Notification Devices screen, click Add.
10. Then choose Instant Messaging from the notification channel dropdown. Verify that the
recipient address is correct in the "Delivery address for the selected channel" textbox, for
example SIP:tom.cruze@scomresources.local. The value should be the notification recipients
SIP URI. Click next
11. On the Schedule screen, leave the default settings, this recipient will receive IM 24/7. Click Next
12. On the General screen, enter a device name, for example John Conner IM, and then click Finish. Click OK again to finish.
13. In the Administration pane, right-click Subscriptions and choose New Notification Subscription to launch the Create Notification Subscription Wizard.
14. Create Notification Subscription Wizard - Introduction: Click Next
15. On the General screen, input a name, for example "all alerts at all time". Input a short
description and then click Add
16. Choose your domain recipient created in the previous section and click OK. Click Next.
17. On the User Role Filter screen, leave the default settings and click Next
18. On the Groups screen, leave default settings, all groups selected, and click Next
19. On the Classes screen, leave default settings, all classes, and click Next
20. On the Alert Criteria screen, leave default settings, all alert criteria, and click Next
21. On the Alert Aging screen, leave default settings, do not notify on alert aging. and click Next
22. On the Formats screen, leave the default e-mail and IM format, click Finish
Additional Resources:
http://www.momresources.org/scom/how-to/scom_notification.pdf
Live Communications Server 2005 Deployment Resources
http://office.microsoft.com/en-us/products/FX011526591033.aspx
In this example we will use Microsoft Exchange 2007, which will use Windows integrated SMTP
authentication when sending e-mails. However, Exchange is not required. You can use just about any SMTP server for sending e-mail notification in Operations Manager 2007, including a local instance of IIS SMTP installed on your Management Server.
NOTE: How to test SMTP services manually in Windows server 2003
http://support.microsoft.com/kb/323350
Setup Notification Channel
In this part we will setup channels SCOM 2007 can use to send IM and SMTP.
1. From the Start Menu, select the SCOM Operations Console
2. In the Navigation pane (left), Click Administration
3. In the Administration pane, click Settings
4. In the Action pane, right click Notification and select Properties from the context menu.
5. On the E-mail tab, select the "Enable e-mail notification" checkbox.
6. Next, we’ll add the SMTP Server. Click the Add button. Enter the FQDN of the target SMTP
Server, port number (In most cases you can leave default port 25), and the authentication
method for the SMTP Server. In this example, the SMTP Server requires Windows Integrated
authentication. Consult your e-mail administrator for the appropriate authentication setting for
your SMTP Server.
NOTE: You can add additional SMTP servers for failover to provide redundancy in the event of
failure of the primary SMTP Server.
7. Next, input the Return address; this address will be shown as sender when notifications are sent to notification recipients. Note that this e-mail needs to be the e-mail address of the Notification Action Account. Accept the default values in the remaining fields.
8. Next, select the Instant Messaging tab. Select the “Enable instant messaging notifications"
checkbox. In the IM Server field, enter the FQDN of your LCS server. In the Return address field, enter the sip address of the Notification Action Account.
NOTE: You must add sip: in front of the return address, for example
sip:scom-notification@scomresources.local.
9. If you have installed a Microsoft Office Live Communication 2005 Server with default settings, you will have to change IM port to 5060. It is important that you use your Notification Action Account instant messaging address; otherwise instant message notifications may fail due to lack of permissions. Accept the remaining default values by clicking OK.
Setup Notification Action Account
In this part we will create an account that will be used to send SMTP and IM notification, the notification action account. Note that this account should have the e-mail and SIP URI that you have filled in as return addresses under notification channels. I have created a domain user account named SCOMNOTIFICATION that will be used to both send SMTP and IM.
1. From the Start Menu, launch the SCOM Operations Console
2. In the Navigation pane (left), Click Administration
3. In the Administration pane, right-click Run As Accounts and choose Create Run As Account from the context menu to launch the Create Run As Account Wizard.
4. On the Introduction screen, click Next
5. On the General screen, choose Windows from the Run as account type drop-down box, input
display name and a short description. Click Next
6. On the Account screen, input user name, password and domain, then click Create. The wizard
will close when done.
Configure Run As Profile for Notification Action Account
We will now configure SCOM to use that account when sending notifications from your Management Server.
1. In the Administration pane click Run As Profiles. In the Action pane, right-click the Notification Account node and choose Properties
2. Select the Run As Accounts tab, then click New
3. On the Alternative Run As Account screen, choose the Run As Account created in previous
section, and then select your Management Server in the matching computer list. Then click OK.
Click OK again to finish.
Create a Notification Recipient to Receive SMTP and IM Notifications
First we will create a recipient and fill in all information about that account. Then we will create a
subscription and setup what notifications will be sent to that recipient. Finally, we will add notification devices to allow the notification recipient to receive notifications via both e-mail and instant message. In this example, we have created a domain account named John Conner that will receive all alerts at all times, both IM and SMTP.
1. From the Start Menu, launch the SCOM Operations Console
2. In the Navigation pane (left), Click Administration
3. In the Administration pane, right-click Recipients and choose New Notification Recipient
4. On the General tab click the button to the right of the textbox to select your notification
recipients’ domain account and click OK.
5. On the Notification Devices tab, click Add to launch the Create Notification Device Wizard.
6. Choose E-mail from the Notification channel dropdown. Verify that the recipient e-mail address is correct in the “Delivery address for the selected channel" textbox. Click Next.
7. On the Schedule screen, leave the default settings and this recipient will receive e-mails 24/7.
Click Next
8. On the General screen, enter a device name, for example John Conner E-Mail. Click Finish
9. On the Notification Devices screen, click Add.
10. Then choose Instant Messaging from the notification channel dropdown. Verify that the
recipient address is correct in the "Delivery address for the selected channel" textbox, for
example SIP:tom.cruze@scomresources.local. The value should be the notification recipients
SIP URI. Click next
11. On the Schedule screen, leave the default settings, this recipient will receive IM 24/7. Click Next
12. On the General screen, enter a device name, for example John Conner IM, and then click Finish. Click OK again to finish.
13. In the Administration pane, right-click Subscriptions and choose New Notification Subscription to launch the Create Notification Subscription Wizard.
14. Create Notification Subscription Wizard - Introduction: Click Next
15. On the General screen, input a name, for example "all alerts at all time". Input a short
description and then click Add
16. Choose your domain recipient created in the previous section and click OK. Click Next.
17. On the User Role Filter screen, leave the default settings and click Next
18. On the Groups screen, leave default settings, all groups selected, and click Next
19. On the Classes screen, leave default settings, all classes, and click Next
20. On the Alert Criteria screen, leave default settings, all alert criteria, and click Next
21. On the Alert Aging screen, leave default settings, do not notify on alert aging. and click Next
22. On the Formats screen, leave the default e-mail and IM format, click Finish
Additional Resources:
http://www.momresources.org/scom/how-to/scom_notification.pdf
Live Communications Server 2005 Deployment Resources
http://office.microsoft.com/en-us/products/FX011526591033.aspx
Subscribe to:
Posts (Atom)