SCOM 2012 Installation fails while deploying Datawarehouse

Hi All,
I have a strange issue, My SCOM 2012 installation fails during Datawarehouse deployment. (This setup is not SCOM 2012 SP1 OR 2012 R2 it is just SCOM 2012)
When i check the SCOM installation logs it says it tried to connect to my Management server and it could not open Port 5724.
During the installation i checked that the SDK Service was stopping frequently and also a Visual studio debugger popup also occured. Can any one assist in solving the issue ?
Screenshots:
Error logs
Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.GetExistingManagementServerFromOMDB(String omSQLServer, Nullable`1 omSqlPort, String omDatabaseName, String& firstWorkingManagementServer)
[01:08:57]: Error:
:Inner Exception.Type: System.ServiceModel.EndpointNotFoundException, Exception Error Code: 0x80131500, Exception.Message: Could not connect to net.tcp://My management server:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:03.0079280.
TCP error code 10061: No connection could be made because the target machine actively refused it 172.17.221.45:5724.
[01:08:57]: Error:
:InnerException.StackTrace:
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
[01:08:57]: Error:
:Inner Exception.Type: System.Net.Sockets.SocketException, Exception Error Code: 0x80131500, Exception.Message: No connection could be made because the target machine actively refused it 172.17.221.45:5724
[01:08:57]: Error:
:InnerException.StackTrace: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
[01:08:57]: Always:
:Management Server My management server failed to connect, now trying another one.
[01:08:57]: Warn:
:Failed to connect to any SDK in the management group, trying again
[01:09:17]: Info:
:Info:trying to connect with server My management server
[01:09:26]: Info:
:Info:Error while connecting to management server: The Data Access service is either not running or not yet initialized. Check the event log for more information.
[01:09:26]: Error:
:Couldn't connect to mgt server stack: : Threw Exception.Type: Microsoft.EnterpriseManagement.Common.ServiceNotRunningException, Exception Error Code: 0x80131500, Exception.Message: The Data Access service is either not running or not yet initialized.
Check the event log for more information.
[01:09:26]: Error:
:StackTrace: at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, ManagementGroupInternal internals)
at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.GetExistingManagementServerFromOMDB(String omSQLServer, Nullable`1 omSqlPort, String omDatabaseName, String& firstWorkingManagementServer)
[01:09:26]: Error:
:Inner Exception.Type: System.ServiceModel.EndpointNotFoundException, Exception Error Code: 0x80131500, Exception.Message: Could not connect to net.tcp://My management server:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:03.0040216.
TCP error code 10061: No connection could be made because the target machine actively refused it 172.17.221.45:5724.
[01:09:26]: Error:
:InnerException.StackTrace:
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
[01:09:26]: Error:
:Inner Exception.Type: System.Net.Sockets.SocketException, Exception Error Code: 0x80131500, Exception.Message: No connection could be made because the target machine actively refused it 172.17.221.45:5724
[01:09:26]: Error:
:InnerException.StackTrace: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
[01:09:26]: Always:
:Management Server My management server failed to connect, now trying another one.
[01:09:26]: Warn:
:Failed to connect to any SDK in the management group, trying again
[01:09:46]: Error:
:Error:Could not connect to management group. Can not continue with DW upgrade...
[01:09:46]: Info:
:Info:got MG connection
[01:09:46]: Error:
:Error:Could not connect to management group. Cannot continue with current action...
[01:09:46]: Error:
:FATAL ACTION: GetManagementGroup
[01:09:46]: Error:
:FATAL ACTION: DWInstallActionsPostProcessor
[01:09:46]: Error:
:ProcessInstalls: Running the PostProcessDelegate returned false.
[01:09:46]: Always:
:SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse Configuration
[01:09:46]: Error:
:ProcessInstalls: Running the PostProcessDelegate for OMDATAWAREHOUSE failed.... This is a fatal item. Setting rollback.
[01:09:46]: Info:
:SetProgressScreen: FinishMinorStep.
[01:09:46]: Always:
:!***** Installing: OMCONSOLE ***
[01:09:46]: Info:
:ProcessInstalls: Rollback is set and we are not doing an uninstall so we will stop processing installs
[01:09:46]: Always:
[01:09:46]: Always:
:****Starting*RollBack*******************************************
[01:09:46]: Always:
[01:09:46]: Info:
:SetProgressScreen: StartMinorStep.
[01:09:46]: Info:
:SetProgressScreen: StartMinorStep.
[01:09:46]: Debug:
:ProcessInstalls: Install Item Data Warehouse Configuration has a Preprocessing delegate of RunXamlPreProcessor. Launching it now.
[01:09:46]: Always:
:Determining actions to be run.
[01:09:46]: Always:
:Done validating action list; now running individual actions.
[01:09:46]: Always:
:Current Action: UninstallPrePreprocessor
[01:09:46]: Info:
:UninstallPrePreprocessor completed.
[01:09:46]: Always:
:Current Action: UpgradePreprocessor
[01:09:46]: Info:
:UpgradePreprocessor completed.
[01:09:46]: Always:
:LaunchExeSetup: Launching E:\SCOM setups\SCOM 2012\Setup\AMD64\SetupInstallItem.exe with arguments:
[01:09:46]: Info:
:SetProgressScreen: Init Exe Install progress.
[01:09:47]: Always:
:LaunchExeSetup: Install return value was: 0
[01:09:47]: Info:
:CheckPointPassed is removing the Rollback property as this is an uninstall.
[01:09:47]: Always:
:SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse
Gautam.75801

