Exchange 2013 Management Tools Install Error on Win8

Hello,
I'm having some trouble installing the management tools for Exchange 2013 on Windows 8. While going through the install if I leave "Automatically install Windows Server roles and features that are required to install Exchange Server" check I get
this error...
Error:
The target of the specified cmdlet cannot be a Windows client-based operating system.
If I uncheck that option and just check the Management Tools option, the error message changes to...
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.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
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Any help on resolving this so I can move on with the installation would be appreciated.
Thanks.

Hi,
To install the Exchange 2013 Management Tools, there are many prerequisites we need to understand before installation. And even
we must manually install some required software.
Here are some references that may be helpful to you:
Install the Exchange 2013 Management Tools
http://technet.microsoft.com/en-us/library/bb232090(v=exchg.150).aspx
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
Thanks,
Winnie Liang
TechNet Community Support

Similar Messages

Exchange 2013 management tools installation on windows 2012 standard edition gives error.

Exchange 2013 management tools installation on windows 2012 standard edition gives following error.
Does anyone observed this issue ?
Error:
The Exchange management tools are supported on servers running Windows Server 2012 and Windows Server 2008 R2 SP1 or later, and also on Windows 8 and Windows 7 client computers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersionForAdminTools.aspx
My Test lab is having
Exchange 2013 installed (xyz.local) domain and working fine.
Now i am installing Exchange Management tools on server which is member of (xyz.local) Domain (base OS : Windows 2012 standard edition : Windows updated)
Best Regards
sameer Prabhune

Hi Sprabhune,
It should work.
Did you install the tool by GUI or cmd?
Please select "Automatically install Windows Server roles and features that are required to install Exchange Server" to have the Setup wizard install required Windows prerequisites.
If possible, please try to install the tool on Windows 7/8 client to test.
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354.aspx
Frank Wang
TechNet Community Support

Installing Exchange 2013 management tools

I am unable to install Exchange Management Tools on other server in network. I am getting error when trying to run unattended setup "exchange server.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI
package is 'Error reading from file: C:\Users\backup-admin\Downloads\Exchange2013\RemoteScripts\ConsoleInitialize.ps1. Verify that the file exists and that you can access it". Also tried to run the setup.exe, but this option not highlighting
"Management Tools" option to select.
Mohammed Qamaruddin

Hi,
Please try the following cmdlet to solve this issue.
set-executionpolicy unrestricted
If this doesn’t work, please try to copy the
ConsoleInitialize.ps1 from a working server to this server then reinstall Exchange management Tool.
If this still doesn’t work, we should consider to re-download Exchange Server 2013 Management Pack from this
site, then try to install.
Related document:
https://technet.microsoft.com/en-us/library/bb232090%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Best Regards.

Error when trying to install MS Exchange 2010 Management Tools Windows 7 x64 SP1

When I try to install Exchange 2010 Management Tools on my Windows 7 Pro x64. I get the message ExSetupUI.exe has stopped working? Has anybody else gotten this message? It doesn't even load into the install screen. It is stopping before then.

Hi
Have you installed the admin tools for windows 7 and all the prerequisites? Try running the setup from an elevated prompt or "as Administrator"
for ref:
http://social.technet.microsoft.com/Forums/en-US/63880f4e-6b6e-4ea9-b3b6-8a535657288f/installing-exchange-management-tools-on-a-win-7-x64-box-getting-error-on-readiness-checks?forum=exchange2010

Exchange 2013 CU5 fresh install suffering issues with services not starting and coexistence with 2007

