Out of Office on OWA; Exchange 2010

We recently migrated from Exchange 2003 to Exchange 2010 and were having issues with out of office.
OOF works fine in outlook but when you try and run it from OWA we get internal server error 500. The OOF URL was pointing to the internal machine and we changed this to the outside and I can access it.
I saw something about rebuilding ECP but I don't know what this actually does so I haven't tried it yet.
Any help would be apperciated

Hi,
Based on the description, you couldn't turn on OOF in OWA and you got the error: internal server error 500. If I misunderstood your concern, please let me know.
OOF is based on the Exchange Web Services, if either the internal or external URL for the EWS is missing or incorrect, OOF will fail and other services may not work as expected.
Please check the URLs assigned to the web service virtual directory using the Get-WebServicesVirtualDirectory command.
If the issue persists, please post the error here for further analysis.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

Certificates for Office 365 Hybrid Exchange 2010 Exchange Online v15

Certificates for Office 365 Hybrid Exchange 2010 Exchange Online v15
We need to set up a hybrid server to allow us to begin moving mailboxes to Exchange Online. We created a new Server 2012 R2 server with Exchange 2013 SP1 to act as our Hybrid server. Reading the literature leaves me with questions about what
certificates I need. My understanding is that the certificates in play on the on-premise Exchange 2010 servers don't need to be changed.
I've looked at the TechNet article "Certificate requirements for hybrid deployments"
http://technet.microsoft.com/en-us/library/hh563848(v=exchg.150).aspx
Certificate requirements for the new Exchange 2013 SP1 server are still unclear to me, I think the new server needs a SAN certificate with:
Hybridserver.domain.edu
autodiscover.domain.edu
EWS.domain.edu
Can anyone clarify?

Cert is required only if you want to deploy ADFS for SSO.
Otherwise you can use your existing Cert for all the Services
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Office 365 to Exchange 2010 Hybrid Mail Box Migration

I'm working on setting up a pilot for Office 365. We have Exchange 2010 SP3, in a DAG configuration (two front end, and 2 mail box servers). I have setup the hybrid configuration. All firewall ports are open.
Problem 1: We can move mail boxes up to office 365 with out a problem. When we try to move them back we get
"[email protected]
Status: Failed
[email protected] Skipped item details
Data migrated: Migration rate: Error: MigrationTransientException: The call to ‎'https://webmail.contoso.com/EWS/mrsproxy.svc City-ExchCAS1.contoso.local ‎(14.3.178.0 caps:05FFFF)‎‎' failed. Error
details: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults ‎(either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior)‎
on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.. --> The call to ‎'https://webmail.contoso.com/EWS/mrsproxy.svc
City-ExchCAS1.contoso.local ‎(14.3.178.0 caps:05FFFF)‎‎' failed. Error details: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults ‎(either from ServiceBehaviorAttribute
or from the <serviceDebug> configuration behavior)‎ on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.. --> The
server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults ‎(either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior)‎ on the server
in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs."
I know someone is going to say "Trun on IncludeExceptionDetailInFaults", please tell me how to do that. I'm not an exchange expert, or an IIS expert.
Problem 2: We can email to account in Office 365. Office 365 can't email to on-site exchange. We do have Mimecast as a spam filter, and I've been digging in that to see if that is a problem.
Just looking to see if anyone has an idea of thing to check for this.

Fixed
1. Connect to the Office 365 Portal http://portal.microsoftonline.com
2. Click “Admin” in the upper left hand corner and go to “Exchange”
3. Click “migration”
4. Click “+” and then “Migrate from Exchange Online”
5. Click “+”
6. Add the users that you need to move back to Exchange on site at Dedicated Computing
7. Click “next”
8. Click “next”
9. Put any name for “*New migration batch name:”
10. Put <your email domain> for “*Target delivery domain:”
11. Put GUID of target database in for “*Target database:”
Commands for Exchange Management PowerShell to find GUID
i. Get-MailboxDatabase
ii. Get-MailboxDatabase <insert database name from last command> |fl
12. Click “next”
13. Make sure both radio buttons for Automatically are check, and click “new”

UAG 2010 SP3 - OWA Exchange 2010 - Large attachments fail to open

