Databases
StackOverflow2013
Postsdbo
POXml serialization and empty file
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POXml serialization and empty file
    primarykey
    data
    text
    <p>I stomped on some very weird bug which is very hard to reproduce I literally cant reproduce it. We have a window service installed on around 300+ PCs. From time to time config file(xml) that is used by this service become clear (on some of them). Totally clear no xml tags, nothing, 0kb. I have no clue what can cause such problem. No exception is logged in our logs. Even after this config becoming clear it's still running however it's not communicating with our web service. This is the class that is used for xml serialization and deserialization. I can’t find what can be possibly causing such behavior. Of course problem might not be in this particular class. Any suggestions?? Maybe some hints what can cause a file to become clear. When any operation on this file is by using this class.</p> <p>Sorry for my bad English.</p> <pre><code>[XmlRootAttribute("xmlconfig", Namespace = "DSD_Config", IsNullable = false)] public class xmlconfig { [XmlElementAttribute(IsNullable = false)] public string ProgramApteczny { get; set; } public string Server { get; set; } public string Database { get; set; } public string User { get; set; } public string Password { get; set; } public string DSDUser { get; set; } public string DSDPassword { get; set; } public string DSDServerAdres { get; set; } //public static string cofFile = System.Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) + "\\DSD_Agent\\config.xml"; public static string cofFile = Application.StartupPath + "\\config.xml"; public xmlconfig() { } public xmlconfig(string sProgramApteczny, string sServer, string sDatabase, string sUser, string sPassword, string sDSDUser, string sDSDPassword, string sDSDServerAdres) { ProgramApteczny = sProgramApteczny; Server = sServer; Database = sDatabase; User = sUser; Password = sPassword; DSDUser = sDSDUser; DSDPassword = sDSDPassword; DSDServerAdres = sDSDServerAdres; } public static void readXMLConfig(out xmlconfig configFile) { XmlSerializer oSerializer = new XmlSerializer(typeof(xmlconfig)); configFile = new xmlconfig(); try { using (FileStream fs = new FileStream(cofFile, FileMode.Open, FileAccess.Read)) { configFile = (xmlconfig)oSerializer.Deserialize(fs); try { configFile.Password = Encryption.DecryptString(configFile.Password); } catch (Exception) { configFile.Password = configFile.Password; } try { configFile.DSDPassword = Encryption.DecryptString(configFile.DSDPassword); } catch (Exception) { configFile.DSDPassword = configFile.DSDPassword; } } } catch { configFile = null; } } public static void writeXMLConfig(string sProgramApteczny, string sServer, string sDatabase, string sUser, string sPassword, string sDSDUser, string sDSDPassword) { xmlconfig oxmlconfig = new xmlconfig(); readXMLConfig(out oxmlconfig); sPassword = Encryption.EncryptString(sPassword); sDSDPassword = Encryption.EncryptString(sDSDPassword); if (oxmlconfig == null) { oxmlconfig = new xmlconfig(sProgramApteczny, sServer, sDatabase, sUser, sPassword, sDSDUser, sDSDPassword, ""); } else { oxmlconfig.ProgramApteczny = sProgramApteczny; oxmlconfig.Server = sServer; oxmlconfig.Database = sDatabase; oxmlconfig.User = sUser; oxmlconfig.Password = sPassword; oxmlconfig.DSDUser = sDSDUser; oxmlconfig.DSDPassword = sDSDPassword; } XmlSerializer oSerializer = new XmlSerializer(typeof(xmlconfig)); TextWriter oStreamWriter = null; try { oStreamWriter = new StreamWriter(cofFile, false); oSerializer.Serialize(oStreamWriter, oxmlconfig); } catch (Exception oException) { WriteToLog(DateTime.Now, "Aplikacja wygenerowała następujący wyjątek: " + oException.Message); // Console.WriteLine("Aplikacja wygenerowała następujący wyjątek: " + oException.Message); } finally { if (null != oStreamWriter) { oStreamWriter.Close(); } } } public static void writeXMLDSDConfig(string sDSDServerAdres) { xmlconfig oxmlconfig = new xmlconfig(); readXMLConfig(out oxmlconfig); if (oxmlconfig == null) { throw new Exception("Aplikacja wygenerowała następujący wyjątek: Musisz zdefiniować wszystkie parametry"); } else { oxmlconfig.DSDPassword = Encryption.EncryptString(oxmlconfig.DSDPassword); oxmlconfig.Password = Encryption.EncryptString(oxmlconfig.Password); oxmlconfig.DSDServerAdres = sDSDServerAdres; } XmlSerializer oSerializer = new XmlSerializer(typeof(xmlconfig)); TextWriter oStreamWriter = null; try { oStreamWriter = new StreamWriter(cofFile, false); oSerializer.Serialize(oStreamWriter, oxmlconfig); } catch (Exception oException) { throw new Exception("Aplikacja wygenerowała następujący wyjątek: " + oException.Message); } finally { if (null != oStreamWriter) { oStreamWriter.Close(); } } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdsolimano
    1. USGrzesiek
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COHow big is this file? If it isn't huge, and you are having problems, I wonder if you should serialize it to memory first (`MemoryStream`), and then **if successful** write the the contents to disk...
      singulars
      1. POXml serialization and empty file
      1. USMarc Gravell
    2. COMaybe you could run some kind of tool which captures all file accesses to see if you can narrow it down to what is changing it and when? You can use [Process Monitor](http://technet.microsoft.com/en-US/sysinternals/bb896645.aspx) to do this. Other than that I would be suspicious about an exception causing the file content writing to be skipped somewhere.
      singulars
      1. POXml serialization and empty file
      1. USMatthew Watson
    3. CONo it's small 1-2KB tops.
      singulars
      1. POXml serialization and empty file
      1. USGrzesiek
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload