EMC initializtion failed

I've installed a fresh copy of Server 2012 and Exchange 2010. When I try to open the EMC I get an Initialization failed, below is the screen shot.
I've tried numerous of things to fix this issue. Restarted IIS, WS-Management, WinRm command.
Any help will be appreciated

Hello,
Please run the "WinRM QuickConfig". Carry out any changes that it asks by simple pressing "Y". and then run the same command again until it retures two positive results.
Please check these services(IIS Admin Service, Windows Remote Management (WS-Management) service and World Wide Web Publishing Service ) are started.
Please make sure the default web site is started.
If these above settings are ok, I recommend you use the EMTshooter to verify some problems with management tools.
Please check if there is any error in application log.
Cara Chen
TechNet Community Support

Similar Messages

EMC Initialization failed: WinRM HTTP error 403

We have an existing 2003R2 server running Exchange 2007. I have just installed a new 2012 R2 server with Exchange 2010 SP3 RU8v2. Opening the EMC on this new server yields the following error:
Connecting to remote server XXXXX.DOMAIN.LOCAL failed with the following error message; The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs
and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".
For more information, see the about_Remote_Troubleshooting help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion 'Version 14.3 (Build 123.4)".
If I open EMS it attempts to connect three times, times out, prompts "Failed to connect to an Exchange server in the current site. Enter the server FQDN where you want to connect.:" I then type my servername.domainname.local and am prompted with
the following error:
Connecting to remote server failed with the following error message: The WinRM client received an HTTP status code of 403 from the remote WS-Management service. For more information, see the about_Remote_Troubleshooting Help Topic. FullyQualifiedErrorID:
PSSessionOpenFailed
^^^My understand of this error is the connection is being established on 443 instead of 80. I have unchecked SSL from powershell and was able to telnet to the old server (2007 exch box) via 80, so I know the port and traffic is open.
I think this is an issue with IIS on the older 2007 server. Obviously I can't use WinRM Quickconfig on that server (2003 R2) and I noticed that there is no "powershell" module in default site in IIS on this box.
On the server 2007 box if I run 'get-exchangeserver' from powershell it shows both the old and the new server. However the old server is not able to connect to the console at all and I can't verify that it's actively able to manage my exchange forest.
Any assistance is greatly appreciated.

Hi ,
Thank you for your question.
This error could be caused by many reasons, for example: IIS authentication, Win RM and so on.We could refer to the following link to troubleshoot:
1. Make sure we have enough permission to open EMC;
2. We could run “WinRM QuickConfig” to make sure IIS WinRM extension is installed:
3. Open IIS go to Powershell virtual directory and check that SSL in disabled and authentification is set only to Anonymous;
4. If the issue persist, we could use Exchange Management Console Troubleshooter
tool to analysis the error and send error information to
[email protected] for our troubleshooting.
Permissions required: In order to run the troubleshooter, the user will have to have the rights to log on locally to the Exchange server (due to local nature of the troubleshooter at this time) and will need permissions to run Windows
PowerShell.
Installing the troubleshooter: First, we download the troubleshooter ZIP file, which we can find here. Installing the EMTshooter is pretty easy. Just drop the 4 files from the ZIP file into 1 folder, rename them to .ps1 and run
EMTshooter.ps1 from a normal (and local) PowerShell window. I personally just created a shortcut for it on my desktop with the following properties: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command ". 'C:\EMTshooter\EMTshooter.ps1'"
However, as most users probably won't run this more than a few times we might not need or want an icon. Just remember that EMTshooter.ps1 is the main script to run.
Resolving WinRM errors and Exchange 2010 Management tools startup failures:
http://blogs.technet.com/b/exchange/archive/2010/12/07/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures.aspx
5. Check the proxy setting by the following link:
https://technet.microsoft.com/en-us/library/cc731131(WS.10).aspx
6. Make sure two files have been in the following path:
“web.config” file (under Program Files\Microsoft\Exchange Server\V14\ClientAccess\PowerShell)
"applicationHost.config" file (located at: \Windows\System32\inetsrv\config)
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Unable to open EMC : Initialization failed in Ex2010

Dear Expert
I have the problem in below.
but I follow this technet reference but it does not work, http://blogs.technet.com/b/whats_on_scotts_mind_today/archive/2012/12/07/exchange-2010-unable-to-open-exchange-management-console-initialization-failed.aspx#pi47623=3
please suggest.

Hello,
Please use get-rolegroupmember "organization management" cmdlet to check if you are a member of organization management role group.
Please check if there is related error in application log.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

EMC initialization failed due to unexpected error

