FAZ 4.3 -- definitely not recommended

[billp]

After about a week into FAZ 4.3, it gets a definite thumbs-down. It should not have been released in its current condition. The Log Access is unreliable at best -- completely non-functional at worst. It' s a crapshoot if any of the logs show up at all when I view them in anything but realtime mode. I am also having problems now with scheduled reports not showing proper results. If anyone is using 4.3 productively, would be great to hear from you. I' m considering wiping out the firmware and reinstalling 4.2.4, but will open up a ticket first to give it a chance. For those on the fence, definitely wait for 4.3.1.

[abelio]

I' m waiting for the opportunity to format log disk and flash and reload 4.3 fresh image one before make conclusions. I' ve upgraded my 400B from 4.2 and, yes, it shows strange things like those you´ve mentioned. But my 2 cents to the " format an load fresh" approach regards A

[abelio]

But my 2 cents to the " format an load fresh" approach

formatted and loaded fresh image; no way back to 4.2.4 regards

[billp]

Abel, Thanks. Very interested in your conclusions. I' ve reformatted my log disk last week -- that seemed to help initially. I have not reformatted the firmware partition yet. I would like to think that the FAZ project manager at FTNT would not release a firmware that is so clearly hobbled.

[ppowell]

I also " upgraded" to this version and it is absolutely ludicrous that the software was released in this state. I doubt this should even have been a Beta release. Peter

[billp]

Yes. It' s useless. I' m trying to figure out when to wipe my box and reload 4.2.4. I' m hoping that 4.3.1 will be released before I get the time. The only thing that works for me is the live log view.

[billp]

Per support, there is a confirmed bug in the new SQL engine. It' s major. (Like, um, it doesn' t work. ) If you go back to the traditional log database system in the FAZ, it seems to work fine. That' s the workaround for now.

[donnat]

The future version 4.3.1 fixes this problem? When version 4.3.1 will it be available?

[billp]

Donnat, The next revision will almost certainly fix this bug. I can' t imagine them releasing a new version that didn' t fix this huge hole. It' s a serious bug. They wouldn' t promise a release date for me or give any hints. The tech said to just switch to the standard database logging system for now, and they would fix in the next patch. Feel free to complain to your nearest FTNT rep :) Releasing a broken product is not a great way to win fans.

[donnat]

Bill, Thank you for the answer.