When you upload .NET Framework assemblies or use the LobSystem.DeleteProxyAssembly() function, this does not flush the assembly cache of dependent assemblies for a .NET Framework connector in a SharePoint Server 2010 LobSystem

Symptoms

Consider the following scenario:

  • You have a server that is running Microsoft SharePoint Server 2010 together with Enterprise client access license (CAL) enabled.

  • You update a Microsoft .NET Framework connector and its primary and dependent assemblies.

  • You upload the .NET Framework assemblies to the LobSystem on the SharePoint 2010 server, or you use the LobSystem.DeletProxyAssembly function to flush out the dependent assemblies.

In this scenario, the dependent assemblies are not flushed out of the .NET Framework connector.

Cause

This issue occurs because, when you upload new .NET Framework assemblies or you use the LobSystem.DeletProxyAssembly function, this overwrites the primary assembly of a .NET Framework connector. However, uploading new .NET Framework assemblies or using the LobSystem.DeletProxyAssembly function does not overwrite the dependent assemblies that are associated with the connector.

Resolution

To resolve the issue, you have to reset Internet Information Services (IIS). Resetting IIS flushes out all assembly caches and then loads the new assemblies. To do this, follow these steps:

  1. Click Start, point to All Programs, and then click Accessories.

  2. Right-click Command Prompt, and then click Run as administrator.

  3. At the command prompt, type iisreset, and then press ENTER.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×