Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3732
  • Last Modified:

What is causing SharePoint Application Event Log Error 6875's

I have a MOSS 2007 server, running on Windows Server 2003, that is showing Error 6875 in my application event logs - I don't have any unique changes or additions to this server prior to this error popping up.  And I can't seem to find any information specific to the message I get:
Event Type:          Error
Event Source:       Windows SharePoint Services 3
Event Category:    General
Event ID:                6875
Date:              1/11/2010
Time:              7:17:48 PM
User:              N/A
Computer:              [Server Name]
Error loading and running event receiver Microsoft.SharePoint.Publishing.Internal.PublishingWebEventReceiver in Microsoft.SharePoint.Publishing, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Additional information is below.

: Access denied.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I don't know how to go about finding the root cause of this error - I get 5-10 of them on a daily basis.  

Any help would truly be appreciated.
1 Solution
juandissimoAuthor Commented:
Hey thanks - I took a look at that once before but since the example given wasn't an ":access denied" I was skeptical about it being the same issue - I'll take a look at it again though. Thanks for the quick response.
Try adjusting your Application Pool Memory settings for a higher number to see if that helps. You can do that in Computer > right-click > Manage >  expand "Services and Applications" > IIS Manager >  Right-click on the Application Pool for your SharePoint site that is having the error > Select Properties. On the "Recycling" tab, if you have the two check boxes on the bottom selected, try raising the memory allocations. I have mine set to 1700 and 1000 respectively.
That is the wrong answer. The proposed solution, a different Error Message, which is just informational. However, the error message above is "critical", not informational and "Access Denied", not "Invalid List Item. The List Item provided is not compatible with a Scheduled Item."

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now