Windows Server TechCenter > Windows Server Forums > Group Policy > Unhandled exception with Group Policy Prefences on Windows 7

Answered Unhandled exception with Group Policy Prefences on Windows 7

  • Friday, September 25, 2009 3:17 PM
     
     

    Hello, we are experiencing problems with group policy prefences with Printers in Windows 7. The problem appears to be related to using Item-Level Targeting that filters a Security Group Item for the Computer account.  We map our printers based on what security group a computer is a member of.

    Event Log generates a Warning and an Error:
    Warning:
    The user '7th Floor Training Room Printer' preference item in the 'Mapped Printers {44848843-5E88-444B-8AA8-620A1B4F6E33}' Group Policy object did not apply because its targeting item failed with error code '0x86012004 The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x2d000000; the memory at 0x2d000000 could not be ???s??Ą.'%100790275' This error was suppressed.

    Error:
    The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x2d000000; the memory at 0x2d000000 could not be ???s??Ą.' See trace file for more details.

    Trace shows:
    2009-09-25 10:12:12.070 [pid=0x3b4,tid=0x6b4] Starting filter [AND FilterRunOnce].
    2009-09-25 10:12:12.072 [pid=0x3b4,tid=0x6b4] Starting filter [AND FilterGroup].
    2009-09-25 10:12:12.170 [pid=0x3b4,tid=0x6b4] Failed filter [FilterGroup]. [ hr = 0x86012004 "The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x00000000; the memory at 0x00000000 could not be ???þ.'%100790275" ]
    2009-09-25 10:12:12.172 [pid=0x3b4,tid=0x6b4] Filters error. [ hr = 0x86012004 "The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x00000000; the memory at 0x00000000 could not be ???þ.'%100790275" ]
    2009-09-25 10:12:12.177 [pid=0x3b4,tid=0x6b4] Cannot suppress an unhandled exception. [ hr = 0x86012004 "The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x00000000; the memory at 0x00000000 could not be ???þ.'%100790275" ]
    2009-09-25 10:12:12.179 [pid=0x3b4,tid=0x6b4] Completed class <SharedPrinter> - 7th Floor Training Room Printer. [ hr = 0x86012004 "The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x00000000; the memory at 0x00000000 could not be ???þ.'%100790275" ]
    2009-09-25 10:12:12.182 [pid=0x3b4,tid=0x6b4] Cannot suppress an unhandled exception. [ hr = 0x86012004 "The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x00000000; the memory at 0x00000000 could not be ???þ.'%100790275" ]
    2009-09-25 10:12:12.183 [pid=0x3b4,tid=0x6b4] Completed class <Printers>. [ hr = 0x86012004 "The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x00000000; the memory at 0x00000000 could not be ???þ.'%100790275" ]
    2009-09-25 10:12:12.185 [pid=0x3b4,tid=0x6b4] Completed package execution. [ hr = 0x86012004 "The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x00000000; the memory at 0x00000000 could not be ???þ.'%100790275" ]
    2009-09-25 10:12:12.187 [pid=0x3b4,tid=0x6b4] Completed execution of apply package. [ hr = 0x86012004 "The client-side extension caught the unhandled exception 'filter expand' inside: 'Access violation (0xc0000005) occurred at 0x00000000; the memory at 0x00000000 could not be ???þ.'%100790275" ]

    I have confirmed that this happening for Printer preference items on both Windows 7 RTM and Windows Server 2008 R2 RTM (Windows Vista machines work fine).  I have searched the internet for this issue and the only thing I found was related to AGPM, which we do not use.

    Has anyone else experienced this problem, or have any suggestions to a solution?

    Thanks! 

Answers