Hi All,
So i got the actual commands to register the SPN. So the above were wrong. Hope the below is useful for some one if the face the above issue.
In Windows Server 2008R2 – the command is SETSPN –A. In WS2012, it changed to SETPSPN –S which checks for duplicates before it allows you to create them.
Legend: SCOM Server - SCOMSVR.Contoso.com
DNS Domain: Contoso.com
SDK Account: SDKSVC
To add SPN for the SDK Service:
===================================
In Win2k 12
setspn -S MSOMSdkSvc/SCOM Server FQDN Domain\SDK Account name
setspn -S MSOMSdkSvc/SCOM Server name without FQDN Domain\SDK Account name
Ex: setspn -S MSOMSdkSvc/SCOMSVR.Contoso.com Contoso\SDKSVC
setspn -S MSOMSdkSvc/SCOMSVR Contoso\SDKSVC
In Win2k8
setspn -A MSOMSdkSvc/SCOM Server FQDN Domain\SDK Account name
setspn -A MSOMSdkSvc/SCOM Server name without FQDN Domain\SDK Account name
Ex: setspn -A MSOMSdkSvc/SCOMSVR.Contoso.com Contoso\SDKSVC
setspn -A MSOMSdkSvc/SCOMSVR Contoso\SDKSVC
To verify the SPN's
============================
1. setspn -L MS Host name without FQDN
Ex: setspn -L SCOMSVR
2. setspn -L Domain\DSK Action account
Ex: setspn -L Contoso\SDKSVC
Post entering the above commands you should see the entries of the Healthservice and not the entries of the SDK Service.
1. If you are are using a Domain account for SDK / DAS then that entry should not appear when execute the command “setspn -L SCOMSVR”. Where SCOMSVR is the name of the MS and it should be without FQDN.
Example: The below entry should not appear when you enter setspn -L SCOMSVR
MSOMSdkSvc/SCOMSVR
MSOMSdkSvc/SCOMSVR.contoso.com
If you get the above entries for "setspn -L SCOMSVR" then you need to delete and re add the SPN again and re check.
If you get Duplicate entries the below post entering "setspn -L Contoso\SDKSVC" then you need to delete the duplicate entries and re add the SPN again and re check.
Ex: MSOMSdkSvc/SCOMSVR
MSOMSdkSvc/SCOMSVR.contoso.com
MSOMSdkSvc/SCOMSVR.contoso.com
MSOMSdkSvc/SCOMSVR
To delete a SPN if required:
===============================
setspn -D MSOMSdkSvc/SCOM MS FQDN Hostname without FQDN Hostname
setspn -D MSOMSdkSvc/Hostname without FQDN Hostname without FQDN again
Ex: setspn -D MSOMSdkSvc/SCOMSVR.Contoso.com SCOMSVR
setspn -D MSOMSdkSvc/SCOMSVR SCOMSVR
Reference used : http://blogs.technet.com/b/kevinholman/archive/2011/08/08/opsmgr-2012-what-should-the-spn-s-look-like.aspx
Gautam.75801

Similar Messages

SCOM 2012 Installation problem - SQL Instance name

