Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Error: The parameter is incorrect when enabling users

Created: 05 Feb 2013 • Updated: 15 Feb 2013 | 4 comments
vmds's picture
This issue has been solved. See solution.

Hey,

 

we migrated our EV 9 environment to EV10.0.2 with the help of the Server Migration Wizard. Since then we are unable to enable new users.

Eventlog says:

Date:          05.02.2013 15:34:25
Event ID:      3139
Task Category: Agent Client Broker
Level:         Error
Description:
An non-specific error has occurred whilst enabling archiving for the mailbox /o=domain.group/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Wagner, Tobias8e2 

 

Error: The parameter is incorrect.  (0x80070057) 
 
and:
 
An non-specific error has occurred whilst enabling archiving for the mailbox /o=domain.group/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Müller, Steffenf7a 
 
Error: The parameter is incorrect.  (0x80070057) 
 
Please note the additional charakters at the end of the ldap paths. 
 
 
The AgentClientBroker dtrace looks like this:
 
:M {CMAPISession::CreateMapiSession:#328} Getting the 'Exchange Server DN' from the privileged mbx
790 15:34:25.149 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::GetExchangeServerDnFromSession} (Entry)
791 15:34:25.149 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::GetExchangeServerDnFromSession:#474} QueryIdentity
792 15:34:25.149 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::GetExchangeServerDnFromSession:#477} Open Session Prop
793 15:34:25.149 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::GetExchangeServerDnFromSession:#480} Calling get Props (PR_EMS_AB_HOME_MTA_W)
794 15:34:25.164 [10456] (AgentClientBroker) <220> EV:M {CMAPISession::GetExchangeServerDnFromSession:#504} ExchangeServerDn = [/o=NT5/ou=00000000000000000000000000000000], ExchangeMsgStoreDn = [/o=NT5/ou=00000000000000000000000000000000/cn=Microsoft Private MDB]
795 15:34:25.164 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::GetExchangeServerDnFromSession} (Exit) Status: [Success]
796 15:34:25.164 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::CreateMapiSession:#354} Getting privileged mbx owner (MAPI property PR_MAILBOX_OWNER_ENTRYID)
797 15:34:25.164 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::CreateMapiSession:#359} Opening privileged mailbox's owner MailUser object
798 15:34:25.180 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::CreateMapiSession:#370} Reading MailUser 'PR_EMAIL_ADDRESS' MAPI property
799 15:34:25.180 [10456] (AgentClientBroker) <220> EV:L {UnEncodeCurlyBraces:#5711} String: /o=domain.group/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Entvault-MBX05
800 15:34:25.180 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::CreateMapiSession:#378} MailUser 'PR_EMAIL_ADDRESS' MAPI property = /o=domain.group/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Entvault-MBX05
801 15:34:25.180 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::CreateMapiSession:#384} Getting IExchangeManageStore object from the privileged mbx
802 15:34:25.180 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::CreateMapiSession} (Exit) Status: [Success]
803 15:34:25.180 [10456] (AgentClientBroker) <220> EV:L {CMAPISession::GetMapiSessionFromPoolEx} (Exit) Status: [Success]
804 15:34:25.180 [10456] (AgentClientBroker) <220> EV:H {CAgentExchSynch::OpenMailboxStore} HRXEX fn trace : Error [0x80070057], [.\AgentExchSynch.cpp, lines {2144,2154}, built Sep 12 21:03:51 2012].
805 15:34:25.180 [10456] (AgentClientBroker) <220> EV:M CAgentExchSynch::OpenMailboxStore - Exit [0x80070057]
806 15:34:25.180 [10456] (AgentClientBroker) <220> EV:H {CAgentExchSynch::EnableMailboxCommonV9} HRXEX fn trace : Returning error [0x80070057], [.\AgentExchSynch.cpp, lines {5048,5278}, built Sep 12 21:03:51 2012].
807 15:34:25.180 [10456] (AgentClientBroker) <220> EV~E Event ID: 3139 An non-specific error has occurred whilst enabling archiving for the mailbox /o=domain.group/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Wagner, Tobias8e2 |Error: The parameter is incorrect.  (0x80070057) |
808 15:34:25.180 [10456] (AgentClientBroker) <220> EV:M CArchivingAgentQueue::EnableMailboxV9 - exiting due to error
 
 
Synchronization of existing users fails with the same error (parameter incorrect, BUT the ldap path name is correct, according to the eventlog).
Still, I get the same dtrace error for the sync, including this one (same lines):
 
{CAgentExchSynch::OpenMailboxStore} HRXEX fn trace : Error [0x80070057], [.\AgentExchSynch.cpp, lines {2144,2154}, built Sep 12 21:03:51 2012].
 
 
 
Any ideas where i can start the troubleshoot?
I have seen http://www.symantec.com/business/support/index?page=content&id=TECH180950 already, but the permissions are set correctly.
 
 
regards
 

 

Comments 4 CommentsJump to latest comment

GertjanA's picture

Hm. I'd look at the account itself, looks like it has 'something' behind the name. PErhaps check your ExchangeMailboxEntry table to see if the entry there is corrcet.

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl

www.quadrotech-it.com

www.symantec.com/vision

vmds's picture

Yes, thats what I have noticed too.

 

I just checked my ExchangeMailboxEntry Table.

1) Lots of those entrys (only new accounts if I see that correctly) have the additional characters under legaxymbxdn. Why's that?

2) Regarding the (failing) synchronization of existing users:
The Legacymbxdn of those users are looking "normal". No addition charakters, nothing obvious there. 

3) Does anyone know if they changed something on how special german characters (aöäüß) are handled?  At some point, the legacymbxnames of users with such characters looks like this:

/o=domain.group/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user2c42ee91

 

 

//Edit

I have just deleted one of the new accounts in the exchangemailboxentry table and did run the provisioning task again. According to the report it did add perfectly fine without any additinal characters. However, in the corresponding SQL LegacyMBXDN it has (the same) 3 additional characters as before.

 

 

 

//Edit2

Forget about that idea. :)

I just checked the rows in my lab and it has similar entrys. 3 Additional characters for every legacymbxentry in a exchange 2007 or 2010 environment. For Exchange2003 entrys the additional characters are missing. Same for the äöüß characters. 

 

vmds's picture

Found the solution.

There was a typing error in our GC value. Still everything was working fine, except enabling/disabling user + synchronization :)

SOLUTION