> > There definitely appears to be a bug in WinXP 32bit version. I have > > all patches and service packs applied. I have shut down anti-virus > and > > windows defender. The error still appears on every attempt to create > a > > new Namespace. Occassionally there is a second error where the second > > error has no additional detail beyond the IOException class > > information (has it bubbled up the stack and lost relevant > > information?).
OK, I figured it out. The error message is misleading - it's actually the ASP.NET worker process itself that has the lock on the file. What's happening is that as we start to write the config file out, the FileSystemWatcher I have set up to watch for changes wakes up and tries to read the file...while it's still being written. It's locked, so this results in an error. Unfortunately an error that says some other process owns the file. The reason I wasn't seeing this is that my machine is faster or slower than yours, and it's a race condition. It's actually a good thing you saw it as often as you did. I'll get this fixed in a jiffy. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
