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?).
When the namespace has a full path, i.e. Namespaces\NewWikiSpace, the creation works correctly, witht he directory and files properly created and the update to flexwiki.config contains correct information about the change, despite the error. When the namespace does not have the full path, i.e. it depends upon the program to provide the path information, it appears to create the namespace about 50% of the time - this may be time related to various keypresses. When the namespace is created the directory created is in the FlexWiki directory, just as the Namespaces directory is, rather than in the Namespaces directory. I have tried some different IIS process configurations, using medium isolation and high isolation. I did not try low as I doubt anyone would want to use that setting unless absolutely forced to. I also ran FileMon (from Microsoft via SysInternals acquisition) and it showed frequent access of the config files by aspnet_wp.exe as one would expect (checking these files every 60 seconds or so to see if the application needs to be restarted due to a configuration file change. I could see the access by the program when needed to read the files and write to them. this was also by the aspnet_wp.exe process. When the file was changed then the framework used the files to rebuild the application. The only strange process that also touched the config files was a svchost.exe running netsvcs?? This is the only WinXP 32 bit computer I have. I would recommend having someone else try to replicate the errors I am seeing, or hopefully telling me that my configuration is screwy and they do not see the errors. Perhaps it is some setting from my development environment (it _should_ not be impacting as I am not invoking the Visual Studio prior to any error, but....). I hope this gives you some clue as to what is going on. The behaviour with the specification of the path makes the system usable, despite the minor error. John Davidson On 4/17/07, Craig Andera <[EMAIL PROTECTED]> wrote: > > I have been running Windows XP 32bit for testing, but I do have Avast > > anti-virus and Windows Defender. I can try again this evening. > > As the only FlexWiki process that touches that file is the ASP.NET worker > process, I suspect that one of the antivirus processes is the culprit. I'll > wait to hear what you find out. > > Hopefully you won't be annoyed by me stating the obvious, but if you do > switch them both off and find that that fixes the problem, please switch > them back on one at a time so we can figure out which it is. > > I do have a workaround strategy we can try if we can verify that this is the > problem. > > ------------------------------------------------------------------------- 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
