SAP failover clustering on windows 2008 r2.

Dear Expert,
I want to configure SAP failover clustering for Production Server. I hard sum questions
1. How to configure SAP failover clustering on server?
2. What is server requirement for SAP failover clustering?
3. What is prerequisites?
We are doing first time, so we need help? How to do this task. Can someone give me step by step document with screen shot?
as We have ECC 6.0 EHP5 Installed in Windows Server 2008 R2 and Oracle 10.2.0.5.0 as our DB.
can anyone share me some helpful documents or links regarding this?
Please Suggest.
Thanks & regard.
Amit

http://service.sap.com/sltoolset
click the link in the yellow text box.
On this page you will find two entries important for you:
Follow the links for Software Provisioning Manager (note, download link, Information links)
At the end of the page you will find links for documentation (System Provisioning). (ECC 6.0 is an SAP Netweaver 7.0 based system).
regards
Peter

Similar Messages

SAP Cryptographic Library for Windows 2008

Hello,
Do you know where can i find SAP Cryptographic Library for Windows 2008 x64?
I was trying to find it in swdc, but there's only for Windows 2003 - and it's not working with 2008.
Best regards
Bartosz

Hi,
Just an information from my experience : I have never been able to download any release of the SAP Crypto library contrary to what all the documentation and SAP notes tell.
We had always to ask our SAP representative and to wait for several weeks to receive a DVD by physical mail.
Regards,
Olivier

SAP Backup Service SAP 8.8 and Windows 2008 R2 64 Bit

Dear All ( Mr Gordon)
I am facing problem with the Backup Service on windows 2008 R2 64 Bit.
1)The Service starts - There is no Issue
2)THere is no Backup - Even though i schedule it perform the backup
3)EvenLog has a lot of messages - Messages says some Dll are Missing or Corrupt.
COmpletely Uninstalled the Server Tools and Reinstalled back ,still there is error.
PLease help !
Best Regards
Dayal

Dear Dayal,
Thank you for your trust on me. To be honest, I never use SAP Backup Service. This is because: SQL Server provides its own Backup Service. No other vendor can compete with its build in function.
Thanks,
Gordon

Error on setup failover cluster with Windows 2008 R2 enterprise and SQL Server 2008 R2 (also with SP1)

Hi!
The setup process fails with this error:
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
I have found some hints by google, but nothing really helpfull.
Has anyone had a simular problem when installing SQL server 2008 R2?
All posts I found are about sql server 2008 (no R2!).
The cluster itself is working (storage, network, msdtc, quorum...).
Any hints?
Andreas
Here is the complete log:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2067791871
Exit facility code:            1216
Exit error code:               1
Exit message:                  Failed: see details below
Start time:                    2012-04-06 11:23:57
End time:                      2012-04-06 12:01:21
Requested action:              InstallFailoverCluster
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x625969A3%400x294A9FD9
Cluster properties:
Machine name: OC-SQLCL02ND01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine name: OC-SQLCL02ND02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine Properties:
Machine name:                  OC-SQLCL02ND01
Machine processor count:       32
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
Installation location:         G:\x64\setup\
Installation edition:          STANDARD
Slipstream:                    True
SP Level                       1
User Input Settings:
ACTION:                        InstallFailoverCluster
AGTDOMAINGROUP:                <empty>
AGTSVCACCOUNT:                 MANAGEMENT\sqladmin
AGTSVCPASSWORD:                *****
ASBACKUPDIR:                   S:\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   S:\OLAP\Config
ASDATADIR:                     S:\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      S:\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  MANAGEMENT\sqladmin
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            MANAGEMENT\administrator
ASTEMPDIR:                     S:\OLAP\Temp
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
CUSOURCE:
ENU:                           True
ERRORREPORTING:                False
FAILOVERCLUSTERDISKS:          Cluster Disk 3,Cluster Disk 4,Cluster Disk 5
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    IPv4;172.29.2.122;Cluster Network 2;255.255.255.0,IPv4;172.29.3.122;Cluster Network 3;255.255.255.0
FAILOVERCLUSTERNETWORKNAME:    CLUSTER02
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             S:\
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
PASSPHRASE:                    *****
PCUSOURCE:                     d:\install\mssql\sp1
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  MANAGEMENT\sqladmin
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLDOMAINGROUP:                <empty>
SQLSVCACCOUNT:                 MANAGEMENT\sqladmin
SQLSVCPASSWORD:                *****
SQLSYSADMINACCOUNTS:           MANAGEMENT\administrator
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBDIR:                  T:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQMREPORTING:                  False
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Analysis Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Integration Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\SystemConfigurationCheck_Report.htm

