Unable to update schedule+ free/busy data Exchange 5.5 SP4

[Matt Fulks]

I get Event ID: 7023 'Error 1069: The service did not start due to logon failure' from the MS Schedule+ Free/Busy Connector service. I am able to log on using the services ID/PW. I get an application error: Source: MSExchangeDSImp, Event ID: 287 "Unable to create object AdminSch because it already exists." And finally I get Event ID: 1051 "The extended configuration data could not be found. The Microsoft Schedule+ Free/Busy Connector recipient will be recreated. You must redefine the properties in the Microsoft Schedule+ Free/Busy Connector Options property page" on source: MSExchangeFB

[Jamie Hughes]

Hi Matt,

Thanks for documenting everything so thoroughly. Have you been having problems on this server or did this just suddenly start? Did it happen after you applied SP4? There's an old problem that's been around since Exchange 4.0 but it still applies for 5.5 and I wouldn't be surprised if you might have run into this. This would be the easiest thing to try first and see if it clears up some or all of the errors. Give this a try when you get a chance and please post a message and let us know how it goes.

http://support.microsoft.com/support/kb/articles/Q163/4/86.asp

Best regards,
Jamie Hughes

[Matt Fulks]

The version numbers are both the same, but the date on the Schedule+ extension is a year older. Is there a way to reinstall the Schedule+ extension separately, or do I need to reapply the entire patch?

[Jamie Hughes]

Hi Matt,

I would try to reinstall the Microsoft Mail Connector from the latest service pack per the Microsoft article. I don't think there's any way to just install Schedule+ separately and I'm not sure that would fix the problem since it seems to be connector related. If that doesn't work, please post a reply and I'll keep looking.

Best regards,
Jamie Hughes

[Matt Fulks]

I removed the MS Mail Connector through the Exchange CD Add/Remove option. Then I added the MS Mail Connector back. Reinstalled the SP4 and I still get the same message. The MSExchangeFB is the only Exchange service that will not start.

[Stephen Maag]

Have you checked the permissions you have assigned to the Schedule+ Extension in Exchange? Look under Configurations, Add-Ins, Extensions for Schedule+ .... in Exchange. Make sure that the server is being logged into as an administrator with rights to the connector otherwise the service won't start.

[Jamie Hughes]

Hi Matt,

Did you get this resolved yet? I've been busy for a few days and just got a chance to come back out here. On the chance it isn't fixed, I thought of one other thing you could try. I've only seen this problem with the IMC but I suppose it could happen with the Schedule+ or Free/busy connector.

First, I believe you said the version numbers are all up to date when you look at the actual files involved. Go ahead and check the files via Explorer and write down the exact build/version number. Now, you need to run the Exchange admin program in raw mode to check the version in there. To do that:

- go to the bin directory and run admin /r.
- when the admin program comes up, click the Configuration container and drill down to the Schedule+/Free Busy connector.
- select File - Raw Properties.
- in the Attribute list, click File Version.

Does it display the same build number as the actual file does when you viewed it with explorer? If not, click on Edit, change the build number, then click SET, then Apply, OK. Unfortunately I don't have that connector installed so I can't test that first on my system to see what it actually looks like. If they are the same, you have something else going on and will most likely need to place a support call with your support folks and have them work on this for you. You will need some in-depth troubleshooting to help resolve this.

Did this just suddenly happen and everything was working fine prior? Or did you make some changes and then this broke? Please give more information around the circumstances of when this happened and if it has ever worked correctly in the past.

Best regards,
Jamie Hughes

[Matt Fulks]

Jaime,
FYI,
I removed the old Exchange server from the configuration. It had been disconnected completely from the network for over a year, but was left in the Exchange settings. Once that was removed the Free/Busy scheduling started working.