This article provides solutions to known problems during the Longview Analytics installation and configuration process.

This is a collection of different problems, and although the content is revisited from time to time we cannot guarantee that all information is up-to-date.  

Problem:

After having installed a multi tier system (web server and application server on different servers) the first attempt to access the home page leads to an error message:

Server Error in '/Longview/10/Analytics/home' Application. 

Could not load file or assembly 'EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.

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.IO.FileNotFoundException: Could not load file or assembly 'EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
(created August 24, 2018)

Details

For some reason some files are missing on the web server as they were not copied from the Engage source folder to the target folder during configuration.

Solution

The issue can be solved by copying the files "EntityFramework.dll" and "EntityFramework.SqlServer.dll" and any other missing DLLs from the directory "c:\Program Files\Longview\10\Analytics\Engage\Engage Program Files\bin\" to the directory "C:\inetpub\wwwroot\Longview\10\Analytics\home\bin" as the files do not exist in the mentioned  web server directory. 

Problem:

After an Analytics Version Upgrade the following message appears when trying to open a specific Framework Application in the Web Client:

"The application cannot be started because the versions of Longview Analytics database and the Longview Analytics Application Framework used by the application do not match"

(created May 29, 2018)

Details

After an Analytics version upgrade, the applications based on the application framework have not yet been re-published via the Longview Analytics Administration Console.

Solution

After an Analytics Versions upgrade, applications based on the application framework must always be re-published via the Longview Analytics Administration Console. The reason is that Framework Applications work with external folders and the files from them are brought together when they are published. Only re-publishing ensures that the current framework files are used with the application.

----------------------------------------------------------------

Problem:

The error "Authorization Error: You are not authorized to open the requested application. Logout in order to try with another user." occurs for applications that have activated the authentication type "Windows and Analytics authentication with login dialog".

(created May 16, 2018)

Details

The error occurs when the application you want to open has activated the authentication type "Windows and Analytics authentication with login dialog" and user-defined authentication is enabled in the Longview Analytics Engage file web.config.

In this case, the following parameters keys are activated under the <appsettings> tag in the web.config:

Solution

Currently, the combination of "Windows and Analytics authentication with login dialog" and user-defined authentication is not supported in Longview Analytics.
If "Windows and Analytics Authentication with login dialog" must be used, the user-defined authentication must be deactivated or rather commented out in the web.config.

Problem:

When opening an Analytics Application in the browser, Users get an error message "An error occurred during the user license check". 

(created Jan 15, 2018)

Details

In rare cases, something unexpected goes wrong during the license check and the license information in the database is not consistent anymore.

Solution

Restarting the server should fix the problem. Unfortunately this will invalidate the currently running sessions so you should consider notifying the users first.
Please inform the Longview support to help improve the quality of the software.
Currently we are unable to reproduce the problem but are working on a revised version that allow the users to work after the message (probably 10.1.0.8228)

----------------------------------------------------------------------------------------------

----------------------------------------------------------------

Problem:

An installation of Longview Analytics fails with a message that the Analytics Server service could not be installed

Message: Dienst "Longview Analytics Server" (LvAnalyticsSvc10) konnte nicht installiert werden.

(created May 16, 2018)

Details

Windows classifies certain files as unsafe downloads and attachments by identifying the files type and the security settings for each file.

Solution

Right click the blocked Analytics setup file and click on Properties.
Click on the General tab, check the Unblock box at the bottom and click on OK.

----------------------------------------------------------------

Problem:

When trying to access Engage in the browser a "Critical error" with a CPluginException containing "LoadAndValidateXML(String i_pathNameXmlFile, ...) " is thrown

(created May 4, 2018)

Details

There is a problem accessing a plugin or the configuration file in "C:\ProgramData\Longview\10\Analytics\Engage\SearcherPlugins". 

Solution

Make sure that the folder is available and contains the "searcherconfig.xml". If the file is there check the privilegues  assigned to this folder unter "Properties -> Security" and make sure that the Windows group "Users" has read access to the file. This is needed for the application pool identity to access the file. The identity of the Engage application pool is used by the IUSR which belongs to the group "Users". It has no access if the "Users" group is not assigned to the folder.

----------------------------------------------------------------------------------------------

Problem:

When trying to send an email or execute a subscription in a Longview Analytics application the following information message is thrown:

Message: The connection information for the SMTP-server is not valid.

