• No results found

Known Issues and Work Around

N/A
N/A
Protected

Academic year: 2021

Share "Known Issues and Work Around"

Copied!
6
0
0

Loading.... (view fulltext now)

Full text

(1)

Issue Work-Around

During Compass 2.0 installation, sometimes you may get a popup message “.Net framework/SQLExpress could not be installed. Install .Net framework/SQLExpress manually”.

Run CompassSetup.exe again from the CD.

After step1, if you still see the same issue, install .Net Framework or MS SQL Express Manually from the Prerequisites folder present in CD.

Sometimes, migration of Access Database might fail in compass. The system may throw the following error: “Could not obtain exclusive lock on database ‘model’. Retry the operation later

Workaround: Restart SQL Service in the PC and then proceed with the migration

The Compass 2.0 Client installations cannot connect to Compass MS SQL Server.

This normally happens when the SQL Express is installed manually. Update SQL server connection settings so that Compass client can connect to Compass database server.

NOTE: Do this setting on server PC only. Check “Updating SQL server

connection settings” at the end of this doc.

When MS ACCESS Database accounts are migrated to SQL Express, you will see default panel names without any personality disc.

Run the appropriate personality disc to see specific company panel type.

On MS Vista OS & MS Windows 7 OS the personality disk application should be launched by right clicking on icon and selecting “Run as Administrator”.

During Installation and Un-installation of Compass or Commander the

following to be kept in mind to avoid unpredictable results. 1. Do not run the installation setup of Commander and Compass 2.0

(2)

Sometimes during installation the following dialog box appears, with a list of applications which are using files that need to be updated by the Compass 2.0 Setup.

Close all the applications before proceeding further.

Sometimes during installation, the following message box appears. You might see this error if another software application is being installed simultaneously along with Compass 2.0. Complete the other installation and later run the Compass setup. If you still see the same message, restart the computer and begin the installation.

Sometimes the installation fails with the message “1628: Failed to complete installation.”

Ensure that you have the required free space on the hard drive. Compass 2.0 recommends 1 GB free disk space.

The Compass 2.0 application does not work with all the Windows user accounts.

(3)

Sometimes during installation, the following error message might appear. Uninstall Compass 2.0 and reinstall Compass 2.0.

Sometimes during installation, feature transfer error appears. This error appears when the installation

is abruptly stopped, due to system reboot.

1. In the CD, from the Utilities folder, run Cleanup Utility.

2. Delete shortcuts from the desktop. 3. Delete Compass 2.0 folder. 4. Reinstall Compass 2.0.

Sometimes Compass 2.0 Client installations do not get connected to the Compass 2.0 Server, where SQL Server/SQL Express is installed.

Update the SQL Server settings.

Follow the steps below to update the SQL Server settings:

1. In the server machine, navigate to Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager.

(4)

Compass 2.0 installation fails with an error message “Database creation failed Contact tech support”. This error occurs (prior to Compass 2.0 installation), if SQL Express has been uninstalled and the uninstallation was incomplete.

Uninstall SQL Express properly. Follow the steps below to uninstall SQL Express properly:

1. From Start Menu run “services.msc”, in the services stop all the SQL

Express Services Running. 2. In Add or Remove Programs, uninstall all SQL Server 2005 components in the following order:

• SQL Server 2005

• SQL Server 2005 Analysis Services • SQL Server 2005 Reporting Services • SQL Server 2005 Notification Services • SQL Server 2005 Integration Services • SQL Server 2005 Tools

• SQL Server 2005 Books Online • MSXML 6.0 Parser

• SQLXML4

• SQL Server VSS Writer • SQL Server 2005 Backward compatibility

• Any other component related to SQL server 2005

• SQL Server Native Client • SQL Server setup support files

For more details, you can refer to http://support.microsoft.com/?kbid=9099 67

During Compass 2.0 installation, if you get any of the following messages:

“.Net framework could not be installed. Install .Net framework manually”.

Or

“SQL Express could not be installed. Install SQL Express manually”.

1. Run CompassSetup.exe again from the CD.

2. If the problem persists, install .Net Framework or MS SQL Express using the ‘dotnetfx.exe or the ‘SQLEXPR.EXE in the prerequisites folder, in the CD.

Compass 2.0 installation fails with the error message ““Data migration from Access to SQL Server failed. Check the Log File CompassMigrateData.log for more details”.

(5)

Installation fails when creating a new compass database, if SQL Express is installed without any password.

Instead of using the existing SQL Express instance, allow installation to create a new SQL Instance by selecting No in the pop up window which appears during installation (see screenshot below). For more details, refer Installation Guide provided in the Documents folder of CD.

The Disk full error message is displayed when migrating from the legacy Compass to access database.

This Disk full error is displayed when Access Database is placed in Windows System Drive having less than required free space. For example, when Access Database size is 100 KB, at least 250 KB of free disk space must be available.

It is observed that in certain cases in MS Windows 7 Operating System, the MS Access to MS SQL migration fails, if the Compass 1.5.8.X MS Access database file is placed on the desktop.

Place the Compass 1.5.8.X MS Access database in local folder on drive (for example, ‘C:\CompasDB’) other than Desktop folder, as Windows 7 users require special privileges to access “…\Documents and

(6)

Access to SQL database migration fails if the Source Access data base has accounts containing long string in Notes field.

Maximum number of letters in Notes must be less than 8000 characters. To resolve this issue, search for all

accounts having long notes and reduce the length to less than 8000 characters.

If you get the below error while migrating the Database, Restart SQL Service in the PC and then proceed with the database migration.

System throws error message Error:1335 message while installation is in progress. This may occur in Operating Systems Windows 7 64 bit version.

References

Related documents

At the end of '99, the standards for reservist training statewide jumped to 650 hours but Blanas could have grandfathered Jack Sellers and other major cronies the way Sheriff

To clarify whether the nanoscale stress concentration dominated the creep fracture, two types of specimens were prepared: a forward specimen (loading with the column

Section 1 − Determine where you need to add space and decide how much Section 2 − Check for available unallocated space in the volume group Section 3 − Check to see if

e ff ects of FSH on early follicle populations in the absence of luteinizing hormone (LH) activity, we examined mature hypogonadal ( hpg ), gonadotrophin-deficient mice

References are times like divorce ok in bible teach on scriptural grounds of me where divorce and provide your wife who is make the one jot or two.. Issue here but allow divorce

In such circumstances, it does not make sense to speak of "too much" anger, as someone like Urmson might do, or to associate virtue with an intermediate condi- tion

Mostafa (2009) holds altruism, environmental concern, environmental knowledge, skepticism towards environmental claims, environmental attitudes to be the main factors that may

Despite spending most of acc championship ncaa college football news, when is the heisman trophy presentation will receive an ncaa football has been fascinated by clicking the trophy