Hi All
Strange problem here, I wonder if anyone else has had the same issue.
I have a two-node SQL Server 2014 (Enterprise) Database server configured with a "SQL AlwaysOn Availability Group & Listener". The listener DNS name is: sql-ag-listener
On a separate server VM I attempted to install SCOM 2012 R2 - but when it came to the setup prompt to enter the "Servername & Instance" for the SQL server / Databases it will not accept my SQL AG Listener DNS name. However if I enter any
of the two individual SQL node names (SQL1 or SQL2) then it does accept those values and proceeds with the setup wizard. I do have a DNS entry for the SQL AG name.
All VMs are hosted in Azure. The SQL Servers are in their own Cloud Service and the SCOM MS Servers are in their own Cloud service.
I tried moving one of the SCOM MS Servers to the same Cloud Service container as the SQL Servers - still the same result.
Interestingly (as a test) - I started the SCOM 2012 Installation wizard on one of the SQL Servers and it DID accept the SQL AG value as the "Servername & Instance".
No firewalls are on. The VM endpoints allow SQL port 1433. Also, I can Telnet to the SQL Servers using 'telnet > O sql-ag-listener 1433' - response = Connected....
Not sure why this wont accept my virtual SQL AG name....?
thanks

Hi,
As when you install SCOM on one of your SQL server, then the AG name can be resolved, so it seems like this issue related with network resolution.
On the server where you want to run SCON setup, please use NSLOOKUP command to make sure it can the AG name to an IP address.
In addition, when you run the setup, don't select reporting server, as reporting server role need to install on a SQL server holding SSRS.
We still can install SCOM on normal database, and then add them into availability group later:
Add SCOM Databases to Availability Groups
http://www.tech-coffee.net/alwayson-part-8-methods-to-add-database-scom/
Regards,
Yan Li
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 Subscriber Support, contact [email protected]

The unattended installation failed while installing SQL Server 2008 R2 ????

Hi gurus,
I got an error while installing SQL Server 2008 R2 in Windows 2008 R2 standard 64 bit operating system.
LOG file*
Customized installation of SQL Server 2008R2 for SAP *
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlWriter_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SystemConfigurationCheck_Report.htm
1/16/2012 10:13:34 PM
Message Box "Installation failed"
The unattended installation failed.
Installation Step: The unattended installation failed.
Return Code:       -2068052377
Log File:          C:\Windows\SQL4SAP.log
Check the log file above.
See SAP note 1144459 for known issues.
Result: vbOK
Registry settings (2/2):
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{2b9034f3-b661-4d36-a5ef-60ab5a711ace}
WRITE(REG_DWORD): 4
1/16/2012 10:37:32 PM
Quit script with return code 1
Please help me out with this issue.
REGARDS,
Raj

Hello Raj,
MS SQL DB installation specific steps for SAP system is clearly documented in SAP Installation guide. Please download from SMP, read it carefully and install as mentioned in the guide.
Hope it helps.
Thanks,
Siva Kumar

SCOM 2012 Gateway fails to communicate - Certificate Problem?

Hello SCOM Guru's
I wonder if someone out there may be able to help.
I have two (non-trusted) domains - both hosted in
Azure. See graphic below (a picture paints a thousand words!)
Just to put some context around the diagram - I have a two domains, the left-hand side contains the SCOM MS and the right-hand side is a non-trusted domain hosting the SCOM GW. The idea is that I want computers (agents) from the right-hand side domain to
be able to talk back to the SCOM MS vai the SCOM GW.
In a nutshell I have followed some great 'how to' guides - for instance:
http://blogs.technet.com/b/pfesweplat/archive/2012/10/15/step-by-step-walkthrough-installing-an-operations-manager-2012-gateway.aspx
After hours of messing around I still cannot get my Gateway Server to talk successfully back to the SCOM Management Server in the other domain. I have deployed my own Certificate Authority and followed documentation to put the relevant Certs on both
servers. I have checked all Certs and they report 'The certificate is OK'.
Also I can confirm that the MOMCertImport tool was run on both the SCOM MS and SCOM GW server (I did the MS 1st and GW 2nd) - both returned a 'Success' cmd prompt. I have also rebooted both servers - to restart all relevant SCOM Services.
On the Azure VMs I have allowed TCP 5723 on both servers. Additionally, the SCOM MS can resolve the SCOM GW server in the other domain via a HOSTS file entry (and vice-versa). I have tested connectivity using
telnet <FQDN> 5723 (both ends seem to connect). No internal Windows Firewalls are enabled on any servers.
The cluster of errors reported by the
SCOM Gateway server are (first to last):
20057: Failed to initialize security context for target MSOMHSvc/SCOM-01.DOMAIN.local The error returned is 0x80090303(The specified target is unknown or unreachable). This error can apply to either the Kerberos or the SChannel package.
21001: The OpsMgr Connector could not connect to MSOMHSvc/SCOM-01.DOMAIN.local because mutual authentication failed. Verify the SPN is properly registered on the server and that, if the server is in a separate domain, there is a full-trust
relationship between the two domains
20071: The OpsMgr Connector connected to SCOM-01.DOMAIN.local, but the connection was closed immediately without authentication taking place. The most likely cause of this error is a failure to authenticate either this agent or the
server . Check the event log on the server and on the agent for events which indicate a failure to authenticate.
The same events repeat every 15 mins in the Operations Manager event log - and thus the SCOM Gateway remains 'Not Monitored'.
I don't get any relevant Events logged from the SCOM MS side - I guess cos it's not even got that far / authenticated?
I'm sure this is a Certificate type of problem but I'm really not sure where I go from here - any suggestions?
Many thanks
Darren

