I'd like to review the contents of all the debug logs on all the devices I use in my fastlane snapshot ui test?
I'm looking for the debug messages that would also be generated using NSLog etc.
I found this output_simulator_logs flag in the documentation, but it doesn't seem to work. I also set namespace_log_files but this just seems to be for the build log.
Although I'm quite happy to achieve this using another fastlane tool or maybe a different tool?
If you pass in result_bundle: true should should get some test_result bundles. In those bundles, you'll get all the logs that you're looking for. Not that *.xcactivitylog files are actually gzip'd text files.
I'm just curious - have any fellow Neo4j-ers ever encountered this behavior?
Right now, I've got 30 queries in the 'Saved Scripts' part of the Neo4j browser interface. When I try to save another, it will remain there until the the page is reloaded/refreshed - it then disappears.
I thought that 30 might be some soft limit determined in a Neo4j configuration file (/etc/neo4j/neo4.conf) but I can't find any statements in the file relating to this. If it's at all pertinent, I'm running x64 CentOS 7 as a VM - this is where my Neo4j has been configured. I've checked the debug logs and I don't see any warnings or errors relevant to this issue.
Is this behavior normal? If so, is there a way to change it?
I solved the problem. Just needed to reboot the VM apparently.
Still not sure what the root cause of this is - but rebooting was, in this case, the remedy.
Sometimes when the rules are deployed from the decision center to RES, although the recent changes are visible in the new archive, on RES, but the execution results don't reflect them. It is as if the changes are not recognized at execution time. A second deployment without any changes to the rules, will fix the situation. Can somebody explain why this is happening?
You can try couple of things -
The XU MBean ruleset archive changed/modified notification might be failing. Check if you have the necessary access for this notification. You can try logging into the RES and Diagnostics->Run Diagnostics; and see if there are any errors. Also, you can see the ODM server logs for any errors, when you deploy the ruleset.
Check if there is any caching issue
I have an MVC application that has been running in debug mode with no problems. Suddenly today I get an error when loading the browser screen (it compiles OK) that cannot find assembly "Excel" which I don't use in the application and have never previously referenced it. Not even sure what assembly it should be.
ANy help?
Thanks
Martin
Maybe you got a suggestion in your Yellow Screen of Death to turn on the assembly binding logging, like so:
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Se also how-to-enable-assembly-bind-failure-logging-fusion-in-net.
If you do this, you will get a lot more detailed information on what whent wrong and why. If that does not in itself give you enough to solve the issure, perhaps share the detailed log here. When you're done, remember to remove the registry value again, lest performance will suffer.
I have a windows service that is failing to start, giving an error "Error 1053: The service did not respond to the start or control request in a timely fashion".
Running the service in my debugger works fine, and if I double click on the the service .exe on the remote machine a console window pops up and continues to run without problem - I can even see log messages showing me that the program is processing everything the way it should be.
The service had been running fine previously, though this is my first time, personally, trying to deploy it with the most recent changes made to the program. I've evaluated those changes and cant figure out how they might cause this problem, particuarly since everything runs fine when not started as a service.
The StartRoutine() method of the service impelmentation is empty, so should be returning in a "timely fashion".
I've checked the event logs on the computer, and it doesn't give any additional information other than it didn't hear back from the service in the 30 second requisite time frame.
Since it works on my machine, and as a double-clicked executable, how would I go about figuring out why it fails as a service?
Oh, and it's .NET 2.0, so it shouldn't be affected by the 1.1 framework bug that exhibited this symptom (http://support.microsoft.com/kb/839174)
The box is a windows server 2003 R2 machine running SP2.
This is a misleading error. It's probably an unhandled exception.
Empty your OnStart() handler then try this in your constructor...
public MainService()
{
InitializeComponent();
try
{
// All your initialization code goes here.
// For instance, my exception was caused by the lack of registry permissions
;
}
catch (Exception ex)
{
EventLog.WriteEntry("Application", ex.ToString(), EventLogEntryType.Error);
}
}
Now check the EventLog on your system for your Application Error.
Could be a number of things and it might help to get a stack trace on the machine exhibiting the problem. There are a number of ways to do this but the point is that you have to see where this is failing in the code.
You can do this with remote debugging, but a simple thing might be to just log to the event logger, or file log if you have that. Literally, putting "WriteLine("At class::function()") throughout portions of the code to see if you've made it there.
This will at least get you looking in the right direction (which ultimately is the code).
Update:
See Microsoft's How to Debug Windows Services article for details in troubleshooting startup problems using WinDbg.
This related question details nice ways to debug services that are written in .NET.
I agree with Scott, the easiest way to find out what's happening is to put some traces in the start-up code (maybe it doesn't even come to your start-up code).
If this doesn't help, you can post your code here so others can take a look.
perhaps lacking some dependence, try this :
- deregister your service
- register again
If fail at register means that lack an module.
If the StartRoutine is empty, you are probably starting it somewhere else.
IIRC you need to fire off a worker thread, and then return from StartRoutine.
One of the problems which may lead to this error is if windows service which needs to be deployed consists of some error i.e it may be simple authorization error or anything as in my case I have referenced some folders and files for logging which were not existing, but when provided the right path of those file and folders it solved my problem.
I ran through every post on this particular subject and none of the responses solved the problem, so I'm adding this response in case this helps someone else. Admittedly this only applies to a new service, not this specific case.
I was writing a File listening service. As a console app, it worked perfectly. When I ran it as a service, I got the same error as above. What I didn't know (and many of the MSDN articles about services conveniently leave out) is that you need to have your class executed from within ServiceBase.Run( YourClassName());. Otherwise, your app executes and immediately terminates and because it terminated, you get the error above even if no error or exception occurred. Here is a link to an article about this. It actually discusses setting up your app for dual use - Console app and service: Create a combo command line / Windows service app
I had that issue and the source of my problem was config file. I edited it in notepad and notepad added one special character which cause service not to run properly because config file was ruined. I saw that special character in notepadd++ and after delete it, service started to run successfully as previous did.
In my case, the correct .NET framework was not installed on the server that I was installing the Windows service on.
One other reason is If you copy the DLL in 'debug' mode to installation folder this issue will come.What you need to do is Run the project in 'Release' mode copy the DLL or directly form Release folder rather than Debug folder,,and copy that DLL in to installation folder,it will work.You can see the reduction in size of DLL ,it will not contain any debug symbols and like that