Exchange Server 2010 autodisovery fail

Hi
we have set up new exchange server recently, after we configured client side , we found that global address book can not update properly, we have try manually update from both client side and server side, it doesn't help, however the outlook web account
is all good to run, further i found when we setup client side outlook, if we UN-select "use cached exchange mode" , it works well, also we run test E-mail Auto Configuration. and it shows tls=no,spa=no,failed(0x800CCC0D). i feel like some miss configure
on the server.any solution for that?

Hi Kulolo,
Please verify the email account type, Hotmail, Exchange or IMAP etc?
For the error code 0x800ccc0d, please follow the troubleshooting steps in KB below:
Error occurs when you send or receive an email message in Outlook or Outlook Express
http://support.microsoft.com/kb/813514/en-us
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Exchange server 2010 backup fails

My exchange server backup keep failing
the exchange server 2010 two node dag
netbackup 7.6
I have contacted Symantec support. They believed it's Exchange server problem as "Vssadin list writers"
show Microsoft Exchange writer Retryable error
Any help?

Hi,
Please try to restart Information Store service for testing.
Also try to refer following blogs:
Troubleshooting Exchange 2007 VSS Backups
http://blogs.technet.com/b/exchange/archive/2008/08/25/3406172.aspx
Exchange and VSS -- My Exchange writer is in a failed retryable state
http://blogs.technet.com/b/timmcmic/archive/2012/03/11/exchange-and-vss-my-exchange-writer-is-in-a-failed-retryable-state.aspx
Thanks
Mavis Huang
TechNet Community Support

Exchange Server 2010 - Authentication fails with DC

I have implemented Windows Server 2008 R2 Active Directory on Server: DC1
I have Implemented Exchange Server 2010 SP2 on Server: EMLSERVER
Previously MDeamon 5.5 was using for Messaging Services.
Manager told me he want only email server to be available after office hours.
For Exchange Server 2010 we have to power on two servers AD and EXCH.
For This reason i install AD on Exchange Server 2010 and Transfer all Roles from DC1 to EMLSERVER.
Now EMLSERVER is our AD and EXCH, and DC1 is our ADC.
To check this configuration i power off current ADC old DC (DC1).
when i try to test OWA, it was not working, and i get HTTP 500 Error, i try to troubleshoot it and finally after enabling Form Based Authentication Service HTTP 500 error has been resolved and i get OWA Page there when i try to Authenticate with Username
and Password i have got HTTP 400 error and i am sucked now.
Can anyone suggest what should i do now.

The Requirement is that I have to provide a solution that is equivalent to MDeamon 5.5, where Company have just one DC which is use for authentication and group policy on Windows and another server which is MDeamon email server.
After office hours they power off DC and just email server is power on.
Therefore new solution must fulfill the same requirement, and in this scenario I have to put DC and Email together so that there is no power overhead.
1- Yes new DC which is together with Exchange is Global Catalog.
2- All Microsoft Exchange services are running.
3- There is no smart card authentication, there is just User/Pass require to authenticate.
4- Old DC/ Current ADC has been powered off after verifying transfer of all AD roles.
5- Previously I have installed DC on DC1 server and Exchange 2010 on EMLSERVER and it was working fine.

Exchange server 2010 SP3 Fails to install

I have just installed Exchange sp3 and has failed at the CAS update this has left a few connectivity issues.
Extract from the log file
[1] The following 1 error(s) occurred during task execution:
[1] 0. ErrorRecord: The virtual directory 'Autodiscover' already exists under 'CALLAN-server.local/Default Web Site'.
Parameter name: VirtualDirectoryName
[1] 0. ErrorRecord: System.ArgumentException: The virtual directory 'Autodiscover' already exists under server.local/Default Web Site'.
Parameter name: VirtualDirectoryName
[1] [ERROR] The following error was generated when "$error.Clear();
          Update-AutodiscoverVirtualDirectoryVersion -DomainController $RoleDomainController;
          $existingVDirs = get-AutodiscoverVirtualDirectory -Server $RoleFqdnOrName -DomainController $RoleDomainController;
          if ($existingVDirs -ne $null)
            $existingVDirs | set-AutodiscoverVirtualDirectory -WSSecurityAuthentication:$true -DomainController $RoleDomainController;
          else
            new-AutodiscoverVirtualDirectory -WSSecurityAuthentication:$true -DomainController $RoleDomainController;
        " was run: "The virtual directory 'Autodiscover' already exists under server.local/Default Web Site'.