Dear All,
I am worrying like anything since morning. I do not know what happened but my EMC is not opening in Exchnage 2010 Sp2.
ERROR:
unexpected error [0x78D6DC13] while executing command 'Get-LogonUser'
Please suggest us something.
Though exchange working fine, i have to work through EM Shell. :(
Regards, Jay.

Hi,
You can try the following solution and check the result:
Simple solution: "C:\Program Files\Microsoft\Exchange Server\V14\Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml" was defect.
Repair it (I copied a working one from another node) and all works fine again.
If you do not need it, delete it and then run >>Disable-CmdletExtensionAgent “Scripting Agent”<<
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

WEb camera initializtion failed in Satellite P750-114

Dear All,
I am facing a problem with the web camera in my Toshiba Satellite P750-114. The laptop is less than two months old and the web camera was working fine, then it suddenly stopped working. The error message is "Web camera initialization failed. Please check your camera device and restart application or computer". The Microphone stopped working as well, as it is related to the web camera device. The operating system is Windows 7 64bits. It seems that the operating system is not seeing that there is a webcam anymore. I tried the following things:
1- I uninstalled the web camera driver, downloaded the most recent driver from Toshiba website (the link is http://uk.computers.toshiba-europe.com/innovation/jsp/supportMyProduct.do?service=UK) , and installed it, but it did not work.
2- I restored the original setting for the laptop, but still the web camera is not working.
Two ways I am using to test the web camera: the Skype and "Web Camera Application" from Start/Toshiba/Utilities
Please if someone has any idea on how to resolve this problem, the laptop is band new and it is fantastic, but this problem is annoying. I searched the Internet for similar problems, some Toshiba models suffer from this problem but not P750-114,
Please help
Bashar

Generally speaking, after recovery image installation all hardware components should be recognized and installed properly so with this factory settings everything should work as on the day after you purchased your notebook and started it for the first time.
If the cam doesn't work with factory settings I can imagine there is some hardware problem.
I recommend you to contact nearest Toshiba service provider and ask for help. They can check cam functionality using their diagnostic tools and exchange cam if necessary.
Of course it will be covered by valid warranty.

Database initialization failed after attach the database.

Hello Everyone,
I have a problem after detaching the database and attaching it again (I moved the database to another partition because of shortage of disk space). Then, I find that the system can not start. (I've two systems and now neither of them could start). The error seems very similar.
In the pure java system(netweaver 04s) log: jvm_bootstrap.out,
com.sap.engine.bootstrap.synchronizationException: Database Initializtion Failed! Check database properties.
com.sap.engine.frame.core.configuration.configurationException: Error while connecting to DB.
Caused by: java.sql.SQLException: [NWMss] [SQLServer JDBC Driver] [SQLServer] Login failed for user 'SAPBP0DB'.
In pure ABAP system(Netweaver 04s) log: dev_w12:
openoledbConnection: MARS property was not set.
openoledbConnection: line 23722. hr: 0x8000ffff login failed for user 'CNDT50083414\SAPServiceBE0'.
sloledb.cpp [openoledbConnection, line 23722]: Error/Message: (err 18456, sev 0), Login failed for user 'CNDT50083414\SAPServiceBE0'.
sloledb.cpp [openoledbConnection, line 23722]: Error/Message: (err 0, sev 0), Invalid string connection attribute.
Is this because the DB not started? In Windows Services, I found 'MSSQLServer' is started.
How can I trace down to this problem? I don't have much idea on DB...
All your kindly help is greatly appreciated.
Best Regards,

Hi Karan,
Thank you for your reply. I attach the dev_w0 file here:
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, MJ
B
B Tue Sep 23 13:16:15 2008
B create_con (con_name=R/3)
B Loading DB library 'C:\usr\sap\BE0\DVEBMGS02\exe\dbmssslib.dll' ...
B Library 'C:\usr\sap\BE0\DVEBMGS02\exe\dbmssslib.dll' loaded
B Version of 'C:\usr\sap\BE0\DVEBMGS02\exe\dbmssslib.dll' is "700.08", patchlevel (0.158)
B New connection 0 created
M sysno      02
M sid        BE0
M systemid   562 (PC with Windows NT)
M relno      7000
M patchlevel 0
M patchno    159
M intno      20050900
M make:      multithreaded, Unicode, 64 bit, optimized
M pid        1704
M
M kernel runs with dp version 237000(ext=110000) (@(#) DPLIB-INT-VERSION-237000-UC)
M length of sys_adm_ext is 576 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 1704) [dpxxdisp.c   1316]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm)          21008     (1616)
M DpShMCreate: sizeof(tm_adm)          5912624     (29416)
M DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
M DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
M DpShMCreate: sizeof(comm_adm)          552080     (1088)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm)          0     (104)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm)          0     (72)
M DpShMCreate: sizeof(vmc_adm)          0     (1864)
M DpShMCreate: sizeof(wall_adm)          (41664/36752/64/192)
M DpShMCreate: sizeof(gw_adm)     48
M DpShMCreate: SHM_DP_ADM_KEY          (addr: 0000000011080050, size: 6604928)
M DpShMCreate: allocated sys_adm at 0000000011080050
M DpShMCreate: allocated wp_adm at 0000000011082150
M DpShMCreate: allocated tm_adm_list at 0000000011087360
M DpShMCreate: allocated tm_adm at 00000000110873C0
M DpShMCreate: allocated wp_ca_adm at 000000001162ABF0
M DpShMCreate: allocated appc_ca_adm at 00000000116309B0
M DpShMCreate: allocated comm_adm at 00000000116328F0
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 00000000116B9580
M DpShMCreate: allocated gw_adm at 00000000116B9600
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 00000000116B9630
M DpShMCreate: allocated wall_adm at 00000000116B9640
M rdisp/queue_size_check_value : -> off
M ThTaskStatus: rdisp/reset_online_during_debug 0
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
X <EsNT> Using memory model view.
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M ThInit: running on host CNDT50083414
M
M Tue Sep 23 13:16:16 2008
M calling db_connect ...
C Thread ID:6104
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'C:\usr\sap\BE0\DVEBMGS02\exe\dbmssslib.dll'
C dbmssslib.dll patch info
C    patchlevel   0
C    patchno      158
C    patchcomment Corrections of odbc-based dbsl: dsql: optype, DSN (1135165)
C np:(local) connection used on CNDT50083414
C CopyLocalParameters: dbuser is 'be0'
C
C Tue Sep 23 13:16:17 2008
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
C OpenOledbConnection: line 23722. hr: 0x8000ffff Login failed for user 'CNDT50083414\SAPServiceBE0'.
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 18456, sev 0), Login failed for user 'CNDT50083414\SAPServiceBE0'.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: line 23722. hr: 0x8000ffff Login failed for user 'CNDT50083414\SAPServiceBE0'.
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 18456, sev 0), Login failed for user 'CNDT50083414\SAPServiceBE0'.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: line 23722. hr: 0x8000ffff Login failed for user 'CNDT50083414\SAPServiceBE0'.
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 18456, sev 0), Login failed for user 'CNDT50083414\SAPServiceBE0'.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn to np:(local).
C Retrying without protocol specifier: (local)
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: line 23722. hr: 0x8000ffff Login failed for user 'CNDT50083414\SAPServiceBE0'.
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 18456, sev 0), Login failed for user 'CNDT50083414\SAPServiceBE0'.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: line 23722. hr: 0x8000ffff Login failed for user 'CNDT50083414\SAPServiceBE0'.
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 18456, sev 0), Login failed for user 'CNDT50083414\SAPServiceBE0'.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: line 23722. hr: 0x8000ffff Login failed for user 'CNDT50083414\SAPServiceBE0'.
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 18456, sev 0), Login failed for user 'CNDT50083414\SAPServiceBE0'.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23722]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn. 0
B ***LOG BY2=> sql error -1     performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY0=> Login failed for user 'CNDT50083414\SAPServiceBE0'. [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY2=> sql error -1     performing CON [dblink#5 @ 431] [dblink 0431 ]
B ***LOG BY0=> Login failed for user 'CNDT50083414\SAPServiceBE0'. [dblink#5 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1440]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10504]
M
M Info for wp 0
M
M    pid = 1704
M    severity = 0
M    status = 0
M    stat = WP_RUN
M    waiting_for = NO_WAITING
M    reqtype = DP_RQ_DIAWP
M    act_reqtype = NO_REQTYPE
M    rq_info = 0
M    tid = -1
M    mode = 255
M    len = -1
M    rq_id = 65535
M    rq_source =
M    last_tid = 0
M    last_mode = 0
M    semaphore = 0
M    act_cs_count = 0
M    csTrack = 0
M    csTrackRwExcl = 0
M    csTrackRwShrd = 0
M    mode_cleaned_counter = 0
M    control_flag = 0
M    int_checked_resource(RFC) = 0
M    ext_checked_resource(RFC) = 0
M    int_checked_resource(HTTP) = 0
M    ext_checked_resource(HTTP) = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M    attachedVm = no VM
M
M *****************************************************************************
M *
M * LOCATION    SAP-Server CNDT50083414_BE0_02 on host CNDT50083414 (wp 0)
M * ERROR       ThInit: db_connect
M *
M * TIME        Tue Sep 23 13:16:17 2008
M * RELEASE     700
M * COMPONENT   Taskhandler
M * VERSION     1
M * RC          13
M * MODULE      thxxhead.c
M * LINE        10724
M * COUNTER     1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   724]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 261]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 1704) [dpnttool.c   333]

