[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

exchange 2007 out of office not working - 'Microsoft.Exchange.Diagnostics, Version=14.0.0.0 NOT FOUND

hi, getting a bunch of errors on my even log sayoing that file cannot be found. out of office wont work, autodiscovery will not either. it was working a while ago, not sure wha t happend.
i have deleted and recreated ews and autodiscover directories, i went in to the config file and its pointing to the right address, i can go and see the file there. not sure why the error says version 14. when on the config file is listed as 8.0.0.0.

what can i do here?

SBS 2008 - exchange 2007
0
Comptx
Asked:
Comptx
  • 10
  • 4
1 Solution
 
ComptxAuthor Commented:
whole error when i go to the autodoscover webpage

Server Error in '/Autodiscover' Application.
--------------------------------------------------------------------------------

Could not load file or assembly 'Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

Stack Trace:


[FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
   Microsoft.Exchange.Autodiscover.Global.Application_BeginRequest(Object sender, EventArgs e) +0
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.4214; ASP.NET Version:2.0.50727.4209
0
 
e_aravindCommented:
Did you tried installing any Management console or any other stuff related to E2010 on this box?

When you try accessing the
https://localhost/autodiscover/autodiscover.xml -->then u are facing this error message correct?

Reason: if you use the FQDN or netbios name..that could be resolving to any other server in the setup?
0
 
ComptxAuthor Commented:
e_aravind, if i go to that url i get the following

  <?xml version="1.0" encoding="utf-8" ?>
- <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
- <Response>
- <Error Time="09:16:06.1018996" Id="4072813690">
  <ErrorCode>600</ErrorCode>
  <Message>Invalid Request</Message>
  <DebugData />
  </Error>
  </Response>
  </Autodiscover>



i used to get an invalid directory, but i installed SP3 and it seems to fix more of the issues, iphone can now connect to the email with autodiscover, but i cant do it from outlook externally, and my out of office stil does not work
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
ComptxAuthor Commented:
results of Test-OutlookWebServices | fl



Id      : 1013
Type    : Error
Message : When contacting https://remote.psghome.com/ews/Exchange.asmx received
           the error The request failed with HTTP status 403: Forbidden.

Id      : 1016
Type    : Error
Message : [EXCH]-Error when contacting the AS service at https://remote.psghome
          .com/ews/Exchange.asmx. The elapsed time was 816 milliseconds.

Id      : 1013
Type    : Error
Message : When contacting https://remote.psghome.com/EWS/Exchange.asmx received
           the error The request failed with HTTP status 403: Forbidden.

Id      : 1016
Type    : Error
Message : [EXPR]-Error when contacting the AS service at https://remote.psghome
          .com/EWS/Exchange.asmx. The elapsed time was 105 milliseconds.
0
 
ComptxAuthor Commented:
success in most of them tho, only fails in those 4
0
 
ComptxAuthor Commented:
test email autoconfiguration test from within outlook completes successfully as well
0
 
ComptxAuthor Commented:
also noticed its trying to look for the autodiscovery on virtual directory "default website" instead of "sbs web applications"
0
 
e_aravindCommented:
Not sure about the SBS server, but generally if you can manage to reach the autodiscover v.directory using the URLs
A) SCP -- if the OUtlook machine is domain joined
b) https://autodiscover.emaildomain.com/autodiscover/autodiscover.xml
c) http://autodiscover.emaildomain.com/autodiscover/autodiscover.xml
d) SRV record
....then Outlook should be able to autoconfigure the settings without much of difficulty


In short,  the location of "Autodiscovery" should not be the issue\matter-to-worry
Rather we should check on the Outlook responses\errors ...using the outlook-logging
0
 
ComptxAuthor Commented:
outlook autoconfigures itself just fine internally, but not externally. OWA oof works fine, but not the outlook client, internal or external.
0
 
e_aravindCommented:
Yes, mostly the OOF from an internet clients would be attempting to use
b) https://autodiscover.emaildomain.com/autodiscover/autodiscover.xml
c) http://autodiscover.emaildomain.com/autodiscover/autodiscover.xml
d) SRV record

..so need to perform the "Test email autoconfiguration" and share the screen-shots for the results and Logs tab.
0
 
ComptxAuthor Commented:
ok everything works now, including out of office. BUT when i try to add the exchange accoutn on my outlook (externally and not part of the domain) i put the email, user and pass, it detects the settings just fine, tells me to exit outlook and open it againand when i do that, it asks me for username and password.  i put domain\user and the password but after that it fails to find the server

if i add it from my iphone it works great. and got another domain laptop with the account already on it ( laptop is not on the network, its externally now) he opens outlook and after entering credentials outlook tries to connext but cant connect to the server
0
 
e_aravindCommented:
So from the external network, outlook is failing to connect to the exchange-server?
If yes, what is that we are trying to connect "tcp\ip profile" or "HTTPs profile"

Or

Do we have issues with the Autodiscover?
0
 
ComptxAuthor Commented:
solved all the issues recreating all the virtual directories.
0
 
ComptxAuthor Commented:
fixed the issue
0

Featured Post

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!

  • 10
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now