Reporting Components

Introduction

When installing systems@work software there are certain components that must either already exist on the IIS server or must be installed as part of the installation process.

Full details are also contained in the systems@work Installation Guide which is available in our Download Section.

In addition clients should regularly check for updates to the components (particularly the reporting ones) as these are often updated to reflect changes in Microsoft's .NET Framework and other Windows updates.

Reporting Components

systems@work software produces rich, dynamic user friendly reports that can be displayed either through the Maintenance Application or via the Browser.

To view these reports certain components need to be installed on the IIS servers. Typically these will have been installed by our Technicians as part of the installation process and are summarised here for the record or incase a reinstallation is required.

The components needed will vary depending on the version of systems@work software being used and the underlying reporting engine (either Crystal Reports or Microsoft Reporting Services or both).

Generally speaking, no components need to be installed on any end user machine to view browser based reports.

systems@work Version 5 & Older

Crystal

MSRS

systems@work Version 6.0.x Only

Crystal

MSRS

systems@work Version 6.1 & Above

Crystal

MSRS

Data Import Components

systems@work software allows data to be imported in bulk either through the Maintenance Application or via the Browser.

To import data, certain components need to be installed either on the local pc (for Maintenance Imports) or on the IIS server(s ) (for Browser Imports). Typically these will have been installed by our Technicians as part of the installation process and are summarised here for the record or incase a reinstallation is required.

The components needed will vary depending on the version of systems@work software being used, the version of Microsoft Office installed and whether you are operating in a 32 Bit or 64 Bit web environment.

Please note that most systems@work implementations or upgrade since 2015 have been 64 Bit Web.

If you wish to import via the Maintenance Application:

Microsoft Office must be installed on the machine where the maintenance application is running.

  • Scenario 1 - If your copy of Microsoft Office is 32 Bit then Maintenance Import works without any extra components being needed.
  • Scenario 2 - If your copy of Microsoft Office is 64 Bit then Maintenance Import requires accessdatabaseengine2007x86 to be installed on the machine where the Maintenance Application is running.

If you wish to import via your Browser:

If Microsoft Office is not installed on the IIS Server:

  • Scenario 1 - If your systems@work software is deployed as 64 Bit (which is most post 2015 implementations) then accessruntime x64 en-us must be installed on the IIS Server.
  • Scenario 2 - If your systems@work software is deployed as 32 Bit then accessruntime x86 en-us must be installed on the IIS Server.

If 64 Bit Microsoft Office is installed on the IIS Server then:

  • Scenario 1 - If your systems@work software is deployed as 64 Bit then no further components are needed.
  • Scenario 2 - If your systems@work software is deployed as 32 Bit then web based import is not possible.

If 32 Bit Microsoft Office is installed on the IIS Server then:

  • Scenario 1 - If your systems@work software is deployed as 64 Bit then web based import is not possible.
  • Scenario 2 - If your systems@work software is deployed as 32 Bit then no further components are needed.