{"id":7111,"date":"2014-05-22T10:06:10","date_gmt":"2014-05-22T10:06:10","guid":{"rendered":"https:\/\/unknownerror.org\/index.php\/2014\/05\/22\/event-id-629-and-crm-outlook-client-collection-of-common-programming-errors\/"},"modified":"2014-05-22T10:06:10","modified_gmt":"2014-05-22T10:06:10","slug":"event-id-629-and-crm-outlook-client-collection-of-common-programming-errors","status":"publish","type":"post","link":"https:\/\/unknownerror.org\/index.php\/2014\/05\/22\/event-id-629-and-crm-outlook-client-collection-of-common-programming-errors\/","title":{"rendered":"Event ID 629 and CRM Outlook Client-Collection of common programming errors"},"content":{"rendered":"<ul>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn<\/p>\n<p>So after creating a new database and moving all users my Event ID 629&#8217;s are back, at least this time I\u00a0have an idea of the cause. We have a MS CRM\u00a0 V4 server here and our Outlook 2007 users have the CRM Outlook Plugin Installed. Ocasionally when our CRM Admin publishes changes to CRM, it hangs up. The fix for CRM is to do an IISReset. Once this is done CRM is fine. However,\u00a0I noticed my log drive on the Exchange 2010 SP1 server begins to fill rapidly. I then ran EXmon to see who was hitting the server. I find one user who has two sessons, one for Outlook, one for the CRM client Plugin. I end task his Outlook.exe and the log growth stops. Of course this was after it dropped 5GB of junk into the database. The next day I start getting the 629&#8217;s in my app log. Anyone know what the CRM client is dropping in the database that can cause logs to grow that fast? I have no idea. I cant keep moving users to a new database every time this happens. What are Unversioned Deletes? Is there some retension period\u00a0I can change to purge these? Or is there some way to determine what user they are associated with so\u00a0I can delete the account. I am desperate for an answer here.<\/p>\n<p>Thanks!<\/p>\n<\/li>\n<li>\n<h3>18 Answers<\/h3>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn1<\/p>\n<p>Well, we opened a case with MS Tech support as well. Here is what he said. Basically there is a bug in CRM\/ CRM Outlook Client calendaring that will query forever, essentially in a loop which generates the massive amounts of transaction logs. He said that CRM Rollup 17 due out in May will address this issue. Until then we are making sure that when our CRM Admin published changes\u00a0we are monitoring Exchange closely. Not the best answer but untill Rollup 17 is installed\u00a0I guess it will have to do.<\/p>\n<p>Our setup is the following:<\/p>\n<p>Exchange 2010 SP1 HF1 on Server 2008 R2<\/p>\n<p>Clients are Outlook 2007, CRM 4, Outlook plugin\u00a0version 4 Rollup 13<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn2<\/p>\n<p>Do you mean event id 623 or 629? 623&#8217;s indicate you are experiencing log stalls and your version store is getting backed up. Third party tools\u00a0and clients can do this causing looping action and generating the massive logs.\u00a0I don&#8217;t have experience with CRM plug in, but I would at least try to uninstall it from these two clients if it&#8217;s always occuring with them and reinstall it.<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn3<\/p>\n<p>Definite 629. Source ESE\u00a0 Warning, Category: Performance<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn4<\/p>\n<p><strong>Quote<\/strong>: \u201cThe database may benefit from widening the online maintenance window during off-peak hours in order to purge such nodes and reclaim their space. If this message persists, offline defragmentation may be run to remove all nodes which have been marked for deletion but have yet to be purged from the database\u201d<\/p>\n<p>For the event, please increase the online maintenance window<\/p>\n<p>Maintain Mailbox Databases<\/p>\n<p>James Luo<\/p>\n<p>TechNet Subscriber Support in forum<\/p>\n<p>If you have any feedback on our support, please contact tngfb@microsoft.com \u00a0<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn5<\/p>\n<p>I have already made the maintenance window as big as possible. including all day Sat and Sunday and 8 or more hours each weekday. The last time this happened\u00a0I moved everyone to a new database and it worked until CRM crashed last week. Now that we are in the CRM forum can someone tell me what this might be or where to look?<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn6<\/p>\n<p>I just found our Exch 2010 (no SP) server experiencing exactly the same symptoms as Aszyman, but adjusting the Maintenance Window on the Exchange store was not our fix.\u00a0 Our Database disk drive ran out off space (and records show some 25GB of higher than normal disk growth for the past 2 weeks on a volume that only contains the mailbox database).\u00a0 Then our Exchange logfile volume ran out of space next.\u00a0 After extending both Database and Log volumes in a pinch, the symptoms continued and we could see logfiles getting created 10-20 per minute.\u00a0 Looking back in Explorer at the rest of the day&#8217;s Exchange mailbox store transaction logs, I was seeing up to 3.5GB of logfiles generated per hour\u00a0over the course of a day.\u00a0 After finding this article, I installed the EXmon utility and found one user connected using Outlook and CRM client plugin and putting a heavy load on CPU and generating a large amount of bytes in and out.\u00a0 After killing Outlook on the user&#8217;s PC, the logs immediately stop filling up.\u00a0 Come to find out, the CRM client installed on this user&#8217;s laptop was a much older version while everyone else using the CRM client plugin had a more current version.\u00a0 Unistalled the CRM client from that PC and restarting Outlook produced no more problems on the Exchange Server.\u00a0 Going to let this site for a while before installing the updated CRM client on that user&#8217;s PC.<\/p>\n<p>Not sure about what to do with all the &#8220;junk&#8221; that was dumped into the Database and whether the maintenance will clear it out eventually or an offline defrag would, but am going to just create a new mailbox database today, migrate mailboxes, and purge the original DB store.<\/p>\n<p><\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn7<\/p>\n<p>Well, we opened a case with MS Tech support as well. Here is what he said. Basically there is a bug in CRM\/ CRM Outlook Client calendaring that will query forever, essentially in a loop which generates the massive amounts of transaction logs. He said that CRM Rollup 17 due out in May will address this issue. Until then we are making sure that when our CRM Admin published changes\u00a0we are monitoring Exchange closely. Not the best answer but untill Rollup 17 is installed\u00a0I guess it will have to do.<\/p>\n<p>Our setup is the following:<\/p>\n<p>Exchange 2010 SP1 HF1 on Server 2008 R2<\/p>\n<p>Clients are Outlook 2007, CRM 4, Outlook plugin\u00a0version 4 Rollup 13<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn8<\/p>\n<p>We are having the exact sames issues as listed above&#8230; I am at least glad to see others are having the same issue and MS is aware of it. Any updates on this issue?<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn9<\/p>\n<p>I have just been babysitting the log drive space usage. Some real time trending app for space usage\u00a0would be\u00a0great.\u00a0Our CRM guy lets us know before he publishes so we can watch EXmon. No issues since.\u00a0No patch has been released as far as we have heard. I have already moved all users to a new database so\u00a0I can get rid of that freaking 629 error.<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn10<\/p>\n<p>So it just happens when when the CRM guy publishes the changes? If that is true I can let my CRM guy to give me some heads up before he publishes.<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn11<\/p>\n<p>So far as we have seen it is after a publish, typically when it times out and we do an IISReset to get CRM working again.<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn12<\/p>\n<p>we are having these issues as well has anyone seen a change after applying roll up 17 ?<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn13<\/p>\n<p>Bump. We just installed the rollup on the server here and we are going to start re-installing the Outlook Client today. Fingers crossed. Anyone have any updates?<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn14<\/p>\n<p>the rollup 17 applied to the outlook Plugin stoped the extras from generating also cleared up the sync errors on the users<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn15<\/p>\n<p>I have a simliar issue with garbage getting dumped in to my exchange log folder and making my database grow very large.\u00a0 But we are currently on CRM 2011 and exchange 2010 sp1.\u00a0 All the clients are office 2010 with CRM 2011 client for outlook.\u00a0 When the problem is happening I can watch log files being added\u00a0by 1-4 logs per second or more, having the users close outlook will make the log folder only grow by 1 log every minute or so, which seems like more normal traffic.\u00a0 I have already moved my users to a new database with a total db size of about 30gb after about 1 to 2\u00a0months after the move my database is already 130gb.\u00a0 Does anyone have and answer or update?\u00a0 I beleive that I\u00a0am on all the latest roll updates for exchange and CRM.\u00a0 We did upgrade from CRM 4.0 and were experiencing the same issues when we were on 4.0.\u00a0<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn16<\/p>\n<p>I dont have an answer, the rollup to CRM (v4)\u00a0seemed to make it go away here. In the mean time to protect your Exchange server I would do the following.<\/p>\n<p>Set up an alert of some sort when drive space on the log drive decreases quicker than normal.<\/p>\n<p>Second, use EXmon to see what user is causing it. Once you find that user, kill all Outlook.exe sessions for the user. That will stop the growth from continuing.<\/p>\n<p>Thats what\u00a0I did until the rollup was released.<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn17<\/p>\n<p>I&#8217;m seeing the 629 warnings in my Exchange 2010 RTM\u00a0system as well, and i&#8217;m now wondering if it&#8217;s related to CRM, since we run that as well (I&#8217;m checking on the version\/rollup status). I&#8217;m wondering what everyone here has for their Exchange environment &#8211; do you have all Exchange server roles installed on one box and using the CRM E-mail router?<\/p>\n<p>In my environment, we have 2 combined Hub\/CAS servers and 2 mailbox servers. CRM is on another machine entirely. We had seen the log files on the Hub\/CAS servers increase significantly in size when we installed the CRM router, and eventually changed CRM to NOT use the router in Exchange &#8211; the log files on the CAS servers went back to normal.<\/p>\n<p>But, I&#8217;m still seeing 629 warnings on my mailbox databases. Changing the online maintenance window didn&#8217;t seem to alleviate the problem, so I&#8217;m wondering if it has something to do with our CRM system.<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/i.msdn.microsoft.com\/dn186180.LOGO_Win1211(id-id,MSDN.10).png\" \/><br \/>\nmsdn18<\/p>\n<p>Hi,<\/p>\n<p>the same situation here. We have CRM in our customer environment and on the mailbox server hosting active copy of CRM mailbox database I can see ESE warning 629.<\/p>\n<p>Widening the maintenance window didnt help.<\/p>\n<p>Regards<\/p>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>msdn So after creating a new database and moving all users my Event ID 629&#8217;s are back, at least this time I\u00a0have an idea of the cause. We have a MS CRM\u00a0 V4 server here and our Outlook 2007 users have the CRM Outlook Plugin Installed. Ocasionally when our CRM Admin publishes changes to CRM, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7111","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/7111","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/comments?post=7111"}],"version-history":[{"count":0,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/7111\/revisions"}],"wp:attachment":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/media?parent=7111"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/categories?post=7111"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/tags?post=7111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}