I have a very frustrating problem that we cannot pin down.
I have a small business2003 domain with 10 pc's and 5 macs connected to it. The PC's need to run an ASP.NET application that runs a time sheet and estimates program all the domain users need this to keep track of jobs work flow etc.
The app runs on the server and then there is a client that runs on the PC's.
The app writes the new documents to a shared drive on the file server
This worked fine whilst the PC's were all part of a workgroup but we recently joined them all into the domain.
The application now launches fine and allows the user to look at the jobs etc recorded on the system, however every time the user tries to create a new job it crashes. Creating a new job involves opening a word document and then saving this back to the shared drive.
This now always fails.
If however the user logs off and then logs on again as an administrator the process works fine.
To get round this I have created a small C# 'wrapper' that runs the application as an admin but this is not a good solution.
What could be going on on the domain?
I have allowed anyone to write to the the shared drive in desparation so now there really is no security on the drives.
This is proving to be a big problem and I need to find a better solution than my ugly hack
I realise I am being somewhat vague here but I am rather lost.
Since joining the PC's to a domain the app fails.
The ap only runs as an administrator why?
I am pretty sure it is not network permissions.
This is the fix currently in place but it does not always work
static void Main(string args)
string pw = "password";
string path = "C:\\Program Files\\Cherry\\Cherry.exe";
string user = "administrator";
string dom = "CHERRY";
System.Security.SecureString password = new System.Security.SecureString();
foreach (char c in pw.ToCharArray())
System.Diagnostics.Process.Start(path, user, password, dom);