Parameter name: VirtualDirectoryName".
[1] [ERROR] The virtual directory 'Autodiscover' already exists under 'CALLAN-server.local/Default Web Site'.
Parameter name: VirtualDirectoryName
[1] [ERROR-REFERENCE] Id=ServicesComponent___a8409d9e1e024948a9cf2805368de7dd Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[1] Setup is stopping now because of one or more critical errors.
[1] Finished executing component tasks.
1] Ending processing Install-ClientAccessRole
Hope someone can help I have been at this for quite some time
Thanks in advance

This explains something, when you run Get-AutodiscoverVirtualDirectory it gives nothing so looks like SP3 installer is also not able to find and trying to create a new autodiscover virtual directory but fails saying its already there.
If you try to run Remove-AutodiscoverVirtualDirectory or New-AutodiscoverVirtualDirectory those would give errors too.
I believe if you go to IIS - > Default Web Site -> Autodiscover you should be able to see it there but looks like it is in inconsistent state.
You won't be able to reset the Autodiscover virtual directory by following Resetting
Autodiscover Virtual Directory but worth trying it.
If not,
- Go to IIS and remove the autodiscover
- Create one by following Create an Autodiscover Virtual Directory
- Go to CMD prompt and run the IISReset
- Run Get- AutodiscoverVirtualDirectory and make sure you see it
- Run the SP3 upgrade
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange server 2010 console not opening, inialization failed

hi,
exchange server 2010 console not opening, inialization failed when i have upgraded service pack to sp1.
please suggest asap or u can reach me @
[email protected]
[email protected]
+918750003544

Even I found the same issue once, and then I realised that the SP and RU should be same in exchange sever and the machine where the issue is.
Could you please check the same if that machine has the same Sp and RU, if not, please upgrade the same? I bet it will start working
Regards,
ASP20
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Event logs fails to start on Exchange Server 2010

My Exchange server 2010 R2 SP1 Enterprise single server is down. All exchange services fail to start. It appears like the Microsoft Exchange Active Directory Topology service isn't starting which is a dependency for all other services.
The error I get when trying to start this service is:
Windows could not start the Microsoft Exchange Active Directory Topology on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code
-2147024882
To make matters worse, the event viewer is not starting either.
When trying to start the Windows Event Log, I get the error:
Windows could not start the Windows Event Log service on Local Computer. Displays Error code 5
This is running on a Windows Server 2008 R2 SP1 Standard box.
Any assistance is appreciated.

When trying to start the Windows Event Log, I get the error:
Windows could not start the Windows Event Log service on Local Computer. Displays Error code 5
Hi,
Based on this error, this problem happens if any of the following conditions are true:
The built-in security group EventLog does not have permissions on the folder %SystemRoot%\System32\winevt\Logs
The Local Service account does not have default permissions on the following registry key: HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability
To solve this problem, we need to restore the default permissions in the list below on %SystemRoot%\System32\winevt\logs.
Authenticated user - List folder/read data, Read attributes, Read Extended attributes, Read permissions
Administrators - Full control
SYSTEM - Full control
EventLog - Full control
Please try the following methods:
Method 1
To restore the default permissions on folder %SystemRoot%\System32\winevt\logs, follow these steps.
Right-click on %SystemRoot%\System32\winevt\logs and select Properties.
Select the Security tab.
Click Edit button and click the Add button in the permissions dialog box.
In Select users, computers, or Groups dialog box ensure that under object types Built in Security Principals and the location as local computer name is selected.
Enter the object name as "NT SERVICE\EventLog" without quotes. And click OK. This group should have full control on the folder.
Once EventLog group is added add the rest of the groups with above mentioned permissions.
Method 2
Identify a Windows Server 2008 machine with default permissions.
Click Start, and then type cmd in the Start Search box.
In the search results list, right-click Command Prompt, and then click Run as Administrator.
When you are prompted by User Account Control, click Continue.
Type the command CD %SystemRoot%\SYSTEM32.
Once the working directory is changed to %SystemRoot%\SYSTEM32 type the command icacls winevt\* /save acl /T.
This will save a file named ACL in %SystemRoot%\SYSTEM32. Copy this file to the C: drive on the problem computer.
On the problem computer, open command prompt with administrator privileges (refer to previous steps 1-3).
Change the working directory to %SystemRoot%\SYSTEM32.
Execute the command icacls winevt\ /restore acl.
Default permissions on the registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability should be:
CREATOR OWNER - Full control
SYSTEM - Full control
LOCAL SERVICE - Query Value, Set Value, Create Subkey, Notify and Delete
Administrators - Full control
Users - Read
To set the permission on this registry key:
Click the Start menu, select Run and type Regedit.
Go to the location HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability.
From the Edit menu click Permissions.
Add the permissions for the accounts as listed above.
In addition, Exchange 2010 SP1 and SP2 are end of support.
https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=exchange%20server%202010&Filter=FilterNO
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Windows Server 2008 R2 Standard "Certificate Authority Service" / Exchange Server 2010 EMC not starting and no AD connectivity for authentication.

