Issue
After logging into Web Applications, all dashboards state "no data returned". In the Application Modules Database, in the Diagnostics.LogEventView table the following message is returned from Data Source Bus:
Product Line
Power Monitoring Expert 8.x
Environment
Web Applications - Dashboards
Cause
Under some conditions, applying SP3 to SQL Server 2012 breaks compatibility between SQLServerSpatial110.dll and the Microsoft.SQLServer.Types library. Should his happen, the DataSourceBus cannot successfully initialize which prevents all of the Web Applications expect for Diagrams and Reports from working. If this condition exists on a server on which PME is being installed or upgraded, the install/upgrade fails on 'Configuring Web Framework'.
Further details on the Microsoft SQL Server compatibility is available at this link:
https://connect.microsoft.com/SQLServer/Feedback/Details/2139143
Resolution
*Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).
Look in "C:\Windows\assembly" to identify which versions of "Microsoft.SqlServer.Types.dll" exist (see attached screen capture).
We hope to see "10" and "11". If so, then we can potentially force a “down-rev” for our AppMods services.
Assuming version 10 exists,
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" />
<bindingRedirect oldVersion="1.0.0.0-12.0.0.0" newVersion="10.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime.>
After logging into Web Applications, all dashboards state "no data returned". In the Application Modules Database, in the Diagnostics.LogEventView table the following message is returned from Data Source Bus:
Message:
An unexpected error has occurred. Please consult the system diagnostic information.
Extended Information:
LogClientExtendedInformation: ApplicationModule: Data Source Bus
Description: The type initializer for 'ExtentPlaceholderCreator' threw an exception.
State: System.TypeInitializationException: The type initializer for 'ExtentPlaceholderCreator' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.EntryPointNotFoundException: Unable to find an entry point named 'SetClrFeatureSwitchMap' in DLL 'SqlServerSpatial110.dll'.
at Microsoft.SqlServer.Types.GLNativeMethods.SetClrFeatureSwitchMap(Int32 clrFeatureSwitchMap)
at Microsoft.SqlServer.Types.SqlGeometry.IsValidExpensive()
at Microsoft.SqlServer.Types.SqlGeometry.Construct(GeoData g, Int32 srid)
An unexpected error has occurred. Please consult the system diagnostic information.
Extended Information:
LogClientExtendedInformation: ApplicationModule: Data Source Bus
Description: The type initializer for 'ExtentPlaceholderCreator' threw an exception.
State: System.TypeInitializationException: The type initializer for 'ExtentPlaceholderCreator' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.EntryPointNotFoundException: Unable to find an entry point named 'SetClrFeatureSwitchMap' in DLL 'SqlServerSpatial110.dll'.
at Microsoft.SqlServer.Types.GLNativeMethods.SetClrFeatureSwitchMap(Int32 clrFeatureSwitchMap)
at Microsoft.SqlServer.Types.SqlGeometry.IsValidExpensive()
at Microsoft.SqlServer.Types.SqlGeometry.Construct(GeoData g, Int32 srid)
Product Line
Power Monitoring Expert 8.x
Environment
Web Applications - Dashboards
Cause
Under some conditions, applying SP3 to SQL Server 2012 breaks compatibility between SQLServerSpatial110.dll and the Microsoft.SQLServer.Types library. Should his happen, the DataSourceBus cannot successfully initialize which prevents all of the Web Applications expect for Diagrams and Reports from working. If this condition exists on a server on which PME is being installed or upgraded, the install/upgrade fails on 'Configuring Web Framework'.
Further details on the Microsoft SQL Server compatibility is available at this link:
https://connect.microsoft.com/SQLServer/Feedback/Details/2139143
Resolution
*Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).
Look in "C:\Windows\assembly" to identify which versions of "Microsoft.SqlServer.Types.dll" exist (see attached screen capture).
We hope to see "10" and "11". If so, then we can potentially force a “down-rev” for our AppMods services.
Assuming version 10 exists,
- Stop the ApplicationModules services
- Edit the file \Applications\bin\Framework.ServiceHost.exe.config by copying in the xml fragment below just above the </configuration> tag at the end of the file
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" />
<bindingRedirect oldVersion="1.0.0.0-12.0.0.0" newVersion="10.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime.>
- Start the ApplicaionModules services
- Monitor the Diagnostics.LogEventView table to verify that the Data Source Bus initializes properly. If you have been successful, you should see a message like:
"Completed data source initialization. The data source was assigned ID 1."
Additional Information:
This workaround forces the ApplicationModules services to use version 10 of the Microsoft.SQLServer.Types library.. This problem has been addressed in Power Monitoring Expert 8.2. PME 8.2 uses version 12.0.0.0 of this library which does not have this problem which we force it to use via the web.config file.
This workaround forces the ApplicationModules services to use version 10 of the Microsoft.SQLServer.Types library.. This problem has been addressed in Power Monitoring Expert 8.2. PME 8.2 uses version 12.0.0.0 of this library which does not have this problem which we force it to use via the web.config file.
Released for:Schneider Electric United Arab Emirates
