Exchange Server 2013 - LoadGen 2013

I am trying to make use of LoadGen 2013 in an Exchange 2013 environment. Initially I started with LoadGen on a different machine (same domain) and then moved LoadGen to the exchange server itself.
When I select the number of mailboxes greater than 20 I get an error message that it is fixing the user count to 20.
If I set it to 19 or 20 I dont get the message.
StoreBuilder.General Error: 0 : 12/01/2014 01:32:39 -- Diagnostic context (user: '87e4cd54-add7-4ca0-8365-66ee438a5b0a'):
distinguishedName 'CN=EXCHANGE1 CA868A55-LGU000042,OU=Exchange1Store,OU=Users,OU=LoadGen Objects,DC=NST,DC=NET', exchServerDn '/o=MCBP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE1', userDn '/o=MCBP/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=CA868A55-LGU000042', mailNickName 'CA868A55-LGU000042', emailAddress '[email protected]'.
StoreBuilder.General Error: 0 : 12/01/2014 01:32:39 -- Diagnostic context (user: '87e4cd54-add7-4ca0-8365-66ee438a5b0a'):
distinguishedName 'CN=EXCHANGE1 CA868A55-LGU000042,OU=Exchange1Store,OU=Users,OU=LoadGen Objects,DC=NST,DC=NET', exchServerDn '/o=MCBP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE1', userDn '/o=MCBP/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=CA868A55-LGU000042', mailNickName 'CA868A55-LGU000042', emailAddress '[email protected]'.
Engine.General Warning: 0 : 12/01/2014 01:32:39 -- Caught a non-fatal exception in executeTaskStub. The exception was handled by the task module: Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005,
ec=2423)
Diagnostic context:
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3644
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-12-01T09:32:39.9530000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 14
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: -1073606646
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 1380
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 2
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 12175
    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: /rpc/[email protected]:6001
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3644
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-12-01T09:32:39.9530000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 14
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 65536
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 1385
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 2
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 8
    Lid: 13976   dwParam: 0x0 Msg: EEInfo: prm[1]: Binary buffer[size=788]
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3644
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-12-01T09:32:39.9370000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 13
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 14
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 3001
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 1
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 12180
    Lid: 59505   StoreEc: 0x977
    Lid: 50544   ClientVersion: 15.0.805.0
    Lid: 52080   StoreEc: 0x977
    Lid: 51152
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
   at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
   at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, TimeSpan callTimeout,
Byte[] tenantHint)
   at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
WindowsIdentity windowsIdentity, String applicationId)
   at Microsoft.Exchange.Swordfish.Extensions.MapiCommon.MapiStoreUtil.<>c__DisplayClass2.<OpenMailbox>b__0()
   at Microsoft.Exchange.Swordfish.IL.ILUtil.DoTryFilterCatch(ThreadStart tryClause, Predicate`1 filterClause, Action`1 catchClause)
   at Microsoft.Exchange.Swordfish.Extensions.MapiCommon.MapiStoreUtil.OpenMailbox(User user, ConnectFlag connectFlags, OpenStoreFlag openStoreFlags)
   at Microsoft.Exchange.Swordfish.Extensions.StoreBuilder.Builder.EnsureMailboxStore(User user)
   at Microsoft.Exchange.Swordfish.Extensions.StoreBuilder.Builder.BuildInboxRules(User user)
   at Microsoft.Exchange.Swordfish.Extensions.StoreBuilder.Builder.BuildMailboxStore(User user)
Could you please let me know a solution.

Hi,
This is a RPC issue. Please try to edit the LegacyExchangeDN value from Exchange database in ADSIEdit.
Refer from this similar thread
https://social.technet.microsoft.com/Forums/en-US/b3c0eb67-cba6-4570-a563-ece482c3d06a/loadgen-2013-getting-mapiexceptionnetworkerror-unable-to-make-connection-to-server?forum=exchangesvradmin
If there is any further problem, please let me know.
Best Regards.

Similar Messages