We have a UAG 2010 SP3 server in front of Exchange 2010 CAS. On the UAG side we have disabled the component installation and activation for UAG within the session configuration. When users access OWA and open attachments it works fine up until a certain
size of an attachment. Somewhere around 10MB we are unable to download externally from OWA. At that point when clicking on the attachment a "The page cannot be displayed" is received.
Attachments of sizes larger than 10MB are able to be opened internally accessing the CAS directly. Under the Download/Upload configuration of the OWA application in UAG Identify by URL is checked for both (Uploads has Identify by size but Download
is unchecked).
Is there a limitation on UAG to OWA download size? Is there any other configuration that should be checked to alleviate this issue?

The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.
home page, and then look for links to the information you want.
Click the Refresh button, or try again later.
HTTP 500 - Internal server error
Internet Information Services
Technical Information (for support personnel)
More information:
<requestLimits maxAllowedContentLength="35000000" />
in web.config doesnt helped

OWA Exchange 2010 and 2013 Co-Existance

Hi All
I have 2 new Exchange 2013 Multi role servers in a test environment. I have setup the namespace's in the following way
Communcal OWA URL - exchange.domain.co.uk/owa
Server 2013 Boxes
OWA URL Internal and External - owa.domain.co.uk/owa
Server 2010 Boxes
OWA Internal - legacy.domain.co.uk
OWA External - legacy.domain.co.uk
Authentication on Exchange 2010 boxes is set to basic, form based.
Authentication on Exchange 2013 boxes is set to basic and form based.
When users hit are exchange.domain.co.uk/owa it is sent to 2013 servers. This we then want to process all requests and proxy connections to 2010. Accessing a 2013 mailbox is fine, however 2010 users just get the message, opening mailbox, it then sticks on
Still Working on it for indefinite and never progress'.
Have tried removing the External URL from 2010 as I have seen suggested elsewhere but this makes no difference.
ECP address' match what OWA are and certificates include all 3 namespaces.
Many THanks in advance for any assistance
Jason

Hi All
I have 2 new Exchange 2013 Multi role servers in a test environment. I have setup the namespace's in the following way
Communcal OWA URL - exchange.domain.co.uk/owa
Server 2013 Boxes
OWA URL Internal and External - owa.domain.co.uk/owa
Server 2010 Boxes
OWA Internal - legacy.domain.co.uk
OWA External - legacy.domain.co.uk
Authentication on Exchange 2010 boxes is set to basic, form based.
Authentication on Exchange 2013 boxes is set to basic and form based.
When users hit are exchange.domain.co.uk/owa it is sent to 2013 servers. This we then want to process all requests and proxy connections to 2010. Accessing a 2013 mailbox is fine, however 2010 users just get the message, opening mailbox, it then sticks on Still
Working on it for indefinite and never progress'.
Have tried removing the External URL from 2010 as I have seen suggested elsewhere but this makes no difference.
ECP address' match what OWA are and certificates include all 3 namespaces.
Many THanks in advance for any assistance
Jason

Unable to open Public Folders in Outlook or OWA (Exchange 2010)

Exchange 2010 Public folders can not be opened from Outlook or from OWA, in the ADIS I do not see Folder Hierarchies. Under the public folder Management Console,i get an error that states "You cant perform this operation because public folder
database isnt mounted. Please mount it and try afain, It wsas running the command ger-publicfolder -getchildren -identity "\"-server 'MBXserver'"

Run "Get-PublicFolderDatabase" and see what it says the status of the database is. This error implies that the database in offline. You will also want to find the status of your public folder copies.
Get-PublicFolder -Recurse | Ft
or
Get-PublicFolder -Recurse | Export-Csv PublicFolderStatus.csv -NoTypeInformation
The first will work if you are checking a small number of folders, but you'll want the latter if you have many of them.

Out of office replies in Exchange 2013 not working for external recipients

