Joe, Event handler is triggered by Sharepoint Timer Service and not w3wp.exe IIS process. Timer Service will try to look the DLL in GAC.
There are several possibilities of this error: - DLL not in GAC - DLL details (eg. namespace, public key token, etc) mentioned in your Feature.xml doesn't match the one in GAC Cheers, Tommy From: [email protected] [mailto:[email protected]] On Behalf Of Daniel W. Brown Sent: Sunday, 14 February 2010 8:12 AM To: ozMOSS Subject: RE: Event Handler Not Firing In short, its saying that it cannot FND the assembly or namespace associated with the event handler. Check the Namespace, Assembly name and Token Info on the list attached to SharePoint. The type is "CreateDocID.CreateDocID", this would appear not to match what is in your assembly. From: [email protected] [mailto:[email protected]] On Behalf Of Joe Breen Sent: Sunday, 14 February 2010 9:37 AM To: ozMOSS Subject: Re: Event Handler Not Firing After installing the SPLogFileViewer I am finally seeing an error in both the Event Log and the SPLogFileViewer. SharePoint did not write this error to the Event log before installing the LogFileViewer. The error I am seeing is: Event manager error: Could not load type 'CreateDocID.CreateDocID' from assembly 'CreateDocID, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1f41dcd496414d1a'. There seems to be scant information available on how to fix this but I have copied the CreateDocID.dll into the BIN folder in wwwroot and registered the assembly in web.config. So there's something wrong with my assembly even though I have installed it using command line and also tried through Deploy function in WSPBuilder in VS 2008. Using these before worked fine for previous Event Receivers. Yet this method of deployment now does not seem to work. Anyone know how to fix this "Could not load type" error?
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