Migrate Active Directory 2003 to 2012 R2 and Exchange Server 2007 to 2013.

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Md. Ramin Hossain

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Domain. For Exchange installation and upgrading to 2013, you need to make sure that your domain controllers can understand attributes of exchange 2013. Besides if you have DC/Exch on the same server which is 2003 is not supported. Because Windows Server
2003 is not supported.
Migrate your domain to at least 2008 R2 and then proceed with Exchange 2013.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Autodiscover Exchange Server 2007 and 2013 Coexistence

Hello
We are having some issues where some users are not being notified when their mailbox is being migrated to E2013.
Before 2013, we never had a load balanced solution for CAS in Exchange Server 2007 or a single name space.
Below is our current config
AutoDiscoverServiceCN : Server2K7CASpd
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {USChicago, UKLondon, SGSingapore}
AutoDiscoverServiceCN : Server2k7CASdr
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {USChicago, UKLondon, SGSingapore}
AutoDiscoverServiceCN : Server2013CASPD01
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {UKLondon}
AutoDiscoverServiceCN : Server2013CASPD02
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {UKLondon}
AutoDiscoverServiceCN : Server2013CASDR02
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {UKLondon}
AutoDiscoverServiceCN : Server2013CASDR01
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {UKLondon}
I believe that we should change the AutoDiscoverServiceInternalUri on the two 2007 CAS to ALSO be the same as our 2013 CAS.
We know that when Outlook is opened, Autodiscover will respond with any of the 6 available CAS, and we think that those Outlook clients that are misconfigured, are those that are not getting notified when their Mailbox is moved to E2013.
Thanks

We are also getting inconsistent results using the Test-OutlookWebServices PS
Test 1
Test-OutlookWebServices -Identity [email protected] | fl
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address [email protected].
Id : 1006
Type : Information
Message : The Autodiscover service was contacted at https://legacy.domain.local/Autodiscover/Autodiscover.xml.
Id : 1016
Type : Success
Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
time was 76 milliseconds.
Id : 1015
Type : Success
Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
time was 0 milliseconds.
Id : 1014
Type : Success
Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.domain.local/UnifiedMessaging/Service.asmx.
The elapsed time was 558 milliseconds.
Id : 1016
Type : Success
Message : [EXPR]-Successfully contacted the AS service at https://legacy.domain.local/EWS/Exchange.asmx. The elapsed time
was 46 milliseconds.
Id : 1015
Type : Information
Message : [EXPR]-The OAB is not configured for this user.
Id : 1014
Type : Information
Message : [EXPR]-The UM is not configured for this user.
Id : 1013
Type : Error
Message : When contacting https://mail.domain.local/Rpc received the error The remote server returned an error: (404) Not
Found.
Id : 1017
Type : Error
Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.domain.local/Rpc. The elapsed time was 93
milliseconds.
Id : 1006
Type : Success
Message : The Autodiscover service was tested successfully.
Id : 1021
Type : Information
Message : The following web services generated errors.
Contacting server in EXPR
Please use the prior output to diagnose and correct the errors.
Test 2
Test-OutlookWebServices -Identity [email protected] | fl
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address [email protected].
Id : 1006
Type : Information
Message : The Autodiscover service was contacted at https://legacy.Domain.local/Autodiscover/Autodiscover.xml.
Id : 1016
Type : Success
Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
time was 46 milliseconds.
Id : 1015
Type : Success
Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
time was 0 milliseconds.
Id : 1014
Type : Success
Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.Domain.local/UnifiedMessaging/Service.asmx.
The elapsed time was 15 milliseconds.
Id : 1016
Type : Success
Message : [EXPR]-Successfully contacted the AS service at https://legacy.Domain.local/EWS/Exchange.asmx. The elapsed time
was 78 milliseconds.
Id : 1015
Type : Information
Message : [EXPR]-The OAB is not configured for this user.
Id : 1014
Type : Information
Message : [EXPR]-The UM is not configured for this user.
Id : 1017
Type : Success
Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://legacy.Domain.local/Rpc. The elapsed time was 187
milliseconds.
Id : 1006
Type : Success
Message : The Autodiscover service was tested successfully.

