SCOM 2012 R2 Management Servers and SQL Server Availability Groups

My team is in the middle of rolling out a brand new install of System Center Operations Manager 2012 R2.
I have set up a SQL Server Availability group that is spread across multiple subnets and installed the initial management server per
here.
As I have gone through attaching new management servers, I have noticed disturbing behavior. When the AG fails over to another node, the management servers will lose connectivity unless I either recycle the service or it fails back to the original
node. This is not a security issue as I have set up permissions. It says it cannot connect to the database anymore at all.
Has anyone else seen this behavior? Is there a setting I am missing somewhere?
Thanks for your help.
Dale

Hi Dale,
What about ApplicationIntent\Readonly?
http://msdn.microsoft.com/en-us/library/hh205662(v=vs.110).aspx
Still thinking about DNS, may be this could be for your case:
http://www.sqlservercentral.com/Forums/Topic1449216-2799-1.aspx
Natalya

Similar Messages

Is it possible to deploy 2 SCOM 2012 R2 reporting in a SQL server which already has SCOM reporting of a different management group but with 2 different reporting instance.

Hi Experts,
I have a typical situation in the LAB environment. Hope some one helps. I have Installed a SCOM 2012 R2 with SQL 2012 SP1 in a single server (Management group 1). I have installed another management group on another server using this SQL server for its database
so i have everything going fine.
The first management group has its reporting installed in the SQL server. For the second i created a new named instance for that. But i cannot run the SCOM setup in the SQL server (Also holding the Management group 1 MS) as 1 st reporting is already there.
When i run the setup it is asking me to repair it. I don't get the install option so i can install the reporting for management group 2 in the named instance.
Default instance is being used by the 1st management group.
Can any one figure a possibility for installing 2 SCOM reporting services for different management groups in a same SQL 2012 server please.
Gautam.75801

Hi Yan Li,
Thank you for the reply. So as you are aware If i need to instal reporting, i need to run the SCOM 2012 R2 setup in the SQL server and select reporting and select the
instance and then mention the management server there right. I am not getting that option there it is asking me to remove or repair the existing installation as there is already a SCOM entire setup including reporting there. As it is a lab there is no problem
in testing. I have 2 reporting instances. Any suggestions for me on how to overcome this issue and deploy the second reporting in the new named instance ?
Below is the screenshot of the error what i am talking about when i run SCOM 2012 R2 setup to install reporting in the SQL server
When i click on add feature reporting is greyed out (As already 1st management groups reporting is installed)
When i click on remove or repair it
uninstalls the existing one. But i want both SCOM 2012 r2 reporting to be there(For both Management group). Is it possible ? If yes What is the trick to run the setup ?
Gautam.75801

Can we recover SCCM 2012 R2 site Servers and SQL DB from hyper V or Vmware VM snapshot

Hi Folks
Can we recover SCCM 2012 R2 site Servers and SQL DB from hyper V or Vmware VM snapshot
if yes is there any challenges or any document available from Microsoft on Hyper V SCCM VM snapshot recovery.

I've made it work and it "should" work. However it's not the best practice method of site recovery. You should recover using a SQL restore.
See good example
http://anoopcnair.com/2012/07/01/sccm-configmgr-2012-primary-site-server-and-database-recovery-part-1/
Note that you should be using snapshots only on occasions when you are carrying out a risky operation. You can revert it the operation fails. It is not a substitute for a robust backup solution.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?

Hi All,
Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?
aa

I think you are confused with the way cluster is installed. Installing SQL on cluster is a two step process. On first node you create a new SQL cluster and on second node you need "AddNode" action.
Same edition media has to be used in above two operation.
you can install two separate instances with one enterprise and one standard.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

OraOledb, Linked Servers and SQL Server 2005 issues

Some issues I've come across when using SQL Server 2005 (and SQL Server Express 2005), the OraOLEDB provider (10.2.0.1) and a linked Oracle database (8.1.7.4.0 64-bit)
1) You must set the OraOledb.Oracle\AllowInProcess value to 1 to allow the OraOledb provider to run in SQL Server's process. Without doing this I receive an 'unspecified error' from the OLE DB provider when attempting to run a query
2) When running a ' select * ' query across a linked server using the provider, I receive the following error: Msg 9803, Level 16, State 1, Line 1
Invalid data for type "numeric". I can, however, select all of the columns by name and the query completes (no error). Sometimes the 'select *' query returns a few rows before the error, sometimes it doesn't. The Microsoft Provider for Oracle does not have this problem

