Xml file because it is being used by another process

CreateElement "ProductFeed" ; topElm. SetAttribute "version", "1. SetAttribute "timestamp", System. Replace " ", ":" ; xProducts. AddRange DB. CreateNode XmlNodeType. Text, "ProductTitle", null ; elmValue. ToString ; elmAttr.

AppendChild elmValue ; subElm. Text, "Price", null ; elmValue. Replace ",", ". Text, "Category", null ; elmValue. Text, "ProductDescription", null ; elmValue. AppendChild elmAttr ; topElm. WriteStartDocument ; xProducts.

Save textWriter ; textWriter. WriteEndDocument ; textWriter. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked Related 3. Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled.

Accept all cookies Customize settings. You need to dispose your XmlTextWriter, either explicitly: writer. Thanks for the quick answer, unfortunately the 'Dispose' method is protected and not to forget the comment provided by Mike "Error 1 'System.

Dispose bool ' is inaccessible due to its protection level Mike, 1 Very unlikely ;- 2 This may be a good hint I will check it, thanks 3 No, the file is just about a few KByte Olli. Mike, 2 was the error cause, thanks a lot. Hello All. Olli: I don't know if this will be of use or not, as I have never tried it the other way, but I always Flush a stream before I close it. Thursday, July 12, AM. Manu Meng Thank you for the update, I understand how to filter event log entries.

I hope the engineering guys come up with something soon. I am planning to install CU10 soon. Looking forward a resolution Thank you, Tom. Friday, July 13, AM. I can also see it happening in my environment, we will need to wait for a fix, if CU10 does not address it future CU's will most likely.

Monday, July 23, AM. CU10 for Exchange does not fix this prd. Sunday, August 26, AM. This by no means is answered or solved. When is Microsoft going to fix this event. It is posting everyday so many times it is filling up my event logs on both nodes.

Hard to ignore when your event log is loaded with the same error If we can ignore this error then why is it posted? We need the ability to suppress this event. A registry change would be nice. Hope someone has an answer Thank you Tom. Friday, September 14, AM.

Friday, April 26, AM. CU14 for Exchange does not fix this either Bye Tom. Wednesday, April 8, PM. Servus Community, but meanwhile I have the suspicion that this event will be logged as long as no new version of the killbit. Unfortunately, my logfile does not go back far enough to see if there is an event that logs the successful download: If this were true, we would only have to try to turn off the error message.

Thursday, April 9, AM. For information, this still persists in the latest Exchange version