Pre-requisites for upgrading exchange server 2007 to 2013(Multiple domain, single forest scenario)

Hi,
We have a forest with multiple Domains in it. Each domain has exchange servers installed in it. & All are installed in Single EXCAHNGE Organization.
One of the domain from the same respective forest has decided to upgrade their exchange server from 2007 to 2013.
So my basic query is, do we require to upgrade the service pack on all exchange servers(which is a pre-requisite) in the organisation forest wide or can we just upgrade the service pack on the exchange server in that specific Domain where this activity is
planned ?
As my organization has around 30 Exchange servers running across 10 Geo locations and are running exchange 2007 Sp1 & exchange 2010 SP1, So immediately installation of service pack in all servers would require additional time and approvals.
Is this possible to just upgrade exchange servers of My domain with latest service pack and install exchange 2013 in domain ????

Hi,
You will not be able to install Exchange 2013, until all of the Exchange Servers in your ORG has been brought up to a supported level.
In other words, your servers should be at:
* Exchange 2010 SP3 + RU5
* Exchange 2007 SP3 + RU13
So No, upgrading the servers only in Y"OUR" domain is not enough.
Martina Miskovic

Problems using Outlook 2013 with Exchange Server Small Business Server 2003

Hello,
We have just upgraded our Office suite from Office 2007 Pro to Office 2013 Pro. When I try to configure Outlook 2013 to connect to Exchange Server 6.5 (SMS 2003) I get an error "Outlook 2013 being blocked by current version of Exchange Server".
Outlook 2013 at present is not communicating with Exchange server 6.5
Are there any fixes I have to install on our SMS 2003 server to allow Outlook 2013 to work with SMS 2003 Exchange Server?
Any configuration changes I need to make? Any help is appreciated.
Thx
John G.
John Grace

Hi
Outlook 2013 is not supported with exchange 2003:
http://technet.microsoft.com/en-us/library/ee624351.aspx#section10
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange Server 2013 architecture

Hi
We are planning to migrate Exchange server 2010 to 2013 with DR.
Could anybody please tell me the recommended design for this..
I am planning to put two CAS Server, two mbx server in production site and one CAS server , one MBX server in DR site.
Enabling DAC in DR site.
This design is ok or else i need to put all roles in two server in production and one in dr..
Please advise...

Either option would leave you with at least one available server per role in the main site, except that with two servers, you would have two servers holding the role not affected by the failure of a given server.
For example, you have CAS1, CAS2, MBX1, MBX2.
If MBX1 fails, you still have two CAS.
If CAS1 fails you still have two MBX.
What's generally more of a problem is quorum for the DAG cluster.
If you loose the main site, the database mailboxes cannot mount in the DR because they would not "have quorum".
This is adressed at the bottom of this article:
http://technet.microsoft.com/en-us/library/dd979799(v=exchg.150).aspx
This also addresses the notion of "quorum":
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/exchange-2013-dag-dynamic-quorum-part1.html
You might address this (at a greater cost) with two DAG nodes in each site and with a FSW and alternate FSW.
Just a note: if you want all-around high availability, you would want to consider the CAS role as well (perhaps you have) which usually involves use of some form of load-balancing (or DNS round robin in a worse case scenario - not optimal).
Load-balancing between distant sites can be more of a challenge. If you have more questions, ask away.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange Server 2010: Convert Mailbox to MailUser

Dear All,
I plan to cutover migration exchange on-premises to exchange online with single-sign-on.
http://community.office365.com/en-us/w/exchange/835.cutover-exchange-migration-and-single-sign-on.aspx
In Step 2: It need to Convert on-premises mailboxes to mail-enabled users. it has only instruction guide for exchange server 2003 and 2007. it didn't have for exchange server 2010 or 2013.
Could you guide what is the best solution to convert mailbox in exchange server 2010?
BR,
Khemarin
[email protected]