In the session trace file the following message can be found:

Error    0    Error:  The connection information for the SMTP-server is not valid.    Program  
Info    0    Info for     Session: 224    RemoteHost:         Current Event: SendEvent("aAF_FCT_SUBSCRIPTION_TASKS.apd";219;2;null;0;0)    Driver:     Cif: |Users:    arcUserDevLVAnalyticsDB10(UNDEFINEDDRIVER,2)    arcUserDevLvAnalyticsDB10(UNDEFINEDDRIVER,2)|Objects And Formulas:    f(14,948)    [aAF_FCT_SUBSCRIPTION_TASKS;OBJ219]    [aAF_FCT_SUBSCRIPTION_TASKS;OBJ219]    f(12,1)    f(20,1)    f(12,1)    f(5,1)    f(12,1)    f(8,33)    [aAF_FCT_SUBSCRIPTION_TASKS;OBJ181]    f(12,1)    f(20,1)    f(12,1)    f(8,57)    Program

(created Jan 23, 2018)

Details

In order to be able using the function SENDMAIL in a Longview Analytics application the Address and the Port number of the Mail Server (SMTP) and the login credentials to access the SMTP server have to be specified.

Solution

Login to Longview Analytics Administration Console and complete the settings for sending e-mails in the Server-Settings dialog.

----------------------------------------------------------------

Problem:

When trying to login to Engage after installation with "Windows Authentication" the following error message is thrown:

In the engageLog.txt the following message can be found:

WARN     ASP.global_asax    Application_Error. Request.Path: /Longview/10/Analytics/home/Services/arcplan-engage-server-RIAServices-CMyArcplanApplicationsService.svc/JSON/GetMyArcplanApplications
Application_Error. Request.Form:
Application_Error. Request.QueryString: %24orderby=it.Name&%24skip=0&%24take=100&%24includeTotalCount=false
Application_Error. Exception in Context.AllErrorsSystem.Net.WebException: The request failed with HTTP status 403: Forbidden.

(created Dec 14, 2017)

Details

Engage is not able to access the CGI-URL specified in the web.config parameter "CgiUrlOnServer". As Engage accesses the CGI locally the link needs to be checked in the browser on the web server machine.

Solution

Adjust the CgiUrlOnServer parameter in c:\inetpub\wwwroot\Longview\10\Analytics\home\web.config

Problem:

During configuration of the Web Server an error is displayed: "CGI url is invalid."

If you try to open the CGI url in a browser, you might get in addition the message "Service Unavailable - HTTP Error 503. The service is unavailable."

Possible side error: In the Application event log, the following error is traced:
"The worker process for application pool 'DefaultAppPool' encountered an error 'Cannot read configuration file
' trying to read configuration data from file '\\?\<EMPTY>', line number '0'.  The data field contains the error code."

(created Nov 23, 2018)

Details

There are many possible reasons why the CGI might not be accessible. In the Solutions section below, known reasons and their solutions are listed. 

With Longview 2017 Analytics Update 2, this error will be changed to a warning, so that afterwards the configuration process continues.   

Solution

Possible reasons:

One of the application pools, which include the cgi component, are stopped.

This can easily be checked in the IIS Manager, in the left window under "Application Pools". If one of these pools is stopped, the access to the CGI is not possible. 

Possible Solutions:

• Restart the Application Pools. But this might not fix it, because during the configuration process the application pool might be stopped again. 
• Open the folder c:\inetpub\temp\appPools. If there are virtual directories with the same name as the stopped Application Pools, delete these folders.
  Then restart the application pools, and restart the web server configuration.

Problem:

During installation of Longview Analyics an error is displayed: "Error 1923. Service Longview Analytics Server (LvAnalyticsSvc10) could not be installed."

(created Nov 23, 2018)

Details

That could happen if a previous uninstall of Longview Analytics has pending uninstallation steps. In this case the Longview Analytics Service is still registered. 

Solution

Restart the machine to complete the last installation process and remove the Longview Analytics service. 

Problem:

During configuration of the arcplan web server components an error is displayed: "An unknown error occured while trying to access the server ..."

Details

There is no Internet Information Server (IIS) installed on the local machine, so the configuration of the web server components is not possible.

Solution

Either an installation of IIS will solve the problem, or a manual installation of the web components on another web server, as described within the Administration Console help file.

----------------------------------------------------------------

Problem:

