Month: October 2013

SCOM 2012 SP1 – Agent Not Monitored

saars1337 Operations Manager 2012 SP1

Symptoms

After installing/attaching agents the state is displayed as “Not monitored”

Image

Note: The agent will likely appear this way after first installing/attaching. wait 24 hours for it to auto-configure and only assume failure if it is still showing the same status after this

Resolution

  1. Connect to server that is displayed as “Not monitored”
  2. Open the run box and type “Services.msc”Run - services.msc
  3. Locate service named “System Center Management”Services - System Center Management
  4. Right click and stop serviceServices - Right click menu
  5. Browse to C:\Program Files\System Center Operations Manager\Agent
  6. Change folder name to “Health Service State Old”SCOM - Health Service State folder
  7. Start service and make sure that a new folder is createdSCOM - Health Service State folder new
  8. Wait 5 minutes and refresh SCOM console to ensure that agent is now monitoredSCOM - Agent monitored

DPM 2012 SP1 – Suspect Tape

saars1337 Data Protection Manager 2012 SP1

Symptoms

  • Tapes will be listed as “Suspect”
  • DPM will not be able to write to these tapes

Troubleshooting

One of the first indication that this was not a legitimate error was that i was seeing this on 7 brand new tapes

Another giveaway was that they were labeled this way after a Fast Inventory, which means that they have never entered the drive to be read or written on

DPM Tape Suspect

Resolution 1

Change the label on the tape.

For me, everything in the 50 range was being marked as suspect. e.g. 450-459, 550-559.

This is not a very good fix but will allow the tapes to be written on should you be hesitant to try anything else

Resolution 2

Open the DPM Shell and enter the following

osql -E -S localhost\MSDPM2012 -d DPMDB -Q “UPDATE tbl_MM_ArchiveMedia SET IsSuspect = 0”

This command will modify the SQL table and change all tapes to non-suspect

DPM Mark all tapes as not suspect

WARNING: if you have any tapes that are legitimately suspect this will also change them so use with caution

Resolution 3

This method will allow you to individually mark tapes as not suspect, but can be quite time consuming

Open Microsoft SQL Server Management Studio

Navigate to Server Instance > Databases > DPMDB > Tables

SQL DPM Tables

Right click on dbo.tbl_MM_ArchiveMedia and click “Edit Top 200 Rows”. should you have more than 200 tapes you can easily expand the amount of rows in the right pane under “Top Specification”, change it to No

SQL Right Click Table

To Identify which tape is which, run a query on the database (DPMDB) and match MediaID to the edit tab

select [BarcodeValue], [MediaID]
FROM [DPMDB].[dbo].[tbl_MM_Media]

Once the correct row is identified change the column marked “IsSuspect” to 0

Note: i am working on a PowerShell script that will make this process easier, but time has been tight and this will be a good starting point for most people