Solved

Exchange 2013 CU3 install error

Posted on 2014-01-17
10
2,226 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 12

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 12

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
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 

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 12

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

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

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

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

739 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