Partager via

80090308 "The token supplied to the function is not valid"

  • Article

 

The customer was getting the above error when clicking on Public Folders in Exchange System Manager.  He was also getting the following error when running the Add Distribution Group wizard and selecting to create an "archive public folder":

 

---------------------------
Add Distribution Group Wizard
---------------------------
The wizard could not successfully configure this group. The following could not be completed:

 

- The Exchange public folder could not be created.

 

Do you want to keep this group?
---------------------------
Yes   No  
---------------------------

 

This article was followed without success.  What we did to resolve it was to remove a value in Active Directory using ADSIEdit.  We had to install the Windows 2003 Support Tools to get access to ADSIEdit.  With the SBS 2003 media, the support tools are located in cd2\support\tools\suptools.msi.  The attribute is msExchSecureBindings.  The value is :443:. 

 

Specifically,

Configuration >

    Services >

        Microsoft Exchange >

            Domain Name >

                Administrative Groups >

                    First Administrative Group >

                        Servers >

                            Servername >

                                Protocols >

                                    HTTP >

                                          1 >

                                              Exadmin

We right clicked on Exadmin and clicked Properties.  We scrolled down until we found msExchSecureBindings and clicked Edit.  By default, the value was/is :443: - we clicked to highlight :443: and clicked Remove.  It then showed <Not Set> for msExchSecureBindings.  We then restarted the Microsoft Exchange System Attendant and then restarted the IISAdmin service. 

 

For all you (us) geeks, here is the full "distinguishedName":  CN=Exadmin,CN=1,CN=HTTP,CN=Protocols,CN=SERVER,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=COMPANY,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=local

 

The root cause is because the certificate that was installed in IIS did not contain the "servername" in the "subject" field (you have to view the certificate and click the details tab to see this field).

Other errors per this article are:

The SSL certificate server name is incorrect.
ID no: c103b404
Exchange System Manager

The connection was aborted. Ensure that the settings on your default Web site are correct and refresh the Public Folder Tree
ID no: c103b402
Exchange System Manager

 

Have a good weekend!

 

Petergal

Comments

  • Anonymous
    January 01, 2003
    PingBack from http://www.keyongtech.com/4145172-sync-public-folders

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    PingBack from http://www.hilpers.com/1206118-exchange-server-2003-problem-public

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    March 25, 2007
    Great - fixed problem straight away, after having spent several hours trying to resolve why I couldn't get to the public folders on the exchange server manager.

  • Anonymous
    December 26, 2007
    Thank you very much.  The fix I have been trying to find for a long time!

  • Anonymous
    February 14, 2008
    Thanks so much Peter! This solved the specific The SSL certificate server name is incorrect. ID no: c103b404 Exchange System Manager error we had on a SBS 2003 SP2 server. All other suggestions, also as mentioned in KB324345 did not work for us.

  • Anonymous
    March 26, 2008
    Thank you very much for this documented solution.  I waded through Microsoft KB articles with no success, and then I stumbled on this.  Problem solved!

  • Anonymous
    May 05, 2008
    Thanks heaps for this. I had an identical problem and had also tried the linked support article to no avail. This fixed it a treat!

  • Anonymous
    August 20, 2008
    thanks very much, this is the 6th or 7th article I've looked at and the only one thus far gave the correct answer my case.

  • Anonymous
    September 08, 2008
    Cheers Peter, worked a treat. NB: I made the edit and did an "iisreset /restart" -- All tested and working (ie. no requirement to restart exchange services) Cheers.

  • Anonymous
    September 26, 2008
    Wow!!  Thank you!!  This fixed us right up.  This is really good documentation. Thanks again! Danny Parrott Region 16 Education Service Center Amarillo, TX

  • Anonymous
    September 30, 2008
    Thanks very much for this... It worked a treat!

  • Anonymous
    October 20, 2008
    Hi I also had this issue on an SBS Standard system but initially the above solution did not resolve the problem. In this case there was a self signed certificate of say server.internalname.local and a purchased certificate of server.internetname.com. When I changed the IIS certificate back to the self signed one it all started to work thus proving that it was definately the certificate causing the problem. IIS restarts, System Attendant restarts, server restarts did not resolve the issue. The 'Require secure channel (SSL)' settings had been removed and the ADSIEdit msExchSecureBinding setting was clear. However, by changing the certificate back to the self signed one, and then back again to the secure external one the ADSI settings had been changed. This time clearing them did the job. So if you still have problems try this:

  1. Remove the 'Require secure channel (SSL)' setting as above.
  2. Change the IIS certificate for the Default Web Site back to the original self signed certificate.
  3. Test the System Manager to make sure you can now access the Public Folders, this ensures that the SSL certificate is the real cause of the issue.
  4. Change the SSL certificate back to the external secure certificate.
  5. Restart IIS with iisreset /restart. Run ADSIEdit in teh mmc console and remove the msExchSecureBinding setting as above.
  6. Test the System Manager again, with luck all should be well.