Hi,
Check this post:
Solving the Gateway 20071 event
http://michelkamp.wordpress.com/2012/01/05/solving-the-gateway-20071-event/
and this: Event ID 21001 and 20057 on SCOM agents - duplicate SPN:
http://blogs.technet.com/b/kevinholman/archive/2011/08/08/opsmgr-2012-what-should-the-spn-s-look-like.aspx
Similar answer has been provided by DKTOA Here:
https://social.technet.microsoft.com/forums/systemcenter/en-US/05019b70-73a3-4a37-993b-66b607f3c222/scom-2012-gateway-server-isses-20057-21001-20071-ids
Did it solve your problem?
Regards
Jure
Jure Labrovic | Blog

SCOM agent installation fail ?

Hi
when I try to push the installation of SCOM 2012 R2 agent through Console on windows server 2008 it always fails with this error:
The Operations Manager Server could not execute WMI Query "Select * from Win32_OperatingSystem" on computer TKTMG01.intranet.local
Operation: Agent Install
Install account: intranet\troll_gw
Error Code: 800706BA
Error Description: The RPC server is unavailable.
Any help would be highly appreciated.
Regards,
Basem

Hi,
As Ed already posted, check the firewall on the server where the agent installation fails. If you´ve turned off the firewall and It´s still failing to install, you need to talk to your network team about this isue since there might as well be a firewall
between the servers blocking the traffic.
A general recommendation in a heavily firewalled environment is to install the agents manually to make as few firewall openings as possible. Check this link for more information on what ports need tobe open in order for the installation to go through: http://blogs.technet.com/b/kevinholman/archive/2007/12/12/agent-discovery-and-push-troubleshooting-in-opsmgr-2007.aspx
Regards,
Daniel
IT Consultant at Viridis IT

SCOM 2012 Reporting Fails During Install

I am having issues installing the Reporting Module for SCOM 2012. Here is my environment:
Stand-alone SQL server with SQL 2012 (Default Instance and only is used for SCOM)
Reporting Services Installed and I am able to browse to the URL
Reader Account has access to both servers and both Report/OPM databases.
Stand-alone Management Server
Everything is running fine.
When I go to install Reporting on the SQL Server it fails during the Configuring Security phase and here are the logs:
Error:All retrys failed!!. Message:SetSRSSecurity Exception, now throwing:Cannot stop ReportServer service on computer '.'.
Error: :SetSRSSecurity failed: Threw Exception.Type: System.InvalidOperationException, Exception Error Code: 0x80131509, Exception.Message: Cannot stop ReportServer service on computer '.'.