The Engage client shows an error during the start process. The Engage logfile contains the following error:
Context.AllErrorsSystem.InvalidOperationException: Unable to generate a temporary class

(created Jan 31, 2014)

Details

According to this article: http://support.microsoft.com/kb/908158/en-us, the issue occurs if the user account does not have the List Folder Contents and Read permissions on the %windir%\Temp folder.

Solution

To resolve this issue, grant the user account the List Folder Contents and Read permissions on the %windir%\Temp folder.

----------------------------------------------------------------

Problem

During the automated configuration of the web server in the Administration Console the following error occurred on Windows 8 or Windows Server 2012:

"Application creation failed"

Filename: \\?\C:\inetpub\wwwroot\arcplan\web.config

Error: Cannot read configuration file

In version 10 it looks a little bit different and the error message changed to "Cannot edit configuration in Longview\10\Analytics\web.config. This happens when a section is locked at a parent level..."

Details

The setup is not able to create the Longview / arcplan folder in ...inetpub\wwwroot\ due to missing privileges

Solution

Create the folder manually and retry the automatic web server configuration.

If this does not help, although Administrator rights have been granted, resetting the IIS to a former configuration can do the trick:

Amanual to restore the IIS settings from a backup can be found here:

https://docs.microsoft.com/en-us/iis/manage/managing-your-configuration-settings/using-configuration-history-with-iis-7-and-iis-8

The following commands in the command line in the windows/system/inetsrv/config can be used according to this article:

appcmd list backups

appcmd restore ba/inetckup CFG_00000006

Details

We also had the case that there was a double backslash in the path generated by the setup between wwwroot and Longview Analytics. This led into the following message:

Type:System.IO.FileNotFoundException
Message:Filename: \\?\C:\inetpub\wwwroot\Longview\10\Analytics\web.config
Error: Cannot read configuration file

This problem came up in ACM between automated web server configuration and Engage (Web server configuration showed all tiles green when executed for the first time. Second time is stopped with the red tile shown above). 

Solution

In IIS Manager, the physical path of the "Default Web Site" changed and needed to be adjusted before Engage Configuration. The following dialog can be found when clicking the Default Web Site and selecting "Basic Settings":

----------------------------------------------------------------

Problem(s)

• During the automated configuration of the web server in the Administration Console the Error Add handler mapping failed occurred:
  
  
                or
• In the Engage client, the following error is displayed: Ooops - There was an error while contacting the engage server
  or
• In the arcplan Engage Configuration Manager the HTTP Activation can not be enabled.

Details

This might occur because HTTP Activation is not enabled. HTTP Activation is required for running Engage on Windows 8/10 or Windows Server 2012/2016.

Solution

Enable HTTP Activation in Windows Features:

On Windows 2012/2016:

• Open Server Manager, and navigate to Manage / Add Roles and Features Wizard.
• In the Features list, click on .NET Framework 4.5 Features / WCF Services / HTTP Activation.

On Windows 10:

• Open Control Panel, click on Programs, click on Turn Windows Features on or off.
• In the Windows Features Dialog, select the option HTTP Activation.

In Windows 10, there is no longer an HTTP Activation option provided, instead it it included in other switches. The following switches are required:

----------------------------------------------------------------

Problem:

When trying to access an html start page for the first time, the browser returns 404.2 (ISAPI and CGI Restriction). The same http code will be returned when trying to access the CGI directly in the browser.

Details

This issue occurs because the arcCGI10.exe is restricted on the computer that is running IIS 7 or IIS 8.

Solution

Check the Handler Mapping for the arcCGI10.exe after navigating to the "Longview\10\Analytics\Scripts" folder in the IIS Manager. The state of the default "CGI-exe" entry needs to be "enabled" and a "Script Map" needs to be assigned to the arcCGI10.exe separately, where the handler has execute permissions. If this is already configured correctly you can try to execute the arcCGI10.exe in  a command prompt on the server. If it does NOT return the error code "-3" security policies on the web server may prevent it from being executed. The error message in the command prompt should give further information.

----------------------------------------------------------------

Problem

 During installation of the Longview Analytics Database the following error occurs: Message: System.InvaldOperationException -- Trigger: [trg_doc_update_delete_filter]

Details

 The collation of the SQL Server instance is set on case sensitive. Currently Longview Analytics requires a case insensitive collation setting in order to work probably.