Hello,
I am a new IT Manager at this company and need assistance big time. Their environment looks as follows:
Server 1. Domain Controller Server (Windows Server 2008 R2 Standard) running active directory.
Server 2. Email Server (Windows Server 2008 R2 Standard) running Exchange Server 2010 .
* Note. No back ups to work with aside from whats mentioned below.
DC had a virus infection causing a lot of issues on the shared network drives 2 days ago locking up all the files with a crypto ransom virus. Running Avast suppressed the infection. Had to recover the file shares which luckily had a back up.
The issue is that the Exchange Server 2 post this lost connectivity with the AD Server 1. Exchange Server 2 when launching EMC could not launch the console stating the following:
"No Exchange servers are available in any Active Directory sites. You can’t connect to remote
Powershell on a computer that only has the Management Tools role installed."
Shortly after I found that it is possible the EMC launcher was corrupt and needed to be reinstalled following another blog post. I deleted the exchange management console.msc per instructions only to discover I couldnt relaunch it because there was
no way how. So I copied another msc file that happened to be on the DC Server 1 back to Exchange Server 2 and got it to launch again.
Another post said that it might be an issue with the Domain Account for the Computer, so to delete it in the AD Server 1 only to find that rejoining it from Exchange Server 2 using Computer>Properties> Chage Settings > Change is greyed out because
it is using the Certificate Authority Service.
I tried manually re-adding the computer in AD and modeling permissions after another server in group settings but no go. After this I was unable to login to the Exchange Server 2 with domain accounts but only local admin, receiving the following Alert:
"The Trust Relationship between this workstation and primary domain failed."
I tried running the Power Shell tools on Exchange Server 2 to rejoing and to reset passwords for domain accounts as noted in some other blogs but no luck as the Server 2 could not make the connection with Server1 or other errors it kept spitting out.
I also during the investigation found the DNS settings were all altered on both the Server 1 and Server 2 which I luckily was able to change back to original because of inventorying it in the beginning when I started.
I need help figuring out if I need to rejoin the Exchange Server 2 manually by disabling the Certificate Authority Service (or removing the CA as listed here:
https://social.technet.microsoft.com/Forums/exchange/en-US/fb23deab-0a12-410d-946c-517d5aea7fae/windows-server-2008-r2-with-certificate-authority-service-to-rejoin-domain?forum=winserversecurity
and getting exchange server to launch again. (Mind you I am relatively fresh to server managing) Please help E-Mail has been down for a whole day now!
Marty

I recommend that you open a ticket with Microsoft Support before you break things more.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

Exchange Server 2010: Undeliverable Message

Dear All,
We are using exchange server 2010 to send a email to a client, however, we got this message back. How can i solve this problem?
Thanks for your attention and help!
次の受信者またはグループへの配信に失敗しました:
[email protected] 受信者の電子メールプロバイダーによって拒否されたため、メッセージを配信できませんでした。
メッセージは次の組織に拒否されました。BL2FFO11FD039.mail.protection.outlook.com。
管理者向けの診断情報:
生成サーバー: xxxx.com
[email protected] BL2FFO11FD039.mail.protection.outlook.com #<BL2FFO11FD039.mail.protection.outlook.com #5.7.0 smtp;550 5.7.0 Relay Access Denied> #SMTP#
元のメッセージヘッダー:
Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.241)
by exch.xxxx.com (192.168.10.32) with Microsoft SMTP Server (TLS)
id 14.3.210.2; Sun, 19 Oct 2014 22:36:47 -0700
Received: from BN1AFFO11FD049.protection.gbl (10.58.52.31) by
BN1AFFO11HUB044.protection.gbl (10.58.52.155) with Microsoft SMTP Server
(TLS) id 15.0.1049.20; Mon, 20 Oct 2014 05:36:44 +0000
Received: from mgcserv4.magsaysay.com.ph (203.167.92.249) by
BN1AFFO11FD049.mail.protection.outlook.com (10.58.53.64) with Microsoft SMTP
Server id 15.0.1049.20 via Frontend Transport; Mon, 20 Oct 2014 05:36:43
+0000
Received: from Crystal ([203.167.92.232]) by
mgcserv4.magsaysay.com.ph (Lotus Domino Release 8.5.3) with ESMTP id
2014102013364607-10992 ; Mon, 20 Oct 2014 13:36:46 +0800
X-TM-IMSS-Message-ID: <[email protected]>
Received: from na01-bl2-obe.outbound.protection.outlook.com ([65.55.169.54])
by magsaysay.com.ph ([203.167.92.232]) with ESMTP (TREND IMSS SMTP Service
7.0; TLS: TLSv1/SSLv3,256bits,AES256-SHA) id 26975997000186d5 ; Mon, 20 Oct
2014 13:40:58 +0800
Received: from BL2FFO11FD041.protection.gbl (10.173.160.33) by
BL2FFO11HUB022.protection.gbl (10.173.161.46) with Microsoft SMTP Server
(TLS) id 15.0.1049.20; Mon, 20 Oct 2014 05:36:36 +0000
Received: from mail.xxxx.com (216.81.51.170) by
BL2FFO11FD041.mail.protection.outlook.com (10.173.161.137) with Microsoft
SMTP Server (TLS) id 15.0.1039.16 via Frontend Transport; Mon, 20 Oct 2014
05:36:36 +0000
Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.236)
by exch.xxxx.com (192.168.10.32) with Microsoft SMTP Server (TLS)
id 14.3.210.2; Sun, 19 Oct 2014 22:36:28 -0700
Received: from BY2FFO11FD056.protection.gbl (10.1.14.33) by
BY2FFO11HUB055.protection.gbl (10.1.14.244) with Microsoft SMTP Server (TLS)
id 15.0.1039.16; Mon, 20 Oct 2014 05:36:15 +0000
Received: from mailgate.zzz.com (14.16.28.51) by
BY2FFO11FD056.mail.protection.outlook.com (10.1.15.193) with Microsoft SMTP
Server id 15.0.1049.20 via Frontend Transport; Mon, 20 Oct 2014 05:36:13
+0000
X-AuditID: c0a81e07-b7f5e6d000000b4e-4d-54449f4b6588
Received: from UNER2.zzz.com (unr2.zzz.com
[192.168.30.13]) by mailgate.zzz.com (Symantec Messaging Gateway) with
SMTP id CA.40.02894.B4F94445; Mon, 20 Oct 2014 13:36:11 +0800 (HKT)
Received: from UN2.zzz.com ([::1]) by UNR2.zzz.com
([::1]) with mapi id 14.01.0438.000; Mon, 20 Oct 2014 13:36:11 +0800
From: Yukihiro <[email protected]>
To: Simonu <[email protected]>, Charles
<[email protected]>
CC: Miln <[email protected]>, FSA
<[email protected]>
Subject: Re: unia s maual / MV Kett Iand
Thread-Topic: unaa sh ml / MVlettsland
Thread-Index: Ac/sEV9D2LsdkU5fRkW0Rd1v4PsvSQAFlzIA
Date: Mon, 20 Oct 2014 05:36:10 +0000
Message-ID: <D06AC01C.21F27%[email protected]>
References: <[email protected]>
In-Reply-To: <[email protected]>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.2.140509
x-originating-ip: [192.168.30.123]
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJIsWRmVeSWpSXmKPExsVyYIUcr673fJcQg8bHChbzDrexW/R3vGG2
OPK31GLjrinMDiwePbO6WAIYo7hsUlJzMstSi/TtErgy/my9w1Zw2LJi74lOxgbGd+ZdjJwc
EgImEq27r7NA2GISF+6tZ+ti5OIQErjIKHF27jdmCGcCo8SpVw3MIFVsAtoS21rusILYIgKR
En8nzgKzmQXiJL7sPAc2SVjAWOLni0tsEDUmEvNOdzNC2EYSp55dZgKxWQRUJa5unwBm8wro
SVzdtgNsvpBAhETH9lawOZxA808+PwxmMwJd9/3UGiaIXeISlyYvYoO4WkBiyZ7zzBC2qMTL
x//A7hEFmtnc9YYRIq4kcfbZAaA5HEC9wRJ3mzgg1gpKnJz5hGUCo9gsJFNnIVTNQlIFEdaU
WL9LH6JaUWJK90N2CFtDonXOXCjbWuJq40IWZDULGDlWMQrlJmbmGOqV5mXqJhZnJuol5+du
YoREJ/sOxg9NlocYBTgYlXh4pzi5hAixJpYVV+YeYpTgYFYS4f2XARTiTUmsrEotyo8vKs1J
LT7EyMTBKdXAKPV7/zEX5dgtO6cd8N8764+UCO+vDPaVj5LWF051+GIx3/pf/dHiA0Gn+Lia
by2Se/tyVqhMYGzs1CpNAcut2bfuLIhUOqbbIDv7buL74s/XWGIu27vcYoi+dJ9BSzA9WNnH
h1NVbn+SgEDAhsL6Cyvs48Ja+1InV76xt515//fJOSLapX/uKbEUZyQaajEXFScCAFed/I2s
AgAA
Return-Path: [email protected]
X-EOPAttributedMessage: 2
X-Forefront-Antispam-Report-Untrusted: CIP:14.1.28.51;CTRY:HK;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(428002)(189002)(66654002)(199003)(252514010)(76176999)(21056001)(71186001)(31966008)(106466001)(81156004)(77096002)(95666004)(54356999)(105586002)(4396001)(50986999)(15975445006)(86362001)(83506001)(107046002)(84326002)(19617315012)(36756003)(85852003)(53416004)(92726001)(15974865002)(19580395003)(19580405001)(44976005)(101416001)(16236675004)(92566001)(87836001)(85306004)(99396003)(2656002)(46102003)(120916001)(15202345003)(20776003)(30436002)(512874002);DIR:INB;SFP:;SCL:1;SRVR:BY2FFO11HUB055;H:mailgate.zzzz.com;FPR:;MLV:sfv;PTR:014168051.static.ctinets.com;MX:1;A:0;LANG:en;
X-Exchange-Antispam-Report-Test: UriScan:;UriScan:;UriScan:;
Received-SPF: None (protection.outlook.com: zzz.com does not designate
permitted sender hosts)
Authentication-Results: spf=none (sender IP is 203.167.92.249)
[email protected];
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-Matching-Connectors: 130582569966280204;(42405700-fa69-4020-a9c4-08d0e394d333);()
X-Forefront-Antispam-Report-Untrusted: CIP:216.81.51.170;CTRY:CA;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(10009020)(428002)(199003)(66654002)(252514010)(189002)(81156004)(106466001)(76176999)(54356999)(36756003)(77096002)(101416001)(53416004)(50986999)(105586002)(95666004)(31966008)(46102003)(20776003)(30436002)(19580395003)(4396001)(44976005)(19580405001)(16236675004)(6806004)(21056001)(71186001)(15974865002)(15202345003)(99396003)(84326002)(120916001)(15975445006)(83506001)(92726001)(92566001)(85852003)(86362001)(2656002)(87936001)(85306004)(107046002)(512874002)(19617315012);DIR:OUT;SFP:1101;SCL:1;SRVR:BL2FFO11HUB022;H:mail.xxx.com;FPR:;MLV:sfv;PTR:216.81.51.170.epikip.net;A:0;MX:1;LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BL2FFO11HUB022;UriScan:;
X-Forefront-PRVS: 03706074BC
X-MIMETrack: Itemize by SMTP Server on mgcserv4/mgc(Release 8.5.3|September 15, 2011) at
10/20/2014 01:36:46 PM,
Serialize by Router on mgcserv4/mgc(Release 8.5.3|September 15, 2011) at 10/20/2014
01:36:47 PM,
Serialize complete at 10/20/2014 01:36:47 PM
X-TNEFEvaluated: 1
Content-Type: multipart/alternative;
boundary="_000_D06AC01C21F27hzzzcom_"
Content-Language: ja-JP
X-Forefront-Antispam-Report: CIP:203.167.92.249;CTRY:PH;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(428002)(252514010)(189002)(66654002)(199003)(76176999)(54356999)(86362001)(15974865002)(50986999)(85852003)(92566001)(92726001)(19617315012)(512874002)(46102003)(85306004)(97736003)(99396003)(120916001)(33186001)(53416004)(44976005)(105586002)(19580405001)(106466001)(16236675004)(77096002)(81156004)(19580395003)(95666004)(31966008)(71186001)(107046002)(21056001)(101416001)(15202345003)(84676001)(68736004)(30436002)(87836001)(2656002)(20776003)(4396001)(6806004)(84326002)(83506001)(15975445006)(36756003)(72026002);DIR:INB;SFP:;SCL:1;SRVR:BN1AFFO11HUB044;H:mgcserv4.magsaysay.com.ph;FPR:;MLV:sfv;PTR:ErrorRetry;MX:1;A:0;LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1AFFO11HUB044;

