gmonks Posted September 27, 2013 Posted September 27, 2013 Hi, Sorry if this is posted in the wrong section. We have a very odd problem on our machines. When opening attachments of any size in web mail IE crashes and throws the error "the action you requested could not be completed please refresh your web browser and try again" I started trying to resolve this problem yesterday and it seemed to be okay in Chrome and in IE with no addons. However, today when I open an attachment in IE with no addons it crashes. I started looking through our group policies yesterday and I managed to nail it down to one policy that was making it crash. However, today when I disable that same policy it still crashes. I'm at a loss as to what the problem could be, it doesn't make any sense! Exchange is also up to date with SP3. Any ideas would be welcomed. Cheers. George.
sukh Posted September 27, 2013 Posted September 27, 2013 same messages/attachments/type/user cause the same crash? can you reproduce this easily?
gmonks Posted September 30, 2013 Author Posted September 30, 2013 same messages/attachments/type/user cause the same crash? can you reproduce this easily? It's not the same message, or size of the attachment. I'll attach a screenshot. So you open the attachment and IE just freezes up.
gmonks Posted September 30, 2013 Author Posted September 30, 2013 Happens to all users who have attachments? Yes. Any user on any Windows 7 machine using IE.
sukh Posted September 30, 2013 Posted September 30, 2013 To rule out your build and network, have you tried from external connection using home PC?
gmonks Posted September 30, 2013 Author Posted September 30, 2013 To rule out your build and network, have you tried from external connection using home PC? Yes, opening attachments work fine externally at home. I think it's something to do with the group policies?
glen_j Posted September 30, 2013 Posted September 30, 2013 I don't think disabling a policy reverts the changes made. you might need to find what setting is causing it and change that.
sukh Posted September 30, 2013 Posted September 30, 2013 What if you create a temp OU, with only the Default Domain policy and move test PC in there. Also, if you have User Policy, exclude those. You say it works in IE without add-ons. So if you test this with the GPO's you have applied to the user & PC. Are you getting consistent behaviour?
gmonks Posted September 30, 2013 Author Posted September 30, 2013 (edited) What if you create a temp OU, with only the Default Domain policy and move test PC in there. Also, if you have User Policy, exclude those. You say it works in IE without add-ons. So if you test this with the GPO's you have applied to the user & PC. Are you getting consistent behaviour? I moved a PC into a test OU with the default domain GPO's and it still crashes. So it must be one of those three policies? EDIT: If I run gpresult /r it says "The following GPOs were not applied because they were filtered out" it then goes on to list the three default domain policies. Edited September 30, 2013 by gmonks Extra info
sukh Posted September 30, 2013 Posted September 30, 2013 OK, remove all GPO's applied to that GPO. Update, then check again.
gmonks Posted September 30, 2013 Author Posted September 30, 2013 OK, remove all GPO's applied to that GPO. Update, then check again. That didn't seem to make a difference. It looks like our support company may have changed something. We have passed the issue onto them. Thanks for the help and will let you know what the problem is/was. George.
sukh Posted September 30, 2013 Posted September 30, 2013 Well it doesn't seems like a Exch issue. I would say it's a build/gpo/add-ons issue. You can probably isolate those.
sukh Posted October 1, 2013 Posted October 1, 2013 what happened? have you tried a different browser on internal network?
RobBaxter Posted October 2, 2013 Posted October 2, 2013 I had this ... have you installed all the latest updates and services packs for exchange. We found out it was our web filter in the end breaking OWA. Mailboxes of large sizes replicate the issue more than smaller ones. Our solution was to install Exchange 2012. If you can't do that... Check that you don't have 2 million transaction log files.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now