Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2711
  • Last Modified:

Exchange 2013 CU3 install error

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
TripapHoniC
Asked:
TripapHoniC
  • 5
  • 3
  • 2
1 Solution
 
ktaczalaCommented:
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
 
TripapHoniCAuthor Commented:
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
 
ktaczalaCommented:
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
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
TripapHoniCAuthor Commented:
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
 
ktaczalaCommented:
There are several files in that path, do you have them all?

Here's a snapshot of that folder:
snapshot
0
 
Marshal HubsEmail ConsultantCommented:
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
 
TripapHoniCAuthor Commented:
I've requested that this question be deleted for the following reason:

Issue was with a failed installation of CU1
0
 
Marshal HubsEmail ConsultantCommented:
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
 
TripapHoniCAuthor Commented:
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
 
TripapHoniCAuthor Commented:
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

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now