Thursday, May 10, 2007

Calendaring agent failed in message save notification with error 0x80040219

Calendaring agent failed in message save notification with error 0x80040219
Exchange 2003 SP2

I had an error message like the one above show up on the exchange server application log. I never seen this message before and was kind of alarmed at what it could be. The details in the log entry pointed out inconsistency problems with several public folders. The original cause and description of the problem that required me to go to this clients office was they said their Internet access and email (and whole network) was running slowly.

Less than half an hour after the call, I spoke with the customer. They said the problem had go away but would like to know what caused it. I dug into the logs first and saw several errors similar to:

Calendaring agent failed in message save notification with error 0x80040219 on the Exchange 2003 server.

At first it didn't click-in as to why this error would slow down everything including Internet access bu then remembered that this customer had a replica server of the exchange box off-site. That site was connected via a VPN. The error had to do with inconsistencies found in the database. Exchange will normally try to fix inconsistencies and be on its merry way - and it did. In this case however, the public folder calendar that contained the inconsistencies had to be replicated to the the other server. The public folder was large and the transfer slowed Internet access down considerably.

5 comments:

MrTechSupport said...

Error numbers sometimes don't even really help. They can be misleading and sent a tech support person in the wrong direction for information as to the real source of the problem. Sometimes they after at least a clue and other times the software error codes actually are right and help for troubleshooting.

Anonymous said...

Calendar usage in exchnage has always been burdened with bugs and problems. Microsft has done a great job in improving the software over the years. I like what they've done with the software in Exchange 2007. It too however will have service packs after service packs before it's realy stable. There are some great software and feature enhancements though and worth taking a look at.

MS Support said...

Although Exchange 2003 on server 2003 was advanced in many ways over previous version of Microsoft Exchange, it will had many shortcomings. Those included calendaring and the web based client of OWA.

grearadams-g said...

The development of OWA (Outlook Web App) has advanced tremendously. OWA in Exchange 2003 was actually a useful working tool. It could not however complete with the full desktop installation client of Outlook. OWA in 2013 Exchange is the most advanced Outlook Web access application for Exchange email. It can almost compete with the full desktop installation at least in many of the core functionality categories. The calendering in Exchange has improved exponentially as well. Not only in the web based application but also in the full desktop installation of the client. The web based user interface uses the latest technologies for HTML, CSS, and back-end web based scripting.

gtech said...

Many applications that have a web based version and a full desktop version or implementation often compete with them selves. The web based application will always be lagging ins functionality and features to their full installation desktop counterparts. The core features of a web based application needed to be the object and focus. Although web based applications do provide faster access to the software and inherently provider more distant and remote access to applications, because of their reliance on a browser does make them vulnerable to issues that are not necessarily caused by the software. Browser based web based application such as those for accessing corporate resources as in the case of email tend to be used general by average computers users. Unlike applications at are more typically used by support professionals themselves. Such is the case with web based desktop support software. Web based desktop support software for online remote computer assistance is such software that competes with a full desktop deployment and installation. Web based applications for providing online computer remote control over the Internet unlike other web based applications have to be developed with the important division of average user and technical support user. 4RemoteSupport web based desktop support software offers opportunity for technical support agents to remotely access computers on the web. Through the web support is a necessity and no longer an obstacle. The advancement in web based technologies has increased the capabilities and functionality of web based support software as well as other user front-end applications. Unlike other web based or desktop apps, remote assistance screen-sharing software has the dividing line as mentioned. Because the whole goal and focus of the software is to connect a computer desktop user with technical support, one end is a regular average user and the other end of the connection is a more technically proficient user. A basic common feature of web based desktop remote support software is the remote computer control. Remote computer access and control is required for the software to be successful. There are some web based and online applications that enable the option of viewing only and with approval from the remote user by request full desktop screen-sharing remote control can be enabled. Online support software in the form of web based desktop support allows remote control access of desktop computers and servers through the web. Computer support through the we bis vital to any information technology department and more so to organizations that provide managed IT support such as managed services. Others include those that provide a hosted servers in which case they may need to correct or repair software which interacts with the web and servers on the web.