Hi Shiloh,
According to your description, my understanding is that you send a message to external user(@xxx.com) fail.
Before going further, I'd like to ask the following question to narrow down the issue:
1. Could you send message to any other external user except xxx.com? like google.com,outlook.com.
2. Try to disable or bypass Transport Scanning in Forefront Protection 2010 and check if any helps.
You can refer to the following article to disable or bypass FPE:
http://social.technet.microsoft.com/wiki/contents/articles/407.how-to-disable-or-bypass-transport-scanning-in-forefront-protection-2010-for-exchange-server-fpe.aspx
Best regards,
Niko Cheng
TechNet Community Support

Problems installing Mailbox role on Exchange Server 2010 SP3

I am in the process of installing Exchange Server 2010 SP3 on a Windows Server 2012 server in order to migrate our existing Exchange 2003 server. Everything went well with the installation process until I went to add the Mailbox server role, which is giving
me the following error (from the log file):
[05/03/2013 21:58:09.0090] [1] Executing:
$wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
$manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
[05/03/2013 21:58:09.0105] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'TAM-FS2.tacomaartmuseum.org', Preferred Global Catalog: 'TAM-FS2.tacomaartmuseum.org', Preferred Domain
Controllers: '{ TAM-FS2.tacomaartmuseum.org }'
[05/03/2013 21:58:09.0105] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
[05/03/2013 21:58:09.0276] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
[05/03/2013 21:58:09.0344] [2] Process standard output:
[05/03/2013 21:58:09.0344] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
[05/03/2013 21:58:09.0347] [2] [ERROR] Unexpected Error
[05/03/2013 21:58:09.0347] [2] [ERROR] Process execution failed with exit code 87.
[05/03/2013 21:58:09.0350] [2] Ending processing Start-SetupProcess
[05/03/2013 21:58:09.0350] [1] The following 1 error(s) occurred during task execution:
[05/03/2013 21:58:09.0350] [1] 0. ErrorRecord: Process execution failed with exit code 87.
[05/03/2013 21:58:09.0350] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
[05/03/2013 21:58:09.0351] [1] [ERROR] The following error was generated when "$error.Clear();
$wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
$manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
" was run: "Process execution failed with exit code 87.".
[05/03/2013 21:58:09.0351] [1] [ERROR] Process execution failed with exit code 87.
[05/03/2013 21:58:09.0351] [1] [ERROR-REFERENCE] Id=MailboxComponent___13A8A6B7DE0A4fe3BEB5CB1D86105DA3 Component=EXCHANGE14:\Current\Release\PIM Storage\Content Indexing
[05/03/2013 21:58:09.0351] [1] Setup is stopping now because of one or more critical errors.
[05/03/2013 21:58:09.0351] [1] Finished executing component tasks.
[05/03/2013 21:58:09.0393] [1] Ending processing Install-MailboxRole
I've searched all over but can't seem to find any reference to "exit code 87" - does anyone have any ideas?
Thanks,
Matt