I also see this error:
[12:50:50]: Error:
:StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingConfigurationHelper.ReportingConfiguration.ModifySRSServiceAccount(String userName, String userPassword, String sqlSRSServer, String srsServiceName, String sqlServerForSRSDatabase,
String srsDBName)
[12:50:50]: Warn:
:Message:SetSRSSecurity Exception Exception: The specified @job_name ('F5DDC431-93E3-41CF-8913-00EDFD457F99') does not exist.
The specified @job_name ('3AA30844-4417-479D-80EF-059C9CAAF84D') does not exist.
The specified @job_name ('A65C33A6-DC11-44AA-B8AD-077A7D94213D') does not exist.
The specified @job_name ('C9192EB7-87D8-475D-9826-100AF193F33F') does not exist.
The specified @job_name ('410DA81B-318F-4BD8-AA5B-14AC61AC82C3') does not exist.
The specified @job_name ('E26B57B7-72CE-449F-AA19-19B192CD10C0') does not exist.
The specified @job_name ('FF9BC31C-E6F9-4987-ABBC-1C20D41E0A7D') does not exist.
The specified @job_name ('BBE14DB5-E183-4F05-AC45-1CD147DD72BE') does not exist.
The specified @job_name ('D69172E5-4FD6-4FF2-9F98-1FA57C98B6B5') does not exist.
The specified @job_name ('566D3953-B305-43EC-9C08-2FA53CABA2FE') does not exist.
The specified @job_name ('B3D9B9B3-9C8A-4109-884B-36899D560A9B') does not exist.
The specified @job_name ('B47669F4-54A5-4F78-AEF4-40A9F40D9BC6') does not exist.
The specified @job_name ('97FA149B-5275-4A4D-A3C8-4E69B20C0D92') does not exist.
The specified @job_name ('86AEBFB5-CAA3-4D2A-859F-4E751B660257') does not exist.
The specified @job_name ('FE970B3F-D021-46A2-8387-4E989590A86D') does not exist.
The specified @job_name ('D6C2E45D-E677-4F2B-81AA-5103FB8E1B92') does not exist.
The specified @job_name ('7412F626-CAD9-48BE-8211-5145A3F51085') does not exist.
The specified @job_name ('17838236-691B-49D7-AD7C-553B1886AB58') does not exist.
The specified @job_name ('5445E14F-A22C-4014-9EB8-55C8BAF5A061') does not exist.
The specified @job_name ('C914C932-C350-404D-9CF4-575D108DDA82') does not exist.
The specified @job_name ('CB87B0AD-069A-4F07-BB62-580FBEF5C31B') does not exist.
The specified @job_name ('BC838396-DFE1-4BC5-8D24-58B194A7214E') does not exist.
The specified @job_name ('D58C71E8-A821-4A73-A0A7-5F5080BC6730') does not exist.
The specified @job_name ('49F42A35-15DA-4C9E-A95B-66F4040E139F') does not exist.
The specified @job_name ('F4F9400D-1212-4DD6-AAFF-671192BF2B25') does not exist.
The specified @job_name ('F0EFEFAA-F2D5-494E-B97E-6D075AC17F2F') does not exist.
The specified @job_name ('0721E6DF-0209-4874-B473-70E5026E8FF2') does not exist.
The specified @job_name ('B2AECE06-0F8F-4C5D-A04E-8148D8F6C255') does not exist.
The specified @job_name ('A9813C14-FB76-4461-80B9-8350CBE9E5BB') does not exist.
The specified @job_name ('71ABB496-3F2E-4D8D-8551-8650DBC45721') does not exist.
The specified @job_name ('EF1AAD40-47DA-41A2-A9F6-87A6AE140BB3') does not exist.
The specified @job_name ('B887666E-E580-427C-ADBA-8B605561E8E9') does not exist.
The specified @job_name ('A19772C9-CA88-455C-9CA7-8E11F960BB84') does not exist.
The specified @job_name ('CAFFEA4E-AE64-4B5F-9129-913272C5251D') does not exist.
The specified @job_name ('826AF562-C9D2-461B-AEEB-91B64FF3003A') does not exist.
The specified @job_name ('09458F97-C2ED-46B5-BB8E-91C4C54C22B4') does not exist.
The specified @job_name ('021AA26B-62EA-4C38-8ACF-975CE6B33FAD') does not exist.
The specified @job_name ('33EA5BB5-35A7-442F-8635-9FE560EDABBE') does not exist.
The specified @job_name ('E7405185-56A5-4C46-87AB-A1FA9FA4271B') does not exist.
The specified @job_name ('CEDDD21A-2E75-4BA6-BA99-A4E5B79073BC') does not exist.
The specified @job_name ('8A6E115B-616F-46D6-9A94-A7C22C94D11C') does not exist.
The specified @job_name ('30A0182B-0A70-4D33-A62F-AB277ABC4D63') does not exist.
The specified @job_name ('5B252CA0-FCFF-49FA-8B40-AD6667B345A1') does not exist.
The specified @job_name ('D0007E85-046E-4264-933A-AF662B8FECF7') does not exist.
The specified @job_name ('D1835177-4454-44C0-8134-B080AFD99B52') does not exist.
The specified @job_name ('B02F7A14-A658-420D-A2B0-B18577080FDD') does not exist.
The specified @job_name ('7CD641D9-C2C3-4907-88F9-BAED4FA93AAF') does not exist.
The specified @job_name ('23241CD1-4317-42EA-887E-C3F7441645D7') does not exist.
The specified @job_name ('9AB583BC-94AA-49BB-B4E4-CACE094A2764') does not exist.
The specified @job_name ('31EAC604-0DF5-4A9C-B510-CD6BEF72B608') does not exist.
The specified @job_name ('8412C87D-CC61-4FA0-9804-CFC8528DB66E') does not exist.
The specified @job_name ('314FBBDC-013B-4742-B65B-D122968AF014') does not exist.
The specified @job_name ('002B780F-351F-4345-9D97-D3DD370E2317') does not exist.
The specified @job_name ('F21C6C3D-5219-4917-BF29-D5AA1B315565') does not exist.
The specified @job_name ('34FCE497-498B-47EE-9A8B-D8EC2CFEC3AA') does not exist.
The specified @job_name ('1B356BC7-8300-4A6A-8E66-E036C1053C47') does not exist.
The specified @job_name ('6C94A462-3025-46AC-BD67-E7575ABBA4D9') does not exist.
The specified @job_name ('A79F3134-A3BC-470F-8D6C-F457C6114EBA') does not exist.