Hi,
Few days ago a couple of company workers went to vacation. They set up OOF automatic replies in OWA 2013. However automatic replies are not working for external recipients (outside of company). Internal users (company users) receive OOF notification.
I'm using smart host in sender connector configuration (SMTP server of internet provider) to deliver emails. Any clues about this problem ? Please find below part of the transaction log. For testing purposes i set up administrator account
to be on vacation.
HARED... SMTP
[email protected]
{[email protected]}             Automatic reply: vacation test
RECEIVE SMTP
[email protected]
{[email protected]}             Automatic reply: vacation test
DROP     ROUTING
[email protected]
{[email protected]}             Automatic reply: vacation test
AGENT... AGENT    [email protected]
{[email protected]}             Automatic reply: vacation test
HARED... SMTP
[email protected]
{[email protected]}             Automatic reply: vacation test
RECEIVE SMTP
[email protected]
{[email protected]}             Automatic reply: vacation test
AGENT... AGENT    [email protected]
{[email protected]}             Automatic reply: vacation test
TRANSFER ROUTING [email protected]
{[email protected]}             Automatic reply: vacation test
FAIL     SMTP
[email protected]
{[email protected]}             Automatic reply: vacation test

Hi Informus,
Please check if it is allowed in AllowedOOFType of the Remote Domain *
In Exchange 2013, the only way to see or change the current configuration for automatic replying and forwarding to the Internet is via the Exchange Management Shell (EMS) with PowerShell commands.
To get the currently configured Remote Domains, use:
Get-RemoteDomain
Name                           DomainName
AllowedOOFType
Default                        *
External
Get-RemoteDomain Default | fl AllowedOOFType, AutoReplyEnabled, AutoForwardEnabled
AllowedOOFType     : External
AutoReplyEnabled   : False
AutoForwardEnabled : False
To change the settings, use the Set-RemoteDomain command.
Enable automatic replies
Set-RemoteDomain -AutoReplyEnabled $true
Enable automatic forwards
Set-RemoteDomain –AutoForwardEnabled $true
Enable OOF for Outlook 2003 and previous (for Exchange 2007 and 2010 support)
Set-RemoteDomain –AllowedOOFType $ExternalLegacy
To change all these properties at once, you can use:
Set-RemoteDomain Default -AutoReplyEnabled $true –AutoForwardEnabled $true –AllowedOOFType $ExternalLegacy
Note:
Valid settings for the AllowedOOFType property are:
External
This is the default and only allows for the new style OOF messages as introduced in Outlook 2007.
ExternalLegacy
This settings allows for both the new style and old style OOF messages and needs to be set if you want to enable external OOF support for Outlook 2003 as well.
None
This setting doesn’t allow for the use of OOF messages at all (both internal and external).
InternalLegacy
This setting only allows for internal OOF messages to be sent for all Outlook versions.
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2010 OWA usage in Exchange 2013

Hi,
I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
Before Migration we want below things to keep in mind...
1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
2. Can i use my Existing Exchange certificate to get the above goal done ?
3. What will be the steps and pre-requsite to achieve the Goal ?
An Early reply would be appreciated !!
Amit

Hi Amit
First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
Configure external DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
Ensure that you are having a seperate name for CAS array from external ews url
Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
Authentication for OUtlook Anywhere should be - NTLM
for OWA exchange 2010 - FBA and windows
Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users
You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
Apply a new certificate with all the required site names included in Exchange 2013 CAS.
Whats more you can refer my blog as well
http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
Cheers :)
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

OWA logs user out when they try to set an Out Of Office Message

After upgrading to Exchange 2013 users can no longer set their Out Of Office (via OWA option 'Set Automatic Replies'). When a user tries to do so via OWA they are immediately logged out and get the error message "The user name or password you entered
isn't correct. Try entering it again."
We are currently on CU3, not sure if the problem was introduced in Exchange 2013 initially or once CU3 was applied.
Users see the same behavior when they try to check a Message Delivery Report via OWA.
Stephen

Hi,
Steps as below:
1. Remove-WebServicesVitualDirectory
2. Get-WebServicesVitualDirectory to ensure the website was removed.
3. New-WebServicesVitualDirectory
More details in the following article:
http://technet.microsoft.com/en-us/library/bb125176(v=exchg.150).aspx
I also found a thread about how to rebuild the EWS VD:
http://social.technet.microsoft.com/Forums/exchange/en-US/214932bf-e5ae-4196-8bb8-79a456bc1d10/rebuild-the-ews-virt-directory
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Migrating user from Exchange 2010 to Exchange 2013 succeeds but OWA redirects to 2010

Hello everyone,
I am migrating users from exchange 2010 to 2013, Users migration works perfectly and completes without any issue but after the user migration finishes I try to login to OWA but user goes to OWA exchange 2010 not 2013 as if the mailbox has not been migrated.
I have checked the HomeMDB attribute and I can see the new database on 2013 is located there. how to solve this? I have retransfered the user back to 2010 and 2013 but it didn't work.
I would appreciate your help.
Thanks
Mohammed JH

