OpenESignForms / openesignforms

Open eSignForms is the first open source SaaS web contracting platform
https://open.esignforms.com
107 stars 50 forks source link

Failed to find the deployment id #180

Closed vovkanaz closed 7 years ago

vovkanaz commented 7 years ago

2017-07-04 11:54:07,779 DEBUG (OpenESignForms) Add provider BC using class org.bouncycastle.jce.provider.BouncyCastleProvider at JCE slot 10 2017-07-04 11:54:07,779 DEBUG (OpenESignForms) SecureRandom: DEBUG starting random with default algorithm and provider 2017-07-04 11:54:07,780 INFO (OpenESignForms) SecureRandom: Created SecureRandom with algorithm: SHA1PRNG; provider: SUN version 1.8 2017-07-04 11:54:08,073 DEBUG (OpenESignForms) SecretKeyGenerator: AES KeyGenerator provider = BC version 1.57 with keysize=256 2017-07-04 11:54:08,301 INFO (com.esignforms.open.db.ConnectionPools) Creating connection pool: esf; type: postgresql; maxConnections: 10; maxIdleMinutes: 10 2017-07-04 11:54:08,309 INFO (com.esignforms.open.db.ConnectionPool) makeConnection(esf) - Creating database connection to db postgresql 2017-07-04 11:54:08,367 INFO (OpenESignForms) The database has been initialized. 2017-07-04 11:54:08,386 ERROR (com.esignforms.open.admin.BootService) loadDeployId() - Failed to find the deployment id Hi all!!! Can you help us resolve this issue? Tomcat 8.5.13, open-esignForms latest, postgresql-9.2.4/ Thank you!

OpenESignForms commented 7 years ago

If you can discuss your questions in the forums (https://groups.google.com/forum/#!forum/openesignformsdev) before entering an issue for developers, we appreciate it because few people will review tickets than the forums.

That said, did you do the 'rundbsetup' steps to initialize the database? After creating a new set of DB tables, you must initialize it so it can create deployment information, keys, the initial 'super admin' user, etc. https://github.com/OpenESignForms/openesignforms/wiki/InstallationUsingVaadin7#create-the-database

OpenESignForms commented 7 years ago

For lack of any update, assuming this has been resolved.