Using OEM to backup/restore DB using EMC Avamar (3rd party)

Hi,
I'm trying to find a solution for using OEM to backup and restore DB using EMC Avamar software.
Normally, we can backup/restore DB using Avamar through RMAN CLI using scripts similar to the following:
connect target /
run {
configure controlfile autobackup on;
set controlfile autobackup format for device type sbt to 'CONTROLFILE.orcl.%F';
allocate channel c0 type sbt PARMS="SBT_LIBRARY=c:\PROGRA~1\avs\bin\orasbt64.dll" format '%d_%U';
send '"--prefix=11g/orcl/" "--flagfile=c:\flagfile\avtar-flags.txt" "--bindir=c:\PROGRA~1\avs\bin"';
backup database plus archivelog delete input;
release channel c0;
Where orasbt64.dll is the name of Avamar's 64bit library and flagfile contains some internal flags necessary for backup/restore operations.
Now, I want to use OEM for the same thing so, what I did was try to specify the Media Management Vendor Library Parameters under Backup Settings in OEM. I saved the following as the parameters:
"SBT_LIBRARY=c:\PROGRA~1\avs\bin\orasbt64.dll";
Even after this, the backup script generated by OEM does not contain this parameter. Naturally, backups to EMC Avamar fail.
I would like answers to these 2 questions:
1. How to correctly specify the Media Management Vendor Library Parameters?
2. Is there a way to specify all the parameters (--prefix, flagfile, bindir, PARMS etc.) so that the script generated by OEM is same (or as close as possible) to the one I use for RMAN CLI backups.
Thanks!

Hi Anant,
I'm also having the same issue. It fails because it doesn't understand the "send" command in OEM. Here is the output of the tape backup test:
RMAN> run {
2> allocate channel oem_sbt_backup type 'sbt_tape' format '%U' parms 'SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so,
3> ENV=(PATH=/bin:/usr/bin:/usr/local/avamar/bin);
4> send "--flagfile=/home/oracle/scripts/backup/my-avtar-flags.txt"';
5> backup as COMPRESSED BACKUPSET current controlfile tag '04302012033156';
6> restore controlfile validate from tag '04302012033156';
7> release channel oem_sbt_backup;
8> }
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on oem_sbt_backup channel at 04/30/2012 15:32:00
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27209: syntax error in device PARMS - unknown keyword or missing =
RMAN> allocate channel for maintenance type 'sbt_tape' parms 'SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so,
2> ENV=(PATH=/bin:/usr/bin:/usr/local/avamar/bin);
3> send "--flagfile=/home/oracle/scripts/backup/my-avtar-flags.txt"';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ORA_MAINT_SBT_TAPE_1 channel at 04/30/2012 15:32:01
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27209: syntax error in device PARMS - unknown keyword or missing =
When I use TSM it doesn't require the "send" command and it backs up successfully. I guess the other option would be to create an EM job to do the backups. However, this wouldn't populate the EM tables for backup reporting.

Unable to create mail database

okay, I had 4 hard drives fail at once on my Storage Server,
Lost the VHD for my Exchange VM
Created a new VM, recovered Exchange 2010 SP3 using setup /m:recoverserver
Didn't appear to have any errors until it was time to mount the database, database wouldn't mount.
Tried to create a new database, getting Error 5000.
When I looked under Exchange\V14\mailbox, I can't actually find a copy of my mail database, so, I am not able to mount because I can't actually create a good mail database.
When I try to create a mail database, I get these errors
From EMC
AcmeMail2
Failed
Error:
Couldn't set the System Attendant for database "AcmeMail2".
The requested search root 'Acmenet.local/Configuration/Services/Microsoft Exchange/Acme/Administrative Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)/Servers/Acme/Microsoft System Attendant' is not within the scope of this operation. Cannot perform
searches outside the scope 'Acmenet.local/MyBusiness'.
Warning:
An error occurred while trying to prepopulate newly created mailbox "/o=Acme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=SystemMailbox{22655608-c412-4e60-baa3-4d716ab38f20}" in database "AcmeMail2" on server "Acme".
"/o=Acme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=SystemMailbox{22655608-c412-4e60-baa3-4d716ab38f20}" may not immediately be available for certain cmdlets and operations until it has replicated. If you need to run the
cmdlet again, and you want more information about the error, please add the -Verbose parameter. Error: 0x8004010F.
Exchange Management Shell command attempted:
new-mailboxdatabase -Server 'Acme' -Name 'AcmeMail2' -EdbFilePath 'C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2\AcmeMail2.edb' -LogFolderPath 'C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2'
From the Application Log
Event ID 5000
Failed to save admin audit log for this cmdlet invocation.
Organization:
Log content:
Subject: Acmenet.local/Users/Administrator : New-MailboxDatabase
Body:
Cmdlet Name: New-MailboxDatabase
Object Modified: AcmeMail2
Parameter: Server = Acme
Parameter: Name = AcmeMail2
Parameter: EdbFilePath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2\AcmeMail2.edb
Parameter: LogFolderPath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2
Property Modified: OrganizationId =
Property Modified: Id = AcmeMail2
Property Modified: DataMoveReplicationConstraint = None
Property Modified: RawName = AcmeMail2
Property Modified: RpcClientAccessServerExchangeLegacyDN = /o=Acme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Acme
Property Modified: Server = Acme
Property Modified: LogFilePrefix = E01
Property Modified: LogFolderPath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2
Property Modified: SystemFolderPath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2
Property Modified: AdminDisplayName = AcmeMail2
Property Modified: ExchangeLegacyDN = /o=Acme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Acme/cn=Microsoft Private MDB
Property Modified: EdbFilePath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2\AcmeMail2.edb
Property Modified: DisplayName = AcmeMail2
Property Modified: MasterServerOrAvailabilityGroup = Acme
Property Original: OrganizationId =
Property Original: Id =
Property Original: DataMoveReplicationConstraint = SecondCopy
Property Original: RawName =
Property Original: RpcClientAccessServerExchangeLegacyDN =
Property Original: Server =
Property Original: LogFilePrefix =
Property Original: LogFolderPath =
Property Original: SystemFolderPath =
Property Original: AdminDisplayName =
Property Original: ExchangeLegacyDN =
Property Original: EdbFilePath =
Property Original: DisplayName =
Property Original: MasterServerOrAvailabilityGroup =
Caller: Acmenet.local/Users/Administrator
Succeeded: False
Error: System.InvalidOperationException: Couldn\'t set the System Attendant for database \"AcmeMail2\". ---> Microsoft.Exchange.Data.Directory.ADOperationException: The requested search root \'Acmenet.local/Configuration/Services/Microsoft Exchange/Acme/Administrative
Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)/Servers/Acme/Microsoft System Attendant\' is not within the scope of this operation. Cannot perform searches outside the scope \'Acmenet.local/MyBusiness\'.\r\n at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String
preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope)\r\n at Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request,
ADObjectId originalId, Boolean emptyObjectSessionOnException)\r\n at Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties)\r\n at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.Microsoft.Exchange.Data.IConfigDataProvider.Save(IConfigurable
instance)\r\n at Microsoft.Exchange.Management.SystemConfigurationTasks.NewMailboxDatabase.SetSystemAttendantObject(MailboxDatabase database)\r\n --- End of inner exception stack trace ---
Run Date: 2014-04-04T19:48:39
OriginatingServer: Acme (14.03.0123.002)
Error:
Exception thrown during AdminLogProvisioningHandler.Validate: Microsoft.Exchange.Data.Storage.ObjectNotFoundException: The discovery mailbox, a hidden default mailbox that is required to search mailboxes, can't be found. It may have been inadvertently deleted.
This mailbox must be re-created before you can search mailboxes.
at Microsoft.Exchange.Data.Storage.Infoworker.MailboxSearch.MailboxDataProvider.GetDiscoveryMailbox(ADRecipientSession session)
at Microsoft.Exchange.Management.SystemConfigurationTasks.AdminAuditLogHelper.CheckArbitrationMailboxStatus(OrganizationId organizationId, ADUser& user, ExchangePrincipal& principal, String& errorMessage)
And Event ID 3154
Active Manager failed to mount database AcmeMail on server Acme.Acmenet.local. Error: An Active Manager operation failed. Error The database was never mounted..
On the Domain Controller, I have run setup /prepareAD several times
Any suggestions?
Don Miller Network Administrator Teton Machine Company