Solution

 Switch the collation of the SQL Server instance to case insensitive as described in this MSDN article: http://msdn.microsoft.com/en-us/library/ms179254.aspx

----------------------------------------------------------------

Problem

 You get an error "Attachment file C:\ProgramData… is invalid (37000)" trying to send a report as attachment via Share & Export Center

Details

 The SQL Server hosting the Longview Analytics database and configuration for Database Mail is a dedicated server. The SQL Server needs to know the exact network path to the shared directory where the Longview Analytics Server saves the PDF files. If the PDF Cache setting in Administration Application points to a local path the SQL Server could not find the file which should be attached.

Solution

 Configure the share for the Longview Analytics Server directory "C:\ProgramData\Longview\10\Analytics\arcServer\PDFCache\Server". Login to application "Administration" and open report "Settings". Select your application you want to configure and change the default value for the parameter "Path to PDF Cache" from "C:\ProgramData\Longview\10\Analytics\arcServer\PDFCache\Server" to the shared network path \\<YourServerName>\<ShareName>

----------------------------------------------------------------

Problem

You get an error "Attachment file C:\ProgramData… is invalid (37000)" trying to send a report as attachment via Share & Export Center

Details

 The parameter value for "Path to PDF Cache" was not set to the directory where the Longview Analytics Server saves the PDF files instead it was inserted a path to an user defined shared directory. The path where the Longview Analytics Server saves the PDF files is not configurable and is "C:\ProgramData\Longview\10\Analytics\arcServer\PDFCache\Server" as default. 

Solution

As the case may be you can only configure a local path or a network path to the shared directory for the parameter "Path to PDF Cache".

If the Longview Analytics Server and the SQL Server hosting the Longview Analytics database and configuration for Database Mail are installed on the same machine leave it the default value.

If the SQL Server is a dedicated server configure the share for the Longview Analytics Server directory "C:\ProgramData\arcplan\8\arcServer\PDFCache\Server" and change the default value for the parameter "Path to PDF Cache" from "C:\ProgramData\arcplan\8\arcServer\PDFCache\Server" to the shared network path \\<YourServerName>\<ShareName>

----------------------------------------------------------------

Problem

 During uninstall or update of a version an arcplan8_xxx_xx.msi file is missed. If it can't be found you won't be able to uninstall or update the version. 

Details

Still unknown circumstances

Solution

 To get the needed arcplan.msi file you have to extract the arcplan8_xxx_xx.exe file from the current installed version. This can be done via command line.

Open CMD in the folder with included arcplan8_xxx_xx.exe for example "C:\>"

Execute the command "C:\><setupfilename> /A". This will start the Installer and prompt you to set a path where you want to save the extracted files. Here you'll find the msi file which can now be referenced during uninstall

----------------------------------------------------------------

Problem

In Engage you get an error message and / or the page "My arcplan applications" remains empty event though the user has access to applications.

In the Engage Server logfile you find an entry:

Application_Error. Exception in Context.AllErrorsSystem.ServiceModel.ServiceActivationException: The service '/arcplan/8/home/Services/arcplan-engage-server-RIAServices-CMyArcplanApplicationsService.svc' cannot be activated due to an exception during compilation.  The exception message is: Memory gates checking failed because the free memory (930390016 bytes) is less than 5% of total memory.  As a result, the service will not be available for incoming requests.  To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.. ---> System.InsufficientMemoryException: Memory gates checking failed because the free memory (930390016 bytes) is less than 5% of total memory.  As a result, the service will not be available for incoming requests.  To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.

Solution

Check wether there is enough memory available on the server. In the concrete example the SQL Server was consuming 19 of 21 GB of memory. The result was, that the IIS was running out of memory and failed to compile the engage services.

----------------------------------------------------------------

Problem:

After a successful installation and configuration you get an error "Network Error: An error occurred while contacting the server", when starting an application in the client.

Details

The error can occur if the default IIS script map module "CGI-exe" is not installed in the web server. Thus the arcCGI10 could not be reached.

Solution

At first uninstall Longview Analytics  \ arcplan. Ensure to choose the option "Remove" for the settings, but "Keep" for the database if still needed when your are asked for your settings and the Longview Analytics database.

Next you need to enable CGI module in Windows Features:

• Open Control Panel, click on Programs, click on Turn Windows Features on or off.
• In the Windows Features Dialog, select the option CGI

 Windows 7/8/10

