export .bsv from 4.8 import into 5.1 problem

nickh

Hi all,

I have exported my .bsv from 4.8 and imported into 5.1.

I have a new PC with awareim and mysql installed as default.
Effectively nothing has been changed except the database names.

everything works fine except any object i have modified fail.
new objects fail and modified objects fail with the following message.

java.lang.numberformatexception: null

tford

Effectively nothing has been changed except the database names.

Don't know what you mean by this.
'

nickh

I am setting up a copy of my system for a colleague.

I have v 4.8

The new system for my colleague is v 5.

I have exported my bsv file and imported into the v 5 system.

everything works fine in production.

I make changes to the v5 version of the system...when testing these changes, any object I changed crashes with the described error. Interaction with any objects I have not altered continue to work OK.

It appears as though there is some environmental incompatibility regarding any changes that I apply.

Is the problem clear?

tford

I really don't know what would cause this, but trying to help with questions that might lead to better understanding the steps.

Did you transfer the data also or just imported the BSV?

When you "imported" the BSV, was it into newly created V5 BSV? Did you click Import option in the V5 Config Tool?

nickh

Tom,

Thanks We have transferred to another environment and are still experiencing the same issues.

Now working with 5.1 Developers Edition.

Imported BSV and Imported the Same Database from previous version.
Any change we make to the Business Space that affects tables will cause the same "null" reference failure. Any cosmetic changes appear fine.

If we make the changes on the original Aware System then export and import all works fine. This just dosn't seem to make sense.

aware_support

We received a support ticket for this problem, but we need additional information in order to process this request:

Please e-mail the following to support@awareim.com:

Your BSV file with the description of steps required to reproduce the problem
The output of Tomcat and Aware IM Server when the problem happens

aware_support

This is the case of using an obsolete 3.0 UI - this UI is not supported any more.