[hitty]

Hi
Im getting this error appear in my MAGT logs:
<N/A> | BlackBerry Messaging Agent BES Agent 1 (Application Event Log on BES) | 02/05/2009 09:57:26 (EFFF2710) -> [DIAG] Error during writing the debug file header : Permission denied (error : 13)

Found this KB on BB website, but it doesnt completely match the error above:
View Document

I was originally on BES 4.1.6. MR1, and thought upgrading to MR3 will fix it.
However a few days later Im still getting these errors pop up 2-3 times a day in my logs.
The devices are appear to be working OK. 2 way sync is working for email, calendar and address book.

Any thoughts?

[Jadey]

Any of this look familiar?
http://www.blackberryforums.com/bes-...6-one-bes.html

[hitty]

Originally Posted by Jadey

Any of this look familiar?
http://www.blackberryforums.com/bes-...6-one-bes.html

Thanks Jadey.

But the error in the thread you posted is different:
[DIAG] Error telling the debug trace file position

It matches the KB i posted earlier and the solution advises to upgrade to MR1. I was on MR1 and upgraded to MR3.

[Jadey]

Sorry, I didn't read the whole thread, but your error is defo listed in there

BlackBerryForums.com : Your Number One BlackBerry Community - View Single Post - Strange error since 4.1.6 on one BES

[hitty]

Originally Posted by Jadey

Sorry, I didn't read the whole thread, but your error is defo listed in there

BlackBerryForums.com : Your Number One BlackBerry Community - View Single Post - Strange error since 4.1.6 on one BES

Thanks for your efforts Jadey.
My error is: [DIAG] Error during writing the debug file
The error in the above post is : [DIAG] Error telling the debug trace file position

[Jadey]

Yes, sorry, I just checked the {diag} and Permission denied (error : 13)

My bad.

[dougb]

We have a similar configuration (2 BES in the same domain with external SQL Server) and have just upgraded both servers to 4.1.6 MR3. The morning after the upgrade, one of the BES servers is reporting exactly the saem problem which goes away after a reboot, only to re-appear again the next morning.

The only slight difference with us is that our controller log files are not unusually big so that clearly isn't the issue here.

So the real problem clearly hasn't been fixed by MR1.

Has anyone else got any news, or ideas on this one? We are not keen on the idea of having to turn off BESAlert.

Thanks,

DougB

[hitty]

Check all your Service logons.

I found on mine that the Database consistency service was enabled and
Router service was logging on as Local service.

After disabling Database Consistency and correcting the Router service logon to BESAdmin, the error has gone.

Havent seen the error for over a week now.

[hitty]

Damn, just popped up again overnight.
Not appearing twice daily anymore.
My Controller and Dispatcher logs are also tiny.