Hi everyone,
Hope you can help me out on a couple of issues I've been experiencing during the initial stages of a project to upgrade an on premise Exchange 2007 to 2013.
On Monday last week I installed the first Exchange 2013 server into the network after a few weeks of careful planning, information gathering and remediation of our current Exchange 2007 environment and associated systems.
The server itself has been having some issues from the word go, some of which I've resolved but none that are show stoppers but I want to get them resolved before building more servers and setting up the planned 2 x 2 node DAG's
The main problems are as follows:
There's usually one service that does not start following an OS restart and it's not always the same service. So far I've seen the following not start: DAG Management, Migration Workflow, Anti-spam Update, Unified Messaging, UM Call Router, Transport
Service.
The critical system event log entries are complaining of timeouts when the services are starting up but I can't imagine that the servers boot time is too long... It's a 2 vCPU/12Gb vRAM VM, Windows 2012 R2
I receive an error in the Event Log regarding RPC over HTTP Proxy
to one of the 2007 CAS servers (not our primary one). The first error was because the Windows Component was missing but since installing it, disabling Outlook Anywhere, reenabling it, restarting the server, I now have a new error which is shown further down
this post
The Exchange 2013 server install is pretty default, CAS/MBX roles and some basic configuration performed such as new DNS entries, Public SSL certs installed and assigned, URL's updates, SCP updated. I have review and resolved some errors from the event logs
for over chatty warnings about disk space (the warning is that we have loads of space...)
This is a brief outline of the environment:
Exchange 2007 SP3 RU13
UK - Two physical locations in a stretch LAN (100Mb WAN)
4 x CCR Cluster Mailbox Servers in two separate CCR Clusters
Cluster 1 - Windows 2003 R2: One physical, one virtual server - don't ask, legacy install and I know the virtual is not a supported configuration.
Cluster 2 - Windows 2008 R2: Two virtuals - New cluster built following a 4 day failure of Cluster 1. The aim was to move to supported config and decommission cluster 1.
Note: Migration of Cluster 1 to Cluster 2 was halted as 2013 was so close it seemed pointless to continue the migration and instead migrate both Clusters to 2013 once in production.
2 x Virtual Windows 2003 R2 - Hub Transport Servers
2 x Virtual Windows 2003 R2 - Client Access Servers
1 x Virtual Windows 2003 R2 - Unified Messaging Server
1 x Virtual Windows 2003 R2 - Edge Transport Server (DMZ)
US - One physical location
1 x Physical Windows 2008 R2 - Mailbox, Client Access, Hub Transport Server
Exchange 2013 CU5
UK - Installed into same site along side Exchange 2007 servers
1 x Virtual Windows 2012 R2 - Mailbox, Client Access Server
Problem 2 Error Message - Please note, server names and domain name changed:
Log Name:      Application
Source:        MSExchange Front End HTTP Proxy
Date:          18/07/2014 10:00:37
Event ID:      3005
Task Category: Core
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EXC2013.domain.local
Description:
[RpcHttp] Marking ClientAccess 2010 server EXC2007CAS1.domain.local (https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll) as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
Event Xml:
<Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event>
<System>
    <Provider Name="MSExchange Front End HTTP Proxy" />
    <EventID Qualifiers="32768">3005</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-18T09:00:37.000000000Z" />
    <EventRecordID>64832</EventRecordID>
    <Channel>Application</Channel>
    <Computer>EXC2013.domain.local</Computer>
    <Security />
</System>
<EventData>
    <Data>RpcHttp</Data>
    <Data>EXC2007CAS1.domain.local</Data>
    <Data>https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll</Data>
    <Data>System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data>
</EventData>
</Event>

Hi Off2work,
I've gone through the article and the Get-OutlookAnywhere commandlet looks fine (especially when compared with our working CAS).
Having looked through IIS I have spotted two additional misconfigurations with a missing setting to require SSL on the RPC folder and also the .NET version was not set.
I've now set those to Require SSL and .NET 2.0.5072 however this has made no difference following restarted of both 2007 CAS and 2013 servers.
I could potentially reinstall the CAS server or additionally decommission it as we have two of them and the other is not causing any errors with the 2013 server. This broken CAS server doesn't even have DNS records (except it's own hostname) or firewall
rules pointing to it, nor does it have any active client connections if I check with a quick netstat -a
As for UM, it's next on my list following some client/server connectivity testing so I have not yet assigned the SSL to the services or setup the dial plans, etc.
The services do start most of the time, but others then don't so it's not a consistent issue with just this service. On my current boot, the DAG Management service failed to start, but again I don't have a DAG implemented yet.
I will see if UM drops out of that list once I've configured it shortly
Thanks for taking the time to respond (and that goes to DareDevil too)

Connect to Exchange 2007 Mailboxes with Exchange 2013 Management shell

Hello,
I was wondering if it is possible to use the Exchange 2013 Management Shell with the older version of Exchange 2007. When I run the console now it give me an error saying no exchange servers are available in the Active Directory site. When I use Exchange
management shell for 2007 the errors do not appear. Wondering if the management shell is backwards compatible.
Thanks,

