Run DLL error popup when testing on a win 8 (NON pro) machine

17 posts, 0 answers
  1. Max
    Max avatar
    17 posts
    Member since:
    May 2012

    Posted 03 Jun 2013 Link to this post

    We have a test suite that runs mostly on Win 7 Pro x64 machines and this works as expected however we also have a Win 8 (NON pro) where, when ever the WPF application is started up, we are getting a "There was a problem starting ArtOfTest.Connector_64.dll The specified module could not be found"

    We are executing with MTM 2010 if that helps.

    Is there a compatibility with Win 8?

    Thanks
  2. Velin Koychev
    Admin
    Velin Koychev avatar
    88 posts

    Posted 04 Jun 2013 Link to this post

    Hi Max,

    I am sorry to hear that you are experiencing this issue.  

    We've only seen that error a few times, and reinstalling Test Studio resolved the issue.
    If reinstalling Test Studio does not help you,  there are a few more things to try:

    • Is the WPF app you're testing 64-bit? Change the Target Platform of its project to 32-bit, rebuild the project, and try recording against it again.
    • Install the Visual C++ Runtime (x64). If this fixes the issue, please let us know so we can pass this issue along to our installer team.
    Looking forward to hearing from you.
    Regards,
    Velin Koychev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  3. Max
    Max avatar
    17 posts
    Member since:
    May 2012

    Posted 05 Jun 2013 Link to this post

    Applologies, I have realsied i posted this in the General Discussion and not the "Telerik Testing Framework" section. I have however tried to install the Runtime (which has a newer version...) and re-install the framework and neither have helped resolve the issue.

    The WPF app we are testing is built as AnyCPU and I have even tried running corflags against the exe to ensure its only running in 32 bit and even though i think i have done that correctly it still shows the error.
  4. Velin Koychev
    Admin
    Velin Koychev avatar
    88 posts

    Posted 06 Jun 2013 Link to this post

    Hi Max,

    I am sorry to hear that this issue still exists.
     

    1) Please check Test Studio's Bin folder and look for the specified DLL file (ArtOfTest.Connector_64). The Bin folder is located here:
    C:\Program Files (x86)\Telerik\Test Studio\Bin
    Is the DLL missing?
    2) Make sure that User Account Control Settings is set to 'Never Notify' and also make sure that your user has administrator privileges.

    I hope this helps.

    Regards,
    Velin Koychev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  5. Max
    Max avatar
    17 posts
    Member since:
    May 2012

    Posted 10 Jun 2013 Link to this post

    dll is there and the user is admin with UAC turned off.

    Any other suggestions?
  6. Velin Koychev
    Admin
    Velin Koychev avatar
    88 posts

    Posted 11 Jun 2013 Link to this post

    Hi Max,

    Can you try working with other sample WPF applications (you can try with one of the Application Samples in MSDN).  Do you experience the same issue with them or it happens only with your application?

    If this issue occurs only with your application, the only way to find a solution for you is to reproduce this issue locally.

    I have shared a dropbox folder and send an invitation to your email address. Would it be possible to upload there your WPF application, or a stripped down version that reproduces this problem?

    Looking forward to hearing from you.

    Regards,
    Velin Koychev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  7. Max
    Max avatar
    17 posts
    Member since:
    May 2012

    Posted 13 Jun 2013 Link to this post

    apologies for taking so long but we have a release of code soon so i am doing this as a background task. I am in the process of trying to get a version of our framework reproducing the issue but I have interestingly found the following from enabling Telerik tracing. You might notice the bit in bold at the end of the log which shows the non 64 bit artoftest.connector.dll well this happened by replacing our start up application using telerik from our testing app to a simple WPF app which is built only for 32 bit so this shows that its not a 32/64 bit issue at least.

    Code to follow when i get a chance.

    [06/13 16:46:08,QTAgent32.exe(7704:14)] First trace message from process 7704: "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\QTAgent32.exe" /agentKey e93804a1-2ab3-4bb0-ab7f-a0d3248f417b /hostProcessId 9524 /hostIpcPortName eqt-48b0c151-f4ce-009f-bfb3-98448549a855
    [06/13 16:46:08,QTAgent32.exe(7704:14)] First trace message from background thread "Agent: adapter run thread for test '_10056CreateANewWorkbook' with id '4c94af81-71b3-4aa7-8e96-e2ef4897ed83'" (managed ID = 14, native ID = 3296).
    [06/13 16:46:08,QTAgent32.exe(7704:14),Framework] Manager.LaunchNewApplication() : Process launched (ID=9760, Path="C:\temp\TestSortedView\TestSortedView.exe", Arguments=" ").
    [06/13 16:46:08,QTAgent32.exe(7704:14),UIAutomation] AutomationExtensions.AddAutomationEventHandler() : Added a(n) WindowPatternIdentifiers.WindowOpenedProperty handler on element System.Windows.Automation.AutomationElement scope Descendants.
    [06/13 16:46:08,QTAgent32.exe(7704:23)] First trace message from pool thread "WaitAsync polling wait worker" (managed ID = 23, native ID = 10792).
    [06/13 16:46:08,QTAgent32.exe(7704:23),Framework] <>c__DisplayClass3f.<WaitForApplicationToConnect>b__39() : WPF HWNDs detected after 10 msec: {1312466}.
    [06/13 16:46:08,QTAgent32.exe(7704:23),Framework] Connector.Start() : Process launched (ID=7004, Path="C:\Windows\SysWOW64\rundll32.exe", Arguments="ArtOfTest.Connector.dll,AttachToWindowEntryPoint 1312466").
  8. Velin Koychev
    Admin
    Velin Koychev avatar
    88 posts

    Posted 18 Jun 2013 Link to this post

    Hello Max,

    Unfortunately I am still not able to reproduce your issue. I tried running tests with Windows 8 64 bit machine, Visual Studio 2010, Telerik.Testing.Framework.2012.2.1420 installed and I had no problems. I tested with this application. Can you try making a simple test with this WPF application, to make sure that your problem is indeed  environment  specific. 

    I would also recommend you to try installing Test Studio Trial version and see if you still experience this issue. 

    I hope this helps.

    Regards,
    Velin Koychev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  9. Max
    Max avatar
    17 posts
    Member since:
    May 2012

    Posted 19 Nov 2013 Link to this post

    Hi,
    This went away for a while but is now back after upgrading to your dev framework 2013.1.1002.0 and TFS 2012 . 

    Do you have the Test Studio Trial version that matches the framework version above so i can try installing it and seeing if it still occurs.

    Thanks
  10. Max
    Max avatar
    17 posts
    Member since:
    May 2012

    Posted 19 Nov 2013 Link to this post

    Just as an update 1st test passes but after that the error occurs on my call to:

     Manager.LaunchNewApplication(Manager.Settings.Wpf.DefaultApplicationPath)

    and the following is in the telerik log at time of this call

    [11/19 14:52:26,QTAgent32.exe(8396:37),Framework] Connector.Start() : Process launched (ID=8536, Path="C:\Windows\SysWOW64\rundll32.exe", Arguments="ArtOfTest.Connector_64.dll,AttachToWindowEntryPoint 1704686").
    [11/19 14:52:31,QTAgent32.exe(8396:37),Error] Connector.Start() : rundll32.exe didn't terminate in the expected timeframe.
    [11/19 14:52:31,QTAgent32.exe(8396:37),Framework] Connector.InjectCode() : ------- Function Start -------
    [11/19 14:52:31,QTAgent32.exe(8396:37),Framework] Connector.InjectCode() : Connection string: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Telerik.TestingFramework.WpfExtension\v4.0_2013.1.1002.0__3fd81c5c4516f739\Telerik.TestingFramework.WpfExtension.dll?Telerik.TestingFramework.WpfExtension.WpfCommunicationEntryPoint?8396
    [11/19 14:52:31,QTAgent32.exe(8396:37),Framework] Connector.InjectCode() : Sending WM_COPYDATA to HWND 1704686 (lpData = "C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Telerik.TestingFramework.WpfExtension\v4.0_2013.1.1002.0__3fd81c5c4516f739\Telerik.TestingFramework.WpfExtension.dll?Telerik.TestingFramework.WpfExtension.WpfCommunicationEntryPoint?8396")...
    [11/19 14:52:31,QTAgent32.exe(8396:37),Framework] Connector.InjectCode() : Returned from sending WM_COPYDATA (LRESULT=0, GetLastError()=ERROR_ALREADY_EXISTS).
    [11/19 14:52:31,QTAgent32.exe(8396:37),Framework] Connector.InjectCode() : ------- Function End -------
  11. Velin Koychev
    Admin
    Velin Koychev avatar
    88 posts

    Posted 21 Nov 2013 Link to this post

    Hello Max,

    I am sorry to hear that this problem is back again.

    In order to help you best we will need some more information:
    1) Did you do something specific the previous time when the issue was resolved?
    2) If I understand you correctly, you again see a message "There was a problem starting ArtOfTest.Connector_64.dll The specified module could not be found"  on your Windows 8 machine?
    3) Can you try to reproduce this issue with our latest internal build 2013.1.1120. You can download it from here.
    4) Could you please send us the full log file and a test file where you reproduce this issue.

    Hope to hear from you soon.

    Regards,
    Velin Koychev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  12. Max
    Max avatar
    17 posts
    Member since:
    May 2012

    Posted 28 Nov 2013 Link to this post

    Hi there,

    In answer to your questions
    1) Did you do something specific the previous time when the issue was resolved? - NO but then the virtual machines have run slowly and as tests were not robust we reduced priority of monitoring the machines to see if it was still happening so my previous comment may not have been true in that it had gone away 
    2) If I understand you correctly, you again see a message "There was a problem starting ArtOfTest.Connector_64.dll The specified module could not be found"  on your Windows 8 machine? Yes, i am getting this as a pop up.
    3) Can you try to reproduce this issue with our latest internal build 2013.1.1120. You can download it from here. Have you actually done anything that will do anything different or are you just hoping? If you have i will try.
    4) Could you please send us the full log file and a test file where you reproduce this issue. Please find attached the log file where the first test does the API call and hence causes the second test to fail with the error. This was reproduced using VS2012 IDE to execute the tests on a Win8 x64

    Please note I have found out the following which is the likely cause...

    I have been able to nail it down a little as to what the cause is but I am afraid that I will not be able to give you our application or test code as it all originates from tests that use one of our APIs of another of our applications which is sensitive. This API feeds the application under test with the data to verify the what is displayed is as expected. Let me however try and explain how it works in the hope you might figure out why all subsequent tests fail because Telerik Test Framework cannot connect to the application under test for the remaining tests in the test run.
    We initialise the API in our test code which, as I am told by the developers, does the following when initiated within the invoking process:
    1. Starts an internal time used for triggering memory flushing – This is never closed down
    2. Initialises static factories used for dependency injection – These are never closed down
    3. Initialises the service locator for unit tests – This is never closed down
    5. Initialises the session manager class – This is never closed down

    I understand these cannot currently change but what it suggests to me that when we use MTM 2012 to run our tests, something in Telerik (we use the same API in CodedUI using MTM 2012 without issue) is still clinging on to the API that was initiated in the previous test and hence why in the following test, when Telerik tries to launch and connect to the application under test which doesn't necessarily use the API, we get the issue we are seeing as telerik framework has not released disposed what's required to enable the next test to initiate.



  13. Velin Koychev
    Admin
    Velin Koychev avatar
    88 posts

    Posted 03 Dec 2013 Link to this post

    Hi Max,

    Thank you for your detailed answers. 

    I am working closely with our developers on your issue. The first thing they want to make sure is that you run Visual Studio as Administrator. The main issues you might have with Windows 8 are related to security restrictions (as you said in your initial reply, you don't experience these issues on Win 7 Pro machines)

    Let me know whether this helps. If not, we will have to go deeper to uncover what is causing these problems. 

    Regards,
    Velin Koychev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  14. Max
    Max avatar
    17 posts
    Member since:
    May 2012

    Posted 03 Dec 2013 Link to this post

    Ok I have ensured I ran VS 2012 as admin and issue is still present. The issue also occurs using TFS 2012 Test agents as well which i think are always ran as admin under the hood.
  15. Velin Koychev
    Admin
    Velin Koychev avatar
    88 posts

    Posted 06 Dec 2013 Link to this post

    Hello Max,

    Thank you for your reply.

    Can you try to reproduce this issue with Visual Studio 2010? Both MTM and Visual Studio 2010 depends on QTAgent, so you should be able to reproduce it with VS 2010 only.
    If you are able to reproduce the same issue with VS 2010 that would mean that MTM is not involved in the problem. 

    Thank you for your cooperation.

    Regards,
    Velin Koychev
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  16. Rory
    Rory avatar
    16 posts
    Member since:
    Jun 2011

    Posted 16 Apr Link to this post

    Installing the VC Runtime helped me when running the test on a Win10 x64 machine with Test Studio 2016.1.330.2 ArtOfTest.Runner.
  17. Boyan Boev
    Admin
    Boyan Boev avatar
    1045 posts

    Posted 20 Apr Link to this post

    Hello Rory,

    Thank you for sharing your knowledge with the community!

    Regards,
    Boyan Boev
    Telerik
     
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
     
Back to Top
  Cast Your Vote at DevPro Connections! Cast Your Vote at  Win IT Pro Connections!