Thanks Nik!

On Mon, Sep 4, 2017 at 5:23 PM, Yakovlev N. <[email protected]> wrote:
> Upgrading OM  J
>
> http://openmeetings.apache.org/Upgrade.html
>
> Nik
>
>
>
> From: Бунин Владимир [mailto:[email protected]]
> Sent: Monday, September 4, 2017 12:54 PM
> To: [email protected]
> Subject: Re: Unable joining to conference
>
>
>
> IE 11. And also tried Opera with the same result.
>
> How to update OM. Stop, upload files and replace them, then start?
>
>
>
> --
>
> С уважением, Владимир!
>
>
>
>
>
>
>
> 04.09.2017, 12:39, "Maxim Solodovnik" <[email protected]>:
>
> IE :)
> What version are you using?
> can you check with OM 3.3.1RC3:
> https://dist.apache.org/repos/dist/dev/openmeetings/3.3.1/rc3/ ?
>
> SCRIPT1015 is very interesting .... not sure how to check it :(
> Is it possible client is on the WiFi and NetworkChanged event occurred?
>
> On Mon, Sep 4, 2017 at 4:28 PM, Бунин Владимир <[email protected]>
> wrote:
>
>  Errors in browser console in screenshots. It happens sometimes and by
>  chance. One employee connects to OM from branch through VPN-tunnel. And
>  another one within local network. And the error is identical.
>
>  --
>  С уважением, Владимир!
>
>
>
>  04.09.2017, 11:48, "Бунин Владимир" <[email protected]>:
>
>  I asked colleague about mistakes in browser console. What concerns
>  openmeetings.log I stiil don't have it. Permissions for the folder log
> 0755,
>  log files with access exist, but no openmeetings.log.
>
>  --
>  С уважением, Владимир!
>
>
>
>  04.09.2017, 11:37, "Maxim Solodovnik" <[email protected]>:
>
>  Anything in the Browser Console? openmeetings.log?
>  Any steps to reproduce?
>
>  On Mon, Sep 4, 2017 at 3:29 PM, Бунин Владимир <[email protected]>
>  wrote:
>
>   Hello!
>   Some of our employees can not join to the conference. Their names doesn't
>   appear among participants, and they have an error on screen which is
>   attached.
>
>   --
>   Regards, Vladimir
>
>
>
>
>
>
>  --
>  WBR
>  Maxim aka solomax
>
>
>
>
>
> --
> WBR
> Maxim aka solomax



-- 
WBR
Maxim aka solomax

Reply via email to