In the case,
the VM is hosted on the Host machine's local drive, the VHD is too.
I created this database about an hour ago (there still isn't a database or log file that has been created), but when I try to mount it manually, I am getting this error
Microsoft Exchange Error
Failed to mount database 'acme'.
acme
Failed
Error:
Couldn't mount the database that you specified. Specified database: acme; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred
during a database operation. Error: An error occurred while preparing to mount database 'acme'. Error: An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'. [Database:
acme, Server: acme.acmenet.local].
An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: An error occurred while preparing to mount database
'acme'. Error: An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'. [Database: acme, Server: acme.acmenet.local]
An Active Manager operation failed with a transient error. Please retry the operation. Error: An error occurred while preparing to mount database 'acme'. Error: An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find
the path specified) from Windows API 'FindFirstFile'. [Server: acme.acmenet.local]
An error occurred while preparing to mount database 'acme'. Error: An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'.
An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'
Don Miller Network Administrator Teton Machine Company

Remote Exchange Management Console "W3SVC isn't running on any Exhange servers in site" and always shows older version after SP2 or SP3 installed

I'm trying to use EMC on a computer to remotely manage Exchange 2010 without having to do from the actual Exchange servers.
First off, upgrading, uninstalling or installing EMC always fails on "Stopping" services. Seams to be a pretty common problem, but no clear fix other than deleting the registry entry (HKLM\SOFTWARE\Microsoft\ExchangeServer) and the
"C:\Program Files\Microsoft\Exchange Server" folder. I'm guessing this is a bug since there should not be any Exchange services that need to be stopped on a computer where I'm just trying to use the EMC tool to manage Exchange.
Next, is where when I open EMC I get "The World Wide Web Publishing Service (W3SVC) isn't running on any Exchange servers in the site. If you want to connect to Remote PowerShell, this service must be running. Make sure that the W3SVC is running on
at least one Exchange server." From all the reading I am pretty sure that this is due to the Exchange servers being on one version and EMC I'm trying to use is another version.
This is the version our Exchange Servers are on:
ProductVersion   FileVersion      FileName
14.02.0375.000   14.02.0375.000   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe
Which finally brings me to the part where no matter what SP I install to run EMC it always shows:
ProductVersion   FileVersion      FileName
14.01.0218.015   14.01.0218.015   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe
I've tried SP2, and even SP3 hopeing that an even newer version would let me connect to Exchange, but no matter what it always shows the 14.01 version above.
I've also tried installing "Exchange2010-KB2874216-x64-en" which should be the same version we are on (Update Rollup 7 for Exchange Server 2010 Service Pack 2), but get a Windows Installer Error stating, "The upgrade patch cannot be installed
by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program." This Error probably makes sense if no matter what I do I'm stuck with a version prior to SP2.
Any ideas?

