problem with Outlook Webaccess

[GerbenB]

Hello,

I'm new here. I don't know if I should start a new thread of my own, or not.

I have a problem with Outlook Webaccess. My suspicion is that some internet explorer DLL's are corrupted (I've tried a lot of other things as well), so I've run SFC /scannow a couple of times and it states it has solved some problems/made some repairs, but has also encountered some problems it's unable to solve.

So now I have a CBS.log-file, containing 10.000 lines. I have no idea where in the file to look for files that should be replaced bij good copies or how to find out which action to take next.

Any chance you can help me ? I'd be very grateful.

And please let me know if I should post this someplace else.

Kind regards,

Gerben.

 

[tom982]

Hi Gerben,

I have an exam tomorrow, Wednesday, Friday and the following Monday but will try and find a minute to look at this as soon as possible. If you could zip up and upload your CBS log, that would be very helpful.

Tom

 

[GerbenB]

Hi Tom,

That sounds like an awful lot of exams in a very short time. Good luck with them and I fully understand where your priorities must lie at the moment. That would not be me, probably ...

I've zipped my CBS log and uploaded it. I've run the program a couple of times and have included one older version of the CBS log, just in case.

Gerben.

 

[GerbenB]

Hi Tom,

Hope your exams went well. I also hope you can find some time to look at the file I posted. Would greatly appreciate it.

Gerben.

 

[tom982]

Hi Gerben,

Sorry for the delay!

I've just had a look through your CBS log and can't find any sign of SFC struggling, can you run it again please?

SFC Scan

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   sfc /scannow
   
   Wait for this to finish before you continue
   
   copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
   
   
4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

 

[GerbenB]

Hi Tom,

Remarkable that you don't find any struggling by SFC. Because SFC says it has some problems, though it tells this in Dutch.

Attached you find two files:
* A printscreen of the dos window after running sfc /scannow.
* And a new version of the CBS.log

The line "Er zijn beschadigde bestanden gevonden, maar deze kunnen niet allemaal worden hersteld" in the dos window literally translated means "Some damaged files were found, but these could not all be repaired".

That would appear to be an indication that something is wrong. Hope the attached CBS.txt-file gives you an idea of what that might be.

Gerben.

 

[tom982]

Hi Gerben,

I have to say, this is very strange indeed. There are no signs of any errors in your SFC log, or your CBS log, yet SFC is still returning an error. There are many different areas that could cause SFC to fail, and I would like to check for registry problems to begin with as this is a very common cause. Can you download and install the System Update Readiness Tool please?

Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [November 2013] from Official Microsoft Download Centre

Post the log when complete:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

 

[Slartybart]

An observation: The raw SFC log doesn't look like a normal completion.

It could be a transfer thing, a limitation of my editor, or confusion on my part.
I expect something like this (the posted CBS log just seems to end abruptly)

POQ 122 starts:
 
POQ 122 ends.
2014-01-30 13:12:44, Info                  CSI    000002e7 [SR] Verify complete
2014-01-30 13:12:44, Info                  CSI    000002e8 [SR] Repairing 0 components
2014-01-30 13:12:44, Info                  CSI    000002e9 [SR] Beginning Verify and Repair transaction
2014-01-30 13:12:44, Info                  CSI    000002ea Repair results created:
POQ 123 starts:
 
POQ 123 ends.
2014-01-30 13:12:44, Info                  CSI    000002eb [SR] Repair complete

:ar: The Checksur [SURT] log will tell more.

Bill
.

 

[GerbenB]

Hi Bill,

Thanks for taking a look, too. See the attached picture, which is showing the end of my CBS.log file. It appears to be much like the ending you expected.

Gerben.

 

[Slartybart]

Hi GerbenB,

Yeah, I don't know... it looks normal now.

The scans on 1/28 (early morning, and early evening) show that SFC was making progress.

Tom knows this stuff much better than I do, so I'm going to suggest that you
restart your machine and
run the System Update Readiness Tool [SURT] he requested in post# 7

I'll step out now, but look in every once in a while. The next step is to look at the SURT log.

