Expiring Today—Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange 2013 CU3 install error

Posted on 2014-01-17
10
Medium Priority
?
2,455 Views
Last Modified: 2014-02-02
Community.  I recently attempted to install CU1 and ran into an error.  It was suggested I should have installed CU3 but I was holding off until SP1 based on the recommendation of an MS Exchange engineer.  I attempted CU1 because it was supposed to correct some scan to email attachment problems.  Regardless, I attempted CU1 and it failed.  I downloaded and tried CU3 and now it's telling me this.

Warning:
An unexpected error has occurred and a Watson dump is being generated: Could not find a part of the path 'C:\Windows\Temp\ExchangeSetup\bin\EnterpriseServiceEndpointsConfig.xml'.

I tried to go to the path of course and it was indeed not navigable.

Any suggestions would be appreciated as mail flow has stopped.
0
Comment
Question by:TripapHoniC
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
  • 2
10 Comments
 
LVL 13

Expert Comment

by:ktaczala
ID: 39790300
try changing you environment tmp/temp file paths to somewhere other that the os folders.

I.E. c:\temp

Don't forget to create that folder manually.
0
 

Author Comment

by:TripapHoniC
ID: 39791726
Changed the temp and tmp folders in environmental variables and get same error, different path.

Warning:
An unexpected error has occurred and a Watson dump is being generated: Could not find a part of the path 'C:\Windows\Temp\ExchangeSetup\bin\EnterpriseServiceEndpointsConfig.xml'.
0
 
LVL 13

Expert Comment

by:ktaczala
ID: 39791755
are you missing the whole path? or Just that xml file?
Here's the xml file.  It's from my exchange 2013 server, although I already have CU3 Installed.
enterpriseserviceendpointsconfig.xml
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:TripapHoniC
ID: 39792952
I tried to put your file in the path it was looking for and even renamed it how it was capitalized in the error and still got the error.

No clue what's going on here but all mailflow is dead.
0
 
LVL 13

Expert Comment

by:ktaczala
ID: 39793106
There are several files in that path, do you have them all?

Here's a snapshot of that folder:
snapshot
0
 
LVL 10

Expert Comment

by:Marshal Hubs
ID: 39793297
I have checked Exchange setup log and discovered the folder with search foundation installation script which was located under %Exchangeinstalldirectory%\Bin\Search\Ceres\Installer\. Then I browse to the folder in powershell and run configuration script manually without arguments first and it provided me with a list of available arguments and in my case it was required to add configuration to existing one.

.\InstallConfig.ps1 -action a

Next run setup of Exchange 2013 CU3 which went fine without any problem. I would say that it happened due to the problem in connecting with DC during setup.
0
 

Author Comment

by:TripapHoniC
ID: 39802585
I've requested that this question be deleted for the following reason:

Issue was with a failed installation of CU1
0
 
LVL 10

Expert Comment

by:Marshal Hubs
ID: 39802586
This problem can happen to anyone, so I don't think this question should be deleted. If the problem of TripapHoniC has been resolved, that's good but let others know the solution if in case, they face the same problem that was asked by TripapHoniC without knowing the actual problem at his end.
0
 

Accepted Solution

by:
TripapHoniC earned 0 total points
ID: 39802973
The problem was related to a partial installation of CU1.  The versions were mismatched in the different Exchange roles.  A Microsoft Exchange engineer worked on this issue for over 5 hours and was able to finally reinstall CU3.
0
 

Author Closing Comment

by:TripapHoniC
ID: 39827479
Resolution was annotated and MS Exchange engineer resolved the issue by manually changing the versions of Exchange 2013 from CU1 to CU3 inside the registry.  After this was completed the CU3 installation was able to finish.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

New style of hardware planning for Microsoft Exchange server.
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question