SCOM 2012 SP1 failed to send notifications by IM Channel

Hello, I have a problem with my SCOM 2012 SP1. When it tries to send notification by IM Channel I get the following alert in SCOM:
Notification subsystem failed to send notification using
device/server 'live.august.ru:5060' over 'sip' protocol to
'sip:[email protected]'.
Microsoft.Rtc.Signaling.OperationFailureException: The GetInbandDataAsyncResult
operation has failed with message: "The data session subscription to server
failed.". See the InnerException and FailureReason properties as well as the
logs for additional information. . Rule id:
Subscription077dc311_59c0_4ba5_a432_072b486cd287
At the same time the following event in the Application Event Log generates on the server with IM service:
Event Type: Warning
Event Source: Live Communications Server Authentication
Event Category: (1003)
Event ID: 16435
User: N/A
Computer: LCS
Description:
At least one invalid authentication signature was detected.
There were 2 messages with invalid signatures in the last 7112 minutes. The last one had the FROM header: sip:[email protected]
Cause: This could be due to a client or server which is not handling authentication correctly, or it could be due to an attacker.
Resolution:
None needed unless the failure count is high (>100). Check your network for any rogue clients. Restart the server if problem persists.
Notifications sent by the SMTP channel work fine!
I Have the following Servers:
LCS (live.august.ru) - Win 2003 EE SP2 + Live Communication Server 2005 SP1
SCOM - Win 2012 + SCOM 2012 SP1
Also I have a third server (Win 2003 + SCOM 2007 R2) and it sends notifications to the same VMLCS server successfully. The configurations of IM Channels are identical on both servers:
IM server: live.august.ru
Return address: sip:[email protected]
Protocol option: TCP
Authentication method: Kerberos
IM port: 5060
I tried to change the Authentication method to NTLM, and the port to 5061, but it doesn't help...

Hi,
Please refer to these following articles to configure IM channel correctly:
How to Create and Configure the Notification Action Account
http://technet.microsoft.com/en-us/library/hh212835.aspx
How to Enable an Instant Message Notification Channel
http://technet.microsoft.com/en-us/library/hh212690.aspx
Enabling Instant Messaging Notifications in System Center 2012 Operations Manager
http://opsmgrunleashed.wordpress.com/2012/02/24/enabling-instant-messaging-notifications-in-system-center-2012-operations-manager/
Alex Zhao
TechNet Community Support

SCOM 2012 Installation does not show the SQL Server Instance for reporting services

I have an issue when I try to install SCOM 2012 with the Reporting Server feature, so in the step that I have to select a SQL Server Instance I cannot do that, because as you can see in the picture no one option appears.
In my scenario I have a DCSERVER, SQLSERVER2008 R2, SCCMSERVER 2012 and in other server I are trying to install SCOM 2012. I are trying to use the same SQLSERVER to SCOM 2012.
Should I do other procedure on SQL Server before to continue? I will apreciate someone could say me what I need to do to resolve this issue.
Regards,
Paul Mendoza.

Hi Paul
Can you confirm that SQL Reporting Services is installed on the server that you are doing the install.
For a lab environment where you have SCOM Management Server, Web Server on one server and SQL Server on another you need to:
- run setup on the SCOM Server and choose NOT to install reporting. The install here will create the OperationsManager database and OperationsManagerDW (reporting) database.
- run setup on the SQL Server where SQL Reporting Services is installed. Then choose to install reporting. You should then see the SQL Reporting Services instance on the above window which is blank in your screenshot.
Take note of the warning in that window - SCOM uses its own role based security within SQL Reporting Services and this can break other reporting. E.g. you can't install SCOM and SCSM reporting (SQL RS component) together.
Cheers
Graham
New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Exchange Server 2013: Installation failed while installing Mailbox role.

Hi,
Mailbox role installation failed. I tried to remove and reinstall so many times but it still fails. (but the uninstall is complete)
Below is log from the lastest installation. Could you please help to veify the problem.
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
$sysMbx = $mbxs[0];
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox.".
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog
-Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
$sysMbx = $mbxs[0];
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox. Property Name: Database".

Hi,
See if deleting the account SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} in ADUC (you should find it in the Users Container) and then rerun
setup.exe /preparead helps you solve your problem.
Martina Miskovic

