Manage Email Signatures centrally from your Desktop - For All Users

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

I just deployed my signatures this morning, and I have a 45% success ratio. I have 147 failed attempts.

I get status 3 / 3001: No data found for bob

All the users are in groups and have signature assigned.

I tried updating the Mdac on one of their computers, but no luck..

Any ideas?

Bjarne Mess · Posted: Fri Sep 14, 2007 8:54 pm Post subject:

Hi,

Please paste in a log file.

Thanks.

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

Error #1 _ I have 62 of these errors

3001: , 430, Class does not support Automation or does not support expected interface

This was on a Windows 2000 machine and was resolved by updating MDAC.

-------------- eMailSignature LOG file -------------------
- Started at 9/14/2007 4:34:11 PM
- sign.exe version 4.8.7 has been run for this user.
------------------------------------------------------------

Connection string to settings database:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\qmsmtdtfs\emailsig$\settings.mdb
9/14/2007 4:34:18 PM Begin finding user DN
User path: LDAP://DC=quantum-native,DC=net
User: genevieve.riendeau (genevieve.riendeau)
9/14/2007 4:34:29 PM License Key valid. Licensed version detected. No modules.

------------------- Signatures to deploy: -------------------
Default signature: NONE
Reply/forward signature: NONE
Signatures to deploy: QMSEng,QMSFre
Origin ID (Internal): 1

-------------------------------------------------------------
Office version 2003 detected.
There will be deployed 2 signatures.

-> Signature QMSEng in htm format (9/14/2007 4:34:30 PM)
Number of parameters in signature: 8
Data will be read from Active Directory
Root context for genevieve.riendeau: LDAP://DC=quantum-native,DC=net
3001: , 430, Class does not support Automation or does not support expected interface

-> Signature QMSFre in htm format (9/14/2007 4:34:32 PM)
Number of parameters in signature: 8
Data will be read from Active Directory
Root context for genevieve.riendeau: LDAP://DC=quantum-native,DC=net
3001: , 430, Class does not support Automation or does not support expected interface
-------------- eMailSignature END LOG file -----------------
- Finalised at 9/14/2007 4:34:33 PM
------------------------------------------------------------
Status: 3001: , 430, Class does not support Automation or does not support expected interface
-------------- eMailSignature END LOG file -----------------
- Finalised at 9/14/2007 4:34:39 PM
------------------------------------------------------------
Status: 3001: , 430, Class does not support Automation or does not support expected interface

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

Error #2_ I have about 80 of these errors.

---------------- eMailSignature LOG file -------------------
- Started at 9/17/2007 10:24:24 AM
- sign.exe version 4.8.7 has been run for this user.
------------------------------------------------------------

Connection string to settings database:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\qmsmtdtfs\emailsig$\settings.mdb
9/17/2007 10:24:54 AM Begin finding user DN
User path: LDAP://DC=quantum-native,DC=net
9/17/2007 10:24:56 AM End Finddistinguishedname
User: jfb ()
9/17/2007 10:25:18 AM License Key valid. Licensed version detected. No modules.

------------------- Signatures to deploy: -------------------
Default signature: NONE
Reply/forward signature: NONE
Signatures to deploy: QMSEng,QMSFre
Origin ID (Internal): 1

-------------------------------------------------------------
Office version 2003 detected.
There will be deployed 2 signatures.

-> Signature QMSEng in htm format (9/17/2007 10:25:23 AM)
Number of parameters in signature: 8
Data will be read from Active Directory
Root context for jfb: LDAP://DC=quantum-native,DC=net
No data found for jfb in GC or in alternative domain specified in registry.
3001: No data found for jfb, DN:

