Solution Properties
Solution ID:
200427112442455
Last Modified Date:
Wed Mar 23 14:26:49 UTC 2022
Taxonomy Path:
Case category//How do I...//governmental/legislative compliance
Author:
[email protected]
Sage Taxation Installation Checker
Description

It can run for a variety of reasons (for example an unsuccessful backup, or as part of software upgrades) or can be run manually.

You can return to this article by selecting the Help button from the Installation Checker toolbar

Cause
Resolution
Understanding your report

Your installation checker report will always start at the bottom of the report with a summary:

3 warnings have occurred.Items which are marked as warnings should be checked before running the software.1 error has occurred.

The errors and warnings are all marked in the left hand margin. You can either scroll up to the relevant section or press the Previous button from the toolbar at the top. This allows you to skip past the various 'info' and 'OK' messages

Warnings

Warnings won't stop you from using the software but are worth reviewing as they can highlight factors you may not have been aware of (such as static file backups)

Errors

Errors are more likely to require you to take some action and will usually stop you from opening the software

Common installation checker reports

Most installation checker reports require you to have access to the server that hosts your Sage Taxation data.

If errors are reported, scan up the left hand side to quickly find the line that starts with 'Error'.

 

Error: DBCC CHECKALLOC failed - The database could not be exclusively locked

This can be caused by other processes trying to access the database whilst certain operations (such as backups, software updates or running the checker itself) are in progress.

This can usually be resolved by restarting SQL and re-running the installation checker

 

Error: Backup directory.... This directory is not accessible

ERROR:    Backup directory: C:\Program Files\Microsoft SQL Server\MSSQL11.SAGESPS\MSSQL\Backup\   WARNING:      This directory is NOT accessible on the SQL Server machine: MyServer

This can be resolved by pointing the backups to a directory that exists on the server using the Backup and Restore utility, or if the directory does exist, make sure everyone has the correct permissions to it.


Error: No data exists within this dataset.

Dataset: Archive   SQL database: TaxData3   ERROR:   No data exists within this dataset.   SQL data file: 10MB for C:\Program Files\Microsoft SQL Server\MSSQL11.SAGESPS\MSSQL\DATA\TaxData3.mdf   SQL log file: 2MB for C:\Program Files\Microsoft SQL Server\MSSQL11.SAGESPS\MSSQL\DATA\TaxData3_log.ldf

This error can be caused by not completing the new dataset wizard when trying to create a dataset and can be resolved by deleting the dataset in Sage Control Centre

 

Error: Setting mismatch.....

This can be caused by various factors including a server move without using our backup utility, or renaming your SQL server.

It can easily be resolved by taking a backup with our backup utility and restoring it straight away. Accept the prompt at around the 10% mark to confirm this change.

Checking Data Directory Structure ERROR: \Docs directory is missing.

This indicates that one (or more) of the required directories is missing. This can usually be resolved by recreating the directory in question on your server machine.


Timeout expired or 'Failed to connect to SQL' errors

Timeout expired messages can have a number of causes, but there are some steps you can try before contacting us.

    • Try restarting the SQL service
    • If you haven't backed up in a while, try taking two consecutive backups using our backup and restore utility. This performs housekeeping and can help trim your SQL log files (this may take a while in some situations)
    • Temporarily disable your firewall and anti-virus software and run the installation checker manually
    • Run the installation checker manually by browsing to C:\Program Files (x86)\Sage\Sage Taxation\Server\TaxReadOnlyDir\Tools and running InstChkr.exe manually. Select Yes to perform data scanning when prompted.
    • Windows updates that are either pending installation or awaiting a reboot can also prevent the software from accessing your database

Please bear in mind that you may have to manually start the SQL service once the updates are complete.

If you're still having issues with timeout expired message, please contact us on 0191 479 5999.

For any errors or warnings not listed

Most entries marked as warnings can be safely ignored, however if you have any specific entries you'd like us to investigate or for any errors not listed please contact us on 0191 479 5999 for further advice.

 


Most entries marked as warnings can be safely ignored, however if you have any specific entries you'd like us to investigate or for any errors not listed please contact us on 0845 111 1111 for further advice

Manually running the installation checker

Unlike backing up your data, running the Installation Checker doesn't perform any housekeeping on your data, so doesn't need to be run routinely

  1. To run the checker manually, first of all make sure everyone is logged out of Sage Taxation and log on to the server machine
  2. Right click on the Start menu and select Run (On Windows 7 or 8, select Start, Run)
  3. Enter: \\LOCALHOST and press Enter or OK
  4. When the file explorer window opens, open SageTaxationReadOnly followed by Tools
  5. Run instchkr.exe and select Yes to data scanning when prompted

You can run this from a workstation substituting LOCALHOST for your server's name (e.g. \\Server-01) at step 3, but depending on the results, you may need to move to the server.

 

[BCB:19:UK - Sales message :ECB]

Steps to duplicate
Related Solutions