Manage Email Signatures Centrally - For All Users

Walter · Posted: Fri Aug 15, 2008 1:46 pm Post subject: logon error

When my users logon via login script they have started to see an error screen popup that states it came from EamilSignature, but has no text in the box just the red error icon and an ok button to close the screen.

I cannot figure out where this error is being generated from.

Any help would be apprecitated.

Dave Culley · Posted: Fri Aug 15, 2008 2:58 pm Post subject:

Hi,
This generally happens when either the script is slightly wrong, or the settings database has become corrupt. Please open the cockpit and use the 'repair the settings database' option if you are using version 5 or open the database in access, if the database is corrupt then an error message will appear asking you if you want to repair it. This should clear your issue.

Walter · Posted: Mon Aug 18, 2008 1:22 pm Post subject: Good fix

Checking the database file did find corruption and fixed the error. Thank you. You mention a version 5? How do i go about getting that version, I have 4.9.2 right now.

Dave Culley · Posted: Mon Aug 18, 2008 1:29 pm Post subject:

Please have a look at the downloads section of this forum for details on version 5, if you wish to upgrade you will need a new license key which you can obtain from the office you purchased from originally. Upgrades are covered under your annual maintainance agreement.

Rob · Posted: Wed Sep 03, 2008 10:21 am Post subject: Same Problem

Hi Dave

I was talking to yesterday regarding the same issue that Walter had.

If you remember you advised me to remove the space in the name of the shared folder, I did that, but I was still getting the error at the client when I tried to run sign.exe.

This morning I carried out a repair of the database like you advised Walter, still no joy.

I know that the sharing and security are ok for the Netlogon folder and the shared folder with the settings.mdb as I can manually navigate to and access them through Windows on my client. I can open the settings.mdb file in Access.

One thing to note is that my Administrator account is the only AD user that has been allocated the signature but this is because I ran sign.exe directly through the cockpit and the cockpit is loaded on our Server with the Administrator account.

Any thoughts?

Thanks

Rob

Dave Culley · Posted: Wed Sep 03, 2008 10:31 am Post subject:

Hi Rob,

Can you confirm the shared folder where settings.mdb is sitting has full control permissions for all users? This could be a case of the users do not have permission to modify the contents of this folder and that is causing this error. You may be able to modify this folder as you will have administrator privileges, but can your other users?

Please check this and give me another call if you are still having issues.

Thanks

aldoseri · Posted: Sun Oct 12, 2008 11:57 am Post subject:

We are facing the same error, i think it has to do with the login script
in which you have to let the script (Deployment) check if the sign.exe is available in the computer & that will not deploy again.

Regards,

Jesper Frier · Posted: Sun Oct 12, 2008 9:45 pm Post subject:

I get the impression that you copy sign.exe to each computer.

If you copy sig.exe to NETLOGON on your domain controller, your script will look like this:

aldoseri · Posted: Mon Oct 13, 2008 5:39 am Post subject:

Jesper Frier · Posted: Mon Oct 13, 2008 10:02 am Post subject:

Please post log file found in Help -> Diagnostics, right click user.
_________________
</Jesper> | Test Email Signature | Showcase |

Dennis Severt [DLA ICT] · Posted: Thu Dec 11, 2008 12:09 pm Post subject: Solution!

Guys I found the solution!
Atleast, it worked for me.

Here's what I did:

The link you have to put in your loginscript was wrong because it was directing to my local harddrive instead of the networkshare!
Because the Cockpit automatically generates this line you won't think that would be the problem.

Example:

Before:
\\sbs-server\NETLOGON\sign.exe Provider=Microsoft.Jet.OLEDB.4.0;Data Source=d:\eMailSignature\settings.mdb

After:
\\sbs-server\NETLOGON\sign.exe Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\sbs-server\eMailSignature\settings.mdb

As you can see the source has changed to a network share.
Which is kinda logica because the clients will never find the settings.mdb on their own local harddrive.

So changing the Source to a network share fixed the problem for me!

Good luck!

Dennis Severt
DLA ICT
_________________
Benelux Sales / Support eMail Signature