No. your management shell MUST be the same roll-up version of exchange. I have applied updates and learned the hard way to block all updates that go beyond the server version you are
running.
http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-bui...
To this end, you can use the same installation media that was used to install your Exchange server "Provided you are hosting your own", just install the management console instead of the whole thing,

Exchange 2010 management tools and others

Win2k8 domain, Exchange 2010 servers
We want to move to Win8.1 but we, the admins, are preventing it because our tools like the Exchange 2010 Management tool doesn't work with Win8.0 so we're stuck with Win7.
I've googled around and most suggestion never worked.
Does Microsoft have any plans at all to have Exchange 2010 management tools and other tools we use to manage our domain work with Win8.1?

Hi Rino,
Thanks for your sharing and efforts put on this issue.
This will benefit others who encounter the similar scenario as yours.
Happy holiday~
Kate Li
TechNet Community Support

Exchange 2013 management shell error

The problem am facing is that when I opened the Exchange management shell on my Exchange 2013 server locally it would fail to connect.The following error is receiving with Administrator account.I add another account in Organization
Management Permission it connect successfully.
following is error
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: mail.abc.com
VERBOSE: Connecting to mail.*.*.
New-PSSession : [mail.abc.com] Connecting to remote server mail.abc.com failed with the following error message :
WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the
computer mail.abc.com. Verify that the computer exists on the network and that the name provided is spelled
correctly. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed
[PS] C:\Windows\system32>

Hi wert
Thank you for your question.
We could run Set U to make sure the logon user is domain administrator, because we use another account logon without any problems. We could check if some permissions are missing for administrator.
We could refer to the following steps to delete administrator profile to check if the issue persist:
Open up "Control Panel | System and Security | System"
In the dialog click on "Advanced system settings" (requires Admin rights)
The "System Properties" dialog will be displayed
Make sure you are in the "Advanced" register
In the "User Profiles" section click on "Settings"
The "User Profiles" dialog is displayed
Select administrator account and Delete it.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Fresh install of Exchange 2013. 500 Internal error after trying to login via ECP

Hi folks,In the process of migrating someone from their onsite infrastructure to Cloud ( local city's datacentre). They currently have AD/File+ Print (2008R2) with Exchange on same VM (yeah I know and I am fixing this with new move) and Terminal Server (2008R2).Cloud move will have Server 2012 R2 AD/F+P, Exchange 2013 SP1 on Server 2012 R2 and RDS on Server 2012 R2 VM's. Have setup VPN between the onsite infrastructure and Cloud VM's. AD/DC are in sync. Exchange has been installed with both mailbox and CAS roles after doing Schema & Domain prep and Domain updates. Exchange server and AD/DC in Cloud are joined to onsite infrastructure domain. Exchange on cloud is using cloud AD/DC's DNS.
Cloud AD/DNS can ping onsite AD/PDC fine. Cloud Exchange can ping onsite TS fine but it cannot ping onsite AD/DNS. This is my 2nd issue. Onsite AD/PDC...
This topic first appeared in the Spiceworks Community

This is Exchange 2013 Sp1 or CU5 ?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 Edge Transport install fails

I'm trying to install the Edge Transport for Exchange 2013 but it gets to step 7 of 9:
then give's the following error
Error:
The following error was generated when "$error.Clear();
new-ExchangeServer
" was run: "Value cannot be null.
Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
Then in event viewer I have the following two events.
Watson report about to be sent for process id: 260, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, ExSetupUI, M.E.Data.Directory, M.E.D.D.ADObjectId.GetChildId, System.ArgumentNullException, 2ac6, 15.00.0847.031.
ErrorReportingEnabled: True
and
Exchange Server component Edge Transport Role failed.
Error: Error:
The following error was generated when "$error.Clear();
new-ExchangeServer
" was run: "Value cannot be null.
Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
I've rebuilt the server but since it has something to do with the GUID I assumed it wouldn't work but I was grasping at straws and it didn't fix the issue.
I can run the setup again and it does finish but it doesn't show up in the list of servers in the ecp management. I've yet to find a solution on this issue if anyone has a suggestion or two it would be greatly appreciated.

Thanks for response.
when I run Get-ExchangeServer I get the following
Name Site ServerRole Edition AdminDisplayVersion
Exchange03 Edge Standard... Version
15.0 (Bu...
and the errors that are in the log
[02/17/2015 20:06:33.0084] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: ADAM is installed on this machine; only the Microsoft Exchange Edge Transport server role may be installed. See the Exchange setup log
for more information on this error.
[02/17/2015 20:07:50.0288] [1] The following 1 error(s) occurred during task execution:
[02/17/2015 20:07:50.0288] [1] 0. ErrorRecord: Service SMTPSVC was not found on computer '.'.
[02/17/2015 20:07:50.0288] [1] The previous errors were generated by a non-critical task and will be ignored.
then I have a load of error that failed to load dependency below is a small sample
[02/17/2015 20:07:57.0648] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V15\bin\edgetransport.exe
Failed to load dependency Microsoft.Management.OData of assembly Microsoft.Exchange.Configuration.ObjectModel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
from HRESULT: 0x80070002)
Failed to load dependency Microsoft.Ceres.InteractionEngine.Processing.BuiltIn of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified.
(Exception from HRESULT: 0x80070002)
Failed to load dependency Microsoft.Ceres.NlpBase.RichTypes of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
from HRESULT: 0x80070002)
Failed to load dependency System.IdentityModel.Tokens.Jwt of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from
HRESULT: 0x80070002)
Failed to load dependency Microsoft.Passport.RPS of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from HRESULT:
0x80070002)
Thanks