SPS 18 Installation fails while asking for Java Crypthography Extension

Hi @ all,
some weeks ago we deployed the file "tc_sec_java_crypto_signed_fs_lib.sda by the SDM. But we didn´t enabled strong encryption in the portal.
Now, i want to update my portalstack from SPS 14 to SPS 18 and while i update J2EE Sapinstaller asks for Java Crypthography Extension-Source-Code. But i don´t want to install it, because automatically the database is set to strong encryption and i can´t use / administrate in anymore.
I still undeployed the IAEK-FS-File but the problem persists.
I´m very pleasent for every answer.
Best Regards
Lars

Hey,
that´s fine Sascha.
It works greatly. SPS 18 not asking für JCE anymore.
The Installation is now running.
Thx a lot!
Greetingz
Lars

Webcenter Sites Installation fail during deployment

Hi
I have been trying to do a proof of concerpt with Webcenter Site on Weblogic 10.3.6 on windows 7, it installs fine but failes with the following error during deployment
An error occurred during activation of changes, please see the log for details.
User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.:org.apache.commons.logging.LogConfigurationException:User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.
has anyone encountered this and how have they resolved this???
Thanks in advance
Thabo

I have managed to fix this problem, by adding the following in the weblogic.xml
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>

11.2.0.3 grid installation fails while selecting OCFS2 for ocr files

We are installing 11GR2 (11.2.0.3) cluster on a 64 bit system. we have OCFS2 filesystem for shared devices. version 1.6.3.
While selecting ocr file locations , we get the following error
[INS-41321] Invalid oracle cluster register [OCR] Location
Cause- The installer detects that the storage type of location is not supported for Oracle Cluster registery
Action - Provide a supported storage location for the Oracle Cluster Registry
Additional information
/crp2db01/OCR/ocr_1 is not shared
However , this mountpoint is shared across both the nodes.
Note: 11201 grid installation was successful and it accepted the above locations for OCR. however ,we need 11.2.0.3 cluster for 11.2.0.3 database

