MaxBlitzer, User (Posts: 68)
May 18, 2020 6:47:14 pm EDT
Yeah, that is very bad practice. The build output from one version of the compiler and build system can vary with the same source code. The building stage is essentially part of the "application" along with the source code. It should be tracked just as the same the code. Some companies have policies that even prevent the release system from ever generating different builds using the same release number to prevent this scenario. Not only do you have your own code issues handling this issue internally, now you have two different "viewer6.12.b2.exe" files that you had posted for almost two weeks on the Internet.Conrad Sallian wrote:
Hello Max,
Thank you for your suggestion.
However, this specific "bug" was just something we overlooked on the building stage rather than a bug in the program itself (related to its functionality, that is). So we decided to keep it the same number.
Conrad Sallian, Support (Posts: 2979)
May 19, 2020 3:52:44 am EDT
I understand your frustration. We updated the release dates for the beta on the site to avoid misleading, although we also had to update that for the Host (despite it wasn't changed). A note to release notes was also added.Right now, my PC has two files names "viewer6.12.b2.exe" with different file sizes. One has a digital signature signing date of May 13, and another one says May 18. The release date is May 6. The server's beta 2 has a signing time of May 5, which is what I'd expect with a May 6 release. But May 13 and May 18th? This implies that you didn't just have TWO different "viewer6.12.b2.exe" with different hashes, but (AT LEAST) THREE. Can you comment on that?
Peter Gray, User (Posts: 46)
May 20, 2020 4:45:40 pm EDT
Other jobs needed doing, so I've only just been able to get back to this. I have bad news and good news.Polina Krasnoborceva wrote:
Hello Peter and Max,
Thank you for your feedback.
We've managed to reproduce the issue and implemented a quick fix for it. We apologize for the caused inconvenience.
An upd ated build of version 6.12 Beta 2 is available on this page. Please try updating your Viewer and see if the issue persists.
Please let us know if you have more questions.
Pauline, Support (Posts: 2815)
May 20, 2020 5:48:58 pm EDT
Could you please confirm that you did not encounter this issue when using version 6.10.10.0 prior to updating to the 6.12 Beta 2 version?Quick test, try to log into several remote machine both internet and local connections, in each case got Access Denied for five trys before it gave up.
Peter Gray, User (Posts: 46)
May 20, 2020 6:06:34 pm EDT
Hi Polina.Polina Krasnoborceva wrote:
Quick test, try to log into several remote machine both internet and local connections, in each case got Access Denied for five trys before it gave up.
Could you please confirm that you did not encounter this issue when using version 6.10.10.0 prior to updating to the 6.12 Beta 2 version?
Pauline, Support (Posts: 2815)
May 21, 2020 10:49:45 am EDT
Peter Gray, User (Posts: 46)
May 21, 2020 11:33:59 am EDT
Peter Gray wrote:
Confirmed I did not have this issue prior to updating to the beta.
It's late here now, and I've shut down both the machines I used for testing. I'll track down the log files and send them to you, but it might not be until the weekend, depends what else needs doing.
OK, it turns out I had some time available this afternoon, so I've done a test and have just emaied you the viewer and host logs for an attempted login from an XP to another XP box on my LAN.Polina Krasnoborceva wrote:
Of course, please feel free to update us further on the issue anytime. Meanwhile, we will try to reproduce the issue as well.
Pauline, Support (Posts: 2815)
May 21, 2020 12:18:07 pm EDT
Peter Gray, User (Posts: 46)
May 22, 2020 5:10:48 pm EDT
Pauline, Support (Posts: 2815)
May 25, 2020 2:42:19 pm EDT
Yes, the Monitor driver has been discontinued and it's automatically uninstalled upon the 6.12 Beta 2 version installation.On a side note, earlier posts mention that the v12 host does not use the display driver. Does intalling the new host automatically remove the driver, or does that have to be done separately?
* Website time zone: America/New_York (UTC -4)