Getting this error on event log for owa. when we log in to owa, error shows :"something went wrong" 500

tried to recreated owa virtua directories and webconfig file but same issue, please help.

Event code: 3008
Event message: A configuration error has occurred.
Event time: 15/9/2014 11:05:36 PM
Event time (UTC): 15/9/2014 3:05:36 PM
Event ID: ec79c7b2c1ef4b95adbb445c80939fc4
Event sequence: 1
Event occurrence: 1
Event detail code: 0

Application information:
    Application domain: /LM/W3SVC/2/ROOT/owa-45-130552671349946251
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\
    Machine name: LBVSMX01

Process information:
    Process ID: 17484
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM

Exception information:
    Exception type: ConfigurationErrorsException
    Exception message: Could not load file or assembly 'Microsoft.Exchange.Flighting, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\web.config line 117)
   at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
   at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
   at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
   at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
   at System.Web.Compilation.BuildManager.ExecutePreAppStart()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)

Could not load file or assembly 'Microsoft.Exchange.Flighting, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)



Request information:
    Request URL: https://localhost:444/owa/exhealth.check
    Request path: /owa/exhealth.check
    User host address: ::1
    User:  
    Is authenticated: False
    Authentication Type:  
    Thread account name: NT AUTHORITY\SYSTEM

Thread information:
    Thread ID: 42
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:    at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
   at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
   at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
   at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
   at System.Web.Compilation.BuildManager.ExecutePreAppStart()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)


Custom event details:

Hello

I want to change our Exchange 2010 - OWA CAS address from https://mail.mysite.ORG/owa to https://mail.mysite.COM/owa

I do not want to change the email addresses to .com from .org but I need to change the CAS access URL.

How do I achieve this with no or minimum impact?

Thank you.

After We migrated the Exchange from 2010 to 2013 any shared mailbox has been migrated  is showing the inbox and all the subfolders from the user's mailbox in Outlook, instead of the shared mailbox content.

note: if we create new shared mailbox it works fine without any issue.

We have tried to removed full access permissions and re-added full access permissions, disabling AutoMapping and then added the shared mailbox manually in Outlook and that works fine but it is not a solution for us as we have 400+ shared mailbox and we cannot do it for every user have access on each shared mailbox.

any ideas.

Ayman Saleh

Fresh installation of Exchange Server 2013 on Windows Server 2012.

Our first test account cannot access their email via Outlook but can access fine through OWA. The following message appears - "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)" is displayed.

If I turn off cached Exchange mode, setting the email account to not cache does not resolve the issue and i get a new error message - "Cannot open your default e-mail folders. The file (path\profile name).ost is not an Outlook data file (.ost). Very odd since it creates its own .ost file when you run it for the first time.

I cleared the appdata local Outlook folder and I tested on a new laptop that has never connected to Outlook, same error message on any system.

Microsoft Exchange RPC Client Access service is running.

No warning, error or critical messages in the eventlog, it's like the healthiest server alive.

Any help would be greatly appreciated. I haven't encountered this issue with previous versions of Exchange.

Is it possible to create archives rule by script (powershel,vbs) or something else? I want to create archives rule on all of the client in organisation… with out manuals, I cant use GPO.
Thank you for your answer.

We use outlook 2010 and Excahge 2013

Hello all,

I had users that have been accessing shared mailboxes from their outlook clients for weeks with no issues. All of a sudden, whenever they try to access the shared mailboxes, the cursor spinds until it times out and then brings up a dialog box saying:

The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.

Our Exchange server is E365, so it is definately up. The permissions on the shared mailbox are correct, because you can open the shared mailbox using OWA.

Any ideas why the long term function of "open these additional mailboxes" under the main account would no longer function?

Thank you!

-Karl

Hello all,

This is something that is occurring for one of my clients, and it has now occurred three times in the last 6 months.  I can always set the count back to correct by unchecking use cached exchange mode, and doing a sync with the server. Again, I know how to fix this.  What I am looking for is an underlying reason to keep this from happening again. 

