thanks, I'll just run it in a console for now and yeah I deal with the "windows" limitations everyday :)
On Aug 27, 12:56 am, "David Cameron" <[EMAIL PROTECTED]> wrote: > Sorry, SCMguy I don't have any more suggestions. > > The issue of interacting with the desktop is pretty fundamental to the > way Windows works. There are really no workarounds. The only ways I > know of getting a desktop are actually logging in and running things > through the console, or the "interact with desktop" option. > Importantly, "interact with desktop" still requires someone to be > logged in for the desktop to exist. So, there is no way to have a > desktop without having someone logged in to the machine. > > Windows just wasn't designed to be used in a scripted, server kind of > way, and it shows through at moments like this. You could run cc.net > on a backroom server that you access through Remote Desktop > Connection, but again, you will need to leave some account logged in > to the server. > > I hope you can be successful running it through the console. > > Dave > > > > On Wed, Aug 27, 2008 at 7:34 AM, SCMguy <[EMAIL PROTECTED]> wrote: > > > Thanks for the response, so I tried what you are saying and yes you > > were right if I run through a shell it just works because it can use > > the "desktop". So one issue about the option of "Allow service to > > interact with desktop", its only available if you login using a "local > > system" account. I am using the option "This account:" which doesn't > > give you the check box "Allow service to interact with desktop".I need > > this service to login using a specific domain user, so that my samba > > mounts can be authenticated without a command that would have to have > > a password in it. For now I can just run it in a console, but if you > > have anymore suggestions that would be great. > > > On Aug 24, 5:16 am, "David Cameron" <[EMAIL PROTECTED]> wrote: > >> Hi > > >> On Tue, Aug 19, 2008 at 7:48 AM, SCMguy <[EMAIL PROTECTED]> wrote: > > >> > Anyone know if there is a known issue with CC handling "pop up" > >> > windows within a certain project. > > >> Pop ups often cause problems. Are you running CCNet as a service? That > >> could be the problem, and as a first troubleshooting step, I would > >> suggest trying your project with the console version of the server. > >> You can run the console version by shutting down the service, opening > >> up a command window, and running ccnet.exe from your CCNet install > >> folder. > > >> When run as a service, CCNet has no desktop access, at least by > >> default. As a result, windows have no where to display and depending > >> how InstallShield is implemented it might just hang there. When run in > >> a console window, ccnet.exe will have access to the desktop and you > >> should see the window flash by, as you would when running the nant > >> task alone. > > >> If the task runs okay from the ccnet.exe console program, you have a > >> couple options. You could continue to use ccnet.exe, I do this all the > >> time so I can have browser-based acceptance tests in my build. Or, you > >> could try checking the "Allow service to interact with desktop" option > >> on the Log On tab of the service's properties dialog. > > >> Let me know if either of those resolve your problem, > >> Dave- Hide quoted text - > > - Show quoted text -
