I wanted to share my experience on the issue which I was working on Azure Site Recovery configuration for enabling the VMM cloud protection. We had configured the VMM provider and registered it successfully with Azure subscription and the server was showing as connected on the Azure Portal.

However, when we navigate to Recovery Services-> <Recovery Vault >-> Protected Items -> VMM Clouds -- we see "No clouds are configured on the registered servers. On the VMM server, Create clouds which you want to protect."

We know that that we had 3 clouds created on the SCVMM server and it should supposed to show on the portal. 

SCVMM version -- 3.2.8071.0

Checked the provider agent version and the CBEngine version are latest.

Tried reinstalling the provider, still the same issue.

The SCVMM server was not installed with HA.

We found that around 6 machines were failing for VM refresh with the errors. Those machines were showing with status as migration failed and HDD missing.

We found these problematic machines from the console and removed them from the SCVMM database using the below cmdlet.

https://technet.microsoft.com/en-us/library/hh801721.aspx

NOTE: When used with the Force parameter, Remove-SCVirtualMachine only deletes the virtual machine from the VMM database. It does not delete the virtual machine itself.

Remove-SCVirtualMachine <MachineName> -Force

Then we refreshed the hosts with VM refresh and the VMs got refreshed without error status.

We restarted SCVMM service and then refreshed the SCVMM server on the Azure portal in the ASR configuration.

Waited for some time till it finishes the refresh job and found that the cloud started showing on the ASR configuration. 

Thanks

Santosh Killekar - Support Escalation Engineer (System Center)

Disclaimer: This posting is provided "AS IS" with no warranties and confers no rights.

Thanks

Santosh Killekar - Support Escalation Engineer (Microsoft System Center)

Disclaimer: This posting is provided "AS IS" with no warranties and confers no rights.

I wanted share my experience while troubleshooting one of the SCSM 2012 R2 transform job issue.

Issue  : 

Transform job was not running as per schedule. The job status was showing always in 'not started' status. If we run the job manually, it was running successfully without errors.  No reports showing latest data. 

Resolution :

• There was no job failure errors for transform job on the DW management server event logs.
• Checked the last 5 number of batches and it was showing as completed. But the batch number for transform job was having huge difference compared to other job batches.
• Tried running the ETL jobs manually and it ran successfully for all the jobs. No errors. It catch up the latest batches.
• The report started showing latest data.
• Found the following errors related to the transform job  Scheduler Data Source Module.
• Checked the job status using get-scdwjob and get-scdwjobschedule, both were showing as enabled for transform job.

 ===========================================================

Log Name:      Operations Manager 

Source:        Health Service Modules
Date:          <Date>

Event ID:      11366

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <ComputerName>

Description:

The Microsoft Operations Manager Scheduler Data Source Module failed to initialize because some window has no day of the week set. 

One or more workflows were affected by this.  

Workflow name: Schedule_Transform.Common

Instance name: ?????????

Instance ID: {37FECB60-26C5-FCDC-950D-F24CE13C3DF6}

Management group: <ManagementGroupName>

===========================================================

• Checked the schedule for all the jobs using get-scdwjobschedule and found that the 'Frequency' column value was missing in the output. It supposed to show '0:30' as per the default schedule. 

Transform.Common                         Daily    17/03/2015 06:00:00      True         <Frequency>       18/03/2015 11:20:00

• Added the following schedule for transform.common job using cmdlet. 

Set-SCDWJobSchedule -JobName Transform.Common -ScheduleType Daily –DailyFrequency 00:30:00 –DailyStart 12:00

• The transform job schedule started automatically after this change. 

Thanks

Santosh Killekar - Support Escalation Engineer (Microsoft System Center)

Disclaimer: This posting is provided "AS IS" with no warranties and confers no rights.

Hello,

I wanted share the steps for successful movement of SCOM 2012 OPsMgr and DW databases movement to the new SQL server.

You can follow the below the below articles for OpsMgrDB and OpsMgrDW database movements.

https://technet.microsoft.com/en-us/library/hh278848.aspx

https://technet.microsoft.com/en-us/library/hh268492.aspx

• Apart from this, you will      also have to edit the following registry settings on each management servers. I have seen customers are missing to edit this registry key and      getting issues.

======================================================================================================

• On each Management you need to update the following registry keys.

              a.  Log on to the management server with Administrator permissions.

              b.  Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor.

     c.  Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCenter\2010\Common\Database, double-click the name DatabaseServerName, and then change the value to the name of the SQL Cluster that will be hosting the OperationsManager Database, and then click OK to save your change.

  (If you are using a named instance of SQL Server, be sure to use the ServerName\Instance name format.)

 ======================================================================================================

