Right i found the problem in the end. Our wonderfull system admins moved our san disks over the weekend and adjusted some of the permissions.
There was a couple of factors here at play it seems. 1. our service account user was changed so that it no longer had domain users membership. 2. the cluster server that we use was changed to look at new san disks. 3. general security persmission of the disks where tweaked... (and not in a nice way) The really annoying thing is that the auditing was changed to not show access error to the disk so looking at the window security was pointless logs. I have submitted a patch on the devel group for the service project that does a bit more logging. Cedric On May 5, 8:56 am, Cedric <[email protected]> wrote: > Working on that theory i used a local admin account, a domain admin > account and my own account (domain admin) an i still get the same > error. I also tryed a release build with no success. > > Help... Production is broken :( > > On May 4, 7:19 pm, Ruben Willems <[email protected]> wrote: > > > > > Hi > > > I got a clue, but do not like it :-( > > > there are Debug.Writline statements in the code, > > but these should not pose poblems. > > > Now I recall that someone from the user/dev list mentioned this : > > the DEBUG constant being used in a release. > > > So we'll have to digg into the build file. > > > now the problem is likely due to security settings, if the problem goes > > away when you run the service as the same user > > as you run the console with, the problem should go away. > > > with kind regards > > Ruben Willems > > > On Tue, May 4, 2010 at 6:00 PM, Cedric > > <[email protected]>wrote: > > > > Chaps, > > > > A different issue for you to think about. After having changed the > > > port number of CCNet and configured the projects correctly. I get an > > > error when i start the service. > > > > here is the event log entry > > > An unhandled exception > > > ('System.Configuration.ConfigurationErrorsException') occurred in > > > ccservice.exe [1000]. Just-In-Time debugging this exception failed > > > with the following error: Debugger could not be started because no > > > user is logged on. > > > > Check the documentation index for 'Just-in-time debugging, errors' for > > > more information. > > > > For more information, see Help and Support Center at > > > > But if i run the console app then all is well. > > > > Any clues? > > > > Cedric- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
