This is a general error returned by the Access drivers. You can try the following;
1) Restart IIS
2) Assign full permissions to all users for the data subfolder of the DbNetSpell installation folder (where the Access data file is stored)
3) Check that you have the latest versions of MDAC and the JET Drivers installed on the server.
If the problem persists, you can migrate DbNetSpell to use Sql Server or MSDE. To do so, take the following steps;
1) Download the appropriate dictionary file and place it in the 'imports' subfolder of the DbNetSpell installation folder. This is a CSV file supplied within a zip archive, so make sure you extract it. The dictionary file may be downloaded from this URL
http://www.dbnetspell.com/dbnetspell/download.aspx
2) Identify the Sql Server database which will serve as the location for the new dictionary table. You can use an existing database or create a new one. You should then take the OLEDB connection string which accesses the database and copy this into the value property of the 'default' connection alias within the web.config file in the DbNetSpell installation folder. For example;
<add key="default" value="Provider=SQLOLEDB;Server=server1;Database=northwind;UID=sa;PWD=;"/>
(note - you can check the connection string first by pasting it into the conection string test utility which is accessible from the DbNetSpell menu page.)
3) You can then run the Dictionary Management utility from the DbNetSpell menu page. Select the correct dictionary source file from the list of Dictionary Source Files and select 'default' from the connection alias drop-down and then click on the button to 'Create Dictionary'. ictionary creation will start and progress will be reported every 1000 words.
Hide Answer |