Hi,
From your description, I would like to clarify the following things:
1. Make sure the World Wide Web Publishing Service is running in Exchange server.
2. Ensure that the account you use to open EMC is a member of Organization Management role group.
3. Based on my knowledge, the error "The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program." occurs if you install
the RU for a different SP. Please re-download the Service Pack 2 and install it on the remote computer since it hasn't been installed successfully from the above information.
What's more, here is a similar thread for your reference.
Unable to install Update Rollup 4 for Exchange Server 2010 Service Pack 2
https://social.technet.microsoft.com/Forums/exchange/en-US/677c21ed-e125-41c1-a468-c268e1f21f8e/unable-to-install-update-rollup-4-for-exchange-server-2010-service-pack-2?forum=exchange2010
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Problem in Creating Table using DB Config. Assistant

Hi, everybody. I see the error messages below when I use DB Configuration Assitant in Oracle 8i to create my database :-
ORA-01034 : Oracle not available
ORA-27146 : post/wait initializtion failed
ORA-01012 : not logged on
Can u tell me how to solve this problem ?

Connect as servermanager and enter on the prompt
"lsnrctl status" it will give you whether you have started the listener service and after that connect as internal and "startup" if the database is started it will give message "database instance already started" or else it will start the database.
also make sure you have created all control files properly
Nadeem

Problems cleaning up 12.1.0.1 agents after upgrading to 12.1.0.3

I have just completed upgrading OEM from 12.1.0.1 to 12.1.0.3. Agents have also been upgraded to 12.1.0.3.0 and I am now attempting to clean up 12.1.0.1.0 agents. In the console I choose Setup -> Manage Cloud Control -> Clean up Agents and choose the Post Agent Upgrade Tasks, select agents to clean up and choose submit and a job is submitted. I wait until the job completes successfully, choose another agent to clean up, submit the job and the submission fails with the error -
ORA-20401: A job with the specified name already exists ORA-06512: at "SYSMAN.EM_JOB_OPS", line 290 ORA-06512: at "SYSMAN.GC_JOB", line 29 ORA-06512: at line 1
I look at job activity and the job shows as having completed successfully. If I wait a period of time (overnight in one case) or from the job console delete the most recent job I am then able to successfully submit another cleanup job.
Has anyone else experienced this or is this a bug or am I doing something wrong?
Thanks
Bill Wagman

Anandu,
Apparently this is a known issue. Oracle's response -
There are some limitations related to user input for job name. These limitations are being tracked by bugs and are deferred to next release.
16689459---> EMCLI UPGRADE_AGENTS FAILS BADLY IF JOBNAME WAS REUSED
16689511---> EMCLI UNEXPECTED INPUT PARSING WHEN JOBNAME HAS SPECIAL CHARACTERS
Suggestion:
Try submitting a new job with a new job name. Job names must be unique.
Thank you.

Solaris 10connectivity to EMC: failed to configure ANY device on FCA port