Okay... I've got a Win2K3 Std Ed server (x64) running 64-bit SQL Server 2005 Enterprise Edition. I've installed the Oracle 10g 10.2.1 full client and admin tools, added two named services via the NetConfig assistant, and successfully set up (and tested) a connection via the ODBC Administrator to an Oracle database.
Now... when I try to create a new connection manager in SQL Server 2005 Integration Services, the OLEDB provider for Oracle can't be found, and when I try to manually add an underlying OLEDB connection to the database, SQL Server reports:
Test connection failed because of an error in initializing provider. The 'OraOLEDB.Oracle.1' provider is not registered on the local machine.
Does anyone know what I need to do to see my ODBC Server data connections in SQL Server 2005 (64 bit)? I don't have this issue on my 32-bit SQL Server 2005 servers.

OraOledb for 64-bit, Linked Servers and SQL Server 2005 issues

Our environment is : SQL Server 2005, Windows Server 2003, 64-bit and 32-bit operating systems.
Problem on 64-bit operating system box: (32-bit works fine).
I am trying to access Oracle 10g database using linked server from our SQL Server 2005. In case of number fileds i got the following error:
Invalid data for type "numeric".
After going through one of the posting in this forumn i was able to resolve the problem by converting those column values to char while querying and then converting them back to numeric type on SQL server side.
But today i ran into another problem. There is a VARCHAR2 column. I was able to retrieve the data yesterday for that column but today i am getting a blank recordset. If i exclude the colum from the query then i am getting all the rows.
I am querying against a view and it has got a number of columns whose data type is VARCHAR2.
Again the problem is on 64-bit operating system only. We have a 32-bit operating system on which i am able to retrieve the data including this column. I looked at the data and everything looks OK. No funny characters etc.
I tried workarounds like using cast, to_char, checking for nulls etc., Nothing works.
Any help is greately appreciated. Thanks.

Did you find a resolution for this? We have similar problem. Set up a linked server in SQL 2006 to Oracle (running on Windows 64-bit) Linked server works and views I had set up were working but they added some new data in the Oracle test database I am using and now I get errors on one of the views.
Error I am getting on the view is "Cannot initialize the data source object of OLE DB Provider "OraOLDEDB.ORacle" for the linked server"
If I fine tune my queries to find the specific table or view that is at issue, then I get the error "inconsistent metadata for a column"

SQL Server Availability Groups

Hello,
If we want to use SQL availability groups and have the secondary used only for reporting purposes and not DR, do we still need to use the Windows clustering?
Thanks,
m

Take a look into replication or database snapshots if AG does not fit you,
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Can Oracle 10g EM manage DB2 or SQL Server

