https://www.logfusion.ca/Discussions/RSS/?TopicID=cb989537-4886-4720-8f3b-81558fc90652 LogFusion RSS: v 3 Betas Sat, 23 May 2026 15:25:26 GMT en hourly 1 https://www.logfusion.ca/Discussions/RSS/?TopicID=cb989537-4886-4720-8f3b-81558fc90652 https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#18 Thu, 28 Mar 2013 01:02:48 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#18 LogFusion The security log issue is very unfortunate, right now we don't have a good work-around, sorry.
I'll take a look at the number column issue. As for reverse sorting, it's on our list of things to do but will require quite a bit of work. ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#17 Wed, 27 Mar 2013 21:52:53 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#17 LogFusion So for the remote security log the number of returned rows are going up ever couple of seconds because of the connection from LogFusion? Starts at 250 and is up to 500 in less than a minute?

When you click auto-column the number column doesn't expand to show all row numbers

Also what about my question: can you change display - i.e. newest at top or clickable column sort?
Pete ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#16 Wed, 27 Mar 2013 21:45:31 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#16 LogFusion Thanks for the feedback again, can you give Beta 8 a try:
http://www.logfusion.ca/Download/Beta/

I've fixed the event log dates. For the remote security log, it's not actually repopulating, it's just that when you query the remote event log it generated a new security record. As a result, when LogFusion polls, it generates new records while doing this. ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#15 Wed, 27 Mar 2013 18:38:19 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#15 LogFusion Jon,
Found more issues:
1) Time stamps are been calculated\shown incorrectly for both local and remote. See images; images taken at approx. 11 a.m. today - times are in future.
2) Remote Security is repopulating it seems - maybe need to check the others.

Question - change display - i.e. newest at top or clickable column sort? ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#14 Tue, 26 Mar 2013 22:15:03 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#14 LogFusion Excellent, thanks. We're planning to do the final release this Thursday, so if you find anything else let me know as soon as you can. ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#13 Tue, 26 Mar 2013 21:21:55 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#13 LogFusion Jon, All good now I will keep testing.
Pete ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#12 Tue, 26 Mar 2013 21:17:39 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#12 LogFusion Good catch! I had colour-coded the event channels in the main window, but I missed this list. Try out the attached test build (B7-Test3) and let me know what you think.

Thanks! ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#11 Tue, 26 Mar 2013 20:53:53 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#11 LogFusion Jon,
Working now.
Another suggestion. Look at attached png. This shows the Settings > Logs. You can't tell if the log is Application std or Application Channel. Can you clarify in the UI what its source was? Obviously this would be true for others that show in multiple places.
Pete ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#10 Tue, 26 Mar 2013 16:10:57 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#10 LogFusion I've updated the name to "Event Channels", to be more consistent with Microsoft's naming. Can you give the attached build (B7-Test2) a try and let me know if it's all working for you now? Thanks! ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#9 Tue, 26 Mar 2013 14:54:22 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#9 LogFusion Jon,
Just for my own reference can you tell me where the name "Channel Logs" comes from?
Regarding item 3, I was just meaning if you compact into just local and remote, you would only need the one authentication dialog at the entry to the remote, if you see what I mean.
Pete ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#8 Tue, 26 Mar 2013 14:23:50 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#8 LogFusion It seems like we're making progress here.

1. The API we use to get the channels returns the normal event logs too, there's no harm in showing them here.
2. Sorry, I've fixed the duplicate lines issue for the next build.

Thank you for the design ideas too, let me cover those as well:

1. I think we'll keep the open prefixes, just so people know what they're getting into. They don't add too much space, and they're often shorter than anything in the history below.
2. I don't want to nest the menus any more than they are right now, and I'd like to avoid combining the event logs with the channels, so people understand what type they are opening. Each one can return different results, and the querying is done completely differently.
3. I'm not sure I understand your third suggestion, sorry, can you please elaborate?