I'm connecting a E2900 server with a EMC symmetrix storage with fiber channel.
But I'm getting the following errors, and I'm not able to see the external disks. Any help is really appreciated.
bash-3.00# cfgadm -al
c3 fc-fabric connected unconfigured unknown
c3::5006048c52a5b746 unavailable connected unconfigured failed
c4 fc-fabric connected unconfigured unknown
c4::5006048c52a5b749 unavailable connected unconfigured failed
bash-3.00# cfgadm -c configure c3
cfgadm: Library error: report LUNs failed: 5006048c52a5b746
failed to configure ANY device on FCA port
bash-3.00# tail -f /var/adm/messages
Nov 27 16:42:12 cosemm1 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Nov 27 16:42:12 cosemm1 Unsupported LUN Addressing method 40 in response to REPORT_LUN
bash-3.00#
SO is Solaris 10 and I have installed recommended pathes:
118833-36 SunOS 5.10: Kernel patch
125100-10 SunOS 5.10: Kernel patch
120011-14 SunOS 5.10: Kernel patch
127111-01 SunOS 5.10: Kernel patch
119130-33 SunOS 5.10: Sun Fibre Channel Device Drivers (only necessary for Leadville Stack driver)
125184-04 SunOS 5.10: Sun Fibre Channel Device Drivers.
120222-21 SunOS 5.10: Emulex-Sun LightPulse fibre channel adapter driver v2.20k (only required for Emulex HBAs running Leadville)
125166-06 SunOS 5.10: Qlogic ISP fibre channel device driver v2.22 (only required for Qlogic HBAs running Leadville)
122640-05 SunOS 5.10: zfs genesis patch (require for zfs)
120473-12 SunOS 5.10: lib nss ldap PAM zfs patch (require for zfs)
119090-24 SunOS 5.10: iSCSI device driver and utilities
Also I have modified /etc/system adding those lines:
set ssd:ssd_max_throttle=20
forceload: drv/ssd
bash-3.00# modinfo |grep qlc
66 7ba7e000 ce1f8 282 1 qlc (SunFC Qlogic FCA v20070717-2.22)
bash-3.00# luxadm -e port
/devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
bash-3.00# luxadm qlgc
Found Path to 2 FC100/P, ISP2200, ISP23xx Devices
Opening Device: /devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl
Detected FCode Version: QLA2460 Host Adapter FCode(SPARC): 1.26 05/17/07
Opening Device: /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl
Detected FCode Version: QLA2460 Host Adapter FCode(SPARC): 1.26 05/17/07
Complete
bash-3.00# luxadm -e port
/devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
bash-3.00# luxadm -e dump_map /devices/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0:
devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 610f13 0 5006048c52a5b746 5006048c52a5b746 0x0 (Disk device)
1 617613 0 2100001b320122b7 2000001b320122b7 0x1f (Unknown Type,Host Bus Adapter)
bash-3.00# luxadm -e dump_map /devices/ssm@0,0/pci@19,600000/SUNW,qlc@2/fp@0,0:
devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 620f13 0 5006048c52a5b749 5006048c52a5b749 0x0 (Disk device)
1 627613 0 2100001b32014eb8 2000001b32014eb8 0x1f (Unknown Type,Host Bus Adapter)

Check the configuration on the EMC side. This error message is the heart of the problem:
"Unsupported LUN Addressing method 40 in response to REPORT_LUN"
A quick Googling leads me to believe this means you're trying to assign a LUN ID higher than 255 to the host.
Best of luck!

EMC - Certificate status could not be determined because revocation check failed.

