Deployment of Component Error

Post any questions regarding Installing or Upgrading Ebase, including problems starting up the Ebase Xi Server or Designer

Moderators: Jon, Steve, Ian, Dave

selbjx
Ebase User
Posts: 22
Joined: Fri Jun 06, 2008 8:35 am

Deployment of Component Error

#1

Postby selbjx » Fri Oct 03, 2008 2:38 pm

Fri Oct 03 11:14:29: Error :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!

Fri Oct 03 11:14:29: Error :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!

Fri Oct 03 11:14:29: Error :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!

Fri Oct 03 11:14:29: Error : Repository database is not same level as
server software - database: version 3.4.0, build 21122007B, software:
version 3.4.0, build 21122007_B

Fri Oct 03 11:14:29: Error : Correct the above problem then restart the
server

Fri Oct 03 11:14:29: Error :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!

Fri Oct 03 11:14:29: Error :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!

Fri Oct 03 11:14:29: Error :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!

Fri Oct 03 11:14:30: Error : LDAP attributes file not specified

Fri Oct 03 11:14:30: UFS Designer server component initialised successfully

Fri Oct 03 11:14:30: FormCacheLoader: start

Fri Oct 03 11:14:31: FormCacheLoader: end

Fri Oct 03 11:15:27: Error : Error detected by the designer server
component:

Fri Oct 03 11:21:54: Error : Message 9001 does not exist

Fri Oct 03 11:21:54: Error : Message 9001 does not exist

Could any one indicate what this error means?

I managed to fix the problem by importing the forms and component from a non live version of the system - however all that we had changed on a component was a field to display only and redeployed - it caused the form to distort, and then afterwards it would not allow us to redeploy - importing over the top was the only fix, thanks.
0 x

ehmd
Ebase User
Posts: 53
Joined: Thu Sep 13, 2007 9:02 am
Contact:

#2

Postby ehmd » Fri Oct 03, 2008 2:46 pm

Fri Oct 03 11:14:29: Error : Repository database is not same level as
server software - database: version 3.4.0, build 21122007B, software:
version 3.4.0, build 21122007_B
You've got a mis-match between the build in the software and the Build stored in your database.

The database shows Build as '21122007B' but the software build is '21122007_B'.

You need to update the database as follows :-

Code: Select all

UPDATE SERVER_DATA SET SERVER_BUILD = '21122007_B'

Regards,


Mark
0 x

selbjx
Ebase User
Posts: 22
Joined: Fri Jun 06, 2008 8:35 am

#3

Postby selbjx » Fri Oct 03, 2008 2:54 pm

ehmd wrote: You've got a mis-match between the build in the software and the Build stored in your database.

The database shows Build as '21122007B' but the software build is '21122007_B'.

You need to update the database as follows :-

Code: Select all

UPDATE SERVER_DATA SET SERVER_BUILD = '21122007_B'
Any idea how this can happen? it had been fine on previous deploys during the week and nothing should have changed - also importing over the forms fixed the problem - seems very strange.
0 x

User avatar
Sarah
Ebase User
Posts: 63
Joined: Fri Sep 07, 2007 2:42 pm
Location: Sandy, UK
Contact:

#4

Postby Sarah » Mon Oct 06, 2008 11:31 am

Please can you confirm which error you mean when you say:
Could any one indicate what this error means?
There are 3 error messages in the extract of the log you have given:
1. Error : Repository database is not same level as server software
2. Error : LDAP attributes file not specified
3. Error : Message 9001 does not exist

If you are asking about the first error, then then ehmd's solution is correct.

The first error cannot be fixed by importing files into the system. The server build setting within the Ebase Repository does not change when importing/exporting projects, forms, elements, etc. This particular error must have been appearing in the server log every time the server has started up since the 21122007_B patch was applied to that system.

I have double-checked all the database scripts for the 21122007_B patch (for Derby, Oracle, SQL Server and MySQL), and they all have the correct "21122007_B" value in them. Therefore, this value must've been updated manually when this instance of Ebase was upgraded, and was simply mis-typed.


If you mean either of the other 2 errors, we'd need to see the full error. Please can you log the problem on the Customer Portal and upload a zipped copy of the entire server log file there, so Ebase Support can investigate.
0 x

selbjx
Ebase User
Posts: 22
Joined: Fri Jun 06, 2008 8:35 am

#5

Postby selbjx » Mon Oct 06, 2008 11:43 am

importing did fix the error and allowed subsequent deployment of this component with error - the other messages have been rectified also. Strange scenario. Ohwell it works anyway

thanks again for your help
0 x


Who is online

Users browsing this forum: No registered users and 60 guests