There was an error during installation.
The tool was unable to install Application Server Role, Web Server (IIS) Role.
[...]
Application Server Role, Web Server (IIS) Role: configuration error.
[...]

You can simply fix this by installing .NET Framework 3.5 Features from Server Manager before running the Product Preparation Tool:

After this step make sure to specify the source location (by clicking Specify an alternate source path) of the installation files (usually D:\sources\sxs) because the source files for .NET Framework 3.5 are not copied to the harddrive during Windows setup.

Protection Agent cannot be installed on machine where DPM is installed

This problem occurs when you’re trying to install the agent from …\DPM\Agents\RA\4.1.3333.0\… folder. Try installing the SP1 RTM agent first by navigating to …\DPM\ProtectionAgents\RA\4.1.3313.0\… After installing this version you can apply the update from the first folder or from DPM Management Console.

In the log I could see that Setup could not create the Datawarehouse database:

EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0×80131904, Exception.Message: CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file ‘E:\SQL\Data.mdf’.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

I have a standalone SQL 2012 SP1 server (SQL) and a Windows Server 2012 machine where I want to install Operations Manager. The data and log files on the SQL machine reside on separated disks: D for logs, E for data. I ran setup a few times and chose different folder names but nothing worked. Then I tried to specify a filename instead, because setup always tried to create the database using [foldername].mdf – you can see this in the log.

With filenames specified for Data and Log file folder setup ran fine and completed without any further errors. But… this lead to wrongly named files on my SQL server:

This, in general, is not really bad. But it’s simply not nice. So I shut down the Operations Manager server and detached the OperationsManagerDW database in SQL Server Management Studio by running this query:

USE master;
GO
EXEC sp_detach_db @dbname = N'OperationsManagerDW';
GO

Then I renamed the OperationsManagerDW.mdf.mdf and OperationsManagerDW.ldf.ldf files by removing the double extension and I deleted the empty folders. After that I reattached the databases with

USE master;
GO
CREATE DATABASE OperationsManagerDW 
    ON (FILENAME = 'E:\SQL\Data\OperationsManagerDW.mdf'),
       (FILENAME = 'D:\SQL\Logs\OperationsManagerDW.ldf')
    FOR ATTACH;
GO

Turn on the TPM security hardware

This computer may require you to change the state of the Trusted Platform Module (TPM) manually. To perform this action, try turning on the TPM through the BIOS or performing a firmware update. Consult the computer manufacture’s documentation for instructions.

There is no such object on the server.

Error code: 0×80072030

This error is a bit misleading as it asserts that there is something wrong with your hardware. But never mind. There is no such object on the server and error code 0×80072030 are Active Directory related. This simply means the wizard could not find an object in AD.

The way Windows Server 2012 and Windows 8 store their TPM owner information changed from previous versions. With Active Directory schema version 48 some TPM objects have been introduced (like msTPM-InformationObject) that store this information in the future. You can have look at these changes, just open the support\adprep\sch48.ldf file from your Windows Server 2012 DVD.

If you want to use AD to store your TPM information the same way you did with Windows Server 2008 R2 or Windows 7 you’ll need to update your schema first to version 56 (Windows Server 2012). This will bring all the necessary changes to your environment. If you cannot update your schema you’ll just have one possibility left: Move your computer object to another ou where the group policy object containing your TMP/Bitlocker settings is not applied. Configure TPM “offline” and store the information in a secure place – you won’t have the owner information in AD for this computer. Then move the object back to its previous ou.

