Ops Mgr DNS Management Pack updated
The DNS Management Pack for Operations Manager 2007 has been updated again to version 6.0.6480.0, but it still doesn’t seem to fix the the major complaint with the previous version (6.0.6278.27).
The DNS Library WINS TTL Monitor, despite getting some updated verbiage in the MP Guide, still appears to be broken. The guidance now specifically mentions that you need to create an A record in DNS, and provides some override information. No matter though, even with creating the A record “placeholder” in the forward lookup zone that corresponds to the domain name of the Ops Mgr management server (i.e. placeholder.mydomain.local), the alert still comes in. Refer back to my previous post about that item. So…this monitor gets overridden again.
Cleanup after DPM 2007 SP1 installation
You might have noticed, if you’ve installed SP1 for Data Protection Manager 2007, that it leaves behind the Visual C++ 2008 Redistributable package contents in your root directory. Tsk, tsk. How did that slip through beta, but yet be specifically called out in the Release Notes?
DPM 2007 SP1 setup leaves Microsoft Visual C++ Redistributable Package installation files in the root directory. You can manually delete the installation files.
Anyhow, here’s a quick and dirty batch (.bat) file that you can run on the local machine to delete the files.
Get it here:
Visual_C_2008_Redist_cleanup.zip (325 bytes, 928 hits)
Data Protection Manager 2007 SP1 turns off Reporting?
Although it’s been reported in the past that you might sometimes see Data Protection Manager 2007’s error 3013 on a Windows Server 2008 system, whereby SQL Reporting Services is not available, it seemed to be rare.
Now it appears that perhaps error 3013 is making a comeback with the installation of DPM 2007 SP1. On a fresh install of Windows Server 2008 x64, DPM 2007 x64 was installed and then SP1 for DPM 2007 x64 was applied. The Reporting feature was verified working before SP1 was installed, but stopped working after SP1 was applied.
The error text:
DPM could not connect to SQL Server Reporting Services server because of IIS connectivity issues.
On the computer on which the DPM database was created, restart the World Wide Web Publishing Service. On the Administrative Tools menu, select Services. Right-click World Wide Web Publishing Service, and then click Start.
ID: 3013
Unfortunately, the guidance given in the error dialog as well in Troubleshooting Reporting Issues page in Technet don’t really accomplish anything. Trust me, I’ve tried. The solution, as others have verified and reported, is almost provided in MSKB 938245…almost, except for one small typo in the instructions and the fact that you really wouldn’t know to get from point A (error 3013 as shown previously) to point B (following the steps in the KB article). Perhaps the DPM team will see to it to have the documentation updated again for Windows Server 2008.
Anyhow, you should be able to get your Reporting functionality working again by completing these steps.
- Close the DPM 2007 Administrator Console.
- Open the Internet Information Services (IIS) Manager, be sure you didn’t accidentally open the Internet Information Services (IIS) 6.0 Manager.
- Expand Web Sites, expand the Default Web Site, and then click the virtual directory for the report server. By default, this would be ReportServer$MS$DPM2007$.
- In the middle pane, while in Features View, double-click Handler Mappings in the IIS section.
- In the right pane, under the Actions section, click Edit Feature Permissions.
- Click to select the Scripts check box, and then click OK.
- Open the DPM 2007 Administrator Console and get some reporting done!
MOCS 2007 “[0x80004002] No such interface supported”
While trying to assist in the new installation of Microsoft Office Communications Server 2007, I ran into this rather unhelpful error in the error logs: [0x80004002] No such interface supported. I had full Enterprise Admin permissions so that ruled out the typical permissions suspects. What I found solved the error was not trying to use complex passwords when the Setup routine asked for service account passwords. So, if you run into this error during your MOCS 2007 setup, perhaps you’re trying to be too safe…now stop using those complex passwords and try something easily guessable like password. I’m not kidding.
Ops Mgr “The WINS Connector has stopped working”
Seems that the v6.0.6278.27 DNS management pack for Operations Manager 2007 has its own bug of fame. The “The WINS Connector has stopped working” alert will likely become familiar to you courtesy of the DNS Library WINS TTL Monitor. It seems that the MP ships with the “hostname” field filled in with “Placeholder”…but if you read the relase notes you’ll know this and know to fill it in with the NETBIOS name of something on your network or to create a WINS record for the host named PLACEHOLDER.
Setting the WINS TTL Monitor
The Windows Internet Name Service time to live (WINS TTL) monitor performs an NSLOOKUP query for a test (A) record named “placeholder” to verify that WINS resolution is working properly. You will need to create a test record called “placeholder” or create an override to change the target name.
Setting the Global Zone Resolution Monitor Target
The global zone resolution monitor performs an NSLOOKUP query for a test (A) record named “placeholder” to verify that global zone resolution is working properly. You will need to create a test record called “placeholder” or create an override to change the target name.
However, what really seems to happen is no matter what you do (or at least no matter what I did), you’ll still get the “The WINS Connector has stopped working” alerts. I tried individual overrrides, I tried a type override, I used upper case hostnames, lowercase hostnames, IP addresses, even tried creating a WINS record named PLACEHOLDER. No joy.
My solution: disable the monitor (DNS Library WINS TTL Monitor) until Microsoft updates the management pack. Have you been able to get it working?
Ops Mgr 2007 “Failed Accessing Windows Event Log”
If you’ve been getting these errors from your Operations Manager 2007 DHCP Management Pack, the solution is at hand! Here’s the typical error you’d get:
Failed Accessing Windows Event Log
The Windows Event Log Provider was unable to open the System event log on computer ‘{69E3F0CF-36C3-9FDC-1892-42FB003E34DB}’ for reading. The provider will retry opening the log every 30 seconds. Most recent error details: The RPC server is unavailable. One or more workflows were affected by this. Workflow name: Microsoft.Windows.DHCPServer.Library.Server.UnitMonitor.DependentServiceHealth Instance name: myserver.mycompany.local Instance ID: {69E3F0CF-36C3-9FDC-1892-42FB003E34DB} Management group: MyCompany-SysCtrOpsMgr
It seems that the DHCP MP v6.0.6383.0 introduced this annoying bug that seemingly had no solution. Well, I guess it really didn’t have a solution…until the next version was released. That version, v6.0.6452.0, was released in November and seems to fix the problem. Before you import this updated version though, be sure to remove any exisitng DHCP management packs. Per the included documentation:
Before you import the Windows Server DHCP Management Pack, take the following actions:
- Perform a full backup of the Operations Manager 2007 database.
- Uninstall any existing DHCP management packs. You may wish to record custom overrides and rules for possible inclusion in the new DHCP management pack.
Of course, the fix for this bug isn’t documented in the release notes, but none the less it does appear to be fixed.
Exchange and SQL OpsMgr Management Packs Updated
Updated Management Packs for Exchange Server 2007 and SQL Server were recently released for Operations Manager 2007. Check out the updates below as listed in the Management Pack documentation. As usual, download your Management Packs from the MP Catalog.
The following list contains the issues that are fixed in version 6.0.6461.0 of the Exchange Server 2007 Management Pack for System Center Operations Manager 2007:
- Updated the display name of the top level folder in the Operations console to “Exchange Server 2007 (Converted)”.
- Changed how the management pack monitors disks. Previously, disk monitoring rules lacked alert suppression. The following rules and monitors were disabled:
- Disk % Free Space low - Red(<10%)
- Disk % Free Space low - Yellow(<15%)
- Disk Free Megabytes low - Red(<20MB)
- Disk Free Megabytes low - Yellow(<40MB)
The following rules were added:
- Disk Free Space Low Red Rule (by default alerts if any disk has less than 20MB free space)
- Disk Free Space Low Yellow Rule (by default alerts if any disk has less than 40MB free space)
- Disk Percentage Free Space Low Red Rule (by default alerts if any disk has less than 10% free space)
- Disk Percentage Free Space Low Yellow Rule (by default alerts if any disk has less than 15% free disk space)
The new disk monitoring rules support alert suppression. It is also possible to use the Server Operating System Management Pack to monitor Exchange disk space, if desired. In that case, the above rules can be disabled.
SQL Server Management Pack version 6.0.6460.0 includes the following changes:
- The DB discovery script no longer casts the values that correspond to “Database Size (MB) (Numeric)” and “Log Size (MB) (Numeric)” as INT, to avoid overflows exceptions within the script itself.
- The DB discovery script now checks for possible overflow on the “Database Size (MB) (Numeric)” and “Log Size (MB) (Numeric)” values and prevents those overflows from occurring.
- For the numeric properties on the database class we are limited to 2147483647 MB (~2047 TB). In the event that a DB or log file exceeds that size then the value will be set to the maximum possible value of 2147483647 to prevent overflows. In these instances the ”Database Size (MB) (String)” and “Log Size (MB) (String)” will support larger values.
Update Rollup 5 for Exchange Server 2007 SP1
A little late, but maybe you didn’t see this yet?
Update Rollup 5 for Exchange Server 2007 SP1 is now available. Read all about the changes and updates by visiting MSKB 953467.
-
Translator
