Ladies and Gents, Just wanted to let you know that the problem appears solved...
Here's all I did... Went into IIS admin and removed my SSL cert from the site... Stopped and restarted the default web site... PF properties were again available in ESM... Reinstalled my cert into the default site but made sure NOT to force SSL on the entire site (even though I'd turned this off after the fact previously, it didn't seem to make a difference)... Force SSL only on the Exchange subdirectory and everything appears to be operating correctly... OWA still forces the secure channel and I can still get to PF properties in the ESM... Thanks again to Chris for responding on a Sunday.. Now it's time to look into the next problem (Can't manually restart the Exchange Event service, EventID:5 with error 0x80004005, any takers? MSKB 265397 wasn't the answer....) Guess I'll post another message in the morning if I can't hunt it down. Hope everyone had a good weekend. Joe Pochedley If you have time to do it twice, you had time to do it right in the first place. -----Original Message----- From: Joe Pochedley Sent: Sunday, March 30, 2003 7:02 PM To: Exchange Discussions Subject: RE: Ex2k - PF error in ESM Chris, Thanks for the response on a Sunday... My SSL cert is for webmail.namfg.com, which isn't the server's 'real' FQDN (or AD name)... Webmail is more user friendly than the server's real name.. I do have a DNS entry for the "webmail" address both internally and externally, and OWA does work properly... Would that cause the problem? I could remove the cert (it's only a temporary cert for testing, I didn't pay for it yet)... Question I'd have then is how can I address the server as "webmail" on the internet if I've got to have the cert named with the real/AD FQDN of the server? Would I have to go to a FE/BE solution instead of running everything off one machine just to have the friendly name? JoeP -----Original Message----- From: Chris Scharff [mailto:[EMAIL PROTECTED] Sent: Sunday, March 30, 2003 1:43 PM To: Exchange Discussions Sounds like you've tried most of the recommended solutions (does your SSL certificate match the server's FQDN BTW?). The only KB article which dealt with Exchange also appears to have been pulled, so if you call into PSS on this one, I thin you'd have a > 80% change of having the issue be non-decremented when all is said and done. But since it sounds like you've tried everything the general wisdom suggests, PSS is the best next step. BTW, well written query and excellent detailing of the steps already tried. Should save people from suggesting a bunch of things you've already tried. On 3/30/03 11:00, "Joe Pochedley" <[EMAIL PROTECTED]> wrote: > Ladies and Gentlemen, I'm hoping someone can help me... > > I've recently migrated my organization to Exchange 2000, and for the > most part things have gone smoothly... Of course now I've developed a > problem... > > The problem started when I was investigating why backup of some of our > PF's wasn't working properly (using BE9, which was complaining about not > being able to find about a dozen of our 1400+ PF's)... I was assuming > that the folders in question did not replicate properly from our Exch5.5 > server, so I wanted to go into ESM and check to make sure the folders > were set to replicate with the Exch5.5 server properly... > > Long story short: Any time I attempt to access the properties of a PF > in ESM, I get the following error: > > The token supplied to the function is invalid > ID Number: 80090308 > Exchange System Manager > > Accessing PF's in ESM did work properly in the past... I've STFW and the > MSKB and the only references I can find relate to LDAP errors, which I > suppose could be the root of the problem, but I have no idea how to fix > it... (LDAP queries for other things appear to work properly)... > > I did find one message in my searching regarding requiring SSL in the > Default web site causing this problem... I have installed a SSL cert to > secure OWA, and changed the security requirement on the default site so > SSL is only required on the /Exchange folder, but that didn't help... > Then I tried not forcing SSL on any of the OWA/IIS folders and it still > hasn't made a difference... > > I'm sure I'm not the only one who's had this problem? Any pointers on > how to fix it would be greatly appreciated. > > Thanks. > > Joe Pochedley > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