Thanks! ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#7 Tue, 26 Mar 2013 05:03:36 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#7 LogFusion Jon,
I think you are nearly there!
1) Questions: The entry to "Open other" - if you look at Open Event Log and the Open Event Log Channel UI's, the items are similar - this seems confusing. Is it possible to filter them? Are they enumerated and or accessed different ways - if so then shouldn't they only show their intended returned values? i.e. the standard logs and only channel logs - or is there some overlap because of how you are accessing them? Why have 2 entry points? Where does the name "Channel logs" come from - it is confusing to me - why not Applications and Services? These are questions of design, but if I am asking it is because the design confuses me - don't think this can be good.
2) the local channel logs all now return messages - however they are re-querying at about 5 second intervals and showing the duplicated rows.

So here is my design take for the "Open other...":
1) The main entry tab says "Open other..." so get rid of all the "Open" prefixes in child dialog
2) Contract the top 4 into a) Local logs and b) Remote logs
3) Add authentication section (i.e. current or other user) to Remote as entry to what logs to show

Obviously this makes assumptions about how you enumerate the logs and then access them but something as above may clean the design, but may not simplify the programming.

Pete ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#6 Mon, 25 Mar 2013 22:36:10 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#6 LogFusion Hi Pete, thanks for the info. Can you give the attached test build a test and let me know if it is any better? Thanks! ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#5 Mon, 25 Mar 2013 20:08:37 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#5 LogFusion Jon,
This is better but I have question and there are issues.
1) Look at image CompareMMCLogFusion for a listing of available logs channel logs; there is difference between what MMC shows and what LogFusion shows?
2) Now look at comparison of local channel log - ChannelLogRowVisibleMissingMessageInfo -MMC to LogFusion - no message showing. However looking at another local log ChannelLogWorking - this works fine
3) Remote connection works and show correctly - RemoteChannel ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#4 Mon, 25 Mar 2013 18:14:33 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#4 LogFusion Can you give this new Beta 7 build a try:
http://www.logfusion.ca/Download/Beta/

Thanks! ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#3 Mon, 25 Mar 2013 14:37:25 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#3 LogFusion Jon,
Jon - Enabled debug logging. When I tried to open another Channel log I got "I need to upgrade to the Pro version". I am guessing that this is why it is not showing the message in the one it already connected to and opens, but it opened the first few local channel logs without it raising this prompt. Can you sent me temp Pro license to continue testing? Maybe I shall wait till next beta is out - you say you have other issues in 6?
I regularly use wmi in vbscripts and powershell and never have any issues with UAC particularly when connecting remotely.
Pete ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#2 Mon, 25 Mar 2013 02:06:07 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652#2 LogFusion Let me see if I can sort this out:
1. That was my fault, it will be fixed in Beta 7.
2. This appears to work for me, which channel are you trying? Can you enable logging in LogFusion and send/post the log here for me to check out?
3. The new LogFusion betas use WMI to connect to the remote machines now, which allows for more fine-grained authentication. Make sure you have the Remote Registry service enabled on the remote machine, and that the firewall is configured correctly. Also, UAC can sometimes block access, do you have UAC enabled on the remote machine?

Did I miss anything, or are there just the 3 issues here? Thanks! ]]> https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652 Sat, 23 Mar 2013 16:45:18 GMT Binary Fortress Software https://www.logfusion.ca/Discussions/View/v-3-betas/?ID=cb989537-4886-4720-8f3b-81558fc90652 LogFusion Jon,
I thought I would start a general thread rather than continuing the specific one related to Channel logs.
Upgraded to v6. v6 opened and connected to the previous remote channel log. It enumerated the log. However none of the rows returned show anything in the message field. I then looked a the changes to the remote UI - this is now good. I then switched to just the remote std log UI and stayed pointing at the same server. Clicking get log brought up access denied. Now I cannot connect to any remote machine with LogFusion either with current credentials of specified - I just keep getting access denied. If I use a standard MMC to connect no problem. Now I open LogFusion and connect to a local log and it doesn't return any rows. Same if I elevate. Not sure how you want me to troubleshoot this. I will post here and then reboot and add any further findings.
Reboot same findings:
1) Local std. logs nothing - any of them - with or without elevation
2) Local Channel Logs return correct log rows but no message info
3) Will not connect to any remote log with current credentials or specified.
4) Uninstalled cleared all registry setting etc.; reinstalled - same result.
Beta 6 seems broken at least on Windows 8 x64; tested on 2 machines one in domain one in workgroup. ]]>