Hi Andreas Plachy,
Please make sure that the Virtual Server Name ‘CLUSTER02’ is unique on the network. In addition, are there any resources named ‘SQL Server’ on the Windows cluster? If that is the case, you may need to rename the related resources to avoid conflicting with
SQL Server, and try again.
Stephanie Lv
TechNet Community Support

How to test node failover in Windows 2008 R2 Failover Cluster?

Can anyone give me advice on how to properly test a node failure with a 2 mode Failover Cluster in Windows 2008 R2?

To test the failover of a clustered service or application
In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click
Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster that you want to configure.
Expand Services and Applications, and then click the service or application for which you want to test failover.
Under Actions (on the right), click Move this service or application to another node.
As the service or application moves, the status is displayed in the results pane (center pane).
Optionally, repeat step 4 to move the service or application to an additional node or back to the original node.
Source page:
http://technet.microsoft.com/en-us/library/cc754577.aspx
Regards,
Housam Smadi

SAP support Windows 2008 x64 server

Hi,
SAP 2007 supports the Windows 2008 x64 server? If support, what I need to do to run the sap add on at this Server.
Please give me any suggestiong.
Thanks and regards,
Lei Nandar Myint

Hi,
You may check this link: https://websmp203.sap-ag.de/smb/sbo/platforms (S-Number logon)
Regards, Yatsea

Failed Windows Server 2003 Enterprise SP2 to Windows 2008 Enterprise OS Upgrade