ERROR: SQL Server error: [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint ‘CollectionQueryRuleTables_PK’. Cannot insert duplicate key in object ‘dbo.CollectionQueryRuleTables’. The duplicate key value is (16777228, 1, vSMS_R_System). Configuration Manager Setup 05.02.2013 09:12:18 4084 (0x0FF4)

The easiest way would be to delete the corresponding rows from CollectionQueryRuleTables table in your SCCM database. This would solve the problem but it is not supported by Microsoft:

1. Note the CollectionID (16777228)
2. Open SQL Management Studio, open SCCM Database
3. Use this query to delete the rows in the table:

   DELETE FROM CollectionQueryRuleTables WHERE CollectionID = [YourCollectionID]

4. Run your update again.
5. Test if the collection still works. You can determine the collection by running this query:

   SELECT * FROM Collections_G WHERE CollectionID = [YourCollectionID]

   CollectionName is the name of the collection in SCCM.

Again: Editing the database directly is not supported. Make a backup of your database before you start! Don’t blame me if something goes wrong.

$schemaContext = Get-ADRootDSE | %{$_.schemaNamingContext}

Foreach ($dc in ([System.DirectoryServices.ActiveDirectory.DomainController]::findall(
   (new-object System.DirectoryServices.ActiveDirectory.DirectoryContext("Domain",$env:USERDNSDOMAIN)))) | 
   %{$_.name})
{
	$path = 'LDAP://' + $dc + '/' + $schemaContext
	$Object = [adsi]$path
	$dc + '  ' + $Object.objectversion
}

3622 spam comments in 2 years – but only 157 “ham” comments. I wished it was the other way round. Buy hey, none of those spam comments where ever shown on my blog… thanks to Akismet.

CUSTOMER NOTICE: (Revised) HP MSL Tape Libraries and HP Tape Autoloaders – Upgrade firmware is temporarily withdrawn due to incompatibility with HP Ultrium LTO-5 tape drives and certain backup configurations

Upgrade firmware, which has new features and also supports the addition of HP Ultrium LTO-6 tape drives in installed HP MSL Tape Libraries and HP 1/8 G2 Tape Autoloaders, is temporarily withdrawn due to an incompatibility issue with systems using HP Ultrium LTO-5 and certain backup configurations. New HP MSL Tape Libraries and HP 1/8 G2 Tape Autoloaders with only HP Ultrium LTO-6 drives are not affected.

Although LTO 6 drive configurations seem to be not affected HP does not offer this firmware version for download anymore. I justed contacted HP support to get the firmware… hopefully I’ll get an answer soon.

Update 1

Today I received the pre-released firmware version 5.90. With that revision the tape drive works really good, but after booting the library I could not enter the pin for the security token used to encrypt the tapes in the drive.

The entered PIN is too long. A maximum of 15 characters are allowed for PIN!

After downgrading to 5.70 I changed the pin to 15 characters. Then I installed 5.90 again and the pin worked – but now Data Protection Manager did not recognize the new drive. I ran Proliant Support Pack, used the latest available drivers from ftp.hp.com and now everything works as expected. Good support HP!

Update 2

HP released firmware version 5.90 for MSL2024 libraries supporting LTO 6 tape drives. You can download the package at http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=de&cc=de&prodTypeId=12169&prodSeriesId=3936307&swItem=co-115010-1&prodNameId=5336420&swEnvOID=4064&swLang=8&taskId=135&mode=4&idx=0. It also contains latest firmware for MSL 4048 (version 8.30), MSL 8048 and 8096 (version 1090) and updates for these drives:

• Ultrium 232 SCSI – P63W (in HP 1/8 Ultrium G2 Tape Autoloader only)
• Ultrium 448 SCSI – S63W
• Ultrium 920 SAS – C25W & Q51W
• Ultrium 920 SCSI – D24W
• Ultrium 960 SCSI – G63W
• Ultrium 960 2Gb FC – L63W
• Ultrium 960 4Gb FC – M63W
• Ultrium 1760 SAS – U61W
• Ultrium 1760 SCSI – W61W
• Ultrium 1840 SCSI – B63W
• Ultrium 1840 4Gb FC – H68W
• Ultrium 3000 8Gb FC – Y5BW
• Ultrium 3000 SAS – Z58W
• Ultrium 3280 8Gb FC – I5EW
• Ultrium 6250 8Gb FC – 22CW
• Ultrium 6250 SAS – 32AW

After a short test of this firmware I can confirm that the problem with PINs exceeding 15 characters still exists – the changelog says nothing about this issue but that it existed in 5.00.

• Welcome Screen of Microsoft System Center 2012 Data Protection Manager Service Pack 1 – choose Install: Data Protection Manager
  
• Setup Welcome Screen, simply click Next
  
• Choose your type of SQL installation, typically you will use the dedicated one
  
• The installer shows a warning, when you need to backup your database first. Do so…
  
• Navigate to your DPM\bin directory and run dpmbackup -db
  
• Enter your product key, click Next
  
• Usually you do not need to change anything here:
  
• Security Settings: Specify the password for your SQL Server service account. You should have this in your documentation
  
• Everything’s ready now, let setup do its job…
  
• After setup is complete you’ll need to update all protection agents in your environment. You may recognize Windows Server 2012 servers that are marked “unreachable” after updating (Data Protection Manager Error ID: 308 / The protection Agent operation failed because DPM could not communicate with the Protection Agent service on xyz / The service did not respond to the start or control request in a timely fashion (0x8007041D)
  
• Looking at the eventlog of that Windows Server 2012 server, you’ll receive this error: “DCOM got error “1053″ attempting to start the service DPMRA with arguments “Unavailable” in order to run the server: {[GUID]}”
  
• Running dpmra.exe from your DPM\bin directory will let you know, that the agent didn’t find VssRequestor.dll (The program can’t start because VssRequestor.dll is missing from your computer. Try reinstalling the program to fix this problem.)
  
• Looking at the DPM\bin directory on your server won’t let you find it either
  

And here comes the solution to this problem. Simply copy the VssRequestor.dll from any non Windows Server 2012 server and hit Refresh on the server in DPM Agent management view. That’s it…

I followed Kevin Holman’s instructions step by step and ran into the same problem he was noticing after the move.

The error I got was:

Error 777971002, severity 16, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.

So I followed the steps he took which did not solve my problem. I still got these errors in the log. But there is another way to fix this – here is my solution to the problem:

1. Login to your SQL Machine
2. Insert SCOM 2007 disc
3. Navigate to D:\SupportTools\AMD64 (or whatever your cd drive and your platform is)
4. Run DBCreateWizard.exe
5. On the Database Information page choose your existing OperationsManager database and clear the “Create New Database” checkbox
6. Fill in all other information according to your environment
7. Finish the wizard

This will take a few minutes. After that the problem should be fixed.