Need to know if Oracle 10g EM do have the capability to manage DB2 and SQL Server, as ct has this requirement. If so ct will manage all DB`s using Oracle 10g EM and use it for his enterprise.

Manage, no. Monitor, yes, so long as you don't mind a bit of work.
Now, for SQL Server, I expect you'll see the capability as a result of the Peoplesoft acquisition in a future release.
DB2, well that's a bit of work if you care that much about it. Grid R2 has a lovely SDK for developing your own plugins to monitor whatever the heck you like. It's alot easier to do in R2 than R1...

SQL AlwaysOn Availability Group modifies preferred owner node on move/failover

I have a two node Windows Server 2012 R2 failover cluster with two SQL Server 2012 Enterprise AlwaysOn Availability groups configured. Within the cluster I have configured a preference order on which node a AlwaysOn Availability Group should run.
Get-ClusterGroup -Name "AlwaysOn1" | Set-ClusterOwnerNode -Owners "node1","node2";
Get-ClusterGroup -Name "AlwaysOn2" | Set-ClusterOwnerNode -Owners "node2","node1";
After configuring the preference and retrieving the preference order it is configured as it should be. When I do a failover the preference order is adjusted to first the node it currently runs on and second the other node instead of leaving the preference
order as it was. It doesn't matter if I use the PowerShell "Move-ClusterGroup" or the "ALTER AVAILABILITY GROUP [AlwaysOn1] FAILOVER" T-SQL command. From the cluster log it is shown that the preference is modified after the resource
has been moved.
INFO [GUM] Node 2: executing request locally, gumId:15859, my action: /rcm/gum/SetGroupPreferredOwners, # of updates: 1
INFO [RCM] rcm::RcmGum::SetGroupPreferredOwners(AlwaysOn1,<vector len='2'>
The default groups within the cluster "Available Storage" and "Cluster Group" keep their preference setting when configured (only configured for testing to verify it has to do with the SQL Server Availability Group resource type).
The Windows Server 2012 R2 servers are updated using the latest Windows Updates and SQL 2012 has build number 11.0.5556.
For other cluster groups which I have configured in the past like file, Hyper-V (used for affinity to get VM's which have a lot of traffic between them within the same virtual switch to reduce latency and additional hops. it would be nice if vNext will have
a affinity option for cluster groups besides the anti-affinity within the current version)
I would like to know if someone could explain why the SQL Server Availability Group resource always modifies the group preference. I might understand this with a three node cluster where the first two are running in Synchronous commit mode and the third
one in Asynchronous commit mode.
Thanks in advance,
Dennis van den Akker

Hi Dennis van den Akker,
Do not use the Failover Cluster Manager to manipulate availability groups, for example:
Do not add or remove resources in the clustered service (resource group) for the availability group.
Do not change any availability group properties, such as the possible owners and preferred owners. These properties are set automatically by the availability group.
Do not use the Failover Cluster Manager to move availability groups to different nodes or to fail over availability groups. The Failover Cluster Manager is not aware of the synchronization status of the availability replicas, and doing so can lead to extended
downtime. You must use Transact-SQL or SQL Server Management Studio.
The related KB:
Failover Clustering and AlwaysOn Availability Groups (SQL Server)
https://msdn.microsoft.com/en-us/library/ff929171.aspx
The similar thread:
SQL Server Clustering 2008 (Multi Node)
https://social.msdn.microsoft.com/Forums/sqlserver/zh-CN/c35fe863-3fed-4a6e-830b-b79aa032c198/sql-server-clustering-2008-multi-node?forum=sqldisasterrecovery
Best Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to configure workflow manager 1.0 ? Scenario "sharepoint 2013 and sql server 2012 workflow manager in one server" .

i have sharepoint 2013 and sql server 2012 in one server . how to configure workflow manager 1.0 on the same server ?

Please follow below technet article :
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
Installing and Configuring Workflow Manager 1.0 (Step by Step)
Note: The steps in this article apply to SharePoint Server 2013.
The SharePoint 2013 Workflow platform is not supported in SharePoint Foundation 2013.
If my contribution helps you, please click Mark As Answer on that post and
Vote as Helpful
Thanks, ShankarSingh(MCP)

I am trying connect to a SQL instance for our CRM program and I am receiving To Connect to this Server you must use SQL Management Studio or SQL Server Management

I am trying connect to a SQL instance for our CRM program and I am receiving To Connect to this Server you must use SQL Management Studio or SQL Server Management
This is a Brand new Server 2012 that is running our CRM product and it is trying to connect to a Server 2008 R2 server with SQL Server 2008 R2 SP2 instance (10.50.4000)
I have seen this in the past where it needed the 2005 backwards compatibility components installed but those are not supported on 2012 server and this is not a 2005 SQL instance.
I am trying to install the Shared Management Objects for SQL Server 2008 but it tells me I need to install the CLR types, which I did install. But it continues to tell me to install the CLR types.
Has anyone ran into any issues like this? (this happens trying to connect to multiple SQL Servers from this new 2012 Server)
Thanks!
-Max

Hello,
Which version and edition of the SQL Server instance did you installed on the new server machine? If you install SQL Server 2012 Express edition, you can try to install SQL Server Management Studio 2012 from
this link.
You can connect to SQL Server 2008 R2 or earily verions with SSMS 2012.
What's more, Microsoft SQL Server 2008 Management Objects Collection requires Microsoft Core XML Services (MSXML) 6.0, Microsoft SQL Server Native Client, and Microsoft SQL Server System CLR Types. You can try to download and install
SQL Serve 2008 Feature Pack
which contains packages above.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Installation of SCCM 2012 R2 and SQL Server 2014 error

Hello All,
I am attempting to setup SQL Server 2014 and SCCM 2012 R2 but I keep running into an error stating that "Configuration Manager requires Microsoft SQL Server
2008 SP2 w/ CU9........ all the way up to Microsoft SQL Server 2012 with CU2 or higher." I am using all evaluation versions for this configuration as we are looking to test and evaluate the products. I was trying it with SQL 2014 because I was running
into the same error with SQL 2012 and according to "http://blogs.technet.com/b/configmgrteam/archive/2015/03/30/updated-sc2012-configmgr-sp1-and-sc2012r2-configmgr-support-sql-server-2014.aspx" SQL
2014 is supported with SCCM 2012 R2. SQL is installed locally on the same box.
Any suggestions would be appreciated.
Thanks,
Tucker
Update: When running the Pre-Req check these are some of the failed returns.....
SQL Server Edition: Failed: Configuration Manager primary site and central administration site don't support SQL Server Express Edition
Not sure why it is recognizing SQL Express as this is a new machine.
SQL Server service running account: Failed: The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE. You must configure
the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
For the SQL Service I am using a domain account created specifically for this.

This has nothing to do with moving or restoring. The kb article says "This hotfix provides updated versions of the setup files and enables new installations
of the System Center 2012 R2 Configuration Manager site database role and the System Center 2012 Configuration Manager SP1 site database role in Microsoft SQL Server 2014"
Torsten Meringer | http://www.mssccmfaq.de

SQL Server 2012 express istallation failing to install "Database Engine Service" and "SQL Server Replication"

I ran SQL Server 2012 express setup as user with administrator privileges and still it's failing to install "Database Engine Service" and "SQL Server Replication".
Any and every ideas on how to resolve this issue is greatly appreciated.

Three weeks passed and I am yet to find a fix for the the failed installation of the database engine on sql server 2012 express installation. I have tried various work-around including uninstalling, deleting all the directory paths, and reinstallation. Still
not able to successfully install sql server 2012 express.
I will greatly appreciate any and every contribution towards resolving this issue. Thanks in advance.
Here is the content of log file after the latest failed installation:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2061893607
Start time:                    2013-12-23 14:42:45
End time:                      2013-12-23 15:07:51
Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name:                  mymachine1
Machine processor count:       4
OS version:                    Windows 7
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x86
Process architecture:          32 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2012      SQLEXPRESS_GT        MSSQL11.SQLEXPRESS_GT          Database Engine Services
1033                 Express Edition      11.0.2100.60    No
SQL Server 2012      SQLEXPRESS_GT        MSSQL11.SQLEXPRESS_GT          SQL Server Replication
1033                 Express Edition      11.0.2100.60    No
SQL Server 2012
Management Tools - Basic                 1033                 Express Edition
11.0.2100.60    No
Package properties:
Description:                   Microsoft SQL Server 2012 Service Pack 1
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
Installation location:         C:\9b6607e524727c7fe1defd80\x86\setup\
Installation edition:          Express
Slipstream:                    True
SP Level                       1
Product Update Status:
Success: KB 2674319
Product Updates Selected for Installation:
Title:                         Service Pack 1
Knowledge Based Article:       KB 2674319
Version:                       11.1.3000.0
Architecture:                  x86
Language:                      1033
Update Source:                 MU
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      true
AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Disabled
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 <empty>
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CLTCTLRNAME:                   <empty>
CLTRESULTDIR:                  <empty>
CLTSTARTUPTYPE:                0
CLTSVCACCOUNT:                 <empty>
CLTSVCPASSWORD:                <empty>
CLTWORKINGDIR:                 <empty>
COMMFABRICENCRYPTION:          0
COMMFABRICNETWORKLEVEL:        0
COMMFABRICPORT:                0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE:               0
CTLRSVCACCOUNT:                <empty>
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     <empty>
ENABLERANU:                    true
ENU:                           true
ERRORREPORTING:                false
FEATURES:                      SQLENGINE, REPLICATION, CONN, BC, SDK, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 <empty>
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS:              false
INSTALLSHAREDDIR:              c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           <empty>
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SQLEXPRESS
INSTANCENAME:                  SQLEXPRESS
ISSVCACCOUNT:                  NT AUTHORITY\Network Service
ISSVCPASSWORD:                 <empty>
ISSVCSTARTUPTYPE:              Automatic
MATRIXCMBRICKCOMMPORT:         0
MATRIXCMSERVERNAME:            <empty>
MATRIXNAME:                    <empty>
NPENABLED:                     0
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
ROLE:                          <empty>
RSINSTALLMODE:                 DefaultNativeMode
RSSHPINSTALLMODE:              DefaultSharePointMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD:                <empty>
SQLSVCSTARTUPTYPE:             Manual
SQLSYSADMINACCOUNTS:           MH\gt038676t
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  false
TCPENABLED:                    0
UIMODE:                        AutoAdvance
UpdateEnabled:                 true
UpdateSource:                  MU
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131223_144132\ConfigurationFile.ini
Detailed results:
Feature:                       Management Tools - Complete
Status:                        Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
Feature:                       Client Tools SDK
Status:                        Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
Feature:                       Management Tools - Basic
Status:                        Passed
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred during the setup process of the feature.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x851A0019
Error description:             Could not find the Database Engine startup handle.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x851A0019
Error description:             Could not find the Database Engine startup handle.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025
Feature:                       SQL Browser
Status:                        Passed
Feature:                       SQL Writer
Status:                        Passed
Feature:                       SQL Client Connectivity
Status:                        Passed
Feature:                       SQL Client Connectivity SDK
Status:                        Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131223_144132\SystemConfigurationCheck_Report.htm

SMS_SRS_REPORTING_POINT - Error retrieving folders with SCCM 2012 and SQL Server 2008 R2 SP2

Hi:
According to all the Reporting Services logs my Reporting Point was setup correctly. When I try and run any report I see the entries below in the srsrp.log on the SQL Server. The report names show up in the Console but when I right any of the
listed reports I get errors and no report runs.
I am running SQL Server 2008 R2 SP2 on a remote server. SQL is installed on its own server. There is no firewall between the Configuration Manager server and SQL Server.
Thanks.
Mark
(!) Error retrieving folders - [A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance
name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because
connected host has failed to respond.)].   SMS_SRS_REPORTING_POINT
1/25/2013 9:15:07 AM    4532 (0x11B4)
No folder configuration information found.
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Next security configuration at [1/25/2013 9:22:42 AM]
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Root Folder exists
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Successfully checked that the SRS web service is healthy on server DBSCCM.LOCAL
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
SRSRP registry key change notification triggered.
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:16 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:16 AM
4532 (0x11B4)
Timed Out...
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Reporting Services URL from Registry [http://dbsccm/ReportServer/ReportService2005.asmx]
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Reporting Services is running
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ManagedDesktops_MD1
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
(!) Error retrieving folders - [A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance
name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because
connected host has failed to respond.)].   SMS_SRS_REPORTING_POINT
1/25/2013 9:17:40 AM    4532 (0x11B4)
No folder configuration information found.
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Next security configuration at [1/25/2013 9:22:42 AM]
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Root Folder exists
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Successfully checked that the SRS web service is healthy on server DBSCCM.LOCAL
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Timed Out...
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Reporting Services URL from Registry [http://dbsccm/ReportServer/ReportService2005.asmx]
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Reporting Services is running
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ManagedDesktops_MD1
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)

Hi:
Windows Firewall is off on both systems.
I can ping the Configuration Manager server from the SQL Server by netbios name, ip address and fully qualified domain name.   I can ping the SQL Server from the Configuration Manager server by netbios name, ip address and fully qualified domain
name.
I have uninstalled and installed the Reporting Point Service a couple of times and everything looks fine according to the logs after the install finishes but these errors only appear each time I try and Run a report.
Mark

SCOM 2012 R2 Management Servers and SQL Server Availability Groups

Similar Messages

Maybe you are looking for