I am running a QTP test that has some libraries associated to it. When I run the action and an error is encountered in one of the libraries, the associated library file is opened and the error is displayed. Is there a way to NOT make the associated file open and be displayed in QTP in this case?
Reason: I have the libraries associated to a common server and is accessed from many PCs. So if any one of those PCs encounters an error, the associated library file is locked by that PC and cannot be modified in the main server.
Thanks,
Charan
You can disable error handling, use
on error goto 0
this will disable the error handling and will move on
also the best option would be to handle the error by yourself by using
on error resume next
hope this helps
Related
I have just updated my R to version 3.1.1 on my Mac machine, and since then have started getting this strange message when running analyses.
Persistent UI failed to open file ..../org.R-project.R.savedState/window_2.data: No such file or directory (2)
Where I have written the .... there is the rest of the file directory, but I didn't think it necessary to add in.
There does not appear to be anything specific that sets off this error. I am usually running a number of R windows at once - which are running difference analyses (around 6) and the error appears across all windows at roughly the same time I think, I am not usually watching the analyses tick over.
It doesn't kill the analyses. And I haven't found it causing any problems.
I am just curious what it means, and how I should fix it?
Thanks,
Sam
This is pretty old, but I just ran in to the same problem.
You see this message because R does not have permission to change your ~/Library/Shared Application State directory.
If you want to change it, 1 just navigate to the folder, 2 right click it, and 3 uncheck the lock checkbox or change the permissions to that folder.
I don't mind the R error message because I hate OSX writing all the current application states to that folder.
It has been answered before, but i don't know the way to find the exact solution. I took whole day to find the solution but i entirely stuck with this.
I was worked with my project nicely on day before yesterday. I designed many modules for doing my project further. AS usual i opened and started doing (I didn't get any errors) my project today in visual studio. To execute my old project(coding) once again, i checked in browser, as soon as i did, my face gone too bad :( because of this strange error. Error is,
Compilation Error
Description : An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
*Compiler Error Message:*CS0009: Metadata file 'c:\Windows\Microsoft.NET\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll' could not be opened -- 'Error importing module 'System.EnterpriseServices.Wrapper.dll' of assembly 'c:\Windows\Microsoft.NET\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll' -- An attempt was made to load a program with an incorrect format. '
Source Error:
[No relevant source lines]
I did deleting temporary files in this area : C:\Users\username\AppData\Local\Temp\Temporary ASP.NET Files. But again I'm getting the root folder when am running the project
Any help, would be more and more helpful to me. Thanks in advance.
The error message
An attempt was made to load a program with an incorrect format
means that there is an incompatibility in processor architecture. I think you installed either the 32- or 64-bit version of .NET and try to run your website in the opposite architecture.
You should install both the .NET framework versions, or change your application pool to use the right processor architecture.
We are using the Telerik RadEditor control, specifically for it's ability to render a PDF via the ExportToPDF() method on the control. We find that this works great in our development and test environments but fails as soon as we get to our client's environment. What I mean by fails is that typically when you execute the ExportToPDF() method, a dialog box pops up with the name of the PDF file, it's size, and whether you want to open it or save it. In our client's environment that dialog window appears, but the file size does not appear. If you save the file, it's a blank document. The machines / environments are equal in their setup (IIS 6 on Windows server 2003). The only exception is that our client's machine is in a secure environment with no access to the internet.
We are loading form letters into the control and then creating the PDF once the user clicks a button, so I don't think this is being caused by bad data / invalid characters causing the PDF not to generate.
My questions are: does anyone have experience running the ExportToPDF() command in an environment with no access to the internet? Could this be a permissions issue? I can't seem to find documentation on whether the ExportToPDF() functionality uses a temporary directory to write the PDF out to while it's rendering. It may be as simple as that, but I'm having a hard time researching this issue.
I've also put a try / catch block around the ExportToPDF() method and I know it's not throwing any errors.
We are running an older version of RadEditor - 2009.3.1208 - it runs in a large application with other Telerik tools so upgrading the entire RadControl suite is not trivial (b/c of testing, etc) and is taking some time.
Any suggestions on what to try next / has anyone encountered anything like this with this control?
Thanks for your help in advance!
Richard
I doubt that the export functionality needs an active internet connection. Most likely something in your secured environment is blocking silently the export and it does not simply happen. My recommendation is to check the permissions/processes you have on the user machine and test the same outside of the local environment to compare the results.
A lot of time can pass between the moment a stack trace is generated and the moment the stack trace is thoroughly investigated. During that time, a lot can happen to the file in question, sometimes obscuring the original error. The error might have been fixed in the meantime (overlapping bugs).
Is it possible to get Stacktraces that show the offending file at the time of the error?
Not elegantly, and you normally don't want the user browsing through code that's throwing unexpected exceptions anyway (open door to an attacker).
Usually, what happens in a dev shop is that the user reports an error, stack trace, and the build it occurred on. As a tester, you can grab that build from your archives (you ARE keeping an archive of all supported releases somewhere handy, RIGHT?), install, run, and try to reproduce the error, working with the user to provide additional info as necessary. I've seen very few bugs that couldn't be reproduced EVENTUALLY, even if it required running the program against a backup of the user's production database to do it.
As a developer, you can download that build's source code from your version control repository (you ARE using version control, RIGHT?), and examine the lines in the stack trace to try to discover the problem by inspection, and/or build and run it to reproduce the error. Then, you go back to the latest source version, build, and run the same steps (a UI automation system can help out here), and if you don't get the error, someone else already found and fixed it. If you still get the error, you also got an updated stack trace with lines that match the current build, allowing you to set your breakpoints and step through.
What KeithS said, plus there are ways to capture more helpful state information at the time of the Exception using the Exception.Data property. See http://blog.abodit.com/2010/03/using-exception-data-to-add-additional-information-to-an-exception/
While KeithS' answer as pretty much correct, it can be easier and more elegant than you think. If you can collect a dumpfile (instead of just a stack trace), you can use a Symbol Server and Source Server in combination with your debugger to automatically pull your correct-version code from source control.
For example: if you enable PDB output and source-server integration in MSBuild, and upload the resulting PDBs to a symbol server, Visual Studio can automatically load the correct source control from a TFS or SourceSafe repository based on the information in a minidump.
I'm trying to use EQATEC Profiler to profile my ASP.Net app. I followed the instructions listed here. It worked the first time, but every since then, when I run my app, I don't get a "Profiled app started" message. Then when I click on the "Take snapshot" button, I get the following:
"Taking snapshot ...failed: The remote server returned an error: (404) Not Found."
Why can't it find my app?
If a profiled app encounters errors it will log these to the profiler.log file. By default you will find this in C:\Windows\Temp\EQATECProfilerLogs. Try to see if it holds some clues. You can also try to enable "Full logging" in the app options, which will at least output something to the log.
A profiled app is actually the "server" when talking to the profiler; it is the profiler that connects to the app, not the other way around. In your case it seems that the old app has stopped listening (otherwise the profiler's attempt to connect would simply be served by the old app), but the new app has not (could not?) started listening.
It seems strange, though, so my best suggestion is to examine the log-file. It will e.g. show if the app could not start its control-server and if so, why not.
1) Try rebuilding (in Equatec) your application. Make sure "enable runtime control" is enabled in the application options when you build.
1a) Try changing the port being used for runtime control.
2) Run your application through Equatec
3) Check if you have anything funny for firewall settings or similar. Some firewalls treat Equatec communication as traffic to be blocked.
4. If all else fails, just close your application normally. Even if taking snapshots fails, you can still see the profile once your application is closed.
Guess I should provide an update on this. The error was resolved once I downloaded the latest version.