Getting exceptions errors in web application running on IIS within XP Pro SP2

Have recently upgraded a web server (XP Pro) to XP SP2 and since then I am getting errors in my web application.  I also upgraded the application at the same time (bad idea) so it is hard to pin point the cause.  I routinely set up this application (Maximizer) and have set up this version of it.  This is my first shot on XP SP2.

The application logs in and displays graphics.  When data is called from a SQL server on a separate server, this error shows up, referencing illegal characters in the path:

Server Error in '/MaximizerEmployee' Application.

Illegal characters in path.
Description: An unhandled exception occurred during compilation using the CodeDomProvider 'Microsoft.CSharp.CSharpCodeProvider'. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentException: Illegal characters in path.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace:

[ArgumentException: Illegal characters in path.]
   System.Security.Permissions.FileIOPermission.HasIllegalCharacters(String[] str) +276
   System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList) +88
   System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath) +43
   System.IO.Directory.GetCurrentDirectory() +205
   System.CodeDom.Compiler.CodeCompiler.Compile(CompilerParameters options, String compilerDirectory, String compilerExe, String arguments, String& outputFile, Int32& nativeReturnValue, String trueArgs) +356
   System.CodeDom.Compiler.CodeCompiler.FromFileBatch(CompilerParameters options, String[] fileNames) +548
   System.CodeDom.Compiler.CodeCompiler.FromDomBatch(CompilerParameters options, CodeCompileUnit[] ea) +428
   System.CodeDom.Compiler.CodeCompiler.FromDom(CompilerParameters options, CodeCompileUnit e) +90
   System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromDom(CompilerParameters options, CodeCompileUnit e) +37
   System.Web.Compilation.BaseCompiler.GetCompiledType() +227

Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

My immediate goal is to isolate whether the problem is:

1. Something in the SQL permissions. (not likely, DSN works).
2. Something in file permissions locally.
3. A windows or IIS problem.
4. A problem in my Maximizer app.

Since the app works in the fat client, and works partially in the web client, I am suspicious of SP2 but I am not sure.  Any insights would be appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

From the stack trace is apears that the exception was thrown due to the appearance of an illegal character in a path for which FileIOPermssion was verified.

I would have to say that this is likely an issue in the applciation itself.  It may be that a character that was legal prior to SP2 isn't any longer or perhaps the directory structure is different in some way on this installation.

Dave Dietz

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
wintecgroupAuthor Commented:
After uninstalling XP SP2 my app works fine again.  It is something, not yet determined what, that SP2 disabled.
wintecgroupAuthor Commented:
There may be things the developers can do with the app, but the app ran fine pre-XP SP2.  Removing XP SP2 does fix the problem for now.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.