Hi Khemarin,
You can use the following cmdlet to convert a mailbox to a MailUser:
$DomainController = (Get-ADServerSettings).DefaultConfigurationDomainController.domain
$MailboxList= Get-Mailbox
foreach ($Mailbox in $MailboxList) {
    Disable-Mailbox -Id $mailbox.Identity -Confirm:$False -DomainController $DomainController
    Enable-MailUser -Id $mailbox.Identity -ExternalEmailAddress ($mailbox.alias +"@domain.com") -DomainController $DomainController
    Set-MailUser -Id $mailbox.Identity `
     -DomainController $DomainController `
     -CustomAttribute1 $Mailbox.CustomAttribute1
For more information, here is an article for your reference.
Converting a Mailbox to a MailUser
http://mikecrowley.wordpress.com/2010/12/09/converting-a-mailbox-to-a-mailuser-and-not-loosing-attributes/
Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any information found there. Please make sure that
you completely understand the risk before retrieving any suggestions from the above link.
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

Windows Azure and Exchange Server

Hi,
Do Azure VMs support installation of Exchange Server 2010 or 2013. I am sure technically you can install.
QUESTION IS: But is that a supported scenario (like sql server 2012)?
-Phani
Technical Architect | BrainScale Consulting | AllThingsAzure.com

Hi,
Yes. Here are some articles about how to do it with steps:
http://theroadchimp.com/2012/11/02/installing-exchange-2013-in-windows-azure/
http://www.msexchange.org/articles-tutorials/exchange-server-2010/migration-deployment/installing-exchange-2010-test-environment-windows-azure-part1.html
http://social.msdn.microsoft.com/Forums/en/WAVirtualMachinesforWindows/thread/2a750e53-d0f2-4f52-a6c7-d4a471bbe1ee
Thanks,
QinDian Tang
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

Hi Team,
Need urgent help in resolution of following error:
Environment Details: VMware ESXi 5.5 (vMotion)
Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
Prerequisites: Installed
Error: Installation gives Error at Step 10 during installation of Mailbox Service
Error Details Below:
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.".

Resolved ! :)
Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
Thanks to all.

Exchange Server 2013 Client Mail are Return.Error is [0x80040305-0x0004de-0x00054a]

Hi,
We are using Exchange Server 2013.we have Outlook 2007 SP3 and 2010 SP2 client .Some clients inform mails are return.
Return massage
"This message could not be sent. Try sending the message again later, or contact your network administrator. Your server administrator has limited the number of items you can open simultaneously.
Try closing messages you have opened or removing attachments and images from unsent messages you are composing. Error is [0x80040305-0x0004de-0x00054a]"
Thanks,
Gayan

1) Disable TCPChimney and RSS on CAS and Mailbox Servers by running below commands
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
2) Disable unwanted Add-Ins in outlook that may open many sessions
3) If above steps doesnt resolve, you can delete existing outlook profile and create new Outlook online profile

How can I clone a completed Exchange Server 2013 in a Lab Enviroment?

I was having great time with my Exchange Server 2013 until I tried to clone it to avoid fresh installation of another Exchange 2013 server. Steps taken
(1)Clone the Exchange1 and turn it off
(2) Brought the Clone Exchange2, renamed it, change the IP configurations,
(3) Re-ran the ADprep/Doamin prep
(4) Checked the ASDIedit to verify the Schema/configuration in AD
(5) Restarted I and was able to logon to the Exchange2
(6) Brought up the Exchange1, but unable to logon because the name was no longer in AD database
What I did to fix this:
(7) Rejoin the Exchange1 to the domain - and was able to logon
(8) Unable to access ECP or OWA of any of the two servers.
(9) Errors received - Fix the configuration file of the application
My Question - How to I fix the configuration file as suggested (via powershell or GUI or ASDIedit.msc)?

Unless you are cloning an entire environment, and then bringing it up in a seperate isolated environment, it is not supported to simply clone an Exchange Server, and then bring it online in an existing environment and rename it to save on setup and configuration
time.
You can script the setup and configuration of Exchange through Powershell, either with scripts or with another product controlling it - something like
System Center Orchastrator.
From the script side of things there are many available on peoples blogs. Check
here.
Edit: and to be clear, there is no need to re-run any prep tasks against Active Directory when installing a new Exchange Server, unless you are installing into a new domain as part of your Forest.
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Cannot connect to an Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service"

