Server Error in '/meet' Application.

Hello,

I recently updated our Lync server 2010 environment to the latest CU and am now seeing the following error when clicking on the "Join Lync Meeting" button from Outlook invites: "Server Error in '/meet' Application." Meet Now sessions are not affected.

This appears to be only affected for internal users as clicking on the same link externally works correctly and connects to the meeting. Trying to go the meeting URL on the front-end reveals the following stack trace:

Bad IL range.


Description:

An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.



Exception Details: System.BadImageFormatException: Bad IL range.



Source Error:


An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.





Stack Trace:


[BadImageFormatException: Bad IL range.]
   .cctor() +0

[TypeInitializationException: The type initializer for '<Module>' threw an exception.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +146
   System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +298
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +79
   System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +10362891
   System.Web.Configuration.Common.ModulesEntry.Create() +80
   System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +212
   System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1891
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +166
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +336
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +350
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +382

[HttpException (0x80004005): The type initializer for '<Module>' threw an exception.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +11305670
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +4342340

I'm unsure as to how to troubleshoot this. Based on the exception above and the error code indicated(0x80004005), it looks to be permission issue? Any thoughts from the community on how to resolve this?

Thanks,

PK

April 23rd, 2015 11:51pm

Hello,

Just wanted to update this in-case anyone else runs into this issue. I ended up opening a support ticket on this and they were able to get it resolved. Support had suspected that the update caused some type of corruption between the IIS Rewrite module and Lync Server Web Components.

They first had me uninstall both the Rewrite module and the Lync Server Web Components. After the uninstall, they asked me to run Step 2 of the deployment wizard so the components were reinstalled based on Topology information. Once this install was complete, support also asked me to run the cumulative updater to re-update the Lync Server Web Components.

After this, the internal Meet URL started to work correctly.

I hope this helps someone else out in the future.

PK

  • Marked as answer by pk40 5 hours 17 minutes ago
Free Windows Admin Tool Kit Click here and download it now
April 25th, 2015 10:07pm

Hello,

Just wanted to update this in-case anyone else runs into this issue. I ended up opening a support ticket on this and they were able to get it resolved. Support had suspected that the update caused some type of corruption between the IIS Rewrite module and Lync Server Web Components.

They first had me uninstall both the Rewrite module and the Lync Server Web Components. After the uninstall, they asked me to run Step 2 of the deployment wizard so the components were reinstalled based on Topology information. Once this install was complete, support also asked me to run the cumulative updater to re-update the Lync Server Web Components.

After this, the internal Meet URL started to work correctly.

I hope this helps someone else out in the future.

PK

  • Marked as answer by pk40 Sunday, April 26, 2015 2:07 AM
April 26th, 2015 2:07am

Hello,

Just wanted to update this in-case anyone else runs into this issue. I ended up opening a support ticket on this and they were able to get it resolved. Support had suspected that the update caused some type of corruption between the IIS Rewrite module and Lync Server Web Components.

They first had me uninstall both the Rewrite module and the Lync Server Web Components. After the uninstall, they asked me to run Step 2 of the deployment wizard so the components were reinstalled based on Topology information. Once this install was complete, support also asked me to run the cumulative updater to re-update the Lync Server Web Components.

After this, the internal Meet URL started to work correctly.

I hope this helps someone else out in the future.

PK

  • Marked as answer by pk40 Sunday, April 26, 2015 2:07 AM
Free Windows Admin Tool Kit Click here and download it now
April 26th, 2015 2:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics