Hi, I have one windows application which is working fine in XP and Windows7 and if installed the same on the ProgramFiles folder in WindowsServer2008 it is throwing an error message : the configuration section for logging cannot be found in the configuration source enterprise library If i install the same application in any of the user documents folder it is working fine. Hint : I am getting this error when my application is looking for a .config file contains setting for logging. Is there anything specific to ProgramFiles folder in Server2008 environment? Please helpMohan

If your application has been designed for Windows XP, it may or may not work properly in higher operating systems. Unfortunately you have given very sparse information framework to find solution. NSDN or .NET forum are better platforms for placing question like this one. Be more specific about technologies used, error and warning logs, etc. My guess is that this is ASP problem and ASP and IIS forums may be helpful. You need to add configuration file to each part of program http://vspug.com/michael/2009/03/27/tips-amp-tricks-microsoft-enterprise-library-configuration/

Hope fully a compatibility problem and one more I would ask "are you trying to copy paste the installed application files to old computers program files to the new windows server program files " if I understood this correctly then you will never be able to run it until you perform the installation using the source application setup fileshttp://www.virmansec.com/blogs/skhairuddin

Hi, The problem is only on the WindowsServer 2008 environment and also if i installed my software in the location C:\ProgramFiles And the same application is working fine if i installed in the location C:\Users\yughandharak\Application Data\...... and on the same server. Mohan

what is the exact error you have ?Right click the Program Files folder and give full permission to the user exclusively and try it if it doesn't works then you might have to use the process monitor to find the root cause http://technet.microsoft.com/en-us/sysinternals/bb896645 http://www.virmansec.com/blogs/skhairuddin

Hi Syed, Thanks for your reply. I am not trying to copy paste the installed application files. And i am trying to install the application using setup only. If i install the application in the ProgramFiles folder than only i am getting this error and its working fine if i do the same in any other folder. Mohan

Mohan perhaps trivial but I did the same mistake. Are you installing your program with elevated rights (Run As Administrator)? There is second possibility, namely to do an analysis with Process Monitor (Sysinternals). This procedure would reveal the critical steps in program. http://technet.microsoft.com/en-us/sysinternals/bb896645 (I mean both the installation and weorking with it.) I have met with similar problem in programs that does not resolve the space in Program Files. I could not resolve this problem and should create new directory. Use application compatibility toolkit and other "tricks" http://searchwindowsserver.techtarget.com/tip/Avoid-application-compatibility-issues-in-Windows-Server-2008-R2 Give more specific data, if you want reasonable response. Regards Milos

Hi Syed, In my code at a certain point of time my application should read some values from the .config file for Logging purposes and that is the place where i am getting the mentioned errors. 1.The configuration section for Logging cannot be found in the configuration source. 2.The current build operation (build key Build Key[Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.ExceptionPolicyImpl, Logging Policy]) failed: Object reference not set to an instance of an object. (Strategy type ConfiguredObjectStrategy, index 2) My application is not able to locate or read the file if i installed the software in ProgramFiles folder(The application is triggered by Outlook). I have admin rights on this machine please let me know if i need to look into any settings related to security. Mohan

you need to have Administrator access and I strongly recommend using the process monitor to find the root cause http://technet.microsoft.com/en-us/sysinternals/bb896645http://www.virmansec.com/blogs/skhairuddin