As for your current problem, just because Oracle "allows" OCFS2 in a GRID environment, I would never suggest nor implement that. It adds a layer of complexity that is totally unnecessary when a GRID/ASM implementation performs circles around OCFS2. ASM is much easier to manage, maintain, expand and shrink than OCFS2. Especially at version 11.2.0.3. When working at a large telco a few years ago, we had a 300TB+ ASM environment. OCFS2 could not even begin to be that big. ASM will provide you a MUCH more stable environment than OCFS2. And with ASM there is a lot of "magic" that happens with OCR/Voting that makes your life MUCH easier. If you "require" shared application files, then use ASM/ACFS. It is a much better "volume manager" than OCFS2.
Since you must present devices to the system for OCFS2, you should not have any problems doing the same for ASM. (and don't use ASMLib as it is going away and is not necessary - just make sure you use a partition that skips the first 1M (usually cylinder 1) and you should be good to go!)
I also would not use a "shared ORACLE_HOME" on either ACFS or OCFS2. The biggest reason is that you lose the ability to do a "rolling" upgrade and when you have a VLC, that becomes much more important that saving a few GB worth of storage.
I would also pay attention to this:
http://docs.oracle.com/cd/E11882_01/install.112/e22489/storage.htm#CDEDAHGB
3.1.4.2 General Storage Considerations for Oracle RAC
Use the following guidelines when choosing the storage options to use for each file type:
You can choose any combination of the supported storage options for each file type provided that you satisfy all requirements listed for the chosen storage options.
If you plan to install an Oracle RAC home on a shared OCFS2 location, then you must upgrade OCFS2 to at least version 1.4.1, which supports shared writable mmaps.
Oracle recommends that you choose Oracle ASM as the storage option for database and recovery files.
For Standard Edition Oracle RAC installations, Oracle ASM is the only supported storage option for database or recovery files.

SQL Server 2008 R2 Express with SP2: 'SQLEXPRESS'-instance installation fails while any other instance name installation succeeds.

We supply our software package that also includes the unattended installation (with /QS and so on) of SQL Server R2 Express (with SP2).
The setup works good in about 99.9% cases, but one customer complained that after the "successful SQL Sever installation (at least, it looked so!) he could not open the supplied database getting some strange error messages...
After some months of trial-n-error attempts we are now able to reproduce the problems this custumer had. But we cannot find the reason of the problem.
So the test computer is a virtual machine with Windows 7 + sp1 32-bit.
Among the programs/tools installed on this machine there were (in the following order):
SQL Server 2008 Express - the default SQLEXPRESS instance
SSMS
VS 2010 Pro (German)
SQL Server 2008 Express R2 (with SP 1 or SP2 - ?) - the default SQLEXPRESS instance
Then some of them were uninstalled in the following order:
SQL Server 2008 Express
SSMS
SQL Server 2008 Express R2
Now we tried to install (in normal mode with UI) the SQL Server 2008 Express R2 with SP2.
When we chose the default SQLEXPRESS instance - it failed with the following info:
Configuration status: Failed: see details below
Configuration error code: 0x7FCCE689
Configuration error description: External component has thrown an exception.
and the Detail.txt file contained the following:
2015-01-20 10:44:09 Slp: External component has thrown an exception.
2015-01-20 10:44:09 Slp: The configuration failure category of current exception is ConfigurationValidationFailure
2015-01-20 10:44:09 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing Validation and scenario Validation.
2015-01-20 10:44:09 Slp: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
2015-01-20 10:44:09 Slp: at SSisDefaultInstance(UInt16* , Int32* )
2015-01-20 10:44:09 Slp: at Microsoft.SqlServer.Configuration.SniServer.NLRegSWrapper.NLregSNativeMethod Wrapper.SSIsDefaultInstanceName(String sInstanceName, Boolean& pfIsDefaultInstance)
2015-01-20 10:44:09 Slp: Exception: System.Runtime.InteropServices.SEHException.
2015-01-20 10:44:09 Slp: Source: Microsoft.SqlServer.Configuration.SniServerConfigExt.
2015-01-20 10:44:09 Slp: Message: External component has thrown an exception..
2015-01-20 10:44:09 Slp: Watson Bucket 1 Original Parameter Values
2015-01-20 10:44:09 Slp: Parameter 0 : SQL Server 2008 R2@RTM@
2015-01-20 10:44:09 Slp: Parameter 1 : SSisDefaultInstance
2015-01-20 10:44:09 Slp: Parameter 2 : SSisDefaultInstance
2015-01-20 10:44:09 Slp: Parameter 3 : System.Runtime.InteropServices.SEHException@-2147467259
2015-01-20 10:44:09 Slp: Parameter 4 : System.Runtime.InteropServices.SEHException@-2147467259
2015-01-20 10:44:09 Slp: Parameter 5 : SniServerConfigAction_Install_atValidation
2015-01-20 10:44:09 Slp: Parameter 6 : INSTALL@VALIDATION@SQL_ENGINE_CORE_INST
When we chose some other instance name then the installation has completed successfully.
So the questions are:
What could be the reason of the problem (and only for SQLEXPRESS instance that was earlier installed and then uninstalled)? I will provide the complete Detail.txt file if needed.
How could we check (if we could) the conditions so some name would be allowed as an instance name for SQL Server installer to success?
With the best regards,
Victor
Victor Nijegorodov

Thank you Lydia!
Unfortunately the simple check the registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL does /did not work in our case since there is no any instance
name there,
However there seem to be some "rudiments" under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and/or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
So I will now try to check the subkeys of these two keys as it was mentioned by Xiao-Min Tan.
Best regards,
Victor Nijegorodov
Victor Nijegorodov

TDS Addon,XL Reporter addon installation failed while connecting Citrix

Hai!
I am using SAP B1 PL 42
I have installed, MS sql Client,SAP B1 client and Addons in my citrix
server.
It's installed successfully and i able to log in,Connect TDS,XLR
Addons.
I publieshed SAP B1 in citrix.While i log in through citrix.
TDS Addon and XL-reporter addon's are showing error and failed to
connect.
Error Msg screen shot is attahched in the SAP B1 Support Message.
Message No: 922695
[https://websmp102.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000610167&_SCENARIO=01100035870000000183&_ADDINC=&]
Pl help me out in this issue.
Note:i log SAP with same user name
Thank you.
K.Thanga Raj
09710445987

Hi,
I cant view the link of the error. are you running citrix remotely or from the box? are all components installed for TDS and XLR?
Please refer to the link also :
Refer this link
ftp://ftp.citixsys.net/
user name: national
password: national
Regards,
Clint
Edited by: clint pow on Nov 11, 2008 8:06 AM

Installation failed while Installing 10g SOA_Suite

Hi,
I am installing 10g soa_suite, but its failed at middle with below mentioned error.
"Unable to locate a valid OC4J URI. The server is probably down."
any suggestion pls.
Thanks,
Santosh M E

Solution: when this error accures do not stop the installation and Start the OC4j manually and resume the installation.

SCOM 2012 Installation fails while deploying Datawarehouse

Similar Messages

Maybe you are looking for