Applies to Calendar E-Mail Extension, Event Management and Employee Training Management.
You may remember that a while ago we wrote about how to troubleshoot incoming e-mails.
If you have followed the instructions in the previous article and are still experiencing problems with e-mails disappearing from the drop folder and the invite status not being updated, this blog post will help you troubleshoot your problems further.
Firstly this article only refers to SharePoint run on multi-server farms. The problem is that the e-mail responses are delivered to the SMTP server on SharePoint and then appear in the drop folder on the server. However, they then disappear from the folder and are not delivered to the calendar.
Calendar E-mail Extension: The invite status should be updated with the response (Accepted, Declined, Tentative,…)
Employee Training Management and Event Management: The Reply column should be updated with the response (Accepted, Declined, Tentative,…)
Depending on the solution and SharePoint version the error in the SharePoint trace log (ULS log) will look like this:
Calendar E-Mail Extension:
SP2010:
Critical Event manager error: Could not load file or assembly 'Sapiens.at.SharePoint.CEE, Version=14.1.0.0, Culture=neutral, PublicKeyToken=a1ab8b914ceb8a5a' or one of its dependencies. The system cannot find the file specified.
Critical Event manager error: Could not load file or assembly 'Sapiens.at.SharePoint.CEE, Version=14.1.0.0, Culture=neutral, PublicKeyToken=a1ab8b914ceb8a5a' or one of its dependencies. The system cannot find the file specified.
SP2013:
Critical Event manager error: Could not load file or assembly 'Sapiens.at.SharePoint.CEE, Version=15.1.0.0, Culture=neutral, PublicKeyToken=a1ab8b914ceb8a5a' or one of its dependencies. The system cannot find the file specified.
Critical Event manager error: Could not load file or assembly 'Sapiens.at.SharePoint.CEE, Version=15.1.0.0, Culture=neutral, PublicKeyToken=a1ab8b914ceb8a5a' or one of its dependencies. The system cannot find the file specified.
Employee Training Management:
SP2010:
Critical Event manager error: Could not load file or assembly Sapiens.at.SharePoint.ETM, Version=14.2.0.0, Culture=neutral, PublicKeyToken= 77dea521c6b64f5d’ or one of its dependencies. The system cannot find the file specified.
Critical Event manager error: Could not load file or assembly Sapiens.at.SharePoint.ETM, Version=14.2.0.0, Culture=neutral, PublicKeyToken= 77dea521c6b64f5d’ or one of its dependencies. The system cannot find the file specified.
SP2013:
Critical Event manager error: Could not load file or assembly Sapiens.at.SharePoint.ETM, Version=15.2.0.0, Culture=neutral, PublicKeyToken= 77dea521c6b64f5d’ or one of its dependencies. The system cannot find the file specified.
Critical Event manager error: Could not load file or assembly Sapiens.at.SharePoint.ETM, Version=15.2.0.0, Culture=neutral, PublicKeyToken= 77dea521c6b64f5d’ or one of its dependencies. The system cannot find the file specified.
Event Management:
SP2010:
Critical Event manager error: Could not load file or assembly Sapiens.at.SharePoint.EVM, Version=14.1.0.0, Culture=neutral, PublicKeyToken= be3cff37ee9f0eea' or one of its dependencies. The system cannot find the file specified.
Critical Event manager error: Could not load file or assembly Sapiens.at.SharePoint.EVM, Version=14.1.0.0, Culture=neutral, PublicKeyToken= be3cff37ee9f0eea' or one of its dependencies. The system cannot find the file specified.
SP2013:
Critical Event manager error: Could not load file or assembly Sapiens.at.SharePoint.EVM, Version=15.1.0.0, Culture=neutral, PublicKeyToken= be3cff37ee9f0eea' or one of its dependencies. The system cannot find the file specified.
Critical Event manager error: Could not load file or assembly Sapiens.at.SharePoint.EVM, Version=15.1.0.0, Culture=neutral, PublicKeyToken= be3cff37ee9f0eea' or one of its dependencies. The system cannot find the file specified.
If you receive these errors, the assembly files used for processing incoming e-mails are missing from the server’s global assembly cache. Please check that this is the case by looking in the following folders:
SharePoint 2010:
C:\Windows\assemblyC:\Windows\assembly
SharePoint 2013:
C:\Windows\Microsoft.NET\assembly\GAC_MSIL
C:\Windows\Microsoft.NET\assembly\GAC_MSIL
If you cannot find the assembly in these folders, this is because the solution is not deployed on the server which processes incoming e-mails. Take a look at the farm solutions in Central Administration.
There are two possible ways to solve this. You either have to deploy the solution on the application server, or you have to process incoming e-mails on a front end server where the solution is already deployed.
I hope you found this guide useful. If you have any problems or any other questions, please send an e-mail to [email protected] or post a comment.