Attempted to upgrade the OS on our Primary Domain Controller which is running Windows Server 2003 Enterprise with Service Pack 2 installed on a HP ProLiant DL360 G4P Server with 2GB of ram, 3.2 GHz Processor and 53.2 GB of free space on C. I took
the following steps prior to attempting upgrade.
1. Determined that Server meet the minmum requirements for upgrade.
2. Installed all Windows Updates.
3. Uninstalled McAfee Virus Scan Enterprise Application
4. Backed Up and Imaged Primary Domain Controller.
5. Tested Domain Replication to ensure Primary and Backup Domain Controllers were communicating with each other.
6. Set Domain Function Level at Windows Server 2003
7. Placed ADPREP folder on C:\ on Primary Domain Controller and ran "adprep /forestprep" and "adprep /domainprep" successfully
8. In the C:\Windowd\System32 renamed the WindowsPowerShell application folder to WindowPowerShell-Old, the application failed the Upgrade compatibility test.
Loaded the DVD: "Windows Server 2008 for Enterprise, Standard and Datacenter 32bit Edition", ran installation in upgrade mode to preserve existing settings and software.  The Ugrade ran to last step, application install and failed at
26% complete with the following errror message:
"Windows installation encountered an error and cannot continue. Your computer will now restart and your previous version of windows will be restored"
My questions are why did the upgrade fail? What can we do to ensure the upgrade will succeed next time?
I have incuded the Setuperr.log below.
2014-08-24 08:48:27, Error      [0x08081e] MIG    Failed to load manifest at C:\$WINDOWS.~BT\Sources\dlmanifests\errorreportingfaults-dl.man: class UnBCL::XmlException: hResult = 0x0, Line = 2, Position = 134;
void __thiscall UnBCL::XmlDocument::Load(class UnBCL::String *)
2014-08-24 08:48:30, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:30, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:30, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:35, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:35, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:35, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:35, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:35, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:35, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:35, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:35, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:35, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:58, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:58, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:58, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:58, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:58, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:58, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:58, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:58, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:58, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:58, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:58, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:58, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:59, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:59, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:59, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:59, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:59, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:59, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:59, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:59, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:59, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:48:59, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:48:59, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:48:59, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:09, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:09, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:09, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:09, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:09, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:09, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:09, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:09, Error      [0x08085f] MIG    MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH)
failed gle=0x7f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x080863] MIG    MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2014-08-24 08:49:09, Error      [0x0808ff] MIG    COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\$WINDOWS.~BT\Sources\dlmanifests\Microsoft-Windows-IE-ESC\EscMigPlugin.dll, {196B9C00-9ECD-11DB-AF15-0014223890F3},
0) failed, hr=[0x8007007f].
2014-08-24 08:49:18, Error      [0x08071d] MIG    CDownlevelOCStore::GetOCCollection, Failed to load C:\$WINDOWS.~BT\Sources\dlmanifests\errorreportingfaults-dl.man.: class UnBCL::XmlException: hResult = 0x0, Line
= 2, Position = 134; . .
void __thiscall UnBCL::XmlDocument::Load(class UnBCL::String *)
2014-08-24 08:49:22, Error      [0x08081e] MIG    Failed to load manifest at C:\$WINDOWS.~BT\Sources\dlmanifests\errorreportingfaults-dl.man: class UnBCL::XmlException: hResult = 0x0, Line = 2, Position = 134;
void __thiscall UnBCL::XmlDocument::Load(class UnBCL::String *)
2014-08-24 09:13:05, Error      [0x080792] MIG    COCEventTracing::COCEventTracing Failed to call StartTrace 87.[gle=0x00000057]
2014-08-24 09:14:26, Error      [0x0802b6] MIG    Could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\AutoEnrollment [EventMessageFile]. Exception class Mig::Win32ErrorException: Win32ErrorException:
Error(0), Skip opening registry entry [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\AutoEnrollment [EventMessageFile]], which is protected by WRP..
void __thiscall Mig::CRegistryDataStore::Create(class Mig::CDataUnit *)
2014-08-24 09:14:26, Error      [0x0802b6] MIG    Could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\AutoEnrollment [TypesSupported]. Exception class Mig::Win32ErrorException: Win32ErrorException:
Error(0), Skip opening registry entry [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\AutoEnrollment [TypesSupported]], which is protected by WRP..
void __thiscall Mig::CRegistryDataStore::Create(class Mig::CDataUnit *)
2014-08-24 09:14:27, Error      [0x0802b6] MIG    Could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\Tlntsvr [EventMessageFile]. Exception class Mig::Win32ErrorException: Win32ErrorException:
Error(0), Skip opening registry entry [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\Tlntsvr [EventMessageFile]], which is protected by WRP..
void __thiscall Mig::CRegistryDataStore::Create(class Mig::CDataUnit *)
2014-08-24 09:14:27, Error      [0x0802b6] MIG    Could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\DfsSvc [EventMessageFile]. Exception class Mig::Win32ErrorException: Win32ErrorException:
Error(0), Skip opening registry entry [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\DfsSvc [EventMessageFile]], which is protected by WRP..
void __thiscall Mig::CRegistryDataStore::Create(class Mig::CDataUnit *)
2014-08-24 09:14:27, Error      [0x0802b6] MIG    Could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\DfsSvc [TypesSupported]. Exception class Mig::Win32ErrorException: Win32ErrorException:
Error(0), Skip opening registry entry [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\DfsSvc [TypesSupported]], which is protected by WRP..
void __thiscall Mig::CRegistryDataStore::Create(class Mig::CDataUnit *)
2014-08-24 09:14:27, Error      [0x0802b6] MIG    Could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\SCardSvr [EventMessageFile]. Exception class Mig::Win32ErrorException: Win32ErrorException:
Error(0), Skip opening registry entry [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\SCardSvr [EventMessageFile]], which is protected by WRP..
void __thiscall Mig::CRegistryDataStore::Create(class Mig::CDataUnit *)
2014-08-24 09:14:27, Error      [0x0802b6] MIG    Could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\SCardSvr [TypesSupported]. Exception class Mig::Win32ErrorException: Win32ErrorException:
Error(0), Skip opening registry entry [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\SCardSvr [TypesSupported]], which is protected by WRP..
void __thiscall Mig::CRegistryDataStore::Create(class Mig::CDataUnit *)
2014-08-24 09:30:13, Error      [0x060005] IBS    CallBack_StampRequiredDrives:An error occurred while fixing paths on black board GLE is [0x0]
2014-08-24 09:30:13, Error      [0x064188] IBSLIB RollbackReinitialize: threw exception.: class UnBCL::ArgumentException: Directory "X:\$WINDOWS.~BT\Sources\Rollback" doesn't exists..
__thiscall OSRollbackService::CCheckpointImpressario::CCheckpointImpressario(const unsigned short *,class OSRollbackService::CCheckpointSequence *,int)
[gle=0x00000003]
2014-08-24 09:33:19, Error      [0x0804b3] MIG    CMigWorkingDirHelper::CMigWorkingDirHelper() failed.: class UnBCL::DirectoryNotFoundException: root of directory to create not found.
class UnBCL::DirectoryInfo *__stdcall UnBCL::Directory::CreateDir(const class UnBCL::String *)
[gle=0x00000003]
2014-08-24 09:33:19, Error      [0x0802fa] MIG    MigStartUp caught exception: class UnBCL::DirectoryNotFoundException: root of directory to create not found.
__thiscall Mig::CMigWorkingDirHelper::CMigWorkingDirHelper(class UnBCL::String *)
__thiscall Mig::CMigWorkingDirHelper::CMigWorkingDirHelper(class UnBCL::String *)
class UnBCL::DirectoryInfo *__stdcall UnBCL::Directory::CreateDir(const class UnBCL::String *)
[gle=0x00000003]