I've exhausted my resources on this issue and am reaching out for some assistance. I have setup Server 2008 R2 Enterprise SP1, running Exchange 2010 SP1. In EMC I have successfully imported a GoDaddy SSL certificate. Although I am receiving the message -
"The certificate status could not be determined because the revocation check failed."
Here are the steps I've taken to troubleshoot this so far:
[PS] C:\Users\Administrator\Desktop>netsh winhttp show proxy
Current WinHTTP proxy settings:
Direct access (no proxy server).
As you can see, direct access. Which is true, no proxy's on this network.
For good measure, I'll dump the urlcache.
certutil -urlcache ocsp delete
certutil -urlcache crl delete
Both return 0, reboot server.
Comes back up, same message in EMC.
From PS, I test exactly what its getting from GoDaddy.
[PS] C:\Users\Administrator\Desktop>certutil -f -urlfetch -verify mail.fluxlabs.net.crt
Issuer:
SERIALNUMBER=07969287
CN=Go Daddy Secure Certification Authority
OU=http://certificates.godaddy.com/repository
O=GoDaddy.com, Inc.
L=Scottsdale
S=Arizona
C=US
Subject:
CN=mail.fluxlabs.net
OU=Domain Control Validated
O=mail.fluxlabs.net
Cert Serial Number: 27b60918638e0d
dwFlags = CA_VERIFY_FLAGS_ALLOW_UNTRUSTED_ROOT (0x1)
dwFlags = CA_VERIFY_FLAGS_IGNORE_OFFLINE (0x2)
dwFlags = CA_VERIFY_FLAGS_FULL_CHAIN_REVOCATION (0x8)
dwFlags = CA_VERIFY_FLAGS_CONSOLE_TRACE (0x20000000)
dwFlags = CA_VERIFY_FLAGS_DUMP_CHAIN (0x40000000)
ChainFlags = CERT_CHAIN_REVOCATION_CHECK_CHAIN (0x20000000)
HCCE_LOCAL_MACHINE
CERT_CHAIN_POLICY_BASE
-------- CERT_CHAIN_CONTEXT --------
ChainContext.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
ChainContext.dwErrorStatus = CERT_TRUST_REVOCATION_STATUS_UNKNOWN (0x40)
ChainContext.dwErrorStatus = CERT_TRUST_IS_OFFLINE_REVOCATION (0x1000000)
SimpleChain.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
SimpleChain.dwErrorStatus = CERT_TRUST_REVOCATION_STATUS_UNKNOWN (0x40)
SimpleChain.dwErrorStatus = CERT_TRUST_IS_OFFLINE_REVOCATION (0x1000000)
CertContext[0][0]: dwInfoStatus=102 dwErrorStatus=1000040
Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=S
cottsdale, S=Arizona, C=US
NotBefore: 8/20/2011 7:49 PM
NotAfter: 8/20/2012 7:16 PM
Subject: CN=mail.fluxlabs.net, OU=Domain Control Validated, O=mail.fluxlabs.net
Serial: 27b60918638e0d
SubjectAltName: DNS Name=mail.fluxlabs.net, DNS Name=www.mail.fluxlabs.net
33 49 57 5d 6e d8 6b aa b9 61 73 95 44 07 c9 2e 55 6e 47 10
Element.dwInfoStatus = CERT_TRUST_HAS_KEY_MATCH_ISSUER (0x2)
Element.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
Element.dwErrorStatus = CERT_TRUST_REVOCATION_STATUS_UNKNOWN (0x40)
Element.dwErrorStatus = CERT_TRUST_IS_OFFLINE_REVOCATION (0x1000000)
---------------- Certificate AIA ----------------
Verified "Certificate (0)" Time: 4
[0.0] http://certificates.godaddy.com/repository/gd_intermediate.crt
---------------- Certificate CDP ----------------
Expired "Base CRL (05)" Time: 4
[0.0] http://crl.godaddy.com/gds1-55.crl
---------------- Base CRL CDP ----------------
No URLs "None" Time: 0
---------------- Certificate OCSP ----------------
Expired "OCSP" Time: 4
[0.0] http://ocsp.godaddy.com/
CRL (null):
Issuer: CN=Go Daddy Validation Authority, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
e5 53 19 6c 54 87 8c 62 23 1b b9 11 e1 d8 3d 3f b2 04 77 3f
Issuance[0] = 2.16.840.1.114413.1.7.23.1
Application[0] = 1.3.6.1.5.5.7.3.1 Server Authentication
Application[1] = 1.3.6.1.5.5.7.3.2 Client Authentication
CertContext[0][1]: dwInfoStatus=102 dwErrorStatus=0
Issuer: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US
NotBefore: 11/15/2006 8:54 PM
NotAfter: 11/15/2026 8:54 PM
Subject: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=
Scottsdale, S=Arizona, C=US
Serial: 0301
7c 46 56 c3 06 1f 7f 4c 0d 67 b3 19 a8 55 f6 0e bc 11 fc 44
Element.dwInfoStatus = CERT_TRUST_HAS_KEY_MATCH_ISSUER (0x2)
Element.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
---------------- Certificate AIA ----------------
No URLs "None" Time: 0
---------------- Certificate CDP ----------------
Verified "Base CRL" Time: 4
[0.0] http://certificates.godaddy.com/repository/gdroot.crl
---------------- Base CRL CDP ----------------
No URLs "None" Time: 0
---------------- Certificate OCSP ----------------
Expired "OCSP" Time: 4
[0.0] http://ocsp.godaddy.com
CRL (null):
Issuer: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US
da 1e d5 63 5c 05 58 50 4e db d2 4e e8 9d 28 9d c4 36 b3 1e
Application[0] = 1.3.6.1.5.5.7.3.1 Server Authentication
Application[1] = 1.3.6.1.5.5.7.3.2 Client Authentication
Application[2] = 1.3.6.1.5.5.7.3.4 Secure Email
Application[3] = 1.3.6.1.5.5.7.3.3 Code Signing
CertContext[0][2]: dwInfoStatus=109 dwErrorStatus=0
Issuer: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US
NotBefore: 6/29/2004 12:06 PM
NotAfter: 6/29/2034 12:06 PM
Subject: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US
Serial: 00
27 96 ba e6 3f 18 01 e2 77 26 1b a0 d7 77 70 02 8f 20 ee e4
Element.dwInfoStatus = CERT_TRUST_HAS_EXACT_MATCH_ISSUER (0x1)
Element.dwInfoStatus = CERT_TRUST_IS_SELF_SIGNED (0x8)
Element.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
---------------- Certificate AIA ----------------
No URLs "None" Time: 0
---------------- Certificate CDP ----------------
No URLs "None" Time: 0
---------------- Certificate OCSP ----------------
No URLs "None" Time: 0
Application[0] = 1.3.6.1.5.5.7.3.1 Server Authentication
Application[1] = 1.3.6.1.5.5.7.3.2 Client Authentication
Application[2] = 1.3.6.1.5.5.7.3.4 Secure Email
Application[3] = 1.3.6.1.5.5.7.3.3 Code Signing
Exclude leaf cert:
b1 04 4b 90 a1 d3 48 de 46 bd d7 50 20 e3 44 b8 3f 68 39 f7
Full chain:
68 36 4d 37 2e 96 bd d2 aa 77 3f d0 e8 78 a9 e6 68 bd 7d 71
Verified Issuance Policies:
2.16.840.1.114413.1.7.23.1
Verified Application Policies:
1.3.6.1.5.5.7.3.1 Server Authentication
1.3.6.1.5.5.7.3.2 Client Authentication
Cert is an End Entity certificate
ERROR: Verifying leaf certificate revocation status returned The revocation function was unable to check revocation because the revocation server was
offline. 0x80092013 (-2146885613)
CertUtil: The revocation function was unable to check revocation because the revocation server was offline.
CertUtil: -verify command completed successfully.
As you can see, the "revocation server is offline."
So I run the same test from another server on the LAN.
Verified Issuance Policies:
2.16.840.1.114413.1.7.23.1
Verified Application Policies:
1.3.6.1.5.5.7.3.1 Server Authentication
1.3.6.1.5.5.7.3.2 Client Authentication
Cert is an End Entity certificate
Leaf certificate revocation check passed
CertUtil: -verify command completed successfully.
It passes. The server's firewall has been disabled. DNS cache has been cleared. I have verified everything I can, and still failing to verify.