Error 87 -with these details below - and a fix. The situation that got me here by the way was an incomplete install that was uninstalled, then installed again.
[02/24/2014 06:49:06.0967] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'xxxxxxxxxxxxxxx', Preferred Global Catalog: 'xxxxxxxxxxxxxxxxxxxxxxxx', Preferred Domain Controllers:
'{ xxxxxxxxxxxxxxxxxxxxxxx }'
[02/24/2014 06:49:06.0967] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
[02/24/2014 06:49:06.0967] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
[02/24/2014 06:49:07.0592] [2] Process standard output:
[02/24/2014 06:49:07.0592] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
[02/24/2014 06:49:07.0592] [2] [ERROR] Unexpected Error
[02/24/2014 06:49:07.0592] [2] [ERROR] Process execution failed with exit code 87.
[02/24/2014 06:49:07.0592] [2] Ending processing Start-SetupProcess
[02/24/2014 06:49:07.0592] [1] The following 1 error(s) occurred during task execution:
[02/24/2014 06:49:07.0592] [1] 0. ErrorRecord: Process execution failed with exit code 87.
[02/24/2014 06:49:07.0592] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
[02/24/2014 06:49:07.0608] [1] [ERROR] The following error was generated when "$error.Clear();
          $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
          $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
          Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
        " was run: "Process execution failed with exit code 87.".