Reference :

Using SQL Server 2012 Always On Availability Groups with System Center 2012 SP1 - Operations Manager

https://technet.microsoft.com/en-us/library/jj899851.aspx

======================================================================================================

On each Management you need to update the registry keys.

a. Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor.

b. Under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup, double-click the value DatabaseServerName, and then change the value to the hostname of the SQL Server-based computer now hosting the OperationsManager database. If you are using a named instance of SQL Server, be sure to use the ServerName\Instance name format.

 c. Click OK.

d. Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DataWarehouseDBServerName - (change this to the new SQL server hosting the DW).

• If your SQL server is not      using the default port, then you need to upadte the registry as below. DatabaseServerName      – HostName\InstanceName,<PortNumber>

======================================================================================================

Thanks

Santosh Killekar - Support Engineer (System Center)

Disclaimer: This posting is provided "AS IS" with no warranties and confers no rights.

Here are the steps which I followed for successful movement of the PROD SCSM 2012 SP1 environment to the DEV SCSM 2012 SP1 environment.

• I added the secondary management server (SCSM DEV) on the prod Environment.
• This installation followed with the proper MSI file which was provided with a hotfix from Microsoft.
• Took a backup of the PROD database which will have the secondary MS entry in the SCSM DB.
• Restore the backup on the DEV SQL server.
• Followed the steps for changing the SQL server name and changing the SCSM DEV server name on the DB. https://technet.microsoft.com/en-us/library/hh914201.aspx.
• Changed the database name registry setting to point to the restore DB on the test SQL server.
• Stoped the System center services on the SCSM DEV server as below. (Which was added as Secondary MS for PROD Env)
• Open the registry editor (Start -> run, type regedit)
• Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\System Center\2010\Common\Database
• There are two keys that can be configured here - one for the server name (DatabaseServerName) and one for the database name (DatabaseName)
• Start the System center services on the SCSM DEV server. https://technet.microsoft.com/en-us/library/hh914223.aspx
• Now I promoted the SCSM DEV server as Primary MS in the DEV environment. https://technet.microsoft.com/en-us/library/hh914188.aspx
• Cleared the health service cache folder on the SCSM DEV server.
• Now I was able to open the SCSM console on SCSM DEV. It was connected to the proper SQL server from DEV.

For getting the SCSM DW on the DEV server, followed the below steps.
Installed the SCSM DEV DW with new DW databases.

Removed the existing DW registration from the SCSM DB on the DEV environment using the following cmdlets.
 

Un-registration of SCSM DW from CMDB : 
 Import-Module 'C:\Program Files\Microsoft System Center\Service Manager 2012\Powershell\System.Center.Service.Manager.psd1'

 Once after importing the cmdlet, I ran the following cmdlet to remove the DW registration.

 $class=get-scclass -Name Microsoft.SystemCenter.ResourceAccessLayer.DwSdkResourceStore

get-scclassinstance -class $class | remove-scclassinstance

 Now I registered the SCSM DW in the DEV environment and it was successful. 
 

Reference :

https://blogs.technet.com/b/servicemanager/archive/2012/04/22/moving-the-service-manager-and-dw-databases.aspx

Thanks

Santosh Killekar - Support Engineer (System Center)

Disclaimer: This posting is provided "AS IS" with no warranties and confers no rights.

I recently gone through an issue where the SCSM 2012 Sp1 Data Warehouse installation was failing with the following error.

"An Error occurred while executing a custom action:_ConfigureAnalysisServer"

Reviewed the installation logs and found the following log information.

==================================================================
ConfigureAnalysisServer error: Errors in the metadata manager. The '\\?\f:\SQLDATA\DWDATA' storage location of the 'DWASDataBase' database can not be located under the server data directory.
.
StackTrace:    at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
   at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate, XmlaWarningCollection warnings)
   at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
   at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
   at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings)
   at Microsoft.Reporting.Setup.ReportingManagedCAs.CreateDatabase(Server svr, String DatabaseName, String DatabaseDataDir)
   at Microsoft.Reporting.Setup.ReportingManagedCAs.ConfigureAnalysisServerCA(Session session) 
NOTE: custom action _ConfigureAnalysisServer unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _ConfigureAnalysisServer returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
==================================================================

Resolution :

This can occur if you try to create SQL Analysis Server database in a separate folder in the data directory. Hence while installation, select the default directory for SQL analysis service database store.

This may be applicable to SCSM 2012 R2 Data Warehouse installation. 

Thanks

Santosh Killekar - Support Engineer (System Center)

Disclaimer: This posting is provided "AS IS" with no warranties and confers no rights.