From: DaveF on 2 Mar 2005 17:49 Hi Dave, I found this KB article that specifically mentions E2K3: How To Reset a Site Folder in Exchange Server 2003 Article ID : 822444 Since I am having the same problem, I was wondering if you reset the site folders and how that worked out for you. I'm considering the same course of action. Dave F "Dave" wrote: > Hello again Brian > Sorry about that last post I'll try again.... I did see the article in > eventid, although it's referenced for Exchnage 2000 not 20003 which is what I > am using! > Anyway It wasn't much help, my Schedule + Free Busy folder looks fine! > Do you or anyone else have any other ideas? > > Many thanks > Dave > > "Dave" wrote: > > > Hi Brian > > > > Thanks for your reply, yes I did see this post in eventid although it does > > reference E > > > > "Brian Desmond [MVP]" wrote: > > > > > Dave- > > > > > > Have you looked at > > > http://www.eventid.net/display.asp?eventid=8277&eventno=1157&source=MSExchangeFBPublish&phase=1 > > > yet? > > > > > > -- > > > --Brian Desmond > > > Windows Server MVP > > > desmondb(a)payton.cps.k12.il.us > > > > > > www.briandesmond.com > > > > > > > > > "Dave" <Dave(a)discussions.microsoft.com> wrote in message > > > news:A307B333-91DA-47F6-A657-FB7C2FD7F04C(a)microsoft.com... > > > > Hi > > > > > > > > I am running Server 2003 with Exchange 2003 and up untill now everything > > > > has > > > > been running just fine! However I have seen the following event pop up in > > > > the > > > > Apps Log over the last two nights: > > > > Product: Exchange > > > > ID: 8277 > > > > Source: MSExchangeFBPublish > > > > Version: 6.5.6940.0 > > > > Component: Microsoft Schedule+ Free/Busy Connector > > > > Message: Error while getting sorted message table for duplicate message > > > > deletion on virtual machine <name>. The error number is 0x80004005 > > > > > > > > Can't seem to find anything on this anywhere, can anyone help? > > > > > > > > Many thanks > > > > Dave > > > > > > > > > > > > > > > > >
First
|
Prev
|
Pages: 1 2 Prev: "Security Policy In Force" Error Next: I couldn't start up Exchange System Attendant |