Hi Amit
After 30 mins approximately we checked the inboxes that have been migrted (2) and we found out they are working.
İ wonder why there is this delay ? İ have already done migration before but it never took this much time. İ would appreciate your reply.
Thanks
Mohammed JH

OOF not working after Exchange 2010 install

I have a Exchange 2007 server environment where I recently installed a new Exchange 2010 server. After installing the 2010 server, my clients are receiving the following error when trying to configure OOF. "Your automatic reply settings
cannot be displayed because the server is currently unavailable. Try again later." I've not moved any mailboxes to the new server, just installed it.
I've done all the tests I can find online and all pass without issue. I'ma able to get to the OOF URL without issue as well.
The 2007 server is on SP 3 rollup 12.

Hi,
The above problem generally occurs because the CAS server uses the credentials that you used to log on to Windows instead of the credentials that you used to log on to the mailbox in Outlook. I recommend you install the hotfix in the following KB to solve
this issue.
"Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later" error when you try to open the Out of Office Assistant in Outlook 2010
http://support.microsoft.com/kb/2596516
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support
Not sure that would be the issue with every machine on the network, plus the user I'm logging in with is the mailbox I need to access so the credentials should be the same.

Upgrading domain controller from Server 2003 to Server 2012 R2, how will this affect Exchange 2010?

Hi All,
Below is an AD and Server related post that I had submitted last week. While I did receive valid responses for the post, I was advised to check with the Exchange forums for the Exchange related question in
bold. All responses are welcomed, thank you!
===========================================================
Hi All,
I am hoping that someone could perhaps provide some insight on this topic as I apparently can't seem to google the best answer.
I have recently acquired an AD domain that is running on a 2003 domain controller. I have been tasked with upgrading our existing domain structure with 2012 R2 domain controllers for our main office and remote offices.
The domain name is company.mynetwork.com, and it is the default first site name. We have multiple offices throughout the US with their own domain controllers (i.e. FL.mynetwork.com, NY.mynetwork.com, DC.mynetwork.com, etc.).
Our main office, and default first site has one domain controller (mynetdc1) running Server 2003 R2. It is also our only DNS server for the main office. It also has an additional domain controller called mynetmaster3 which is running Server 2003.
Both mynetdc1 & mynetmaster3 NTDS settings show them as global catalogs under AD Sites & Services. Both servers are also in the AD Domain Controllers OU, along with all of the other satellite office domain controllers.
Additionally, our main office is running Exchange 2010 with the latest service pack. My questions are:
Can we demote and retire mynetmaster3, then replace mynetdc1 with a newly promoted 2012 R2 global catalog domain controller without harming anything in the domain tree and interrupting connectivity to the other offices (this of course goes without saying
after a 4 hour maintenance window to get the task completed has passed)?
Should we upgrade the satellite offices first after raising the functional level for mynetdc1, or should we do the opposite (upgrade main office, then satellite offices)?
MS Exchange 2010 is heavily dependent on AD, what effect will this entire project have on our email server? What steps should we take beforehand to ensure email continuity?
Finally, is there any shame for a Net Admin to suggest that we hire an implementation specialist for this task? :)
Any advice would be greatly appreciated!

As long as the operating system on your Exchange servers isn't upgraded, and as long as you do the Active Directory domain and forest updates in the supported manner (the following link is a good example -
http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/), Exchange will happily operate behind the scenes. Exchange 2010 is supported in the Windows
forests (domain controllers, domain functional level and forest functional level) mentioned in the following TechNet article, which includes both Windows 2003 and Windows 2012.
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Due to this, you should be good as long as you do the domain controller, domain, and forest upgrades carefully. Oh, and before you start each step, get a nice backup.

DB size for exchange 2010

Hello,
How do I find out the database size in Exchange 2010 please?
Kind Regards,
Jerome

You can use powershell commandlet.
Get-MailboxDatabase -Status | FL ServerName, Name, DatabaseSize
Regards
SK

Exchange Server 2010 SP3 RU3 - OWA - Out of Office issue