Exchange 2013 Mailbox Role Installation Error

Hi All,
I am getting the below error when installing Exchange 2013 Mailbox Role. This is a Windows Server 2012. Previous Exchange 2013 setup was removed since it had issues with CAS. Now we have removed all previous Exchange software and attributes.
Error:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Microsoft.Exchange.Management.Metabase.IISGeneralCOMException: An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.
. HResult = -2147024893 ---> System.Runtime.InteropServices.COMException: The system cannot find the path specified.
   at System.DirectoryServices.DirectoryEntry
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.RefreshCache()
   at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName)
   at System.DirectoryServices.PropertyCollection.KeysCollection.GetEnumerator()
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetWebSiteSslCertificate(String webObjectPath)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.FindIisCertificate()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Any views on this is appreciated.
Regards
Boniface
Senior Systems Administrator

Hi,
After uninstalling the IIS, please run the following command to install prerequisites.
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Then remove the “water mark” key and “action” key under the following registry and initiate the setup again.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15.0\HubTransportRole
In addition, please disable any third-part software for troublwshooting.
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

SQL 2008 R2 Management Tools Install Fails - The specified account already exists

Hello,
The installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Below is the Summary Log.
Thanks.
Paul
Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal):           -2068052700
Exit facility code:            1212
Exit error code:               1316
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time:                    2014-10-20 09:02:16
End time:                      2014-10-20 09:05:57
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\sqlncli_Cpu64_1.log
Exception help link:
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name:                  WS287
Machine processor count:       4
OS version:                    Windows 7
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:
\\SRVDIA18\MSSQL2008R2Install\x64\setup\
Installation edition:          STANDARD
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 <empty>
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    False
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    <empty>
INSTANCENAME:                  <empty>
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          <empty>
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 <empty>
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
Detailed results:
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\SystemConfigurationCheck_Report.htm
The specified account already exists

