Manage Email Signatures Centrally - For All Users

hjones · Posted: Sun Jul 31, 2011 9:49 pm Post subject: Status 3001 - LDAP Error

Pushing the full deployment starting this weekend, full push will be Monday morning. So far have 137 signatures deployed and only one issue. I have one user that failed with Status 3001 Type Mismatch. Log info is below. Any thoughts?

---------------- eMailSignature LOG file ---------------------------------
- Started at 7/31/2011 2:32:48 PM
- sign.exe version 7.5.0
- Microsoft Windows 7 Professional - 0409 1033
--------------------------------------------------------------------------

Connection string to settings database:
Provider=sqloledb;Data Source=servername;Initial Catalog=eMailSignature;User Id=username;Password=cpassword;
7/31/2011 2:34:01 PM Begin finding user DN
User path: LDAP://DC=DOMAIN,DC=COM
Running in the context of the user 'vinmur'.

----------------- License Key Information ---------------------------------
The license key is valid.
Enterprise Gold Edition licensed. License issued to My Company for 1500 users.
---------------------------------------------------------------------------
7/31/2011 2:40:05 PM OU based deployment applied. If no OU rules apply, 'Default for All' will be used.

------------------- Signatures to deploy: ---------------------------------
Default signature: Industries Signature
Reply/forward signature: eMailSignature Demo
Signatures to deploy: Industries Signature
Internal Deployment ID: 29
Deployment method: Default for all has been applied.
(no OU rule criterions have been met).
---------------------------------------------------------------------------
Office version 2007 detected.
1 signature to deploy.
Outlook Signature folder Signatures.
All existing signatures not being generated by eMailSignature have not been changed.

-> Signature Industries Signature in htm format (7/31/2011 2:40:05 PM)
-> Campaign Mode: Campaign for groups.
The user is not a member of any groups so no group campaign will be added.
11 merge fields in this signature.
Data will be merged from Active Directory.
Root context for vinmur: LDAP://DC=DOMAIN,DC=COM
3001: <LDAP://DC=DOMAIN,DC=COM>;(&(objectCategory=person)(sAMAccountName=vinmur));distinguishedName, 13, Type mismatch
-------------- eMailSignature END LOG file -------------------------------
- Finalised at 7/31/2011 2:40:12 PM
--------------------------------------------------------------------------
Status: 3001: <LDAP://DC=DOMAIN,DC=COM>;(&(objectCategory=person)(sAMAccountName=vinmur));distinguishedName, 13, Type mismatch
-------------- eMailSignature END LOG file -------------------------------
- Finalised at 7/31/2011 2:40:27 PM
--------------------------------------------------------------------------
Status: 3001: <LDAP://DC=DOMAIN,DC=COM>;(&(objectCategory=person)(sAMAccountName=vinmur));distinguishedName, 13, Type mismatch

Bjarne Mess · Posted: Mon Aug 01, 2011 1:22 am Post subject:

Please send a log file for a user where it reports OK.

As you have many confidential information in the log to hide, please take it off forum by sending it to support@brandedmails.com and we will get back with the conclusion.

Thank you.

Bjarne Mess · Posted: Mon Aug 01, 2011 2:33 am Post subject:

A shot addition: It seems like it cannot find the account 'vinmur'. Can you please check that this is the real name in AD?

hjones · Posted: Mon Aug 01, 2011 11:34 am Post subject:

Logs and additional information sent via email as requested Bjarne.

Bjarne Mess · Posted: Mon Aug 01, 2011 12:30 pm Post subject:

It cannot find that user in AD. Please can you confirm that this account exists with this name?

hjones · Posted: Mon Aug 01, 2011 12:37 pm Post subject:

The user does exist in AD, however, his AD logon name is vinmur, but his Exchange alias is tadmur. Users name is Vincent Murphy, but he is known as Tad Murphy, thus explaining the differences. Which would need to be changed, logon account, or alias?

hjones · Posted: Mon Aug 01, 2011 12:39 pm Post subject:

Bjarn, please disregard. I just checked the cockpit now and the error seems to have resolved itself. Thanks for your time.