your installation was not successful
could you please share the link you were using to download OM?


On 25 August 2014 19:43, Murat Tamer Ataol <[email protected]>
wrote:

>   DB server is up and running. It is creating 48 tables out of 49 in the
> install. mysql*.jar file is there. Telnet is connecting from 3306. I have
> the line in the persistence.xml.
>
> I am installing the default language (english).
>
> Is there anything else I should check for. By the way I reinstalled
> openmeetings and it gives exacly the same error.
>
>
>
>
>
>    Murat Tamer Ataol
> Sistem Yönetimi Daire Başkanlığı
>
> Sağlık Bakanlığı
> Sağlık Bilgi sistemleri Genel Müdürlüğü
> Mithatpaşa Cad. No:3 Çankaya / Ankara
>
>              Yasal Uyarı :
> Bu elektronik posta işbu linki kullanarak ulaşabileceğiniz Koşul ve
> Şartlar dokümanına tabidir :
> http://www.saglik.gov.tr/sbsgm/belge/1-17902/yasal-uyari.html
>
>   ------------------------------
> *Kimden:* Maxim Solodovnik [[email protected]]
> *Gönderildi:* 25 Ağustos 2014 Pazartesi 15:32
> *Kime:* Openmeetings user-list
> *Konu:* Re: YNT: YNT: YNT: YNT: Openmeetings problem
>
>   first of all check if DB server is up and you able to connect it
> in your persistence.xml you have the line:
> *Url=jdbc:mysql://your_server:3306/openmeetings*
>
>  start terminal and type:
> *telnet* *your_server 3306*
>
>  if connection is successful then check if mysql*jar driver is present in
> webapps/WEB-INF/lib folder
>
>
>
> On 25 August 2014 19:17, Murat Tamer Ataol <[email protected]>
> wrote:
>
>>   If this is a connection failure to the database, how can I fix it? Any
>> suggestions?
>>
>>
>>
>>   Murat Tamer Ataol
>> Sistem Yönetimi Daire Başkanlığı
>>
>> Sağlık Bakanlığı
>> Sağlık Bilgi sistemleri Genel Müdürlüğü
>> Mithatpaşa Cad. No:3 Çankaya / Ankara
>>
>>              Yasal Uyarı :
>> Bu elektronik posta işbu linki kullanarak ulaşabileceğiniz Koşul ve
>> Şartlar dokümanına tabidir :
>> http://www.saglik.gov.tr/sbsgm/belge/1-17902/yasal-uyari.html
>>
>>   ------------------------------
>> *Kimden:* Vasiliy Degtyarev [[email protected]]
>> *Gönderildi:* 25 Ağustos 2014 Pazartesi 14:32
>> *Kime:* [email protected]
>> *Konu:* Re: YNT: YNT: YNT: YNT: Openmeetings problem
>>
>>   I suppose that this is problem of connection to openmeetins database:
>>
>> ERROR 08-25 12:22:50.369 o.a.o.r.r.ScopeApplicationAdapter:151
>> [Launcher:/openmeetings] - [appStart]
>> org.springframework.transaction.CannotCreateTransactionException: Could
>> not open JPA EntityManager for transaction; nested exception is
>> <openjpa-2.2.2-r422266:1468616 nonfatal general error>
>> org.apache.openjpa.persistence.PersistenceException: Communications link
>> failure
>>
>> Vasiliy
>>
>>
>>
>>
>> On 25.08.2014 18:10, Murat Tamer Ataol wrote:
>>
>> Here are the log files. error.log has 0 bytes in it. So there is no error
>> in the error.log.
>>
>>
>>
>>   Murat Tamer Ataol
>> Sistem Yönetimi Daire Başkanlığı
>>
>> Sağlık Bakanlığı
>> Sağlık Bilgi sistemleri Genel Müdürlüğü
>> Mithatpaşa Cad. No:3 Çankaya / Ankara
>>
>>       Yasal Uyarı :
>> Bu elektronik posta işbu linki kullanarak ulaşabileceğiniz Koşul ve
>> Şartlar dokümanına tabidir :
>> http://www.saglik.gov.tr/sbsgm/belge/1-17902/yasal-uyari.html
>>
>>  ------------------------------
>> *Kimden:* Vasiliy Degtyarev [[email protected]]
>> *Gönderildi:* 25 Ağustos 2014 Pazartesi 13:23
>> *Kime:* [email protected]
>> *Konu:* Re: YNT: YNT: YNT: Openmeetings problem
>>
>>  Please send log files.
>>
>>
>>
>> On 25.08.2014 16:26, Murat Tamer Ataol wrote:
>>
>> I did what you said to create database and reinstalled the application.
>> Still appoinments table is not there. Same message appears in the log and
>> the login screen doesnt come.
>>
>>
>>
>>   Murat Tamer Ataol
>> Sistem Yönetimi Daire Başkanlığı
>>
>> Sağlık Bakanlığı
>> Sağlık Bilgi sistemleri Genel Müdürlüğü
>> Mithatpaşa Cad. No:3 Çankaya / Ankara
>>
>>      Yasal Uyarı :
>> Bu elektronik posta işbu linki kullanarak ulaşabileceğiniz Koşul ve
>> Şartlar dokümanına tabidir :
>> http://www.saglik.gov.tr/sbsgm/belge/1-17902/yasal-uyari.html
>>
>>  ------------------------------
>> *Kimden:* Vasiliy Degtyarev [[email protected]]
>> *Gönderildi:* 25 Ağustos 2014 Pazartesi 12:10
>> *Kime:* [email protected]
>> *Konu:* Re: YNT: YNT: Openmeetings problem
>>
>>  You should not create tables, you should create database use this
>> command:
>> CREATE DATABASE openmeetings DEFAULT CHARACTER SET 'utf8';
>>
>> If you update openmeeting you should make backup and import.
>>
>> Thanks,
>> Vasiliy
>>
>>
>> On 25.08.2014 16:02, Murat Tamer Ataol wrote:
>>
>> I am following the Installation of Apache OpenMeetings 2.x or 3.x in
>> CentOS 6.5 guide from cwiki.apache.org.
>>
>> I am not creating the tables by myself. Installation did that. And there
>> were no errors in the installation.
>>
>>
>>
>>
>>   Murat Tamer Ataol
>> Sistem Yönetimi Daire Başkanlığı
>>
>> Sağlık Bakanlığı
>> Sağlık Bilgi sistemleri Genel Müdürlüğü
>> Mithatpaşa Cad. No:3 Çankaya / Ankara
>>
>>      Yasal Uyarı :
>> Bu elektronik posta işbu linki kullanarak ulaşabileceğiniz Koşul ve
>> Şartlar dokümanına tabidir :
>> http://www.saglik.gov.tr/sbsgm/belge/1-17902/yasal-uyari.html
>>
>>  ------------------------------
>> *Kimden:* Vasiliy Degtyarev [[email protected]]
>> *Gönderildi:* 25 Ağustos 2014 Pazartesi 11:50
>> *Kime:* [email protected]
>> *Konu:* Re: YNT: Openmeetings problem
>>
>>  What sql server you use?
>> What command you use to create openmeetings database.
>>
>> Please send full log files.
>>
>> Vasiliy
>>
>> On 25.08.2014 15:38, Murat Tamer Ataol wrote:
>>
>> Hello,
>>
>> I checked the log files. There is one error in openmeetings.log.
>>
>> ----------------------------------------------------------------------------------------
>> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Table
>> 'openmeetings.appointments' doesn't exist {prepstmnt 641714439 SELECT
>> t0.id, t1.id, t1.comment_field, t1.deleted, t1.name, t1.starttime,
>> t1.updatetime, t2.id, t2.activatehash, t3.id, t3.additionalname,
>> t3.comment_field, t3.deleted, t3.email, t3.fax, t3.phone, t3.starttime,
>> t4.id, t4.code, t4.deleted, t4.name, t4.shortName, t4.starttime,
>> t4.updatetime, t3.street, t3.town, t3.updatetime, t3.zip, t2.age,
>> t2.availible, t2.deleted, t2.externalUserId, t2.externalUserType,
>> t2.firstname, t2.forceTimeZoneCheck, t2.language_id, t2.lastlogin,
>> t2.lastname, t2.lasttrans, t2.level_id, t2.login, t2.owner_id,
>> t2.pictureuri, t2.regdate, t2.resethash, t2.salutations_id, t2.sendSMS,
>> t2.show_contact_data, t2.show_contact_data_to_contacts, t5.id, t5.allow,
>> t5.callbackextension, t5.context, t5.defaultuser, t5.fullcontact, t5.host,
>> t5.ipaddr, t5.lastms, t5.md5secret, t5.name, t5.nat, t5.port,
>> t5.regseconds, t5.regserver, t5.secret, t5.type, t5.useragent,
>> t2.starttime, t2.status, t2.time_zone_id, t2.type, t2.updatetime,
>> t2.user_offers, t2.user_searchs, t0.is_connected_event, t0.deleted,
>> t0.description, t0.appointment_endtime, t0.icalId, t0.starttime,
>> t0.isdaily, t0.ismonthly, t0.isweekly, t0.isyearly, t0.language_id,
>> t0.location, t6.id, t6.activatehash, t6.adresses_id, t6.age,
>> t6.availible, t6.deleted, t6.externalUserId, t6.externalUserType,
>> t6.firstname, t6.forceTimeZoneCheck, t6.language_id, t6.lastlogin,
>> t6.lastname, t6.lasttrans, t6.level_id, t6.login, t6.owner_id,
>> t6.pictureuri, t6.regdate, t6.resethash, t6.salutations_id, t6.sendSMS,
>> t6.show_contact_data, t6.show_contact_data_to_contacts, t6.sip_user_id,
>> t6.starttime, t6.status, t6.time_zone_id, t6.type, t6.updatetime,
>> t6.user_offers, t6.user_searchs, t0.password, t0.is_password_protected,
>> t7.id, t7.deleted, t7.fieldvalues_id, t7.name, t7.starttime,
>> t7.updatetime, t8.id, t8.activatehash, t8.adresses_id, t8.age,
>> t8.availible, t8.deleted, t8.externalUserId, t8.externalUserType,
>> t8.firstname, t8.forceTimeZoneCheck, t8.language_id, t8.lastlogin,
>> t8.lastname, t8.lasttrans, t8.level_id, t8.login, t8.owner_id,
>> t8.pictureuri, t8.regdate, t8.resethash, t8.salutations_id, t8.sendSMS,
>> t8.show_contact_data, t8.show_contact_data_to_contacts, t8.sip_user_id,
>> t8.starttime, t8.status, t8.time_zone_id, t8.type, t8.updatetime,
>> t8.user_offers, t8.user_searchs, t0.is_reminder_email_send, t9.id,
>> t9.allow_font_styles, t9.allow_recording, t9.allow_user_questions,
>> t9.appointment, t9.auto_video_select, t9.chat_moderated, t9.chat_opened,
>> t9.comment_field, t9.confno, t9.deleted, t9.demo_time, t9.externalRoomId,
>> t9.externalRoomType, t9.files_opened, t9.hide_actions_menu,
>> t9.hide_activities_and_actions, t9.hide_chat, t9.hide_files_explorer,
>> t9.hide_screen_sharing, t9.hide_top_bar, t9.hide_whiteboard,
>> t9.is_audio_only, t9.is_closed, t9.isdemoroom, t9.ismoderatedroom,
>> t9.ispublic, t9.name, t9.numberOfPartizipants, t9.owner_id, t9.pin,
>> t9.redirect_url, t9.roomtypes_id, t9.show_microphone_status,
>> t9.sip_enabled, t9.starttime, t9.updatetime, t9.wait_for_recording,
>> t0.appointment_starttime, t0.appointmentname, t0.updatetime FROM
>> appointments t0 LEFT OUTER JOIN appointmentcategory t1 ON t0.category_id =
>> t1.id LEFT OUTER JOIN om_user t6 ON t0.user_id = t6.id LEFT OUTER JOIN
>> appointmentremindertyps t7 ON t0.remind_id = t7.id LEFT OUTER JOIN room
>> t9 ON t0.room_id = t9.id LEFT OUTER JOIN om_user t2 ON t1.user_id = t2.id
>> LEFT OUTER JOIN om_user t8 ON t7.user_id = t8.id LEFT OUTER JOIN address
>> t3 ON t2.adresses_id = t3.id LEFT OUTER JOIN sipusers t5 ON
>> t2.sip_user_id = t5.id LEFT OUTER JOIN state t4 ON t3.state_id = t4.id
>> WHERE (t0.deleted = ? AND t0.is_reminder_email_send = ? AND (t0.remind_id =
>> ? OR t0.remind_id = ?) AND (t0.appointment_starttime >= ? AND
>> t0.appointment_starttime <= ? OR t0.appointment_endtime >= ? AND
>> t0.appointment_endtime <= ? OR t0.appointment_starttime < ? AND
>> t0.appointment_endtime > ?))} [code=1146, state=42S02]
>>         at
>> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
>> ~[openjpa-bundle-2.2.2.jar:2.2.2]
>>         at
>> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
>> ~[openjpa-bundle-2.2.2.jar:2.2.2]
>>         at
>> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:59)
>> ~[openjpa-bundle-2.2.2.jar:2.2.2]
>>         at
>> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeQuery(LoggingConnectionDecorator.java:1118)
>> ~[openjpa-bundle-2.2.2.jar:2.2.2]
>>         at
>> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:268)
>> ~[openjpa-bundle-2.2.2.jar:2.2.2]
>>
>> -----------------------------------------------------------------------------------
>>
>> I dont exacly know why this table is not there. Installation didnt give
>> any problem. How can I fix this one?
>>
>> Kind regards,
>> Tamer Ataol
>>
>>
>>
>>   Murat Tamer Ataol
>> Sistem Yönetimi Daire Başkanlığı
>>
>> Sağlık Bakanlığı
>> Sağlık Bilgi sistemleri Genel Müdürlüğü
>> Mithatpaşa Cad. No:3 Çankaya / Ankara
>>
>>      Yasal Uyarı :
>> Bu elektronik posta işbu linki kullanarak ulaşabileceğiniz Koşul ve
>> Şartlar dokümanına tabidir :
>> http://www.saglik.gov.tr/sbsgm/belge/1-17902/yasal-uyari.html
>>
>>  ------------------------------
>> *Kimden:* Vasiliy Degtyarev [[email protected]]
>> *Gönderildi:* 25 Ağustos 2014 Pazartesi 11:26
>> *Kime:* [email protected]
>> *Konu:* Re: Openmeetings problem
>>
>>  Hello Tamer Ataol,
>>
>> Please check log files in the log directory.
>>
>> Thanks,
>> Vasiliy
>>
>>
>> On 25.08.2014 15:22, Murat Tamer Ataol wrote:
>>
>> Hello,
>>
>> I have a problem after installation. Installation completes ok. After
>> that when I hit the "Enter the Application" link notinited page comes. I
>> tried writing localhost:5080/openmeetings on the address bar. It didnt
>> work. I couldnt find how to come to login page. Login page never comes.
>>
>> Can you be of any help?
>>
>> Kind regards,
>> Tamer Ataol
>>
>>
>>
>>   Murat Tamer Ataol
>> Sistem Yönetimi Daire Başkanlığı
>>
>> Sağlık Bakanlığı
>> Sağlık Bilgi sistemleri Genel Müdürlüğü
>> Mithatpaşa Cad. No:3 Çankaya / Ankara
>>
>>      Yasal Uyarı :
>> Bu elektronik posta işbu linki kullanarak ulaşabileceğiniz Koşul ve
>> Şartlar dokümanına tabidir :
>> http://www.saglik.gov.tr/sbsgm/belge/1-17902/yasal-uyari.html
>>
>>
>>
>>
>> ------------------------------
>>
>> YASAL UYARI:
>> Bu e-posta'nın içerdiği bilgiler (ekleri de dahil olmak üzere) gizlidir.
>> T.C. Sağlık Bakanlığı onayı olmaksızın içeriği kopyalanamaz, üçüncü
>> kişilere açıklanamaz veya iletilemez . Bu mesajın gönderilmek istendiği
>> kişi değilseniz (ya da bu e-posta'yı yanlışlıkla aldıysanız), lütfen
>> yollayan kişiyi haberdar ediniz ve mesajı sisteminizden derhal siliniz.
>> T.C. Sağlık Bakanlığı bu mesajın içerdiği bilgilerin doğruluğu veya
>> eksiksiz olduğu konusunda bir garanti vermemektedir. Bu nedenle, bilgilerin
>> ne şekilde olursa olsun içeriğinden, iletilmesinden, alınmasından,
>> saklanmasından T.C. sağlık Bakanlığı sorumlu değildir. Bu mesajın içeriği
>> yazarına ait olup, T.C. Sağlık Bakanlığı görüşlerini içermeyebilir.
>>
>> Bu e-posta bizce bilinen tüm bilgisayar virüslerine karşı taranmıştır.
>>
>> DISCLAIMER:
>> This e-mail (including any attachments) may contain confidential and/or
>> privileged information. Copying, disclosure or distribution of the material
>> in this e-mail without The Ministry of Health of Turkey's authority is
>> strictly forbidden. If you are not the intended recipient (or have received
>> this e-mail in error), please notify the sender and delete it from your
>> system immediately. The Ministry of Health of Turkey makes no warranty as
>> to the accuracy or completeness of any information contained in this
>> message and hereby excludes any liability of any kind for the information
>> contained therein or for the information transmission, reception, storage
>> or use of such in any way whatsoever. Any opinions expressed in this
>> message are those of the author and may not necessarily reflect the
>> opinions of The Ministry of Health of Turkey.
>>
>> This e-mail has been scanned for all computer viruses known to us.
>> ------------------------------
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>  --
> WBR
> Maxim aka solomax
>
>
>
>


-- 
WBR
Maxim aka solomax

Reply via email to