Windows 2012/2016:

Next install Longview Analytics again and start the automatic web configuration in the Admin Console again. 

Now you should be able to connect to the applications.

----------------------------------------------------------------

Problem:

In the Engage client, the following error is displayed: Ooops - There was an error while contacting the engage server.

and in ECM an exception occurs with the following error: 

System.Configuration.ConfigurationErrorsException: Failed to decrypt using provider 'RsaProtectedConfigurationProvider'. Error message from the provider: Bad Data.

Details

The Engage server can not decrypt the encrypted connection string to the Database. We don't know yet why.

Solution

Change the password for the DB user engageSecurityUser8 und replace the encrypted connection string in web.config with a correct one in clear text. Please contact support or development team for details.

----------------------------------------------------------------

Problem:

When trying to open an application from Engage, you get the error message 'Network error', and looking in the browser developer tools (shortcut key in browser is usually F12) you see the browser reports a "Cross Origin Resource Sharing / CORS" error:

Details

The domain name in the URL in the browser address is not the same as the engage setting for the CGI Url, seen in ECM:

The browser refuses to load javascript from a different domain, due to security issues.

Solution

Enter the correct domain name in the browser address bar URL.

In the above example:

false:

• http://myserver/arcplan/8/home
• http://localhost/arcplan/8/home   (if accessing the website from the server)

correct:

• http://www.mycompany.com/Longview/10/Analytics/home
• http://www.mycompany.com/arcplan/8/home

----------------------------------------------------------------

Problem:

The Longview/Analytics/10/home page in the browser is empty. Looking in the browser development tools, we see that the javascript files loaded from the server have content length of 0, although the http status code of the response is 200/OK 

Details

In IIS, the Role Service for static content' was not installed.

Solution

Install the Static Content role.

----------------------------------------------------------------

Problem:

No application is listed in Engage.

Details:

The arcGallery.log shows the following exception (in German): Der Dienst '/arcplan/8/home/Services/arcplan-engage-server-RIAServices-CWidgetService.svc' kann aufgrund einer Ausnahme während der Kompilierung nicht aktiviert werden. Die Ausnahmemeldung lautet: Die für IIS konfigurierten erweiterten Schutzeinstellungen stimmen nicht mit den für den Transport konfigurierten Einstellungen überein.

Solution:

Set Extended Protection for the Windows Authentication back to the default: "Off"

----------------------------------------------------------------

Problem:

Could not load type 'System.ServiceModel.Activation.HttpModule'

Details:

The following error message appears when opening the Home Page:
"Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'."
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.TypeLoadException: Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

Solution:

You need to re-register .NET Framework 4 with IIS. Try the following: Open command prompt as an administrator then navigate to your .NET folder (%windir%\Microsoft.NET\Framework\v4.0.30319). Then, issue the following command:
aspnet_regiis -iru

Source: http://social.msdn.microsoft.com/Forums/en/wcf/thread/1110b8c4-5fb5-402f-bb39-ce63b25ae5fe

----------------------------------------------------------------

Problem:

Critical error: The underlying provider failed on Open ---> Fehler bei der Anmeldung für den Benutzer 'arcSearcher8'.

Details:

The following error message appears when opening the Home Page after updating arcplan:

Application_Error. Exception in Context.AllErrorsSystem.Data.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: Fehler bei der Anmeldung für den Benutzer 'arcSearcher8'.

Solution:

Use the ECM to update the outdated Searcher Plugin.

----------------------------------------------------------------

Problem:

The Engage Server doesn't start. In ECM in module "arcplan Engage Web Application" is an internal error displayed. 

Details:

Wenn man die home-Seite aufruft, wird eine .net Exception angezeigt. Im Callstack sieht man, dass der Fehler innerhalb der Methode LoadAndValidateXML auftritt und eine CPluginException auftritt. Aufgerufen wird die Methode durch CSearcherConfigReader.

If the home page is opened, a .net exception is displayed. The file searcherconfig.xml could not be opened, because the Engage process doesn't has access to that file. The AppPool run with the ApplicationPoolIdentity. 

Solution:

Switch the AppPool to another account with enhanced permissions. 

Problem:

During Engage configuration an error 500 is displayed in the "arcplan Engage Web Application" tab. When trying to access the arcplan/8/home page an error 500 is thrown too.

Details:

Not clarified, maybe the ASP.Net Framework registration failed.

