• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4219
  • Last Modified:

Public folder expansion error 80090308

I recently installed a new version of sbs 2003 r2 and when i switched our exchange server to native mode, it bombs when i try and expand the public folders in esm. The error is "80090308: the token supplied is invalid".  

I have looked all over the internet for this and i have tried a bunch of different things that people have suggested to do, but nothing seems to fix the issue. Does anyone have any idea how i might fix this problem?
0
skaface69
Asked:
skaface69
  • 3
1 Solution
 
december41991Commented:
Not sure if you had a failed installation. Did you have a SSL cert installed here.

Anyway try this if its applicable to you as this KB is more relavant

http://support.microsoft.com/kb/324345

Dominic
www.exchangeserverinfo.com
0
 
skaface69Author Commented:
I have a third party cert installed in the default website in IIS.  The cert is through godaddy.  

in regards to the KB article, when it says to publish the cert with the FQDN, what exactly does that mean?  I am only using it for mail.mydomain.com/exchange.  our main website is hosted off site.
0
 
december41991Commented:

FQDN , : Full qualified domain name .. like name of your public folder.domain.com
well, also
try this :
This can be caused if the HTTP keep-alive setting is not checked on the virtual web
site that hosts the exadmin virtual directory.

To remedy this:
1. Right click on the Virtual Web site that hosts the 'exadmin' virtual directory
and click Properties.
2. On the Web Site tab, make sure to check the "HTTP Keep-alives Enabled" box.
3. Click OK.

More information:
This happens because HTTP Keep-alives are required for NTLM (Windows Integrated
Authentication) to work, and the Exadmin virtual directory uses NTLM authentication
by default.

0
 
december41991Commented:
or best remove the requirement on the public folders virtual directory to require SSL.
0
 
SembeeCommented:
Firs thing I would check is that you do not have require SSL enabled on either /exadmin or /public virtual directories in IIS manager. That can cause this sort of problem.
If it continues, remove the certificate (you will still have the certificate on the system so you can put it back). After removing it, drop in to a command prompt and type iisreset.
Does the problem go away then?

If it does, put the certificate back and see what happens if you make no further changes.

Simon.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now