Manage Email Signatures Centrally - For All Users

dhimmel73 · Posted: Thu Mar 17, 2011 4:27 am Post subject: constantly corrupt database

I have a issue whereby every few days the microsoft access database will corrupt itself and I have to restore a previous settings.mdb file to get it working again. I have tried using SQL 2007 database, but still had the same issue, so reverted back to MS access as it is easier to repair. I have also tried removing antivirus scans to the emailsig folders, but nothing seems to help. Any ideas on what is corrupting the db, as it is becoming a bit annoying.

Jesper Frier · Last edited by Jesper Frier on Tue Mar 29, 2011 6:53 am; edited 1 time in total

Unfortunately, I have never heard of eMailSignature SQL database getting corrupted (we have thousands out there).

If you have MS SQL Server 2005/2008, we always recommend SQL database instead of the default Access database.

Create SQL 2005/2008 settings DB executing a single SQL Statement

SQL Server 2005/2008 or SQL Express?
Did you create database using above script?
Please explain in more details your problem using SQL database?

Please forward log file to support@ for further analysis (please refer to this post).
_________________
</Jesper> | Test Email Signature | Showcase |

dhimmel73 · Posted: Fri Mar 18, 2011 4:16 am Post subject:

When using either SQL or Access, usually a few days later I cannot open the administration tools. It either says the access database has an error and needs to be repaired, or when on SQL it just fails to open the tool, sometime with a message, sometimes not. when I replace the files with previous ones that worked, it works again for another few days. Also where do I find the log file to send?

jesperfrier · Site Admin Joined: 09 Sep 2006 Posts: 16777215

The log file is found in Diagnostics menu (version 7).

Please create the SQL 2005/2008 database using our script and there is no problem whatsoever - as long as users have access to the database.

Only if the SQL Server is not available, you wil have problems. I suggest you create the database on SQL Server in production.

Bjarne Mess · Posted: Mon Mar 21, 2011 10:10 am Post subject:

To me it seems like you have misunderstood something. What do you mean by SQL fails when you open the tool? I don't understand what you are trying to open. Access and SQL are two completely seperate applications. Access is a horrible database when you have more than 50 users and SQL can manage everything and do not get corrupted.

Please move everything to SQL and cancel the Access if you want to avoid the corruption.

dhimmel73 · Posted: Wed Mar 23, 2011 1:22 am Post subject:

ok, maybe i haven't explained myself properly. We have 300+ users, using access as the current database, which after a few days will get corrupted and the cockpit fails to open and says the database needs to be repaired. I tried moving a clean access database via import into SQL, as I do not want to recreate all the signatures again. After a few days, a similar thing happened with the SQL database, the cockpit would not open properly. I restored the SQL database from a good copy, and it worked again fine, but again after a day or so, cockpit would stop working again.

Jesper Frier · Posted: Wed Mar 23, 2011 12:31 pm Post subject:

Unfortunately, exporting from Access to SQL is not supported by us. We have seen it work if you use Access 2007 (but not with older versions of Access).

Instead, please create a new clean SQL database using our script and copy/paste templates from editor code view.

With e.g. 10 email signature templates it's not that big a deal.
_________________
</Jesper> | Test Email Signature | Showcase |

dhimmel73 · Posted: Thu Mar 24, 2011 4:40 am Post subject:

ok I have created a new database using the script, and copy and pasted the templates. I will see how in goes in the next few days.

Jesper Frier

Is your new SQL back-end database meeting your expectations?
_________________
</Jesper> | Test Email Signature | Showcase |

dhimmel73 · Posted: Wed Mar 30, 2011 1:31 am Post subject:

so far, so good. Been about a week now with the new database built from scratch in SQL. This is better than every second day dropping out. So thank you for the help, and I will keep posted if any changes.