==> Problems after exchange offline defrag <==

[noname111]

We are running Microsoft exchange 2003, sbs 2003 and blackberry professional 4.1.4.15

Over the weekend we took our information store offline to perform an exchange defrag. When we started it again emails weren’t being forwarded to any of our 3 blackberries. All the blackberry services were stopped and when I tried to start them I got the error:

"Could not start the blackberry router service on local computer" Error 1069: The service did not start due to a logon failure.

This error was caused because for some reason the services were not logging on as a local system account (which apparanty is essential). I fixed this and now all the services start and in blackberry manager everything reports as running okay but the last contact time shows as the 23rd July and still noone receives anything on their blackberry. I have tried restarting the server and resending the service books but this hasn’t helped.

I then found the following error in the event logs:

"The description for Event ID ( 20406 ) in Source ( BlackBerry Controller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 'JNLSERVER' agent 1: will not restart - reached the maximum of 10 restarts per 24 hours."

Any help with this would be very much appreciated.

Thanks

> noname

[titanjhb]

Unless I'm mistaken, the Blackberry services actually need to run as the BESAdmin service account (or whatever you named it), this would include the blackberry router. The last error is actually "normal" for the controller. The controller basically sits there are watches the other services and restarts them if and as needed, but it stops trying if it has failed 10 attempts in a 24 hour period.

[noname111]

I have solved this now thanks I had a local admin login that never expires but I think my BESadmin account was set to expire even though I thought it didn't which may have caused the issue. It all works now in any case.