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?
skaface69Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.