Hi,
Here are some limitation of upgrading:
Upgrading is supported from x86-based and x64-based computers, but cross-architecture upgrades are not supported.
Cross-language upgrades are not supported.
Upgrading from Windows Server 2003 to a Server Core installation of Windows Server 2008 is not supported.
We cannot upgrade the failover clusters from Windows Server 2003 to Windows Server 2008. Before upgrading, we must uninstall failover clustering.
For detailed information about Upgrading to Windows Server 2008, please refer to the link below,
http://technet.microsoft.com/en-us/library/cc755199(v=WS.10).aspx#BKMK_Supported
Besides, to confirm that it isn't an IO issue, could you please try to copy the DVD to the local disk?
If error occurs, it may be an IO issue.
Best Regards.
Steven Lee
TechNet Community Support

Failover Clusters Licesing in MS SQLServer 2008 R2 license delivered by SAP

Dear Experts,
I need to know if the MS SQL Server 2008 R2 Enterprise Edition license delivered by SAP include the rights to use the Failover Clusters Feature of MS Windows Server 2008 R2 Enterprise Edition for the DB Instance. And if so, how many nodes would be covered as such.
Best Regards,
Mohamed Awny
SAP NW Technology Consultant
Smart Consulting Solutions - SCS - Egypt

Hi Mohamed Awny
As per the SAP recommitted to use in the windows 2008 cluster environment you have to use two node clusters, further details you can check the installation guide in the sap Site https://service.sap.com/pam
Regards
Sriram

SAP ECC 6.0 installation in windows 2008 clustering with db2 ERROR DB21524E

