More problems with CruiseControl and Vault

ian_sg · Post by **ian_sg** » Thu Jun 01, 2006 8:30 am

Any chance there's some firewall software on this machine that might be behaving differently for the service process than it does for ccnet.exe? For example, did the Windows firewall give you a pop-up asking to unblock ccnet.exe the first time you ran it?

TimK · Post by **TimK** » Thu Jun 01, 2006 9:48 am

No firewall or anything like that.

I have a local copy of vault server installed and the errors are exactly the same which seem to suggest there is something wrong with the service?

TimK · Post by **TimK** » Thu Jun 01, 2006 9:58 am

If I connect as a Local System Account and check the box "allow service to interact with desktop" it works

If I uncheck the box it does not work.

ian_sg · Post by **ian_sg** » Thu Jun 01, 2006 10:24 am

Can you remove the proxy settings and see if that makes a difference?

TimK · Post by **TimK** » Thu Jun 01, 2006 10:29 am

No diff.

ian_sg · Post by **ian_sg** » Thu Jun 01, 2006 12:48 pm

I see you've taken it to the mailing list, which is probably a good next step. My next guess at this point is that it's a bug in one of the latest CC.NET builds. I can tell you that we've never used the system account (with or without desktop interaction) turned on, but we're on an older build.

I'll upgrade us to a newer build, but it probably won't be for a couple of weeks, as we can't afford to break the build server before TechEd.

ian_sg · Post by **ian_sg** » Thu Jun 01, 2006 1:23 pm

Another thing to try: can you add your windows user the Administrators group on that machine, and see if that makes a difference? (Or use another local admin account, if you have access to one.) Vault itself doesn't require this, but CC.NET (and in particular on of the latest builds) might. In any case, it will narrow the field of possible issues a bit more.

TimK · Post by **TimK** » Thu Jun 01, 2006 2:20 pm

My login details are already in the admins group and I'm connecting to my local Vault server but still no luck.

This is driving me nuts

ian_sg · Post by **ian_sg** » Thu Jun 01, 2006 2:53 pm

I'm also somewhat at a loss, at this point. Another idea that probably doesn't matter, but is worth trying as I'm out of other ideas: create a local administrator user (local to the CC.NET machine) and set the service to log in as that user. Perhaps there's some domain security policy that's screwing things up.

TimK · Post by **TimK** » Thu Jun 01, 2006 3:10 pm

OK, downloaded latest build (1.1.0.2370) - no diff

Created user Tim with full admin and added to allow log on locally in Local Security Policy - no diff

It must be an error in CCNet but surely other people would have experience it.

TimK · Post by **TimK** » Fri Jun 02, 2006 5:59 am

Ian, any insperation over night?

ian_sg · Post by **ian_sg** » Fri Jun 02, 2006 7:34 am

I'm afraid not. Do you have access to another machine (or a virtual machine) where you could install CC.NET and see if the same thing occurs?

TimK · Post by **TimK** » Sat Jun 03, 2006 3:57 am

Tried this on my server (previously tried on my WinXP laptop) and it worked great.

So is this an XP thing or my laptop config?
Any ideas?

ian_sg · Post by **ian_sg** » Mon Jun 05, 2006 8:31 am

There's nothing XP-specific that I'm aware of, other than making sure the Windows firewall allows the traffic, which we already looked at. Our CC.NET server here runs on XP Pro with no issues.

Dhominator · Post by **Dhominator** » Wed Jun 07, 2006 3:33 pm

disclaimer: i'm late in this thread and only skimmed it

I have a vague recollection of a similar problem I had when I first setup ccnet/sourcecontrol block. Think the [build] user had inherited the proxy setting. Removing the proxy got ccnet/vault.exe talking to vault. Just a thought.

/jhd