Troubleshooting Web Parts

‘<ENV>’. Can not find the webservice dlls.

It can be one of the following problems:

  1. QLx or the Software Windows application hasn’t been installed on the server running the HR Web Service.
  2. In the HR Web Service web.config, which is different to the Sharepoint web.config, is a key called Jane.Environment. It must be set to ‘QL’ for QLx and ‘JANE’ for Jane HR.
  3. If you are running the HR Web Service on a 64-bit operating system, the web site where the HR Web Service is running must be set to a 32-bit environment. This is determined by the Application Pool the web site is running under. Under Advanced Settings of the Application Pool, check that Enable 32-bit Applications is set to true.

The data base connection provided was invalid.

  1. Verify that the database connection details are valid.
  2. For Jane, verify that the HR portal user has been set in the Connection Manager. For QL, ensure that the REMOTE_HR user has been created and can log into QL.

Invalid User Name Provided

If running the Jane windows application, verify that a HR portal user has been set up in the connection manager.

A Web Part or Web Form Control on this page cannot be displayed or imported. The type could be found or it is not registered as safe.

This is a generic error message and can be caused by a number of issues.

To get a descriptive error message, in the HR Portal web.config, search for CallStack=”false” and change it to CallStack=”true”. Find customErrors mode=”On” and change it to customErrors mode=”Off”. Also search for debug=”false” and change that to true. Make sure to set these options back to the defaults afterwards as they can cause a significant slowdown.

Ensure the web parts are installed correctly and can be seen by Sharepoint. Create a blank web part page and add the HR Version Numbers web part. Verify it is displayed correctly and shows the version number installed.

If the web parts were installed with the globalinstall switch, verify that the QLHRWebParts and Infragistics DLLs are listed in the Windows GAC (C:WindowsAssembly). If you didn’t do a global install, then the DLLs will be installed in the bin directory of the Sharepoint site. This requires that the Trust Level in the HR Portal web.config is set to Full.

If you are using SharePoint 2003 and upgrading from ASP.NET 1.1.4322, verify from within Internet Information Services (IIS) Manager that the Sharepoint site the web parts are installed to is using ASP.NET 2.0.50727; Go to the properties of the web site -> ASP.NET -> ASP.NET version.

This message can also occur If you are using Sharepoint 2003 and you update the operating system’s .NET Framework to 3.5 SP1 or greater. Please view this Microsoft Knowledge Base Article: https://support.microsoft.com/kb/957254

In the web.config, there should be the following safe control entry for QLHRWebParts:

<SafeControl Assembly=”QLHRWebParts, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d2ce353b3387dae8″ Namespace=”QLHRWebParts” TypeName=”*” Safe=”True” />

This line tells SharePoint that the HR Portal web parts are safe controls and should be trusted. If this line is missing, then the cab file should be reinstalled. In a SharePoint farm, the solution should be globally installed to make sure that all SharePoint servers web.configs are modified to include the SafeControl entry.

Pages Timeout

This can indicate a problem with the web service. Verify that the web service can be accessed by entering https://<SERVER>/HRWebService/CallComObject.asmx in a web browser.

It can also be a problem with mismatched QLP DLLs. Ensure that the DLLs are the appropriate version for the web parts.

Cannot Create ActiveX Component

This indicates that an application DLL cannot be accessed. This is typically because it has not been registered successfully. This can occur if an application DLL is manually upgraded whille the SharePoint site is running. It is recommended to register the DLL again, but to stop IIS/Sharepoint first e.g.

  • iisreset /stop
  • unregister/re-register DLLs
  • iisreset /start

System.Web.HttpException: Session state can only be used when…

All web parts require session state to be available in the HR Portal web.config. Refer to the installation instructions, configuring the web.config section.

Javascript errors with grids and other controls (Sharepoint 2003 Only)

Load up Central Administration. Under Virtual Server Configuration, click Configure virtual server settings. Select the Sharepoint site. Under Virtual Server Management, click Define managed paths. In the Excluded Paths section there should be a path called webresource.axd. Add it if it doesn’t exist.

Unable to establish an environment reference

QL-x requires an environment reference to know which server and databases to access.

For the portal, this reference is set in the web.config appSettings section e.g.

<add key=”Agresso.QLP.Environment” value=”X” /> <!– QL Administrator – Connection Code –>

<add key=”Agresso.QLP.Qualifier” value=”X” />  <!– Password for REMOTE_HR user –>

Replace X with the appropriate values.

Unable to establish the required HR Record reference

For a user to access any web parts, they need their Windows/Sharepoint user id to be “mapped” to an employee. The employee’s user name (login) needs to be set in the HR Record -> Personal Details. The domain prefix should not be included. For example, if the user logs into Sharepoint as DOMAINUser, then the windows user field should only contain User.

User is not recognised as an Authorised User

By default, all users using the HR Portal are set as self service users. To make a user an authoriser, it is required to set their HR Application User field in HR Record -> Personal Details to their QL-x/Jane login name.

SharePoint Products Configuration Wizard fails after installing Web Parts

As part of the installation of the Jane web parts, the web.config of the SharePoint site needs to modified to enable the Session State module. If the line, <remove name=”Session” />,  has been commented out (using <!– –>) instead of removed then the configuration wizard will fail when it tries to update the web.config. The commented out line should be removed.