Hi all:
A exciting information , late yesterday the RTM of Operations Manager 2007 R2 was released. You can point this link to downloads SCOM2007 R2 RTM evaluation edition.
http://www.microsoft.com/downloads/details.aspx?FamilyID=93ddf25b-1ef0-4851-81b0-5fb9a2f76181&displaylang=en
General Availability of the product will be 1st July 2009 !
Enjoy!
Justin Gao
Microsoft (China)
Last week , i test SCOM 2007 R2 RC , according to my wont, i prepare a test environment , one DC(Windows Server 2008) , one DB(Windows Server 2008 + SQL Server 2008) and one RMS(Windows Server 2008) role.
frist , i install OpsMgr 2007 R2 Database successfully , on RMS Server i install windows components :
- ASP.NET 2.0 AJAX Extensions
- PowerShell 1.0
- .Net Framework 3.0
- ASP.Net
- IIS Management Console
when install phase , occur rolling back , setup unsuccess.
i checked log,
CAPACK: Extracting custom action to temporary directory:
C:\Windows\Installer\MSI2532.tmp-\
CAPACK: Binding to CLR version v2.0.50727
Calling custom action
WebCAManaged!Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.ConfigureAction
ConfigureAction: Error: Unknown error (0x80005000)
StackTrace: at System.DirectoryServices.DirectoryEntry.Bind(Boolean
throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.RefreshCache()
at Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.Install(String
targetDir, Int32 portNumber, String rmsServer, Boolean windowsAuthOn, String
rootWebConfigFile, String mobileWebConfigFile, String rssWebConfigFile,
String publicKeyToken, String version)
at
Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.ConfigureAction(Session
session)
Exception thrown by custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by
the target of an invocation. --->
System.Runtime.InteropServices.COMException (0x80005000): Unknown error
(0x80005000)
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.RefreshCache()
at Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.Install(String
targetDir, Int32 portNumber, String rmsServer, Boolean windowsAuthOn, String
rootWebConfigFile, String mobileWebConfigFile, String rssWebConfigFile,
String publicKeyToken, String version)
at
Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.ConfigureAction(Session
session)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object
arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean
skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at Microsoft.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32
sessionHandle, String entryPoint)
MSI (s) (D8:8C) [12:55:03:674]: NOTE: custom action
_ConfigureAction.2FD07918_9082_437D_99BC_FD43602A4625 unexpectedly closed
the hInstall handle (type MSIHANDLE) provided to it. The custom action
should be fixed to not close that handle.
Action ended 12:55:03: InstallFinalize. Return value 3.
MSI (s) (D8:08) [12:55:03:694]: User policy value 'DisableRollback' is 0
MSI (s) (D8:08) [12:55:03:694]: Machine policy value 'DisableRollback' is 0
MSI (s) (D8:08) [12:55:03:716]: Executing op:
Header(Signature=1397708873,Version=405,Timestamp=981100209,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (D8:08) [12:55:03:716]: Executing op:
DialogInfo(Type=0,Argument=1033)
MSI (s) (D8:08) [12:55:03:716]: Executing op:
DialogInfo(Type=1,Argument=System Center Operations Manager 2007 R2)
MSI (s) (D8:08) [12:55:03:717]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing
backup files,CleanupTemplate=File: [1])
I checked some document , i find this error source of IIS management compatibility , and i add this component , reinstall and successfully!
J
Enjoy!
Justin Gao
Microsoft(China)
Many people told me Exchange Server 2007 install on Windows Server 2008 not stability and occur many error .
Today , i will share my little case of troubleshooting with you.
I setup Exchange 2007 with sp1 (x86 or x64) on Windows Server 2008 , when install Hub transport role phase, display Service "MSExchangeTransport" on server not reach state "Running" . in Eventlog application logs , i find Event ID 2114 , Level is Error . Description: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE(PID=2776). Topology discovery failed,error 0x80040a02(DSC_E_NO_SUITABLE_CDC).
The same way to install on Windows Server 2003 you can't encounter this error . I find Windows Server 2008 TCP/IP protocol including IPv4 and IPv6 , because i haven't IPv6 topology , so i unselected TCP/IPv6 , result in this fails.
when i selected TCP/IPv6 and reinstall Exchange Server 2007 , setup successful! J
Enjoy!
Justin Gao
Microsoft(China)