[02/24/2014 06:49:07.0608] [1] [ERROR] Process execution failed with exit code 87.
I found I could fix this by removing the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Microsoft-Exchange-Troubleshooters/Operational
and everything underneath it.
My guess is that wevtutil didn't like adding an event log where it already existed but was slightly different in setup (no idea how, exactly).
After 24 hours I'll try post again - giving things time to make sure they are actually working.

Exchange server 2010 redundancy using static IPs in different sites

Dear All;
We are facing a problem in Exchange server 2010 which is that we need to provide redundancy for two different sites which contain the same exchange databases using DAG but the issue is that if the main exchange server fails, users from the internet will
not be able to access the server because the main static IP is in the main site ...
========================================
My question is how to provide redundancy using two Global IPs in two different sites, and is there any consequences of doing such a setup?
========================================

Hi,
From your description, I would like to clarify the following things:
1. It is recommended to configure the IP Configuration for both the MAPI and Replication NIC on DAG nodes.
2. A site failure is managed differently from the types of failures that can cause a server or database failover. A site failure is considered to be a disaster recovery event, recovery should be manually performed and completed for the client service to
be restored and for the outage to end.
For more information, here is an article for your reference.
Switchovers and Failovers
http://technet.microsoft.com/en-us/library/dd298067(v=exchg.141).aspx
Besides, what do you mean by "global IPs"?
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange Server 2010 Installation