Dear Sir.,
Am installing sap ECC 6.0 on windows 2008 clustering with db2.
I got one error in the phase of Configure the database for mscs. The error is DB21524E 'FAILED TO CREATE THE RESOURCE DB2 IP PRD' THE CLUSTER NETWORK WAS NOT FOUND .
DB2_INSTANCE=DB2PRD
DB2_LOGON_USERNAME=iil\db2prd
DB2_LOGON_PASSWORD=XXXX
CLUSTER_NAME=mscs
GROUP_NAME=DB2 PRD Group
DB2_NODE=0
IP_NAME = DB2 IP PRD
IP_ADDRESS=192.168.16.27
IP_SUBNET=255.255.0.0
IP_NETWORK=public
NETNAME_NAME=DB2 NetName PRD
NETNAME_VALUE=dbgrp
NETNAME_DEPENDENCY=DB2 IP PRD
DISK_NAME=Disk M::
TARGET_DRVMAP_DISK=Disk M
Best regards.,
please help me since am already running late with this installation to run the db2mscs utility to Create resource.
Best regards.,
Manjunath G
Edited by: Manjug77 on Oct 29, 2009 2:45 PM

Hello Manjunath.
This looks like a configuration problem.
Please check if IP_NETWORK is set to the name of your network adapter and
if your IP_ADDRESS and IP_SUBNET are set to the correct values.
Note:
- IP_ADDRESS is a new IP address that is not used by any machine in the network.
- IP_NETWORK is optional
If you still get the same error debug your db2mscs.exe-call:
See the answer from Adam Wilson:
Can you run the following and check the output:
db2mscs -f <path>\db2mscs.cfg -d <path>\debug.txt
I suspect you may see the following error in the debug.txt:
Create_IP_Resource fnc_errcode 5045
If you see the fnc_errcode 5045
In that case, error 5045 which is a windows error, means
ERROR_CLUSTER_NETWORK_NOT_FOUND. This error is occuring because windows
couldn't find the "public network" as indicated by IP_NETWORK.
Windows couldn't find the MSCS network called "public network". The
IP_NETWORK parameter must be set to an MSCS Network., so running the
Cluster Admin GUI and expanding the Cluster Configuration->Network to
view all MSCS networks that were available and if "public network" was
one of them.
However, the parameter IP_NETWORK is optional and you could be commented
out. In that case the first MSCS network detected by the system was used.
Best regards,
Hinnerk Gildhoff

Windows 2008 failover clustering fails with Event ID 1205 1069 1558

I have a two nodes Windows 2008 and SQL 2008 cluster running in active\passive. I was restarting
my nodes after applying windows update then I received the following error message below within Failover Cluster Manager. I get errors with Event ID 1205 1069 1558 this happens every month .. Could someone help me on to find the root cause for
this issue how to check if it is an issue with network or Quorum drive ?

First, take a look at the 1069 event. This should point out which resource is failing.
Then, open a command prompt and run the command: cluster log /g
This will generate a cluster.log file that you can use to further troubleshoot this issue. The log file will be located in the C:\Windows\Cluster\Reports folder.
The cluster.log will be based on GMT time, so you may need to translate this to the local time zone in order to find the events you are looking for. Look for ERR or WARN messages and these should hopefully give you more insight as to why the resource is
failing.
Hope this helps.
Visit my blog about multi-site clustering

Can I remotely failover clusters with powershell from a non clustered server? Windows Server 2008 R2

Hello,
I'm trying to remotely administer my windows clusters and fail them over with a PowerShell Script. The server I'm using is not a clustered server. I've already installed the Failover Clustering Tools. I'm able to retrieve information about
my clusters but when I try to fail them over I receive an error saying "The cluster service is not running."
The command I'm using is 'Get-ClusterNode $Server | Get-ClusterGroup | Move-ClusterGroup'
Error message: 'Get-ClusterNode : The cluster service is not running. Make sure that the service is running on all nodes in the cluster'
Is there a way to install the cluster service or is there a different way to go around this error?
Thank you!

