Blackberry Administration Service issue
I cannot add a new AD user to an Blackberry User account. I removed the old one and when I click Add Active Directory Authentication I get this description below:
If you delete the authentication type for a user account on the User Information tab and then try to add Microsoft Active Directory authentication to the user account, the BlackBerry Administration Service unexpectedly logs out and displays an error. (DT 640074)
I got this from Blackberry under known issues. How do I resolve it?
Thanks
If you delete the authentication type for a user account on the User Information tab and then try to add Microsoft Active Directory authentication to the user account, the BlackBerry Administration Service unexpectedly logs out and displays an error. (DT 640074)
I got this from Blackberry under known issues. How do I resolve it?
Thanks
Jamie Gillespie
Check under "pending removal" as the old account probably hasn't been completely removed from BES?
ASKER
Where do you find "pending removal"? I'm in the BlackBerry Administration Service. I cannot find this feature/heading.
It depends which version your using?
I know if you search for current users theres and advanced filter where you can select pending users to be deleted. Well on these lines anyway, I would need to look at it. Let me know if you can't find it and I'll hunt it down.
I know if you search for current users theres and advanced filter where you can select pending users to be deleted. Well on these lines anyway, I would need to look at it. Let me know if you can't find it and I'll hunt it down.
ASKER
I only have five users. I am using BES Express 5.0.2.29 I believe.
Same version I have..
This should help bud;
http://www.blackberry.com/btsc/microsites/search.do?cmd=displayKC&docType=kc&externalId=KB18404&sliceId=1&docTypeID=DT_SUPPORTISSUE_1_1&dialogID=1120624120&stateId=0
This should help bud;
http://www.blackberry.com/btsc/microsites/search.do?cmd=displayKC&docType=kc&externalId=KB18404&sliceId=1&docTypeID=DT_SUPPORTISSUE_1_1&dialogID=1120624120&stateId=0
alternatively, the pending Q is normally cleared with a server restart. log back in with your besadmin account and see if you can re-add the user from AD. At a push you could shut down all BES services and restart them, but its usually easier to restart, especially if you may have other server patches awaiting a restart.
alternatively you can try an advanced user search and immediate removal as Jamie mentioned above, though i have had some former staff members get 'stuck' on removal and the restart helped.
alternatively you can try an advanced user search and immediate removal as Jamie mentioned above, though i have had some former staff members get 'stuck' on removal and the restart helped.
ASKER
Restarting the server did not work.
ASKER
Jamie
After I followed the instructions you provided. After doing a Search it brought back no results. It still brings up an error when trying to Add Active Directory Authentication. Any other ideas?
Thanks
Matt
After I followed the instructions you provided. After doing a Search it brought back no results. It still brings up an error when trying to Add Active Directory Authentication. Any other ideas?
Thanks
Matt
Did you select the tick box to filter user pending for deletion?
ASKER
Yes. Nothing was listed. I don't know what to do.
ASKER
Jamie - this is from a previous post: "mattmcglone:Jamie
After I followed the instructions you provided. After doing a Search it brought back no results. It still brings up an error when trying to Add Active Directory Authentication. Any other ideas?
Thanks
Matt "
After I followed the instructions you provided. After doing a Search it brought back no results. It still brings up an error when trying to Add Active Directory Authentication. Any other ideas?
Thanks
Matt "
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It took too long for anyone to assist with this issue. Furthermore the answers provided did not work. I ended up fixing it myself by recreating the account in BES.