Spider Knowledge Base

Spider Knowledge Base

Spider Setup: Existing database name chosen

0 0 310
Symptoms The Setup reports you have chosen a database name to be created, that already exists. Cause You specify a new database to be created, and this database already exists on the SQL server. Resolution Choose a different name for your database, ...
by Moderator jborchers Moderator

Spider Setup: Existing database is not empty

0 0 297
Symptoms The setup reports a database not being empty. Cause The chosen database was found to have tables, this probably means it has been used before. Resolution Choose another database or let the setup create a database.
by Moderator jborchers Moderator

Spider Setup: SQL server collation

0 0 502
Summary Setup reports SQL Server collation as invalid. Symptoms Setup reports SQL Server collation as invalid. Cause As described in System Requirements - SQL Server the collation on the server must be a case insensitive (CI) collation. Resolution Ch...
by cheld Level 3

Spider Setup: SQL database collation

0 0 314
Summary Spider setup reports SQL database collation as invalid. Cause As described in System Requirements - SQL Server the collation of the databases must be a case insensitive collation, for example SQL_Latin1_General_CP1_CI_AS. Resolution Create a ...
by sfdcowner Level 9

Spider Setup: System Requirements - Microsoft .Net

0 0 330
Summary Setup reports missing valid Microsoft .Net Framework. Symptoms Columbus setup reports missing valid Microsoft .Net Framework. Cause Some operating systems do not have the required Microsoft .Net Framework installed by default. Resolution ...
by sfdcowner Level 9

Spider Setup: Administrative privileges for installation

0 0 335
Summary Installation User needs administrative privileges for Spider. Cause Since the system configuration needs administrative privileges for certain tasks, it is necessary that the executing user of the setup is an administrative user of the machin...
by sfdcowner Level 9