<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Wow - that is a lovely error! in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Error-in-spying-operation/m-p/44435#M903</link>
    <description>Wow - that is a lovely error!  Are you running Application in the correct Mode?  It might be worth playing around with the internal/external 32bit/64bit settings in the App Model wizard to see if that can fix it.

If not, than I think your next point of call is the Blue Prism support team.</description>
    <pubDate>Thu, 10 Mar 2016 20:50:00 GMT</pubDate>
    <dc:creator>Denis__Dennehy</dc:creator>
    <dc:date>2016-03-10T20:50:00Z</dc:date>
    <item>
      <title>Error in spying operation</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Error-in-spying-operation/m-p/44434#M902</link>
      <description>Hi,

When I am trying to highlight the spied items (using Win32 mode), I am getting an error as follows:
"There is a problem in Spying operation."
Detailed error is:
"System.ApplicationException: The window spied was not found in the model at BluePrism.AMI.clsAMI.Spy(clsElementTypeInfo&amp;amp; elementType, List`1&amp;amp; identifiers) at Automate.frmIntegrationAssistant.HandleSpyOrLaunchClick(Object sender, EventArgs e)"

Has anyone else encountered this error and knows how to get rid of it?</description>
      <pubDate>Thu, 10 Mar 2016 15:48:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Error-in-spying-operation/m-p/44434#M902</guid>
      <dc:creator>hemant_chawla</dc:creator>
      <dc:date>2016-03-10T15:48:00Z</dc:date>
    </item>
    <item>
      <title>Wow - that is a lovely error!</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Error-in-spying-operation/m-p/44435#M903</link>
      <description>Wow - that is a lovely error!  Are you running Application in the correct Mode?  It might be worth playing around with the internal/external 32bit/64bit settings in the App Model wizard to see if that can fix it.

If not, than I think your next point of call is the Blue Prism support team.</description>
      <pubDate>Thu, 10 Mar 2016 20:50:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Error-in-spying-operation/m-p/44435#M903</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2016-03-10T20:50:00Z</dc:date>
    </item>
    <item>
      <title>When we do it for the first</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Error-in-spying-operation/m-p/44436#M904</link>
      <description>When we do it for the first time, it works all well. As soon as we close the application, open it again, attach it and try to identify it again, it gives the above error. (Without any change in the system configurations)
For solving the issue, we have to close all instances of both BluePrism and application.</description>
      <pubDate>Fri, 11 Mar 2016 13:26:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Error-in-spying-operation/m-p/44436#M904</guid>
      <dc:creator>hemant_chawla</dc:creator>
      <dc:date>2016-03-11T13:26:00Z</dc:date>
    </item>
  </channel>
</rss>