Dear All,
I cannot connect to my Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service".
First I would like to present my network environment, I have 4 physical servers;
The first one is holding the Domain Controller 1, IP@: 192.168.1.10
The second server is holding the additional Domain Controller which it is DC2, IP@: 192.168.1.11
The third server is holding the Exchange 2013 Mailbox, IP@: 192.168.1.15
And the last server is holding the Exchange 2013 CAS-HT, IP@: 192.168.1.16
I am doing the steps below:
1-Creating a new profile in outlook and start configuring the exchange account by entering the IP address of the Exchange-CAS Server, 192.168.1.16
2-entering the account name: [email protected]
3-Go to "More Settings" > "Connection" > "Connect to Microsoft Exchange using HTTP" > and entering the "Exchange Proxy Settings"
4-type the exchange CAS Server URL, https://192.168.1.16
5-Check the "Connect using SSL Only"
6-Authentication Settings: "NTLM Authentication", and pressing Apply
7-When I press the "Check Name" button, a message occurred> "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action".
8-I go back to the "Exchange Proxy Settings" and I Uncheck the "Connect using SSL Only" and pressing Apply
9-i press the "Check Name" Button, a small window occurred to enter a Username and Password, so I enter the Administrator username and the administrator password and pressing "OK", but nothing is changed, I tried to enter my
username and password in the small window and I still got the same result.
I cannot verify the account name and I cannot complete the process.
I appreciate you kind assistance.

Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
1. Try to login the test account through OWA.
2. Check the Autodiscover settings: get-clientaccessserver |fl autodiscoverserviceinternaluri
3. Check the result of directly accessing the following URL:
https://autodiscover.domain.com/autodiscover/autodiscover.xml
Thanks,
Angela
Angela Shi
TechNet Community Support

Outlook 2013 with Exchange Server - Changed custom form for contacts is not shown

Hello,
Our infrastructure:
Exchange Server 2010
Outlook 2010
Outlook 2013
Windows 7 Pro, Windows 8 Pro and Windows 8.1 Pro
The situation:
We've used an old custom form for contacts, worked perfectly fine
I've updated the form (adding some new custom fields and checkboxes) using Outlook 2013 and publishing the form (with a new name) to the Exchange folder
I've set the form as default form in our contacts folder
I've used this Script to set the new form for the existing contacts and the name of the new form is saved correctly
BUT if I open a contact in our Exchange contacts folder, Outlook 2013 (Outlook 2010) still shows the old form
Steps I've taken so far:
Cleared Outlook forms cache
Repeated the above steps 1-4 in Outlook 2010
Switched Cached Exchange Mode off and back on
Allowed Scripts in Trust Center Settings
Used a new clean Windows installation with a new Outlook 2013 installation
Used different Exchange users on different systems, but some behavior when opening contacts
I'm out of options I can think of, so maybe somebody else has some new view on this problem.
Thank you very much in advance!
Greetings,
Karl

Hi,
Is the Exchange folder in which the custom form is published available to all users?
From the description, the script used to work for the old custom form, correct? Which version of Outlook did you use with the old custom contact form? Outlook 2010/Outlook 2013 or an earlier version? If you used the script with an earlier version of Outlook,
we can't make sure it will still work with Outlook 2010/Outlook 2013.
In addition we may also try creating a new contact form and test the steps to see if it will work.
Please let me know the result.
Regards,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
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]

Exchange Server 2013 and Remote Access VPN on a single server running Windows Server 2012?

