Hi In the 'Log on' tab First check the 'Local System account' check the 'allow interaction with desktop'
next check 'This Account' and fill in user and password the check 'allow service to interact with desktop' stays checked. Hope this helps ... with kind regards Ruben Willems On Sat, Oct 18, 2008 at 8:43 AM, UnKnoWn <[EMAIL PROTECTED]> wrote: > > Hey , > The problem was indeed our i was using Windows Server 2003 and after > through allot of research and tests it seems that the interactive > desktop dosent work with later versions of windows (windows server > 2003,vista ...). > > So now im using windows xp and now outlook does start up after > checking the interactive desktop option but throws an error > saying"Microsoft Outlook has encountered some errors and needs to > close " but the outlook does open up as another "outlook.exe" process > but my tests dont run.All the processes are created under "SYSTEM" > Do u have any suggestion i can try ? > Also u mentioned that "change the ccnet service from running as > system to running as a user and allow it to interact with the > desktop. ". As far as i know only LOCAL SYSTEM ACCOUNT has that use > interactive desktop option.Can you tell me how did you set another > user to have that interact with desktop? > > Thanks > > On Oct 14, 2:34 am, "James Prolizo" <[EMAIL PROTECTED]> wrote: > > Other thing I had to do in this situation was change the ccnet service > from > > running as system to running as a user and allow it to interact with the > > desktop. that fixed all my NUnit GUI tests.. > > > > Hope this helps. > > > > On Mon, Oct 13, 2008 at 8:05 AM, Phil Sayers <[EMAIL PROTECTED]> wrote: > > > > > If Outlook has never been started by the user account under which the > ccnet > > > service is running, then i'd wager a 6-pack that the UI is stuck at the > > > "first run" dialog for username & initials, or even some mailbox setup > > > wizard prompt. > > > > > The way around this is... > > > > > login to the server as with the same user account that is running the > ccnet > > > service. > > > Manually start outlook and click through thost first-run prompts. Then > > > close outlook. > > > Re-run outlook again and make sure you get zero user dialogs/prompts, > if > > > you > > > get dialogs, make whatever changes you need to so you no longer get > them > > > when outlook starts. > > > log off. > > > > > force a build through ccnet. > > > The outlook process should start & finish normally, but it will still > be > > > non-visible. > > > > > -----Original Message----- > > > From: [email protected] [mailto:[email protected] > ]On > > > Behalf Of UnKnoWn > > > Sent: Monday, October 13, 2008 6:11 AM > > > To: ccnet-user > > > Subject: [ccnet-user] Re: Problem with CCnet Service and UI Automation > > > > > Hey Rubin, > > > > > We are using the Windows Server 2003 (Standard 64 BIT Edition) . No we > > > havent started an instance of outlook manually.The UI test will start > > > the outlook instance ,clicks some buttons ,asserts for the presence of > > > some windows and exits outlook which closes the outlook process. > > > > > When we run this same test when the ccnet console is running the tests > > > run properly and the each test open and instance of outlook. > > > > > Now when the same is run when the ccnet service is running a process > > > "OUTLOOK *32 .exe " is seen in the task manager but the outlook GUI is > > > not seen and the tests fail and we have to manually kill the outlook > > > process after that. > > > > > Ive even tried creating a custom windows service that starts the > > > ccnet console but the same problem happens as mentioned above. > > > > > Even enabling the the interact with desktop option does not help. > > > > > Is there any other way of getting the outlook GUI to load using the > > > ccnet service ? and any other suggestions that I could try ? > > > > > Thanks > > > > > Ruben Willems wrote: > > > > Hi > > > > > > have you started outlook on that machine already? > > > > Maybe it is asking for a confirmation or something. > > > > Like a mailbox setting or whatever. > > > > > > wiht kind regards > > > > Ruben Willems > > > > > > On Mon, Oct 13, 2008 at 9:59 AM, UnKnoWn <[EMAIL PROTECTED]> > wrote: > > > > > > > Hi Ruben, > > > > > I did try tht and the same thing happened ,the GUI of outlook does > not > > > > > get loaded.(process shows up in task manager but) > > > > > > > On Oct 13, 12:30 pm, "Ruben Willems" <[EMAIL PROTECTED]> > wrote: > > > > > > Hi > > > > > > > > You can try to set the the ccnet service to allow interaction > with > > > the > > > > > > desktop. > > > > > > It's a check box in the log on tab of the ccnet service. > > > > > > > > Hope this helps ... > > > > > > > > with kind regards > > > > > > Ruben Willems > > > > > > > > On Mon, Oct 13, 2008 at 6:25 AM, UnKnoWn <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > > Hi, > > > > > > > There is a problem I am facing trying to integrate my UI > Automation > > > > > > > tests with cruise control. > > > > > > > > > The tests basically opens an instance of outlook and runs a > couple > > > of > > > > > > > tests ( eg:searches for specific windows,clicks buttons > etc).The > > > tests > > > > > > > are run using NUnit.Now I have integrated these tests in the > cruise > > > > > > > control. > > > > > > > > > The problem faced here is that when the cruise control is > running > > > > > > > through ccnet windows service and I run my tests no GUI of > outlook > > > > > > > opens ,only a process is seen in the tasks manager .Hence since > the > > > > > > > tests looks for various outlook windows and forms it fails. > > > > > > > > > Now if I run the same tests when cruise control is running > through > > > > > > > ccnet console.exe the tests run perfectly and even the outlook > GUI > > > > > > > opens without any problem on the server. > > > > > > > > > I would like to know that, is there a way to run the UI > Automation > > > > > > > tests when cruise control is running through the ccnet windows > > > > > > > service?? > > > > > > > > > Awaiting for a reply > > > > > > > > > Thanks.- Hide quoted text - > > > > > > > > - Show quoted text - >