What causes this?  The environment is this:  Office 365 Enterprise (I know this may be in the wrong forum, but according to microsoft the technologies, including screens you see, are the same between Hosted Exchange 2013 and Enterprise O365), Windows 7, Outlook 2013.  They do have good internet, so if the answer is leaving cached exchange mode off, I could implement that, but don't really want to.  I do not think this user gets his emails anywhere other then the computer he works on, but am not fully sure, and am not sure how not using cached exchange mode will work in this case. 

I appreciate all suggestions, but again, am really looking to find out what causes this to occur.  I have done some reading on other forums, and in this forum, but it seems all there is to find is how to fix the issue after it has occurred, not keep it from occurring.  Thank you all in advance. 

I work in IT at a community college and I now have a second user that has had the same issue.  When they are trying to attach a file to an email in Outlook 2013 with their Exchange email account, it appears to attach normally.  When you go to send the email, however, they receive an error stating that the "file location cannot be found".  At least some of the files are located locally on the machine, and the users both are set as admin on their respective machines.

I have tried Outlook safe mode, disabling Outlook extensions/plug-ins, creating a new profile in Outlook, repairing Office 2013 install, even re-installing Office 2013.  The only thing that seemed to make a difference was re-imaging the computer, which leads me to believe it's something with how Windows 7's Windows Explorer (specifically file paths) and Outlook 2013 interact.  

I actually, initially had a small success by changing the way I navigate to the file.  At first, I was navigating to the file using the "Favorites" links in the "Insert File" window.  I changed to navigating to the file manually through "Computer" then "C:" etc., in the "Insert File" window.  It seemed this had something to do with the answer since I was able to send a few files that way, but even that started giving me the same error, or at least would not reliably work.

Does this sound familiar to anyone, and if so, any guidance as to the cause and solution to this issue?  I would like to avoid re-imaging the computer if possible.

Hi everyone.

I  am using Exchange server 2007 and i am going to upgrade to exchange 2013 in couple of months.
My SSL certificate(DigiCert) is expiring.
Currently i am using the following SAN names 

mail.mydomain.com
www.mydomain.com
mydomain.com
autodiscover.mydomain.com

and i am adding one more SAN name thinking of Exchange server 2013  legacy.mydomain.com.

Do i require any more SAN names. please do guide me.

We are currently using the Exchange Kiosk email plan and I'd like to create a shared email for two new employee's and the department we're setting up.

I know the kiosk plan won't work with 'shared emails'; will the Exchange Online Plan 1 work for setting up and using a shared email account? We're setting up a Customer Care / BDC center and want to use One(1) email for them(department); I'd like to give each person their own email address and have them share a Dept. email. eg., "customercare at company . com" 

Can I setup the new people with an Exchange Online Plan 1 and will they be able to share the generic dept email account?

Will I need a higher Plan to be able to "share" an email account?

brad

Hello, tried to install SP2 for Exchagne 2010, errors occurred, logfile:

Summary: 15 item(s). 10 succeeded, 1 failed.
Elapsed time: 00:33:08
Organization Preparation
Completed
Elapsed Time: 00:03:14
Preparing Setup
Completed
Elapsed Time: 00:00:04
Stopping Services
Completed
Elapsed Time: 00:03:09
Languages
Completed
Elapsed Time: 00:00:00
Remove Exchange Files
Completed
Elapsed Time: 00:03:10
Preparing Files
Completed
Elapsed Time: 00:00:00
Copy Exchange Files
Completed
Elapsed Time: 00:03:01
Language Files
Completed
Elapsed Time: 00:08:31
Restoring services
Completed
Elapsed Time: 00:00:02
Languages
Completed
Elapsed Time: 00:03:52
Hub Transport Role
Failed