Bill

 

[GerbenB]

Oops.

I posted the SURT-log here yesterday, I thought. Must have pushed a wrong button. New try.
It looks scarily normal ....

Gerben.

 

[Slartybart]

No errors detected in the log - that's a good sign.

This is an interesting thread; the SFC log looks good, the SFC Cmd window states errors, the SURT is good.

I'm going to step back again and see where Tom wants to go.

Bill
.

 

[tom982]

Hi Gerben,

This is quite possibly the strangest SFC issue I've ever dealt with, and I have to say, I'm not quite sure where to go with this one. I will ask a few friends for assistance, but in the mean time can you try running SFC from boot:

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

I don't usually advise this as it doesn't offer any advantages, but in this case it may well.

Tom

 

[GerbenB]

Hi Tom,

I used a different method from the one described in the tutorial. I went into the startup menu and started the command prompt in safe mode. I thought it'd be easier that way and probably would not make a difference. If it does, tell me, and I'll do it again from a boot command prompt from a Windows 7 DVD. Just didn't have one handy.

CBS.txt file is attached (zipped). Windows told me again it found some flawed files it can't fix.

Maybe telling you exactly what problems I'm experiencing might help you locate the problem ? Any use to make a description ? There's a very strange workaround involving toggling internet explorer safe mode on and off. Not very practical, actually. But it might hint on the cause of the problem.

Gerben.

 

[Slartybart]

Gerben & Tom,

I took a quick look at the cbs log and thought perhaps a different tact might shed some light. so I searched the file for "error" (nothing found) and for "fail".

I've attached the resulting SFC_'fail'-srch.txt file. I don't know what the upload erros are or if they might be causing the Cmd Screen to display an error when the CBS SFCdetails.txt file looks good.

Back to being an observer.

Bill
.

 

[tom982]

@Bill,

Nice try, but all of those errors are perfectly normal. Open up your CBS log and you'll see the same

@Gerben,

I asked a friend (who knows a lot more than me about all of this) for help with this thread and this has stumped him - not many things do! It's something we've both run into before but have no idea what could possibly cause this, especially when the logs are so uninformative. As much as I hate to say this, I think your best bet at this stage is to do a repair install:

http://www.sevenforums.com/tutorials/3413-repair-install.html

Sorry I couldn't have been of more help, but this is somewhat of a strange race condition.

Tom

 

[GerbenB]

Problem solved, sort of ...

Hi Tom (and Bill),

Thanks again for trying to help me out. Sometimes Windows 7 and Microsoft work in such wondrous ways that simple solutions and answers are hard to find. Sorry it wasn't possible to get back to you sooner: I had a week off (helping my son to move) and was very busy afterwards at work.

I tried one last thing, because I was afraid a repair install would eventually lead to a total reinstall.
The problem occurred in IE10, as I wrote. I had uninstalled IE 10 earlier (uninstalling microsoft update), but tried it once more, because, you know, well you never know.
And then all of sudden, I was able to use Outlook Webaccess without any problems in IE9. I then upgraded to IE10 again, hoping the problem would have disappeared there as well. I couldn't help myself. Off course it hadn't helped: still the same 'out of memory' message whenever I tried to open a mail or attachment. The workaround toggling protected mode on or off still worked however.

So I uninstalled IE10 again. After which the solution in IE9 had also magically disappeared. That's what you get (and deserve) when your try to fix something that's not (entirely) broken. Now IE9 also gave the 'out of memory' error and would also only work using the protected mode workaround. Possible but not practical.

And then suddenly: a miracle! When entering Outlook Webaccess everything worked again. After a little research I found out that Windows 7 had opened Webaccess in 64-bit mode. No idea why or how. But: when I start Outlook Webaccess in IE9 64-bit mode my problem is gone.

No inclination to try and fix anything anymore and not upgrading to IE10. I normally use Chrome and only use IE because that's the only browser that will not restrict me to Webacces Light, which misses a lot of functionality.

Thought i'd let you guys know. And this might help others. Possibly even using IE10 in 64-bit mode.

And thanks again for your help.

Gerben.