Re: Out of Office Not working - BUG???

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On May 19, 10:46 pm, Lava Flow James <sp2...@xxxxxxxxx> wrote:
Group,

I'm stumped.  I get this error in my logs:

Watson report about to be sent to dw20.exe for process id: 5512, with
parameters: E12IIS, c-RTL-AMD64, 08.01.0240.006, WS, unknown,
M.E.S.E.<>c__DisplayClass7.<GetUserOofSettings>b__4,
System.InvalidCastException, 8842, unknown.  ErrorReportingEnabled:
False

This shows up in my IIS Logs:

2008-05-20 03:13:08 192.168.1.110 POST /ews/exchange.asmx - 443 -
192.168.1.182 HTTP/1.1 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft
+Office+Outlook+12.0.6213;+Pro) - -www.domain.com401 2 5 261 759 15
2008-05-20 03:13:08 192.168.1.110 POST /ews/exchange.asmx - 443 -
192.168.1.182 HTTP/1.1 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft
+Office+Outlook+12.0.6213;+Pro) - -www.domain.com401 2 5 261 294 0
2008-05-20 03:13:08 192.168.1.110 POST /ews/exchange.asmx
SoapAction=GetUserOofSettingsResponse;ADRequests=2;ADLatency=16;TimeInGetUs­erOOFSettings=22;
443 domain\useraccount 192.168.1.182 HTTP/1.1 Microsoft+Office/12.0+
(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - -www.domain.com
500 0 64 0 1413 31
2008-05-20 03:13:08 192.168.1.110 POST /ews/exchange.asmx - 443 -
192.168.1.182 HTTP/1.1 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft
+Office+Outlook+12.0.6213;+Pro) - -www.domain.com401 2 5 261 759 0
2008-05-20 03:13:08 192.168.1.110 POST /ews/exchange.asmx - 443 -
192.168.1.182 HTTP/1.1 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft
+Office+Outlook+12.0.6213;+Pro) - -www.domain.com401 2 5 261 294 0
2008-05-20 03:13:08 192.168.1.110 POST /ews/exchange.asmx
SoapAction=GetUserOofSettingsResponse;ADRequests=2;ADLatency=0;TimeInGetUse­rOOFSettings=8;
443 domain\useraccount 192.168.1.182 HTTP/1.1 Microsoft+Office/12.0+
(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - -www.domain.com
500 0 64 0 1413 15

These IIS log entries show up when a user click on out of office
assistant in outlook 2007.  Everything else works perfectly -
autodiscover, outlook anywhere, etc...

Can change OOF in web client just fine, but not from client.  There is
nothing useful on the web after literally hundreds of searches to find
an answer.  I have installed Rollup 2 onto SP1, so the server is
latest and greatest bits.

I've turned on detailed tracing in IIS and get this in the trace:

ModuleName IsapiModule
Notification 128
HttpStatus 500
HttpReason Internal Server Error
HttpSubStatus 0
ErrorCode 0
ConfigExceptionInfo
Notification EXECUTE_REQUEST_HANDLER
ErrorCode The operation completed successfully. (0x0)

Very frustrating...is this a known bug or a config issue.  The 500
errors showing up the IIS logs tells me it's a bug...but who knows.
Anyone hit this sucker?

J

Should note that the issue in the IIS logs is that the 3rd request
gets a HTTP 500 error. Sorry to dump the raw in there - it doesnt
make for good reading - basically, it's a 401, 401, and 500 sequence.
.

Relevant Pages

  • Re: Hacking attempts?
    ... Windows logs logon type 3 in most cases when you access a computer from elsewhere on the network. ... One of the most common sources of logon events with logon type 3 is connections to shared folders or printers. ... You can use the IIS logs to track down the ip addressthat are attempting unauthorized login. ...
    (microsoft.public.windows.server.sbs)
  • Re: hack attempts howto find ip
    ... IP logging is not offered until Windows XP with ICF firewall ... logs if you have, say, an FTP or NetBIOS attack. ... show up in the IIS logs. ...
    (microsoft.public.inetserver.iis.security)
  • Out of Office Not working - BUG???
    ... This shows up in my IIS Logs: ... ConfigExceptionInfo ... ErrorCode The operation completed successfully. ...
    (microsoft.public.exchange.setup)
  • Re: How/Where do I check the most frequently used Search words?
    ... Or getting the logs into SQL using log parser for example. ... I do not recommend you try and extract the IIS logs straight into a SQL ... Get the IIS logs created on the WFE server and then use Log Parser ...
    (microsoft.public.sharepoint.portalserver)