Error:
The following error was generated when "$error.Clear(); 
          Write-ExchangeSetupLog -Info "Creating SBS certificate";

          $thumbprint = [Microsoft.Win32.Registry]::GetValue("HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Networking", "LeafCertThumbPrint", $null);

          if (![System.String]::IsNullOrEmpty($thumbprint))
          {
            Write-ExchangeSetupLog -Info "Enabling certificate with thumbprint: $thumbprint for SMTP service";
            Enable-ExchangeCertificate -Thumbprint $thumbprint -Services SMTP;

            Write-ExchangeSetupLog -Info "Removing default Exchange Certificate";
            Get-ExchangeCertificate | where {$_.FriendlyName.ToString() -eq "Microsoft Exchange"} | Remove-ExchangeCertificate;

            Write-ExchangeSetupLog -Info "Checking if default Exchange Certificate is removed";
            $certs = Get-ExchangeCertificate | where {$_.FriendlyName.ToString() -eq "Microsoft Exchange"};
            if ($certs)
            {
              Write-ExchangeSetupLog -Error "Failed to remove existing exchange certificate"
            }
          }
          else
          {
            Write-ExchangeSetupLog -Warning "Cannot find the SBS certificate";
          }
        " was run: "The internal transport certificate cannot be removed because that would cause the Microsoft Exchange Transport service to stop. To replace the internal transport certificate, create a new certificate. The new certificate will automatically become the internal transport certificate. You can then remove the existing certificate.".

The internal transport certificate cannot be removed because that would cause the Microsoft Exchange Transport service to stop. To replace the internal transport certificate, create a new certificate. The new certificate will automatically become the internal transport certificate. You can then remove the existing certificate.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.247.1&e=ms.exch.err.Ex88D115&l=0&cl=cp

Error:
The following error was generated when "$error.Clear(); 
          Write-ExchangeSetupLog -Info "Creating SBS certificate";

          $thumbprint = [Microsoft.Win32.Registry]::GetValue("HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Networking", "LeafCertThumbPrint", $null);

          if (![System.String]::IsNullOrEmpty($thumbprint))
          {
            Write-ExchangeSetupLog -Info "Enabling certificate with thumbprint: $thumbprint for SMTP service";
            Enable-ExchangeCertificate -Thumbprint $thumbprint -Services SMTP;

            Write-ExchangeSetupLog -Info "Removing default Exchange Certificate";
            Get-ExchangeCertificate | where {$_.FriendlyName.ToString() -eq "Microsoft Exchange"} | Remove-ExchangeCertificate;

            Write-ExchangeSetupLog -Info "Checking if default Exchange Certificate is removed";
            $certs = Get-ExchangeCertificate | where {$_.FriendlyName.ToString() -eq "Microsoft Exchange"};
            if ($certs)
            {
              Write-ExchangeSetupLog -Error "Failed to remove existing exchange certificate"
            }
          }
          else
          {
            Write-ExchangeSetupLog -Warning "Cannot find the SBS certificate";
          }
        " was run: "Failed to remove existing exchange certificate".

Failed to remove existing exchange certificate
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.247.1&e=ms.exch.err.Ex88D115&l=0&cl=cp

Elapsed Time: 00:08:00
Client Access Role
Cancelled
Mailbox Role
Cancelled
Management Tools
Cancelled
Finalizing Setup
Cancelled

Did some research and, it looks like the certificate is replaced with a old selfsigned one. And we use a third party SSL, so i rekeyed the certificate, and installed it and assigned roles to the new certificate. And now we have a lot of certificates, and OWA/Exchange is still in a mess

Thumbprint                                Services   Subject
----------                                --------   -------
7A95DEA4B209CDBA1A48730279322AD649681C0E  IP.WS.     CN=remote.bisas.no, OU=Domain Control Validated
BF0AD2F6F404EAFAE23F6B1084FC9E69EED877C0  ......     C=no, S=Akershus, L=Son, O=Byrået i Son AS, OU=IT, CN=remote.bi..
F295A8652724845111DD24183865315786A42C57  ......     C=no, S=Akershus, L=Son, O=Byrået i Son AS, OU=IT, CN=remote.bi..
4ADC5F22F4AAFBA5C3B38D5095C47D4D94687FAD  ......     CN=SERVER.Bisas.no
4AED7F32D805F47F4BC249C5C1476CA9049F4F07  IP..S.     CN=remote.bisas.no, OU=Domain Control Validated
56DF302E31FCE9016A26F4B8599FCEA72469E5BF  IP.WS.     CN=remote.bisas.no
4D99DBD6F0A95774CE9CB5D7DF2278521A554C68  ....S.     CN=Sites
9DA624C4FE40F7C6759206872C18E03D2E757570  ......     CN=Bisas-SERVER-CA
06F3BAB6369397DC32BB8FB4664BABD8DBB85AF7  ......     CN=WMSvc-WIN-DEJJDJ89L6K