Hi Armando,
To get cluster node information, please try to use the cmd cluster.exe, like:
cluster.exe node NodeName /force
For more detailed information to use clusterexe, please refer to this article:
Mapping Cluster.exe Commands to Windows PowerShell Cmdlets for Failover Clusters
To remotely manage Cluster server, you can also try the powershell pssession with the cmdlet enter-pssession to accesss the remote server:
Learn How to Manage Remote PowerShell Sessions
I hope this helps.

Multiple identical Windows 2008 Clusters for file sharing, how to create a failover, since DNS CNAME is not an option?

Hello,
We have multiple SAN devices that expose block storage to multiple Windows 2008 Storage Edition clusters, which consume them via iSCSI. To simplify, here is what we have:
machine1+machine2 --> cluster --> storage1 (accessible via
\\storage1.domain.name\shares)
machine3+machine4 --> cluster --> storage2 (accessible via
\\storage2.domain.name\shares)
The 2 clusters have replication from active (storage1) to standby (storage2), so in theory they both include pretty much all the files.
We have hundreds of applications that are pointing to \\storage1\shares. In case of a disaster, however, it is an immensely laborious task to change all the end-points from
\\storage1\shares to \\storage2\shares, and then back.
I was trying to declare a CNAME (\\activestorage) in our internal DNS, and point it to the
currently active storage system. I tried both an alias and an IP pointing to the cluster. However, when I try to access
\\activestorage\shares, I got an error that the network share does not exist. I have been reading about this, and now I understand that CNAMEs are not possible in 2008 and only allowed in 2012 for this particular purpose.
I also understand that I may have to register a CAP (Client Access Point) to create an "alias" for my storage. However, the CAP approach does not seem to address (or does it?) my initial problem - I am not looking to create an alias just for a
particular storage cluster, but rather for the
active storage cluster. This way, if disaster strikes, I can simply go and change an IP somewhere, and all the applications will starting using the standby storage system.
I realize that there is an extra administration of ensuring that the two clusters are identical from shares perspective, and that's something we are already doing. All I need is a clue into how to make this architecture work in a less painful way.
Thank you for your help,
Isaac

I think you got confused between DFS and DFS replication. The primary use of DFS is namespace virtualization. It also has additional components which aid in real time replication. You can opt to use only the name space virtualization and not the replication.
The following link may provide some detailed information about DFS in 2008 R2. As I said.. You may not want to sue DFS Replicaiton, but DFS Namespaces is a perfect fit for your requirement (and very simple to implement)
http://technet.microsoft.com/en-us/library/cc732006.aspx
Regards Sivakarthi

Windows 2008 R2 Failover Clustering Issue - The operation returned because the timeout period expired.

I am trying to get a new Windows 2008 R2 cluster to work on two VMware servers (VMware ESXi 5.0.3) and am experiencing some form of timeout issue during the creation of the cluster according to the logs.
All validation checks pass successfully, whether trying to create a single node or dual node cluster, but the same error message is seen when creating the cluster. I have tried various suggestions found but none of them have made a difference. In an effort
to further diagnose the issue I enabled the following diagnostic logs:
- FailoverClustering
- FailoverClustering-Manager
- FailoverClustering-Client
The only useful error I can find is in the FailoverClustering-Client log which reports an error 'Couldn't resolve tcp binding to cluster' for each physical node to be part of the cluster.
In order to further diagnose the cause of the issue, I am looking for any options for increasing logging when attempting to create the cluster. Is there a way to increase the logging to see what the actual timeout is occurring with?
Alex.

