Error TF259096 deploying virtual environments

Question

In Microsoft Test Manager, in the 'Lab Center', on the 'Libary' tab, I was able to create a virtual environment using a template I had created and imported from the HyperV System Center Virtual Machine Manager (SCVMM).

However, when I went to deploy the environment, I got the following error:

Environment message: Type=Error; Message=TF259096: Team Foundation Server has stopped the following operation because of an internal error: Deploy environment. Additional information: Sequence contains no matching element. Try the operation again. If the problem persists, contact your system administrator.;

Does anyone have any ideas on what I might be doing wrong or have configured incorrectly?

Thanks.

Answer 1

Thanks  Glen for reporting the problem.

I need more information  reqarding the above  problem you encountered.

-I am assuming you did following operations a) and b)

a) Create a Stored LabEnvironment (  Library -> new Virtual Environment )

b) Onece the above creation is sucessful .  Click Deploy.

 Did you try to Cancel the above operation ? Generally above (Message=TF259096:) message is seen when Lab Operation is being aborted.

 

 

 

Answer 2

Yes... In 'Lab Center', I went to the 'Library' section and then on the 'Environments' tab I:

a) successfully created a stored lab environment
b) right clicked on the environment and clicked 'Deploy'. On the 'Deploy evironment' confirmation window, I clicked 'Deploy environment'. I did NOT try to cancel the operation.

I was then taken to the 'Lab' section where the new environment was listed and the progress bar showed the environment being created. After about 30 seconds, the 'Status' on the new environment changed to 'Create failed' and viewing the error details showed the error described above.

Thanks for looking into this for me... Let me know if I can provide any additional information that might help resolving this.

Answer 3

Hi Glen,

a) What is the  version of TFS ?

 

Answer 4

I'm running on the Team Foundation Server 2010 RC version.

Answer 5

It looks like there seems to be a known bug in RC  which got fixed in RTM

Can you  upgrade to RTM version ?

Answer 6

Hey  I need more information here

a) Were you able to create active LE from Lab Environment page ?

b) Can you try creating active Lab Environment  using differnt lab template ?

b) Is this issue coming for all clones ?

 

Answer 7

I am unfortunately unable to upgrade to the Visual Studio 2010 Ultimate Edition RTM version at this point.

a) I am able to create an 'active' (by 'active', I assume that you mean an environment that can be started, stopped, RDP'ed to, etc) virtual environment using virtual machines already deployed on a host using SCVMM.

b) I am able to import a template from my Hyper-V server library into the Lab Manager library. I am then able to create a virtual environment in the Lab Manager library using the template. However, when I attempt to deploy the library virtual environment, I get the error. I have created multiple environments using different templates and each time I try to deploy them, I get the same error.

c) I am also able to import a virtual machine from my Hyper-V server library into the Lab Manager library. I am then able to create a virtual environment in the Lab Manager library using the virtual machine. However, when I attempt to deploy the library virtual environment, I get the error.

Hope this clarifies my predicament. Thanks again.

Answer 8

- Thanks Glen for letting us know the details.

Let me know if following is working 

a) Can you try  Lab -> New -> New virtual Environment  (  add the machine  use the  same Lab templte you used to create environment in library tab ) ?

 I need more info to  get to the root cause : Enable Soap logs and try the  clone opertion again . please send us the file generated C:\temp\myListener.log.

-Modity the  mtm.exe.config file . All bold content is newly added  . close MTM.exe and open again and perform the clone operation

  <appSettings>
<add key="LabManagement.EnableSoapTracing" value="true" />
  </appSettings>
  <system.diagnostics>
    <switches>
      <!-- Trace settings for MTR -->
      <!-- Change the value to change the level of tracing you want.
            You must use integral values for "value". 
            0 ==> off,
            1 ==> error,
            2 ==> warn,
            3 ==> info,
            4 ==> verbose.
            Note that each value is inclusive of the last.
        -->
      <add name="UITestTraceLevel" value="4" />
      <add name="EqtTraceLevel" value="4" />
      <add name="LabManagement" value="4" />
    </switches>
    <trace autoflush="true">
      <listeners>
        <add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="C:\temp\myListener.log" />
      </listeners>
    </trace>
  </system.diagnostics>

 

Answer 9

I have the exact same issue, but I am on the RTM version.  I can generate a listener.log  file if you can help.

 

Thanks

 

Answer 10

Please send  me the listener.log . I will take a look and get back to you .

Answer 11

Where do you want me to send it?

Answer 12

JoeyM

- Problem you are seeing because you are using  clustered hosts .  Lab Management does not support clustered hosts in  VSTS 2010 RTM

Work around.

- Create a new host group with non-clustered hosts.

- Try clone and deploy of LabEnvironment  to the above created host group.

 

Please let me know , if you still get the same error message.

 

Answer 13

Joey and Glen: Have you been able to resolve this issue? Was it the clustered hosts?

Vijay

Answer 14

I'm getting this error trying deploy an environment. Running TFS 2010 SP1.

I don't have a clustered host, but I previously did add an additional host (clustered) but removed it after I discovered that it isn't supported.

I have generated a log file as per above instructions that I can send to be reviewed.

-david

Answer 15

David:

 

We noticed this problem with one customer when one of the disk partitions on the host has a name that starts with \\...

Open disk management mmc console and verify whether one of the drives has a volume name that starts with \\

The only way this customer could get rid of the problem was to re-install the OS.

Vijay