I also see in Event Viewer:

The Module DLL C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\exppw.dll failed to load.  The data is the error.

Source: IIS-W3SVC-WP

Because of this error above, i tried to register the exppw in IIS, but no luck.

Followed this link regarding exppw: http://h10025.www1.hp.com/ewfrf/wc/document?cc=no&lc=no&dlc=no&docname=c03190765

Someone with any suggestions?

Best regards

Aksel

Hi Everyone,

I'm running Exchange Server 2013 on a Windows Server 2012.

Some of my user are sometime asked for credentials.

It happens both at outlook launch and when outlook is running.

And when we just cancel the credentials windows without password, outlook is connected to exchange again.

Everyone is running Office 2010 with SP1.

I have tried to put Outlook anywhere to NTLM and Negotiation authentication but it doesn't work either.

Any idea ?

Thanks in advance

I have just converted from Exchange 2003 to Exchange 2010. I installed a UCC SSL certificate from go daddy on my exchange 2010 server. The Outlook 2007 clients started getting a certificate mismatch warning because the built in certificate that the Outlook clients were pointing to was the internal name of the server (blgexchserv1.blg.local).
I did some research and came accross this post:
http://exchangeserverpro.com/outlook-2007-clients-display-certificate-mismatch-error-after-mailbox-migration/
I attempted to  change the URL of the Autodiscover services within Exchange 2010. I completed the first entry, but the outlook clients are still getting the certificate error. I did not think I needed to modify the web services url at all. I tested OWA internally and it is resolving fine. What am i doing wrong? what else do I need to do to get rid of the error.

I did install the third party cert from Godaddy, but then I had issues with the cert error and switch the services back to the internal (self-signed) cert. I knew I had to get this resolved so I then reset IIS services to point to the godaddy cert, I ran the autodiscover commands on my test network and that seemed to work, but on my live environment the clients are still looking for the server.local cert name and giving me the error.

Hi ALL,

My environment there are two sites. Internet Facing Site A and Non-Internet Facing Site B.

The mailbox that are on the Site A it's working via Outlook AnyWhere.

But, the mailbox on the Site B isn't work.

I configure Outlook AnyWhere (from internet) to connect https, click in check name and mailbox its OK.

I type user and password and the mailbox authentication on the CAS Server (Proxying), configuration with success.

When I open Outlook client, show this message:

Cannot start microsoft outlook. cannot open a the outlook window. the set of folders cannot be opened. you must connect to Microsoft Exchange.

OBS:

I configured Mailbox Database (Site B) RPCClientAccessServer to CAS Internet Facing (Site A).

Set-MailboxDatabase "mailbox" -RPCClientAccessServer "cas.internet.facing"

Any idea?

Regards

R.Blanco

We are using online archives in exchange 2013 for several users.  For one user, the online archive is not showing up in her outlook 2013 client. It does show up in OWA for her, so I don't think it's a server side issue.  I did some research and some users mentioned making sure the product is licensed which I have verified.

Thanks

Carlos

Hello all,

I have the following strange issue:

Some, but not all of our users have issues opening OWA. After logging in, the web page stays blank.

In IIS on the CAS server, I see a HTTP 500 error. On the MBX server, I see the following error (multiple times) at exact the moment the user logs on:

Event 65, MSExchange OWA

The users do not have other issues. Mail syncs perfectly in Outlook (2013) and on mobile devices.

Environment: Exchange 2013 SP1 (2x CAS servers, load balanced, 3x MBX servers in a DAG). 

How can I troubleshoot this?

Regards,

Stephan van der Plas

You know you're an engineer when you have no life and can prove it mathematically

Hello all,

I'm testing Exchange 2013. I have setup 2 exchange 2013 CU1 Servers (1x CAS, 1x MBX) in an existing 2010 SP3 environment. The mailflow is working fine. OWA doesn't work.

After logging on to the  OWA sign-in page, the browser window stays blank. In the IIS logs, I see that /owa/languageselction.aspx is presented, but I do not see it in the browser.

ECP does work fine.

Can someone help me troubleshoot?

Regards,

Stephan van der Plas

You know you're an engineer when you have no life and can prove it mathematically