[PS] C:\Users\Administrator\Desktop>Get-ExchangeCertificate |fl
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.Acces
trol.CryptoKeyAccessRule}
CertificateDomains : {mail.fluxlabs.net, www.mail.fluxlabs.net}
HasPrivateKey : True
IsSelfSigned : False
Issuer : SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy
, Inc.", L=Scottsdale, S=Arizona, C=US
NotAfter : 8/20/2012 7:16:57 PM
NotBefore : 8/20/2011 7:49:30 PM
PublicKeySize : 2048
RootCAType : ThirdParty
SerialNumber : 27B60918638E0D
Services : IMAP, POP, IIS, SMTP
Status : RevocationCheckFailure
Subject : CN=mail.fluxlabs.net, OU=Domain Control Validated, O=mail.fluxlabs.net
Thumbprint : 3349575D6ED86BAAB96173954407C92E556E4710
[PS] C:\Users\Administrator\Desktop>Enable-ExchangeCertificate -Thumbprint 3349575D6ED86BAAB96173954407C92E556E4710 -Services POP,IMAP,SMTP,IIS
The command has already been executed. Yes, I have seen those sites. Neither have worked. Like I said, it is directly connected; and no proxies are set.
-- Jeremy MCSpadden Flux Labs

Exchange 2010 sp2 emc initialization error using "kerberos" authentication failed

We use exchange 2010 SP2.
We have 2 management stations, both w2k8 R2 SP1.
I have one mangement station on which the emc and ems works ok.
On the other management staiton (which is also in another ad site) the emc and ems don't work.
I get the following error message : The attempt to connect to
http://fqdnCasServer/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
I have checked the time on the management station and on the exchange server and this is ok.
It is not a permissions issue because the user functions ok on the other management station.
On the bad management station I can open the emc once and after a minute I get an error message and the message access denied. From then on I can't connect any more.
What am I doing wrong?
Anyone any tips?
Thanks,
JB

This is what I get in the eventlog of the bad management station.
Log Name:      MSExchange Management
Source:        MSExchange CmdletLogs
Date:          1/10/2012 11:39:27
Event ID:      6
Task Category: (1)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.domain.com
Description:
The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Get-ExchangeServer
{Identity=Servername}
Domain/ou/ou/ou/ou/username
Exchange Management Console-Local
3080
22
00:00:00.3593888
View Entire Forest: 'True', Configuration Domain Controller: 'FQDN DC', Preferred Global Catalog: 'FQDN DC', Preferred Domain Controllers: '{ FQDN DN }'
Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'FQDN MGMTSTATION' couldn't be found on 'FQDN DC'.
Context
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange CmdletLogs" />
    <EventID Qualifiers="49152">6</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-01T09:39:27.000000000Z" />
    <EventRecordID>11</EventRecordID>
    <Channel>MSExchange Management</Channel>
    <Computer>FQDN MGMT STATION</Computer>
    <Security />
</System>
<EventData>
    <Data>Get-ExchangeServer</Data>
    <Data>{Identity=MGMT STATION}</Data>
    <Data>domain/ou/ou/ou/ou/username</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>Exchange Management Console-Local</Data>
    <Data>3080</Data>
    <Data>
    </Data>
    <Data>22</Data>
    <Data>00:00:00.3593888</Data>
    <Data>View Entire Forest: 'True', Configuration Domain Controller: 'FQDN DC', Preferred Global Catalog: 'FQDN DC', Preferred Domain Controllers: '{ FQDN DC }'</Data>
    <Data>Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'FQDN MGMT STATION' couldn't be found on 'FQDN DC'.</Data>
    <Data>Context</Data>
    <Data>
    </Data>
</EventData>
</Event>

Exchange 2010 EMC Failed Initialization

Hi
Server 2008 64bit SP2 running on hyper V
Just done an install of exch2010 on a vanilla test DC 2008, passed all the readiness checks after installing all the bits and pieces. I also ran the following:
1) winrm quickconfig
2) For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:
sc config NetTcpPortSharing start= auto
ServerManagerCmd -ip Exchange-Typical.xml -Restart
all seemed to install OK but when I try and start the EMC when clicking on the "Microsoft Exchange ON-Premises" I get an initialization failure with the following detail:
The following error occured when searching for On-Premises exchange server:
[testdc08.company.com] Connecting to remote server failed with the following message : The WSMan client
cannot process the request. Proxy is not supported under http transport. Change the transport to https and
specify valid proxy information and try again. For more information , see the about troubleshooting help topic
I understand this stuff is to do with remote managing exchange servers across the internet, but in my case I am trying to simply access the exchange server (on the DC) from the DC???
Can anyone shed light on this install of doom,
thanks

Dear All,
I have faced same issue with my exchange 2010 server on Windows 2008 R2 O/S. There is some problem in my winhttp settings (proxyycfg). To resolve this issue I deleted WinHttpSettings from registry keys. It will reset it to default. Below is the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings
-->Delete WinHttpSettings
Regards,
Khurram Awal Khan
Senior System Engineer
Alnafitha Int.
Hi Khurram
This worked for use as well. Thank you

EMC initializtion failed

Similar Messages

Maybe you are looking for