M
Martin Christiansen
Hi, everyone. I need a bit help here:
I have written an application for my company. That application runs at my
company's customers as part of a larger solution. Now some customers
complain that the application occasionally crashes and/or refuses to start
up.
Here are som facts about the application:
Applikation type: Windows Forms application.
Language : C#
..NET framework : 2.0
Developed using : VS2005
Runs on : Windows XP Prof machines (at customers). Runs under a
regular user account with administrator rights.
Logfiles returned from the customers show that the problem is due to the
following exception:
"Unable to generate a temporary class (result=1). error CS2001: Source file
'C:\WINDOWS\TEMP\xxtyxecu.0.cs' could not be found error CS2008: No inputs
specified"
Having googled around quite a bit I've learned that the real problem might
relate to insufficient rights on the C:\WINDOWS\TEMP folder, which is used
for generating temporary classes on the run (during serialization or
deserialization of classes to/from XML). This makes perfect perfect sense to
me and matches my stack trace.
But every time Google finds a description of the problem, there is always
some ASP, IIS or WebServices involved, which means that the process
generating and compiling the temporary classes runs under another account
(eg IIS_WPG, ASPUSER or NETWORK account). And that account does not have
sufficient rights on the TEMP-folder. The advice in those cases are always
to add the missing rights on the TEMP-folder for those accounts, and that
solution usually works out.
But in my case, it's different. My application is a plain Windows Forms
application that does not make use of any web services or services on any
other machine whatsoever, and my application runs under a plain user account
with all necessary rights (the account can be verified in Task Manager, and
the necessary rights on the TEMP-folder are usually present for both
adimistrators and ordinary users).
So, I can't figure out how a rights-related issue can suddenly arise,
especially when the application is normally running fine. I can't believe
either, that the customers tamper with folder rights and that way create
problems for themselves.
Does anyone have any idea about what is going on? Any help is very much
appreciated.
Regards, Martin, Denmark.
I have written an application for my company. That application runs at my
company's customers as part of a larger solution. Now some customers
complain that the application occasionally crashes and/or refuses to start
up.
Here are som facts about the application:
Applikation type: Windows Forms application.
Language : C#
..NET framework : 2.0
Developed using : VS2005
Runs on : Windows XP Prof machines (at customers). Runs under a
regular user account with administrator rights.
Logfiles returned from the customers show that the problem is due to the
following exception:
"Unable to generate a temporary class (result=1). error CS2001: Source file
'C:\WINDOWS\TEMP\xxtyxecu.0.cs' could not be found error CS2008: No inputs
specified"
Having googled around quite a bit I've learned that the real problem might
relate to insufficient rights on the C:\WINDOWS\TEMP folder, which is used
for generating temporary classes on the run (during serialization or
deserialization of classes to/from XML). This makes perfect perfect sense to
me and matches my stack trace.
But every time Google finds a description of the problem, there is always
some ASP, IIS or WebServices involved, which means that the process
generating and compiling the temporary classes runs under another account
(eg IIS_WPG, ASPUSER or NETWORK account). And that account does not have
sufficient rights on the TEMP-folder. The advice in those cases are always
to add the missing rights on the TEMP-folder for those accounts, and that
solution usually works out.
But in my case, it's different. My application is a plain Windows Forms
application that does not make use of any web services or services on any
other machine whatsoever, and my application runs under a plain user account
with all necessary rights (the account can be verified in Task Manager, and
the necessary rights on the TEMP-folder are usually present for both
adimistrators and ordinary users).
So, I can't figure out how a rights-related issue can suddenly arise,
especially when the application is normally running fine. I can't believe
either, that the customers tamper with folder rights and that way create
problems for themselves.
Does anyone have any idea about what is going on? Any help is very much
appreciated.
Regards, Martin, Denmark.