Hi,
We have just upgraded out test lab to Exchange 2010 SP3 RU3.
We have 2 CAS-servers and 2 Mailbox-servers. All servers er fully patched.
Question - reason for upgrading is that our Production environment is running Exchange 2010 SP2 RU7, and we have issues with IE 11(light mode only) which is resolved in SP3 RU3. But we have discovered a another issue after upgrading.
After upgrading Exchange, IE 11 is fixed at the login screen, and we can now choose which login methode we want to use, so this is good.
But if you login with IE 11 chosse Options > See all Options > Organize E-mails > Automatic Replies - then the page is blank.
If you choose to use Firefox or Chrome everything is working correctly..
Does any else have the same problem?

Hi,
Yes, running in IE’s compatibility mode is a temporarily workaround. Let’s wait for the update.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 - OWA "Something Went Wrong", Out of office in Outlook "Server unavailable"

Hi,
We have a new deployment of Exchange 2013 CU2 V2 running on a Windows 2012 server. Everything has been running without issues and then without any real clue to why, we are now getting an issue where OWA says "Something Went Wrong" after processing
your login, (it appears to process the login as if I type in incorrect details it tells me the password/username is wrong).
At the same time we have also lost the ability to run the Out Of Office in Outlook which comes back saying the server is not available and we can't seem to share calendars correctly either. (Can set Out Of Office via the Management Shell without issues).
When running a Get-Serverhealth on the OWA.Protocol it tells me the OWASelfTestMonitor is unhealthy.
I've tried re-creating the OWA, EWS Virtual Directorys and also the autodiscover but with no effect. I've also restarted the server.
Outlook 2013 and mobile phones are working fine on the server and the Exchange Admin Centre is also working without issues.
I am getting tempted to apply CU2 again to see if this sorts it but don't really like doing this on a server with 50 live users on it...
In the eventlog I can see lots of the 2 errors listed below which seems to line up. (System Log and Application Log seem to be clear of other errors or warnings.)
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 04/11/2013 11:25:00
Event time (UTC): 04/11/2013 11:25:00
Event ID: 2fcdb9112c794b63a9ea9577a23e4603
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/owa-411-130280378905273269
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
    Machine name: SERVERNAME (I altered this for post)
Process information:
    Process ID: 9648
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: HttpException
    Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Lots more code.......
AND
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 04/11/2013 11:24:24
Event time (UTC): 04/11/2013 11:24:24
Event ID: 2586a044b2d74b97a1095aec478bf4ae
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/EWS-668-130280378564324526
    Trust level: Full
    Application Virtual Path: /EWS
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\EWS\
    Machine name: SERVERNAME (I have changed this for post)
Process information:
    Process ID: 9840
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: HttpException
Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
lots more data...

Hi Angela,
I can't see any re-directions on the website and have certainly not set any intentionally. I did try installing the Remote Web Gateway on the server and then found that it doesn't work on an exchange box and removed it but the server was working after
this.
The HTTP Redirect in Default Web Site is not showing anything set and the same for the Back End.
The bindings on the default site all look normal with;
http     80   127.0.0.1
https   443 127.0.0.1
http     80    *
http    443   *
The same is mirrored in the Exchange Back End site but with ports 81 and 444.
Running the Outlook auto configure just using Autodiscover all looks good with the URLs listed all pointing to (http)://mail.mydomain.co.uk/whatever... and the log says Autodiscover to (https)://mail.mydomain.co.uk/Autodiscover/Autodiscover.xml Suceeded
(0x00000000)
But, if I type in the OOF address of (https)://mail.mydomain.co.uk/EWS/exchange.asmx I get a login prompt but once user details are entered I then get;
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
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.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
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.
Stack Trace:
[XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) +163
   System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() +7572550
   System.Xml.XmlTextReaderImpl.ParseDocumentContent() +62
   System.Xml.XmlReader.ReadToFollowing(String name) +112
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.ReadKillBitXmlContent(XmlReader reader, Int32& refreshRate) +185
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.TryReadKillBitFile(Int32& refreshRate, DateTime& lastModifiedTime) +710
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitTimer.Start() +202
   Microsoft.Exchange.Services.Global.Application_Start(Object sender, EventArgs e) +975
[HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12864205
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475
[HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12880948
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12722137
Really wishing I had installed Exchange 2010 at this point!! Just can't see why its not working :(

Out of Office on OWA; Exchange 2010

Similar Messages

Maybe you are looking for