I am getting the following error while installing Exchange Server 2010 on Server 2008 R2. Following is the log file:
Summary: 3 item(s). 1 succeeded, 1 failed.
Elapsed time: 00:00:02
Preparing Setup
Completed
Elapsed Time: 00:00:00
Mailbox Role
Failed
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Error:
The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
(join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
} Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
-Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
-Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
/t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
was run: "Process execution failed with exit code 1.".
Process execution failed with exit code 1.
Elapsed Time: 00:00:02
Finalizing Setup
Cancelled

Hi,
Please make sure the account has required permissions: Schema Admins, Domain Admins, Enterprise Admins, and Organization Management.
And please check if you have meet the prerequisites for Exchange 2010 installation.
Exchange 2010 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.141).aspx
In addition to the prerequisites, we also need to prepare AD and domain for Exchange 2010.
Prepare Active Directory and Domains
http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
To narrow down the issue, I recommend you check the setup log to see if there is any clues.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange Server 2010 SP3 test environment - email flow to/from internet

Today I set up test environment for Exchange Server 2010 SP3 - domain controller running Windows Server 2008 R2 SP1, Exchange Server 2010 SP3 on Windows Server 2008 R2 SP1 and client computer running Windows 7 Pro SP1 x64 with Outlook Pro 2010 x64. These
machines are VMs on vSphere 5.0 cluster made of 4 esxi 5.0 hosts.
I have three years of experience in working with Exchange Server 2010 in my production environment but until recently I have not had enough resources to build a test environment. Does "testing" Exchange Server 2010 infrastructure have
a real life purpose considering the fact that only internal email flow is possible since authoritative SMTP accepted domain is not hosted anywhere thus not visible to outside world. This limited email flow combined with absence of possibility to test
ActiveSync, Outlook Anywhere, OWA from WAN, . . . really hurt and make Exchange Server rare technology that can not be tested completely before introducing something new into the production. Services that are not possible to test from the outside world are
useless and whole point of Exchange-like technologies is availability from anywhere and from whatever device.