All Replies

  • Monday, September 28, 2009 2:00 AM
     
     

    Yep we're seeing exactly the same thing with any Group Policy preference - printers, shortcuts etc - on Windows 7 when Item Level Targetting specifies a Security Group. Apart from removing the targetting, I don't know of any resolution.

  • Tuesday, September 29, 2009 10:56 AM
    Moderator
     
     
    Hi,

    This is a known issue of Windows 7 GPP client-side extension. Product Team is working on this issue. If there is any update, I will post here.

    Thanks.

    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Tuesday, September 29, 2009 11:00 AM
     
     
    Thanks Mervyn
  • Tuesday, September 29, 2009 12:28 PM
     
     
    Thanks Mervyn!  Is there any sort of estimated ETA for a fix?  (So we know approx. how long we need to hold off on our mass Win7 deployments).  Thanks!
  • Tuesday, September 29, 2009 12:43 PM
     
     
    Would have been nice if the Product Team had admitted their horrible implementation of the CSEs in my post from over a month ago:

    http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/fa8eb821-4f7c-4478-b913-e7724bf53968/
  • Tuesday, October 20, 2009 2:28 PM
     
     
    It's been several weeks, we've had another patch Tuesday and Windows 7 is just about available for the public... do we have a fix?

    Thanks
  • Thursday, October 22, 2009 3:11 PM
     
     
    I'm trying to decide on the title for today's post, perhaps someone can help:

    "Windows 7 is released, but is incompatible with Windows."

    "Microsoft warns that Windows 7 is for home users, not for Enterprise."

    "Windows 7 ushers in paperless world as known bug."

    "Windows 7 snubs Admins: "Who needs to print?"


  • Thursday, October 22, 2009 4:06 PM
     
     
    Yes, this is causing us a lot of problems, any ETA for a fix (now that Win7 is GA, we are being pressured to get this fixed now)?  Thanks!
  • Friday, October 23, 2009 1:07 AM
    Moderator
     
     
    Hi,

    The KB976399 was now available to fix this problem. Please try to contact CSS to get the hotfix.

    Thanks.

    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Friday, October 23, 2009 4:53 PM
     
     
    Mervyn, I contacted MS Support to attain the hotfix and was informed that the hotfix has been put on hold for further testing and changes by development.  Do you have any further information on this fix?  Thanks!
  • Monday, October 26, 2009 1:58 AM
    Moderator
     
     
    Sorry, I don’t have more information than CSS. They are in fact authority in hotfix issue.

    Thanks.

    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Tuesday, November 03, 2009 4:30 AM
     
     
    Hey all,

    I am experiencing the same problem. Any got the hotfix from MS CSS yet?

    Mark
  • Tuesday, November 03, 2009 2:20 PM
     
     
    Has there been any progress with this? we are also suffering with this problem.

    Al
  • Tuesday, November 03, 2009 4:00 PM
     
     
    I still have not been able to get the hotfix from Microsoft (I have an open case with support), has anyone else had any luck?
  • Wednesday, November 04, 2009 11:55 AM
     
     
    has anyone tried using the ldap query trigger?
  • Friday, November 06, 2009 9:00 PM
     
     
    I'm having the same issue - printers work fine on Vista, unhandled exception error in event log on all Windows 7 machines.
  • Saturday, November 07, 2009 12:29 AM
     
     
    http://www.google.com/search?q=KB976399 - you can now find the update through, err, unofficial channels. I haven't tested it, but will Monday. This being the case I'd have thought Support will supply it now.
  • Monday, November 09, 2009 9:22 AM
     
     
  • Monday, November 09, 2009 7:26 PM
     
     
    I have also done some preliminary testing and all of my GPPs are now processing correctly on Windows 7.  I plan on doing a little more testing before I give my desktop group the thumbs up to start rolling Win7 out to the masses, but it's looking very promising now.  Thanks a million hornetfig & arowanuk!!!!
  • Wednesday, November 11, 2009 3:29 PM
     
     
    Any word on the "official" hotfix?  Will it be the same number as mentioned in this thread?
  • Thursday, November 19, 2009 3:40 PM
     
     
    Is there a status update on when something official will be available?  It's ridiculous that 1 month after general release, this OS is not usable in a corporate environment due to issues reported back in September.

    And they wonder why businesses like to wait for the first SP.
  • Tuesday, December 01, 2009 12:18 PM
     
     
    3 months since first reported, and still no fix.
  • Thursday, December 10, 2009 9:03 AM
     
     Answered
    • Proposed As Answer by OpsTech Thursday, December 10, 2009 9:48 AM
    • Marked As Answer by Mervyn ZhangModerator Thursday, December 10, 2009 10:18 AM
    •  
  • Thursday, December 10, 2009 10:20 AM
    Moderator
     
     
    Good news!
    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Thursday, December 10, 2009 1:22 PM
     
     
    Great!  Thanks for letting us know the KB has appeared; will be getting this rolled out today!
  • Thursday, December 10, 2009 2:47 PM
     
     
    I have installed the hotfix. It solves the problem!
  • Tuesday, March 09, 2010 1:00 PM
     
     
    I have the same problem, BUT with a little twist. The difference is that I make a ILT which filters on a user security group instead of a computer security group. I try to copy a file from a DFS share to the users desktop. When I remove/disable this single ILT filter (1 out of 4 ILT filters), the GPO works perfectly.
    I have installed hotfix from KB976399 on my Windows 7 Enterprise x64 computer.
  • Tuesday, June 15, 2010 9:00 PM
     
     

    I am having this exact problem only it is with Windows 2008 Server NOT Windows 2008 R2 Server.  The hotfix only applies to the R2 version of Windows 2008.  What can I do for a non-R2 version of Windows 2008?

     

    Thanks,

     

    -A