Sorry, I should have been more clear ...The servers I am attempting to create a cluster with are Virtual Servers running on a VMware ESXi (5.0.3). They have access to two shared disks (connected to each VM using a separate SCSI Controller from that for the
disk used to install the OS) with Virtual SCSI Bus Sharing set within VMware.
Each Virtual Server has two NICs configured (with static IPs) - one for internal (domain connectivity) and the other for heartbeat connectivity. The servers can ping each other via both interfaces, as expected, but only domain connectivity works via the
internal NIC.
I have tried creating a single node or dual node cluster and get the same error each time. When the cluster is attempting to be created I can see the new computer object is created in Active Directory (which is then deleted when the cluster creation fails)
and I have also tried pre-creating the computer object and specifically setting permissions on it.
When creating the cluster I have tried via the GUI and via PowerShell (both with and without the option to attach the shared storage) but always get the same type of timeout error message. I am hoping there are further debugging options that can be used
to provide a better output as to what the timeout is occurring with.

SAP EHP5 MSCS installation with IBM DB2 9.7 on windows 2008 R2

Dear Sir
i am installing SAP EHP5 high availability with IBM DB2 9.7 on windows 2008 R2
first cluster node installation is completed,
now i am going to install database instance, before that i am configuring the database for MSCS as per installation guide,
but the database group is note creating in Failover cluster manager.
if you have any solution please reply
regards
gourishankar baikerikar

HI,
Thats a printing mistake in installation guide..
copy db2mscs.ese file to db2mscs.cfg ...
Remove all the unwanted stuff like explination of parameter paragraphs
Confgure required parameters like below and make sure there are no unwanted spaces in the txt file.
#Global section
DB2_INSTANCE = DB2SID
DB2_LOGON_USERNAME = XXXXXX\db2sid
DB2_LOGON_PASSWORD = password
CLUSTER_NAME = GXXXXX
MSCS Group for Node 0
GROUP_NAME = DB2 SID Group
DB2_NODE = 0
#IP_NAME = DB2 IP SID
#IP_ADDRESS=192.168.0.xx
#IP_SUBNET=255.255.255.0
#IP_NETWORK=Ethernet(3)
NETNAME_NAME = DB2 NetName SID
NETNAME_VALUE = DB2SID
#NETNAME_DEPENDENCY = DB2 IP SID
Open you cluster console and select NODE A there you should be able to identify the disks for DB clustering,
Copy that name and paste it here for DISK_NAME
DISK_NAME = DATABASE_CD2
DISK_NAME = DBLOGS_CD4
#INSTPROF_DISK = Disk M:
#TARGET_DRVMAP_DISK = Disk M:
With the above process you should be able to cluster your DB.
2) Please provide all the steps that you were identified to install , that would give more clarity to reply back where ever required.
Thanks,
Rahul

Windows 2008 R2 Failover

We have a 2 node Failover cluster created in a Node and Disk Majority (recommended) condition. The nodes have shared Quorum and Data Disks on iSCSI SAN.   The only application on these nodes is SQL Server.   When we
tested the failover by moving the application, we found that the Quorum disk did not failover and the services did not start automatically.    My readings on Windows 2008 R2 failover suggests that the first situation with the Quorum is normal
but I don't know about the services.   Can anyone assist?   This is our first go at Failover.

We have a 2 node Failover cluster created in a Node and Disk Majority (recommended) condition. The nodes have shared Quorum and Data Disks on iSCSI SAN.   The only application on these nodes is SQL Server.   When
we tested the failover by moving the application, we found that the Quorum disk did not failover and the services did not start automatically.    My readings on Windows 2008 R2 failover suggests that the first situation with the Quorum is normal
but I don't know about the services.   Can anyone assist?   This is our first go at Failover.
SQL Server is one of a very few application you'd better install using own clustering features instead of a generic failover clustering. See:
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/06/15/an-overview-of-ha-dr-solutions-available-for-sql-server.aspx
http://technet.microsoft.com/en-us/library/ms189134.aspx
http://www.brentozar.com/archive/2012/02/introduction-sql-server-clusters/
Hope this helped a bit :) Good luck!
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

SAP failover clustering on windows 2008 r2.

Similar Messages

Maybe you are looking for