There is definitely more amusing endeavours in this world, than trying to understand why an SQL Server install failed. The log files are verbose - but somehow the real information about what went wrong seems to be hiding. Never have proverb about not being
able to see the forest for all the trees felt more appropriate.
Nevertheless, this is where things go sour:
MSI (s) (F4:EC) [09:04:15:744]: Resolving source.
MSI (s) (F4:EC) [09:04:15:744]: Resolving source to launched-from source.
MSI (s) (F4:EC) [09:04:15:744]: Setting launched-from source as last-used.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourceDir property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{2180B33F-3225-423E-BBC1-7798CFD3CD1F}'.
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR ==> \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR product ==> {2180B33F-3225-423E-BBC1-7798CFD3CD1F}
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (F4:EC) [09:04:15:744]: Determining source type
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 2203 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi 3: -2147287038
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 1316 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: Error determining package source type
MSI (s) (F4:EC) [09:04:15:744]: SECUREREPAIR: SecureRepair Failed. Error code: 524F91D34B8
MSI (s) (F4:EC) [09:04:40:775]: Product: Microsoft SQL Server 2008 R2 Native Client -- Error 1316. The specified account already exists.
What account? I supposed you have already asked yourself that and just shaken your head.
But there is another error code 2203, NET HELPMSG 2203 says "The password parameter is invalid." And I note that the source is apparently on a share.
So where is my guess: the MSI installer - which runs as a service, somehow does not have permissions to read the installation from the share. Or is trying to log on to the share with your username/password? No, I don't know, I am just speculating widely.
But my advice would be to copy the installation directory from the share to a local disk.
Maybe that CryptAcquireContext is significant as well - I don't know.
Oh, wait, here is something just before the section above in the log:
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2205 2: 3: Environment
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2228 2: 3: Environment 4: SELECT `Name`,`Value` FROM `Environment`,`Component` WHERE `Component_`=`Component` AND (`Component`.`Action` = 1 OR `Component`.`Action` = 2)
Action start 9:04:15: WriteEnvironmentStrings.
2205 is "The logon processor did not add the message alias." I see that in a successful log that I have, so that is probably benign. But 2228 seems to be
"There are too many names in the user accounts database."
Exactly what that means, I have no clue, but it could be a Windows problem.
Erland Sommarskog, SQL Server MVP, [email protected]

Exchange SP1 Edge Transport Install Error

Hi everyone,
I've successfully installed multiple Mailbox and CAS 2013 SP1 servers into an existing Exchange 2010 environment.
However, when I get to the Edge Transport role on a separate server, at step 7 of 9, it throws the following error:
Error:
The following error was generated when "$error.Clear();
new-ExchangeServer
" was run: "Value cannot be null.
Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
Any ideas what could be causing this? I haven't been able to find anything of significance while searching around...
Thanks!

Hi,
Make sure prerequisites for Exchange 2013 Edge Transport server role are met. For more details about this, you can refer to the following article.
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx#WS2012Edge
If you have checked above, and this issue persists, please check the set up log to see if there is related error message to narrow down the issue.
Besides, here is an article about Edge Server installation for your reference.
Install the Exchange 2013 Edge Transport role using the Setup Wizard
http://technet.microsoft.com/en-gb/library/dn635117(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 MSExchange Certificate Notification Error 2001