Just by way of background, I have been installing and administering network servers, e-mail systems, VPN servers, and the like for many years. However, my involvement with Exchange and Windows Server has been mostly on the forensics and data recovery
level, or as a (sophisticated) user. I have never tried to deploy either from scratch before. My deployment experiences have been mostly with Linux in recent years, and with small private or personal "servers" running such cutting edge
software as Windows XP back when it was new. And even NetWare once.
When a client asked me if I could set up a server for his business, running Exchange Server (since they really want Outlook with all of its bells and whistles to work, particularly calendars) and providing VPN access for a shared file store, I figured it
could not be too difficult given that its a small business, with only a few users, and nothing sophisticated in the way of requirements. For reasons that don't bear explaining here, he was not willing to use a vendor hosting Exchange services or cloud
storage. There is no internal network behind the server; it is intended to be a stand-alone server, hanging off a static IP address on the Internet, providing the entirely mobile work-force of about 10 people with Exchange-hosted e-mail for their computers
and phones, a secure file store, and not much else. If Exchange didn't need it, I would not need to install Active Directory, for example. We have no direct need for its services.
So I did the research and it appears, more by implication than outright assertion, that I should be able to run Windows Server 2012 with Exchange Server 2013 on a server that also hosts Remote Access (VPN only) and does nothing else. And it appears
I ought to be able to do it without virtualizing any of it. However, I have spent the last three or four days fighting one mysterious issue after another. I had Remote Access VPN working and fairly stable very quickly (although it takes a very
long time to become available after the server boots), and it has mostly remained reliable throughout although at times while installing Exchange it seems to have dropped out on me. But I've always been able to get it back after scrounging through the
logs to find out what is bothering it. I have occasionally, for a few minutes at a time, had Exchange Server willing to do everything it should do (although not always everything at the same time). At one point I even received a number of e-mails
on my BlackBerry that had been sent to my test account on the Exchange Server, and was able to send an e-mail from my BlackBerry to an outside account.
But then Exchange Server just stopped. There are messages stuck in the queues, among other issues, but the Exchange Administration Center refuses now to display anything (after I enter my Administrator password, I just get a blank screen, whether on
the server or remotely).
So, I am trying to avoid bothering all of you any more than I have to, but let me just begin with the basic question posed in the title: Can I run Exchange Server (and therefore Active Directory and all of its components) and Remote Access (VPN only) on
a single Windows Server 2012 server? And if so, do I have to run virtual machines (which will require adding more memory to the server, since I did not plan for it when I purchased it)? If it can be done, can anyone provide any pointers on what
the pitfalls are that may be causing my problems? I am happy to provide whatever additional information anyone might like to help figure it out.
Thanks!

An old thread but I ran into this issue and thought I share my solution since I ran into the same issue. Configuring VPN removes the HTTPS 443 binding on the Default Site in IIS for some strange reason; just go and editing the bindings, add HTTPS and things
should be back to normal.

Error when try to install exchange Server 2013 in windows server 2008 R2 Sp1

Hi
I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise
Admins" and "Schema Admins"
in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case
I have to install exchange 2013 in windows Server 2008 r2 sp1
the functional level 2008 R2 I getting these errors please help.
Errors:
This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
Error:
A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency. See the Exchange setup log for more
information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

I think it's from subnet in site and services
have 3 site A,B,C and new site is "D"I have problem in "D" site
A subnet is 10.33.50.0/24 AD 2012 ,exchange 2013
B subnet is 10.35.50.0/24 AD 2012 ,exchange 2013
C subnet is 10.36.50.0/24 AD 2012 ,exchange 2013
D subnet is 10.100.100.0/25 AD 2008 ,exchange 2013 error when install it
find event error
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:
test-SetupPrerequisites
{Roles={LanguagePacks, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport, Cafe}, LanguagesAvailableToInstall=True, DomainController=, CustomerFeedbackEnabled=True, ExchangeVersion=15.0.847.32, LanguagePackDir=D:\Exchange
Server Software, SufficientLanguagePackDiskSpace=True, ADInitError=Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites
or by rep, ScanType=PrecheckInstall, LanguagePackVersioning=True, HostingDeploymentEnabled=False, TargetDir=C:\Program Files\Microsoft\Exchange Server\V15, SetupRoles={LanguagePacks, AdminTools, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport,
Cafe}}

Exchange Server 2013 - LoadGen 2013

Similar Messages

Maybe you are looking for