-> Signature QMSFre in htm format (9/17/2007 10:25:25 AM)
Number of parameters in signature: 8
Data will be read from Active Directory
Root context for jfb: LDAP://DC=quantum-native,DC=net
No data found for jfb in GC or in alternative domain specified in registry.
3001: No data found for jfb, DN:
-------------- eMailSignature END LOG file -----------------
- Finalised at 9/17/2007 10:25:27 AM
------------------------------------------------------------
Status: 3001: No data found for jfb, DN:
-------------- eMailSignature END LOG file -----------------
- Finalised at 9/17/2007 10:25:41 AM
------------------------------------------------------------
Status: 3001: No data found for jfb, DN:

Bjarne Mess · Posted: Mon Sep 17, 2007 5:22 pm Post subject:

I notice that it cannot find this domain LDAP://DC=quantum-native,DC=net

Please, can you correct this to the right LDAP root as it seems not to connect.

Can you preview in the Cockpit at all?

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

That is weird.

In my advanced technical settings I have

LDAP://DC=quantum-group,DC=net

This setting is soemthing I treid during truoble shouting atleast a month ago

LDAP://DC=quantum-native,DC=net (not good).

How do I get it out of the database?

Yes I can preview fine.

Bjarne Mess · Posted: Mon Sep 17, 2007 5:57 pm Post subject:

OK, please try to enter data source manager and see if you can identify the LDAP string here and then delete it.

Does this help?

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

There is nothing under special root context. Is there a way to look into the Database and see if it there?

Bjarne Mess · Posted: Mon Sep 17, 2007 6:06 pm Post subject:

Please check the following:

content of 'rootcontext' in the settings database - should be blank
existence of a key 'root' in the registry - can be deleted.

Thanks,
Bjarne

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

I don't see any referrence to 'rootcontext' under "settings database". Th e only place I find it is under the "Manage data sources" window.

Under settings database, the current database has no reference to root context.

Under Manage data sources windows the "special root context" the field is blank. Even if I try setting it to the correct string

LDAP://DC=quantum-group,DC=net

and save. If I leave the window and come back it is still blank.

Quote:
existence of a key 'root' in the registry - can be deleted.

Where do I find this registry key? Who registry? where the cockpit is installed?

Bjarne Mess · Posted: Mon Sep 17, 2007 9:00 pm Post subject:

Yes, where the Cockpit is installed.

The key is: HKCU\SOTWARE\Office add-on\eMailSignature.

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

Two people have the cockpit installed.

Both registry entries have the proper root context.

I have gone into the "manage data sources" and deleted all data sources.

I then re-created the AD one, and reasigned it to all the signatures.

I am now checking to see if it has cleared the incorrect Root context.

I will post when I have confirmation of success or failure.

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

I am still getting this error.

User path: LDAP://DC=quantum-native,DC=net (wrong root context). I can't seem to get rid of it.

The problem however seems to be random. Some users who now have the error, already updated the signatures the day before.

I am also noticing this error

Status: 3001: , 430, Class does not support Automation or does not support expected interface

and this one.

Status: You are not logged into a domain (3001B)

Of course they are logged in, they ran the logging scripts which triggered Sign.exe.

My successes and failures vary depending on the radomness of the error above.

This morning I had 181 Success 133 failure
Noiw I have 178 success and 135 failure.

HELP!!! :-)

Jesper Frier · Posted: Wed Sep 19, 2007 6:59 pm Post subject: WORKAROUND

Here's a quick workaround starting with a new database:

1) Copy standard settings.mdb from installation folder to \\qmsmtdtfs\emailsig$\
2) Enter license key
3) Ajust Outlook settings (font type and word as editor)
4) Create new signatures and copy QMSEng and QMSFre in code view
5) Set Default signature: NONE
Reply/forward signature: NONE
Signatures to deploy: QMSEng,QMSFre

Same problem?

seanb · Just can't stay away Joined: 17 Jul 2007 Posts: 43

I was affraid you were going to say that.

Then I looked at the smile on your face (Avatar) and I could just imagine you snickering as you typed the message telling to redo my signatures in a new database. Made my laugh. :-)

I will let you know.