ALL,
I'm trying to develop my app on Windows 8.1 with MSVC 2017.
I recently updated it (the original install was couple of years old) and now when I try to run it from the IDE I get an error:
verifier.pdb is not loaded.
What is this and why I didn't get it from the original version?
I presume that this verifier.dll is a good thing and will help me with the development in the long run, but right now it prevents me from debugging my application.
Could someone please help.
TIA!!
P.S.: I'm adding application-verifier tag, but I'm not sure that it is related. I apologize in advance if its not.
EDIT:
That question is related but the answer{s} there does NOT explain how to remove the error I'm seeing.
Moreover the linked question does not see the issue I'm having.
So those 2 - mine and the linked one - are NOT duplicates.
Also, I'd appreciate if the question I'm posting is not closed immediately - post the CONSIDERED dup and give me a time to respond.
On top of that the link referenced in one the comment still doesn't work and the updated one does NOT say how to cancel the specific error I'm seeing.
And finally - the lionked question was talking about debugging the application with the RT.
I am starting the application inside MSVC and so I don't have ANY means to continue running the application, while the presumed OP seems to imply the application was running fine after starting and therefore was able to perform the task semi-successfully.
TIA!!
It is application verifier.
I am guessing this is the original issue - Mysterious verifier.dll
Related
I work in a company that started using VDIs for certain SQAs. We have just noticed that in Microfocus ALM in the VDI only, when anyone tries to print a report through the Document Generator, an error occurs. See first screenshot. If you close this out, it freezes the browser and you have to close. When you try again, you'll get the second error below. In researching these, it seems the first could be caused by a Word incompatibility, which we have checked and ruled out. The second can be caused by files in the path of the TD_80 folder, which we have tried to remove as suggested, but the error persists.
Does anyone know what else might cause this error on the VDIs only?
Details from first error
Details from second error
After submitting a ticket to Micro Focus, they said Report Generator is no longer supported. They pointed us to their documentation on creating reports in the Analysis View module under the Dashboard. This seems to work similarly, but the filtering is a little bit different.
During my process there is a drop-down html element that I have spied and set correctly. I run through the Object and Process studio without any issues. Once the same process is ran through the Control Room the element throws and error that it cannot be found.
I have tried multiple different configurations without any luck and the element is still found without issue when ran manually. I even checked by signing into the VM having it error and on the second retry had the VM up; at this stage the element was found without issue. It seems to only be when the bot is running and the screen is not up. No other elements give this issue and the next step is the same dropdown, but for a stop time not start.
Any help would be appreciated!
I have added pics of the STARTSPIED - START and ENDSPIED - END spied configs,the Navigation Stage, and the process correctly running in the Object Studio OB Studio correct.
Thank you!
For the person who down-voted this item...Configs here are my two days of config changes and research that I tried on my own before asking for help. This is my 5th automation that I have put into deployment without help, so thank you for down-voting someone trying to get help where they are stuck.
Your problem is most likely connected with the fact that processes run in the control room are executed much faster than in studio and your webpage might not be loaded on time (that would explain why it works after retry).
Best practice approach would be to add a dynamic wait stage after attach and use “Parent Document Loaded” option on the element you want to interact with. It will wait for the page to be loaded and then check exist for the element. I would also suggest splitting your action into two, first to set start date and second for end date.
I'm a beginner with this framework and I'm frustrated. I've just about given up on learning Angular2 for now, but can someone please explain to me how I can copy line for line the code in the docs and it still not work?
Earlier on I've seen instances of it calling classes that I've long gotten rid of. I reinstalled everything, upgraded npm to 3.1.0, made sure node is up to date, and tried again. Maybe I shouldn't have taken this unfinished language up when I'm a beginner (no idea how to debug), but I'm speaking of the 'Heroes' tutorial on their site.
The view is supposed to show "Loading..." then get info from the app component. In the beginning, it loads as it should, but then I get to that "Master/Detail" in the tutorial and it all goes to boom boom. Let me show you my code:
Well this is the app component. This code worked at first until I got deeper into the tutorial. I go back to this code, and it doesn't work anymore. What gives? Followed the doc to the 't'
I had to comment out this code because it made the app mysteriously stop working. Stopped when I passed the array in the constant HEROES to the property heroes. Again, this is in the docs.
The index and module files are fine. I've stopped and restarted at least four times and I've about had it. I think I'll just finish learning the regular MEAN stack. Unless someone can come up with a reason why all of this is happening? I see no fault in my code. And even if there was, changing my code or undoing changes should produce results. IT DOESN'T!
I'm thinking it's more to do with the transpiling process, and it not updating TS to JS properly? Which could explain why I was still seeing error messages saying it was trying to call classes I've already gotten rid of.
I'm getting 110 warnings in my build after installing Azure SDK 2.3 that I don't recall seeing before. They are all for the file "Microsoft.WindowsAzure.targets".
An example of one such warning is:
The element 'PropertyGroup' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element 'CloudToolsVersion'.
Has anyone else encountered this problem or know the right way to fix it?
Well, it looks like I just needed to close any open editors for msbuild project files to get those to disappear. Other answers I found suggested on the web were to disable schema validation or to extend the schema myself.
Very scary! From your solution and hints from other similar questions, I think I know what's going on: When any build script file (such as a .props) is open in a text editor, it turns on /validate. This is used to see red wavies in the editor and gives the warnings when the project is loaded by any MSBuild task. The schema holds the various element used by the MS targets infrastructure, and doesn't know anything else. I'm not sure what good that is, but there you have it.
I posted a few threads the other day on the Watir General Google Group, one of which detailed my difficulty using set_no_wait on a validated text field (link below); and was asked by Jarmo Pertman whether it was in a frame. It is, and this concerns me a little; as sadly the site I'm testing is heavily frame-centric, with no immediate plans to modernise.
I recently migrated from an ageing Ruby1.8.6/Watir1.6.2 test environment to Ruby1.8.7-334/Watir2.0.1, and am now noticing more methods that are no longer working for me in frames. For instance, click_no_wait on a button that presents a new window works perfectly fine in my old environment, but not in my new one.
This is a question to the Watir developer group. Are no_wait methods known to be failing in frames in Watuir 2.0.1? If so, are they being addressed? If they're not, then I'll be forced to revert back to an archiac version of Ruby and Watir. For many reasons, I don't want to do this.
(Environment: Ruby 1.8.7-334. Watir 2.0.1. XP Pro. IE8)
http://groups.google.com/group/watir-general/browse_thread/thread/85a1a872d1e054dc
from the comments:
Something occured to me last night; I had installed DevKit, which was required to get the FastDebugger working in Netbeans 7.0.1. After completely reinstalling Ruby1.8.7/Watir2.0.1 without DevKit, click_no_wait and set_no_wait now seems to be working for me. It means I'll have to use something else other than Netbeans to run my scripts, but at least my scripts work again. (github.com/oneclick/rubyinstaller/wiki/Development-Kit) I hope this info helps someone else. GJHmf – GJHmf Sep 1 at 10:19
(inserting this answer because:
the OP was requested to but had not done so within a months time.
it removes this from the list of 'un-answered' watir related
questions
)