[1492] No compatible agents

After I upgraded from build 1480 to build 1492, I couldn't run my sln2005
configuration, as the server says that there are 'No compatible agents'.

Any idea why?

Regards,
Pablo

--

--

A wise person makes his own decisions, a weak one obeys public opinion.
-- Chinese proverb

Pablo Montilla
www.odyssey.com.uy

0
3 comments
Avatar
Permanently deleted user

Hello Pablo,

Please, check if system.DotNetFramework2.0 property is defined in you agents
properties file
(\bin\buildAgent.properties) system.DotNetFramework1.1 and system.DotNetFramework2.0 are .NET Framework availability markers on agent computer. -- Eugene Petrenko JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!" PM> After I upgraded from build 1480 to build 1492, I couldn't run my PM> sln2005 configuration, as the server says that there are 'No PM> compatible agents'. PM> PM> Any idea why? PM> PM> Regards, PM> Pablo PM> A wise person makes his own decisions, a weak one obeys public PM> opinion. PM> -- Chinese proverb PM> Pablo Montilla PM>]]> www.odyssey.com.uy


0
Avatar
Permanently deleted user

On Fri, 28 Jul 2006 07:32:39 -0300, Eugene Petrenko
<eugene.petrenko@jetbrains.com> wrote:

Hello Pablo,

>

Please, check if system.DotNetFramework2.0 property is defined in you
agents properties file (<agent install path>\bin\buildAgent.properties)

>

system.DotNetFramework1.1
and
system.DotNetFramework2.0

>

are .NET Framework availability markers on agent computer.

>
That did the trick.

You should probably include that property in the default installation.

Regards,
Pablo

--

No special reason, just government policy.

Pablo Montilla
www.odyssey.com.uy

0
Avatar
Permanently deleted user

Hello Pablo,

Thank you.
We have an issue to make agent discover available .NET Frameworks automaticly
and set up
those properties implicitly.

--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

PM> On Fri, 28 Jul 2006 07:32:39 -0300, Eugene Petrenko
PM> wrote: PM> >> Hello Pablo, >> >> Please, check if system.DotNetFramework2.0 property is defined in you >> agents properties file (> path>\bin\buildAgent.properties) >> >> system.DotNetFramework1.1 >> and >> system.DotNetFramework2.0 >> are .NET Framework availability markers on agent computer. >> PM> That did the trick. PM> PM> You should probably include that property in the default PM> installation. PM> PM> Regards, PM> Pablo PM> -- PM> PM> No special reason, just government policy. PM> PM> Pablo Montilla PM>]]> www.odyssey.com.uy


0

Please sign in to leave a comment.