After registering the data warehouse, and everything was going just fine, I lost the connection between the management server and the data warehouse, that’s when I lost the “Data Warehouse” and “Reporting” workspaces, but when I tried to register it again, I got the following error:
But, when I checked the registered management groups in the data warehouse management server, I found out that the management group of the Management Server and the data warehouse are there.
In order to check the registered management group follow the following steps:
- Run PowerShell as Administrator.
- Enter the following Cmdlet (Import-Module “.\Microsoft.EnterpriseManagement.Warehouse.Cmdlets.psd1”).
- Run the following Cmdlet “Get-SCDWSource”
In order to fix that error, you’ve to follow the following steps:
Using the same Powershell session, Enter the following Cmdlet:
UnRegister-SCDWSource –ComputerName “Data Warehouse Management Server” –DataSourceTypeName “ServiceManager” –DataSourceName “Management Server Management Group”
Once done you can register your Data Warehouse again, and everything will be okay.
When you restart your SCSM Management Server, or even shut downed it for a while and starting it up again, you would face the following error when you try to open the Service Manager Console.
As shown in the screenshot “The Data Access Service is either not running or not yet initialized”.
And, actually that is the reason why the connection to the Service Manager Management Server fails. When the server starting up after a reboot or a shutdown, the service does not start. Although that service startup type is Automatic, but sometimes it doesn’t just run, so you have to manually start or restart that service by following the following steps:
- Press Win+R to open the Run.
- Write Services.msc to open the services.
- Hover over “System Center Data Access Service”.
- Right click on the service and click on “Start”, if it is grayed out click on “Restart”
Once done, open the service manager console again, and everything would go just fine.
When you try to create an AD Connector in SCSM 2016, everything would go just fine if you choose the default option while selecting a domain or OU step, but if you want to determine the a specific domain or OU, you will have to browse and select it, and that’s when that error will be raised.
Actually, this is a known issue and is documented in the release notes which you can see from here.
The workaround for this issue is to install “Microsoft Visual C++ 2012 Redistributable”.
Registering the data warehouse is the first thing to be done once you install your SCSM Console, but facing an error during the registration process would cause a headache to you especially, there are no errors logged in the event log.
However, the first thing you would think about when you are using any Microsoft Product GUI, is that it turns into Powershell, and it is the reason for that error.
The DW registration wizard uses Powershell cmdlet to trigger that task, but since the Powershell execution policy prevents the execution of registration cmdlet, that results in that error.
In order to solve that issue, you have to follow the following steps:
- Open Powershell on the server from which you are trying to register the DW.
- Make sure you run it as Administrator
- Run the following cmdlet “Set-ExecutionPolicy RemoteSigned“.
- Restart the Service Manager Console.
The data warehouse management server is one of the most important components of SCSM, that’s why the first thing we do after installing the Service Manager console is to register the data warehouse, but some times Winds do not blow as the vessels wish, and we face errors like the following one:
The main reasons for that errors are:
- The firewall is blocking the connection between the console and the data warehouse management server.
- The System Center Data Access Service and System Center Management Configuration are not running on the data warehouse management server.
So in order to solve this issue, you have to check whether the required ports are open or not, and check whether the mentioned services are running or not.
Once you check both of them, everything will be okay, as you see in the following screenshot:
It’s common to see an installation failure due to some misconfigured prerequisites.
But sometimes you may face some abnormal case, as shown in the following screenshot:
Mainly, when you face such a situation, you go directly to the “Event Viewer” or the Logs to get more details about the issue.
So, once you checked the “Event Viewer”, you will figure out that the “System Center Management Configuration Service” connection has timed out.
And, in order to solve such an issue, you’ve to follow the following steps:
- Open the “Registry Editor”
- Go to the following path “HKEY_LOCAL_MACHINESYSTEM/CurrentControlSet/Control”
- Look for “ServicesPipeTimeout” Value, if it exists Modify its decimal value to “600000”, if not You’ve to create a DWORD Value and set its decimal value to “600000”.
- Restart your server.
Once you open it again and restart your installation, everything will work just fine.