Solution:

Press the "Register" button in the IIS Operations area of the "arcplan Engage Web Application" tab of the ECM and reload the page.

----------------------------------------------

Problem:

When accessing the home page or any other application the message "Ooops there was an error while contacting the Engage server" is thrown.

Details:

Not sure, maybe the WCF components are not installed.

Solution:

Enable the Windows feature "WCF activation for http" under .net Framework. Afterwards go to ECM and press  the "Register" button in the IIS Operations area of the "arcplan Engage Web Application" and reload the page. If Longview 2017 is used the regiis command needs to be executed because ECM is not available anymore.

------------------------------------------------

Problem:

When clicking a tile in the Longview Close home page, the following error is displayed: "The Longview application failed to initialize. Your session has timed out. Please sign in again."

Solution:

The  missing part again was the Windows feature "WCF activation" which was not  installed on the server. We saw that in the developer tools of the  browser as there was a 404 pointing to the RIA services which were not  accessible.

After  we installed it and clicked on the "IIS Operations -> Register"  button of the Engage Configuration Manager which refreshes the ASP.net  Framework registration the home page as well as the Administration  application was accessible without issues.

----------------------------------------------------------------

Problem:

An initial installation of the Analytics User Management database fails with error message "An SQL error occured during the update of the user management database" even though the SQL Server Management Console does not display any installed Analytics databases

Details

Possibly a previously installed Analytics database was manually deleted without removing the associated .mdf and .ldf files.

Solution

Ensure that the SQL Server Data directory (default C:\Program Files\Microsoft SQL Server\<InstanceName>\MSSQL\DATA) does not contain any orphaned Analytics .mdf and .ldf files (e.g. LvAnalyticsDB10.mdf and LvAnalyticsDB10.ldf)

----------------------------------------------------------------------------------------------

Problem:

When trying to access the home page (Engage) the following error message is shown in the browser:

Critical Error

The Longview Analytics Engage Server failed to start your session

Additional information is available in the server logfiles.

System.TypeInitializationException: The type initializer for 'arcplan.engage.server.CCssLinkTags' threw an exception. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. at System.Security.Cryptography.MD5CryptoServiceProvider..ctor() at arcplan.engage.server.CBundleHelper.CalculateChecksum(String i_physicalPath) at arcplan.engage.server.CBundleHelper.CacheBustingReference(String i_deployedPath) at arcplan.engage.server.CCssLinkTags.InitializeThemes() at arcplan.engage.server.CCssLinkTags..cctor() --- End of inner exception stack trace --- at ASP.main_aspx.__Render__control2(HtmlTextWriter __w, Control parameterContainer) at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) at System.Web.UI.HtmlControls.HtmlHead.RenderChildren(HtmlTextWriter writer) at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) at ASP.main_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) at System.Web.UI.Page.Render(HtmlTextWriter writer) at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Details

The Windows environment of the web server is configured to use FIPS encryption that is conflicting with MD5 hashes. Hence the Engage application fails to start

Solution

Disable FIPS in the "Local Security Policy":

Go  to Start > Control Panel > Administrative tools > Local  Security Policy. The Group Policy dialog appears. Under the "Local  Policies" heading, select "Security Options" and look for the entry,  "System cryptography: Use FIPS compliant algorithms for encryption,  hashing, and signing." If this entry is enabled, disable it. 

----------------------------------------------------------------------------------------------

Problem:

When trying to access the home page (Engage) the following error message is shown in the browser:

403 - Forbidden: Access is denied.
You do not have permission to view this directory or path using the credentials that you supplied.  

Details

The engageLog.txt contains the following error message:

Application_Error. Exception in Context.AllErrorsSystem.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm
at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint)
at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at arcplan.engage.server.arcplanWebService.arcplanAnalyticServices.HasLicenseFor(String Component)
at arcplan.engage.server.authorization.CArcplanWebService.HasLicenseFor(String i_component)
at arcplan.engage.server.license.CLicenseManager.HasLicenseFor(String i_component)
at arcGallery.Web.Global.CreateUseJavaClientCookie()
at arcGallery.Web.Global.CreateCookiesIfNecessary()
at arcGallery.Web.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Application_Error. Exception.TargetSite:System.Net.WebResponse GetWebResponse(System.Net.WebRequest)
Application_Error. Exception.Source:System.Web.Services

Solution

