I am trying to Run a project in Xojo, which used to run okay previously.
Currently observed behavior:
Clicking "Run", has Xojo display various messages, including "Done Assembling Code".
Then, "Build Failed" dialog box flashes briefly. So briefly, I cannot even grab a screenshot.
And then it disappears, and no diagnostic error/warning messages are given.
I am new to Xojo. The project used to build okay. Something must have changed. Is there a way to somehow see what the problem is? Right now it looks like the IDE keeps on working but the Run process just dies, after barely flashing "Build Failed" Dialog Box.
I will consider it a successful answer if it helps or aids me in the direction of solving this issue.
Turns out the Debug folder was locked by another process. Releasing the lock, restored Run operation.
Where can I find crash reports?
Windows allows you to collect a Minidump when a crash occurs.
The procedure requires modifying a registry value using Regedit. You can also do so with the Xojo command Registry http://docs.xojo.com/index.php/Registry
See https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396 for the exact procedure.
Related
Question:
Does anyone know how to fix this aside from completely reinstalling the entire Fortify software suite?
Background:
Audit Workbench was up then my PC restarted. Now the Project summary does not show (nor does the code preview).
What I have tried so far:
I tried resetting the display and restarting my PC but it does not bring the Audit Workbench module back.
Previous Fix:
Before when I had this issue, I had to get Fortify completely reinstalled to get it fixed. Because this is on a Government Pc, it will take a while to get it reinstalled. I need this for my job.
Edit: Best Path Forward (Until bug is fixed):
When I open the for through the application (start menu, Fortify SCA folder, Audit Workbench, choose for file), it shows the module. For some reason, a forced restart causes Fortify to not show the module when opening the FPRs directly from the file system.
The other thing is that you cannot pin Audit Workbench to the taskbar which makes this bug more annoying than it should be. I will make a script that I can pin to the taskbar to open the Audit Workbench without going through the start menu every time.
Edit: Found temporary solution
I did a bit of testing and whenever I open the FPR with Audit Workbench, I need to open 2 windows, 1 immediately after the other, to get the project summary back. The first one I open will not show the Project Summary but the 2nd one will. It only shows the pane on the 2nd window for some reason.
Check question for "Path Forward"
I have a build which hangs in Jenkins. I have deconstructed the build down to a single windows command call, a directory change and a couple of echoes in an effort to isolate the problem. It would appear that the problem lies with a single call to a program executable (now the only call in my build). The build calls the program & then hangs for 30+ minutes (I cancel the build after this time) when it should take less than 1 second. Ordinarily I would be inclined to blame the executable or my misuse thereof, but for the fact that the same call (quite literally copied & pasted) in an ordinary command prompt works perfectly fine. Further muddying the waters is my knowledge of the fact that the build I'm trying implement is working just fine on another Jenkins server I know of, executable and all, and has never had an issue. I'm sorry I can't provide details on the executable in question but it's sensitive information. It may very well be the case that the executable is to blame, but the exact same call in three environments and only one hangs? What do you think?
More info on request.
So there I was, waiting for a reply when I decided to click on one of the "Related" topics on the right hand side. Lo and behold, there it was, a solution to my problem in answer to a different question. In short it goes like this:
Jenkins is a service. Services (on Windows) have a "Log On" account, of which the default appears to be "Local System". This had the effect of forcing (though I don't know why) my program out of quiet mode and thus hanging the build. Changing the "Log On" account to my own seems to have changed the behavioural relationship between Jenkins and the executable so that it now runs smooth and silent.
I have problems with creating a job in jenkins. At the "Build" step I select Build "execute windows batch command", where I want to start a browser such as opera, google chrome portable or firefox portable, the command never terminates.View screenshot
For IE, firefox and chrome I do not encounter any problems
If someone has a solution. thank you in advance
What do you expect? You have launched an executable that shows a form, albeit in a session that can never have a console session attached.
Jenkins, by design, will sit there until the executable terminates - which generally happens when the form is closed by a user interacting with it. Since there is no GUI, this process can only ever terminate if someone kills it with Task Manager.
What are you actually trying to achieve? There's almost certainly a reasonable way to do it.
I have been trying to do a GUI test with DUnit which includes interacting with modal windows via a message loop timer system by #tomazy (see my earlier question for more details: (How) Can I use FutureWindows with standard file open dialogs? ).
My solution in the other question works fine when I run the tests manually, but when I run this within a continuous build system in TeamCity, it hangs when the dialog's OK message should be handled. The service that runs the tests has the permission "interact with desktop" set, and I have verified that the hanging happens ONLY if the OK is pressed (i.e. the CDN_FILEOK notification happens). I can close the dialog using WM_CLOSE, but this naturally does not cause the dialog to return an OK modal result, and thus is not usable.
If I can't get this to work, I'll probably have to modify the production code (target of test) to publish an event to give the filename and have the test hook into it and give it without a dialog, but I'd like to know what is causing this problem and preferably of course solve it without modifying the production code.
When connecting to a remote TFS 2010 installation via my Visual Studio 2010, Process tab of Build Definition freezes. Everything seems to be disabled. Is there any work-around?
UPDATE 1:
By freezing I mean:
I can navigate to all tabs: General, Trigger, Workspace, Build Defaults, Process and Retention Policy. Except for Process tab, they all are working as excpected. When I click Process tab, it is showed, but none of parameters are shown, and the tab itself is in gray. Actually nothing could be clicked. It is like that Visual Studio is waiting for something to be completed or loaded.
UPDATE 2:
I have explored that when I leave Visual Studio alone for a long time about 20 or 30 minutes, the Process tab goes normal. That means all parameters appears and can be edited. That seems downloading or getting something from server causes this very very long delay.
You might want to check out exactly what rights you have on that server with regards to administrating builds.
http://intovsts.net/2009/09/03/more-fine-grained-permissions-in-tfs2010/ and
http://msdn.microsoft.com/en-us/library/ms252587.aspx
I think one of the main ones is "edit build definition"
If you don't have rights, then there won't be a workaround.
UPDATE:
The only things I can really think of at this point is to put a sql monitor on the TFS Database and possibly, watch the network traffic to see how the network interface is being used.
It's possible that something is wrong on the database server causing a huge amount of load. The other possibility is that the network is badly configured and running at 1Mb instead of 100Mb+.
Beyond those, I'd say call MS Support and open a trouble ticket. This is by no means normal and is likely indicative of some underlying hardware or installation issue.
Afsharm,
Happend with me too. This happened when i had the build defination open on one VS instance in edit mode and i opened it for editing on another pc. After a while it errored saying "TFS 20391: Locked for blah blah..." I had to close my visual studio instance on both the machines and restart, it worked there after. These are very occassional cases and very hard to replicate. I would suggest restarting your visual studio session and trying again.
PS - Worth checking if some one else have the process template open for edit as well?
HTH.
Cheers, Tarun