I literally have no idea of what to do with this error. I only see it when I restart the our Exchange 2013 Front End server.
Log Name:      Application
Source:        MSExchange Certificate Notification
Date:          9/20/2013 2:28:46 PM
Event ID:      2001
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      front end server
Description:
A transient failure has occurred. The problem may resolve itself. Diagnostic information:
Microsoft.Exchange.Data.DataSourceOperationException: The request failed. The remote server returned an error: (401) Unauthorized. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error:
(401) Unauthorized. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
   at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalFindFolders(IEnumerable`1 parentFolderIds, SearchFilter searchFilter, FolderView view, ServiceErrorHandling errorHandlingMode)
   at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view)
   at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
   at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.GetOrCreateFolderCore(String folderName, FolderId parentFolder, Func`1 creator)
   at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.GetDefaultFolder()
   at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<>c__DisplayClass1b`1.<InternalFindPaged>b__13()
   at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
   at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<InternalFindPaged>d__21`1.MoveNext()
   at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.<GetNotificationDetails>d__57.MoveNext()
   at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
   at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.RemoveAllNotification()
   at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.UpdateDataInMbx(List`1 certificates)
   at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.Work()

We're in the same boat. This is a production installation, running on Windows Server 2012, that we've been getting that error on for months. We just updated to CU3 and the error is still there. It doesn't seem to impact anything as far
as I can see, so I'm not certain that it matters.
For what it's worth, we use a single certificate for the IIS,POP,IMAP,SMTP services on all of our CAS servers. It's issued from our internal CA and has ~13 entries in the SAN for various purposes. It was issued from a custom template that we
use for various purposes, so it's possible there's something about the certificate that something somewhere doesn't like.   Unfortunately the error doesn't seem to contain any specifics, so it's difficult to tell what's happening.
The event immediately after the error is information event 2002:
A round of expiration check has finished. The next round is scheduled at...
Also at the same time there is a warning in the system log for Event 6037, LSA (LsaSrv)
The program w3wp.exe, with the assigned process ID 2804, could not authenticate locally by using the target name HTTP/owa.langslb.domain.com. The target name used is not valid. A target name should refer to one of the local computer names, for example,
the DNS host name.
Try a different target name.
The address is the address used by our hardware load balancer for our CAS servers. The IP for the name will be one of the CAS. On reboot, even if the load balancer doesn't have time to detect one of the systems being offline, it would have a
percentage chance of getting the IP of an already online system.
I have the exact same error with Exchange 2013 CU3 CAS servers. can any one explain what is that about? and how to resolve it?

SCSM Management Server install error

Hi All
I have a curious error with regards to an SCSM 2012 R2 Management Server install to a Windows Server 2012 with local SQL Server 2012 Standard); the SCSM 2012 R2 Data warehouse Server installed fine on a separate server. I've checked that the install
account has full SQL, Local and Domain Admins (for install), I've also fired the install from an elevated command prompt but with same error, I've also checked that PowerShell is set to Unrestricted. There is also mention of a Timeout in the below error,
which has lead me to think it could possibly be SQL SPN issue, however please see below and let me know if anyone has seen this before \ any suggestions welcome!
The error I'm seeing in the MSI log is as follows:
Calling custom action CAManaged!Microsoft.MOMv3.Setup.PreExtensionRegistration.PreRegisterExtensions
PreRegisterExtensions: Begin
PreRegisterExtensions: Starting in deferred mode
PreRegisterExtensions: 20 extension records decoded
PreRegisterExtensions: Connecting via InProc SDK
PreRegisterExtensions: Loading management pack C:\Program Files\Microsoft System Center 2012 R2\Service Manager\System.Library.mp
PreRegisterExtensions: Importing management pack C:\Program Files\Microsoft System Center 2012 R2\Service Manager\System.Library.mp
PreRegisterExtensions: System.ArgumentException: The requested management pack is not valid. See inner exception for details.
PreRegisterExtensions: Parameter name: managementPack ---> : Database error. MPInfra_p_ManagementPackInstall failed with exception:
PreRegisterExtensions: Database error. MPInfra_p_ManagementPackInstall failed with exception:
PreRegisterExtensions: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
PreRegisterExtensions: The statement has been terminated.
PreRegisterExtensions:
PreRegisterExtensions:    --- End of inner exception stack trace ---
PreRegisterExtensions:    at Microsoft.EnterpriseManagement.ManagementPackManagement.TryImportManagementPack(ManagementPack managementPack, IDictionary`2 resources)
PreRegisterExtensions:    at Microsoft.EnterpriseManagement.ManagementPackManagement.ImportManagementPack(ManagementPack managementPack, IDictionary`2 resources)
PreRegisterExtensions:    at Microsoft.MOMv3.Setup.PreExtensionRegistration.PreRegisterExtensions(Session session)
PreRegisterExtensions: End (fail)
MSI (s) (D8:E4) [13:20:43:793]: NOTE: custom action _PreRegisterExtensionsDeferred unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _PreRegisterExtensionsDeferred returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
04/02/2014 13:20:43.824 [3032]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
04/02/2014 13:20:43.878 [3032]: Detailed info about C:\Windows\assembly\tmp\CPSNRJPD\Microsoft.EnterpriseManagement.OperationsManager.Apm.StatisticCounters.ScriptingLibrary.dll
04/02/2014 13:20:43.878 [3032]: File attributes: 00000080
04/02/2014 13:20:44.124 [3032]: Restart Manager Info: 1 entries
04/02/2014 13:20:44.125 [3032]:   App[0]: (3032) Windows Installer (msiserver), type = 3
Kind Regards
Andrew

Thanks Thomas
Yep had checked permissions, see below. Any others that I may have over looked that you can think of?
1. Login \ install account as local Admin on the Server
2. Login \ install account has full SQL SysAdmin rights, was also used for installing the SQL Instance locally
3. Checked account in AD so that it is ok for Kerberos Delegation
One thing is that I have specified this account for all account options during install (since its a test environment), in production would usually create distinct accounts, is this likely to be an issue though?
Will attempt install again but use Local System etc instead of specifying my domain account just to check \ see if error changes.
Kind Regards
Andrew

Exchange 2013 Management Tools Install Error on Win8

Similar Messages

Maybe you are looking for