We have had a few customers run into the “Error 3000: Unable to register to the Advisor Service” while trying to connect their OpsMgr 2012 Management group to System Center Advisor. There are two reason why a customer may run into this. 1.Their internal proxy server\firewalls are blocking communication to the Advisor service endpoints 2.The server clock is off sync with the current time by more than 5mins. The below article shows you how to work through the first issue the second issue you can resolve pretty easily by changing the clock time on your server to match the current time, you can accomplish this with opening command prompt as an Administrator type w32tm /tz to check the time zone, and w32tm /resync to sync.
PROXY REGISTRATION CONFIGURATION STEPS
Step 1: Request exception for the service endpoints
The following domains and URLs need to be accessible through the firewall for the management server to access the Advisor Web Service.
Resource | Ports |
service.systemcenteradvisor.com scadvisor.accesscontrol.windows.net scadvisorservice.accesscontrol.windows.net scadvisorstore.blob.core.windows.net/* data.systemcenteradvisor.com ods.systemcenteradvisor.com *.systemcenteradvisor.com | Ports 80 and 443 Ports 80 and 443 Ports 80 and 443 Ports 80 and 443 Ports 80 and 443 Ports 80 and 443 Ports 80 and 443 |
The following domains and URLs need to be accessible through the firewall to view the Advisor Web portal.
Resource | Ports |
*.systemcenteradvisor.com *.live.com *.microsoft.com | Ports 80 and 443 Ports 80 and 443 Ports 80 and 443 |
Also ensure the Internet Explorer proxy is set correctly on your computer you are trying to login with.
If none of the above steps resolve your issue please login to the Advisor Preview portal click the ‘Feedback’ button on the bottom right of the web page and file a ‘Feedback’ item and we will respond and help you troubleshoot further within 24hours.
POST-REGISTRATION PROXY CONFIGURATION STEPS
Once you have completed registering your OpsMgr Environment to the Advisor Service you need to follow Steps 2, 3 and 4 to allow your Management servers to send data to the Advisor Web Service.
Step 2: Configure the proxy server in the OpsMgr Console
Open the OpsMgr Console
Go to the “Administration” view
Select “Advisor Connection” under the "System Center Advisor" Node
Click “Configure Proxy Server”
- Check the checkbox to use a proxy server to access the Advisor Web Service
- Specify the proxy address
Step 3: Specify credentials if the Proxy Server requires Authentication
If your proxy server required authentication, you can specify one in the form of an OpsMgr RunAs account and associate it with the ‘System Center Advisor Run As Profile Proxy’
In the OpsMgr Console, go to the “Administration” view
Select “Profiles” under the "RunAs Configuration" Node
Double click and open “System Center Advisor Run As Profile Proxy”
![]()
- Click ‘Add’ to add a 'RunAs Account'. You can either create one or use an existing account. This account needs to have sufficient permissions to pass through the proxy
- Set the Account to be targeted at the ‘Operations Manager Management Servers’ Group
- Complete the wizard and save the changes
Step 4: Configure the proxy server on each Management Server
Open Command Prompt as an Administrator on the Management Server
Type netsh winhttp set proxy myproxy:80
- Restart the ‘System Center Management’ Service (HealthService)
- Do step 2 on each of your management servers in your management group
If none of the above steps resolve your issue please login to the Advisor Preview portal click the ‘Feedback’ button on the bottom right of the web page and file a ‘Feedback’ item and we will respond and help you troubleshoot further within 24hours.
VERIFYING IF THINGS ARE WORK POST COMPLETING THE CONFIGURATION WIZARD
Step 1: Validate if the following MPs get downloaded to your OpsMgr Environment
Note: Only if you added these intelligence packs from the Advisor Portal will you see all these MPs.
You can additionally check for these MPs using OpsMgr PowerShell and typing these commands
get-scommanagementpack | where {$_.DisplayName -match 'Advisor'} | select Name,DisplayName,Version,KeyToken
get-scommanagementpack | where {$_.DisplayName -match 'Advisor'} | select Name,DisplayName,Version | ft
Step 2: Validate if data is being sent up to the Advisor service
- Open ‘Performance Monitor’
Select ‘Health Service Management Groups’
Add all the counters that start with ‘HTTP’
![]()
If things are configured right you should see a lot of perf mon activity for these counters
Step 3: Check for Errors on the Management Server Event Logs
As a final step if all of the above fails see if you are seeing any errors in the Operations Manager event log and filter by Event Sources:Advisor, Health Service Modules, HealthService. You can copy these event and post them in the Advisor Preview portal ‘Feedback’ view so we in the product team can help you further.
The Advisor engineering team is committed to resolving all your onboarding issues so please contact us if you run into any issues. We are here to help.
-Satya Vel
Advisor Preview Twitter Handle: @mscAdvisor