Seems to be related to the TLS versions used by the browser and the ASP.NET version on the web server. See ticket 27251

-------------------------------------------------------------------------------------------------------------------------------------------

Problem:

When trying to access the home page (Engage) after an update from 10.3 to 10.4 the following error message is shown in the browser:

Critical Error

The Longview Analytics Engage IIS Application failed to start

Details

The engageLog.txt contains the following error message:

arcplan.engage.server.ServerSideHelpers.CAppInitializationException: Application_Error. Exception without Request Application_Error. Exception in Context.AllErrorsSystem.InvalidOperationException: The Entity Framework provider type 'Npgsql.NpgsqlServices, EntityFramework6.Npgsql' registered in the application config file for the ADO.NET provider with invariant name 'Npgsql' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See https://docs.microsoft.com/de-de/ef/ef6/fundamentals/configuring/config-file#ef-database-providers-ef6-onwards for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) at System.Data.Entity.Internal.AppConfig.<.ctor>b__2(ProviderElement e) at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at System.Lazy`1.CreateValue() at System.Lazy`1.LazyInitValue() at System.Data.Entity.Infrastructure.DependencyResolution.AppConfigDependencyResolver.RegisterDbProviderServices() at System.Data.Entity.Infrastructure.DependencyResolution.AppConfigDependencyResolver.GetServiceFactory(Type type, String name) at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory) at System.Data.Entity.Infrastructure.DependencyResolution.AppConfigDependencyResolver.GetService(Type type, Object key) at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext() at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate) at System.Data.Entity.Infrastructure.DependencyResolution.CompositeResolver`2.GetService(Type type, Object key) at System.Data.Entity.Infrastructure.DependencyResolution.DbDependencyResolverExtensions.GetService[T](IDbDependencyResolver resolver, Object key) at System.Data.Entity.Core.EntityClient.EntityConnection.ChangeConnectionString(String newConnectionString) at System.Data.Entity.Core.Objects.ObjectContext.CreateEntityConnection(String connectionString) at arcVegaORM.CEngageSchemaDataModelFactory.CreateEngageSchemaDataModel(String i_sqlConnectionString) at arcplan.engage.server.userProfile.CADUserInfoCache.InitializeFromDatabase() at arcGallery.Web.Global.InitializeUserInfoCache() at arcGallery.Web.Global.Application_Start(Object sender, EventArgs e) Application_Error. Exception.TargetSite:System.Data.Entity.Core.Common.DbProviderServices GetInstance(System.String, System.String) Application_Error. Exception.Source:EntityFramework at arcplan.engage.server.Main.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)"

Solution

Reason is that DLLs in "c:\inetpub\wwwroot\Longview\10\Analytics\home\bin\" have not been updated after install. So re-running the web server configuration is needed to get all assemblies up-to-date. Copying the files manually is not sufficient.

-----------------------------------------------------------------

Problem:

When trying to access the home page (Engage) after initial installation/configuration the following error message is shown in the browser:

Critical Error
The Longview Analytics Engage IIS Application failed to start
Additional information is available in the server logfiles.

Details

The engageLog.txt contains the following error message:

arcplan.engage.server.ServerSideHelpers.CAppInitializationException: Application_Error. Exception without Request Application_Error. Exception in Context.AllErrorsSystem.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Invalid object name 'engage.engage_user'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext) at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) --- End of inner exception stack trace --- at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context, ObjectParameterCollection parameterValues) at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.b__5() at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation) at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) at System.Data.Entity.Core.Objects.ObjectQuery`1..GetEnumerator>b__0() at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext() at arcplan.engage.server.userProfile.CADUserInfoCache.InitializeFromDatabase() at arcGallery.Web.Global.InitializeUserInfoCache() at arcGallery.Web.Global.Application_Start(Object sender, EventArgs e) Application_Error. Exception.TargetSite:System.Data.Common.DbDataReader ExecuteStoreCommands(System.Data.Entity.Core.EntityClient.EntityCommand, System.Data.CommandBehavior) Application_Error. Exception.Source:EntityFramework at arcplan.engage.server.Main.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Solution

Problem arises from using an SQL user not having the necessary privilegues on the SQL Server. Reason for the error message is that the engage.engage_user was created but contains no entry. Apart from that no other engage table is created. Rerunning Engage configuration does NOT solve the problem.

Only way to get this working is removing and re-installing the Longview user management database!