I set up Internet Send Connector (by default this type of send connector uses DNS MX records to route email automatically). Having sent an email to my gmail account I did not receive it and in transport logs I saw that mx record was found successfully
but there is the following line:
2014-08-05T20:39:51.942Z,Internet Connector,08D17F000FE36010,1,,2a00:1450:4013:c01::1b:25,*,,"Failed to connect. Error Code: 10051, Error Message: A socket operation was attempted to an unreachable network 2a00:1450:4013:c01::1b:25"
I tried also to send an email to my production email address (we have Symantec Messaging Gateway which is used as a smart host (antispam,antimalware,content filter appliance)) but then error is:
2014-08-05T20:50:08.395Z,Internet Connector,08D17F000FE36019,1,,91.238.7.10:25,*,,"Failed to connect. Error Code: 10061, Error Message: No connection could be made because the target machine actively refused it 91.238.7.10:25"
Telnet from test exchange to 91.238.7.10 on port 25 also is not working.

Exchange server 2010 DAG failover

Hi team ,
We have configured exchange server 2010 in DAG environment .
We have added 3 mailbox server in DAG . but my active mailbox copy failed the database are failover to another passive copy server & status is mounted . after failover emails service are not working.
Note : We have also configured NLB on CAS server .All exchange servers placed in single AD site
Please suggest

Hi
So are all your exchange servers the same? settings?
have you tried to fail the DB back to its original server? all services started on the other server?

Exchange Server 2010 SP3 Databases are not mounting after the recovery process

Hi,
We are using Exchange server 2010 SP3 in our office. Databases are stored in an ISCSI drive mapped with the exchange. We are taking daily full backup of my Exchange server using Symantec Backup exe 2012. As a testing purpose I created a test environment
same like my existing live environment to check the disaster recovery and backup. Thankfully disaster recovery worked well and I am able to open the exchange management console and powershell. But I am not able to mount the recovered databases ending
with an error saying "Couldn't mount the database that you specified. Specified database: officialrecover; Error code:
An Active Manager operation failed.........." and even I am not able to use the utility eseutil.exe to the database with an error "access to source database failed with jet error 1811". I am able to create a new database and mount
it.
I am using Windows Server Ent 2008 R2 64 Bit with Exchange Server 2010 SP3 in the Live environment with 3 partitions called C (279 GB), E (4.46 TB, ISCSI), F (976 GB) in my Live environment.
For test it is Windows Server Ent 2008 R2 64 Bit with Exchange Server 2010 SP3 with 3 partitions C (240 GB), E (1.4 TB), & F (240 GB).
Please help me with your valid comments to solve and mount the database and close the issue for ever.
With Regards
Jay

Jared is correct that in essence the message is saying the DB cannot be found.
When you restored to your recovery server are all the paths the same, i.e. if the DB existed on E:\XYZ on the production server it must be the same on the recovery server
When you restored into the recovery site do you have AD restored into that site as well?
For the recovery server are you using iSCSI storage for it as well? If so am I correct to assume that you have copies of the databases just for use on this server and are not trying to reference the same instance of the DB from the production
and test/recovery server?
I have also seen an issue where DB's getting written to disk from Symantec mess up the header of the DB. If you want to validate that the DB is actually intact and accessible you might want to check out our DigiScope product
http://www.lucid8.com/product/digiscope.asp using a free DEMO license. If it works i.e. you are able to mount in DigiScope from same location where its failing on the recovery server we know the
DB your pointing at is good and accessible from the current path but something else is amiss in your configuration
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange Server 2010 autodisovery fail

Similar Messages

Maybe you are looking for