Hi
How do I resolve this error when trying to test an application:
Exception changing business space version Aware IM server encountered the following error .Error persisting business space Coul not find stored procedure '#jtds00003'.
Help appreciated.
Error Message: Exception changing business space version
-
- Site Admin
- Posts: 65
- Joined: Sun Jan 02, 2005 4:36 am
- Contact:
I started with a fresh database (i.e. recreated BASDB BASBDTEST) and it resolved the problem. However, this would not be ideal if it was aproduction database, which fortunately it was not.
Any plans to move the application out of the production database in a future version? From my perspective it mitigates the risk somewhat.
Thanks.
Any plans to move the application out of the production database in a future version? From my perspective it mitigates the risk somewhat.
Thanks.
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
That's exactly what I do.
From my perspective then, it would be good if this design be reconsidered for future versions.
Or maybe even open it up for debate - there may be other issues I have not considered - like expensive licensing on the part of Oracle / Microsoft - cause they may require another connection to a new database.
From my perspective then, it would be good if this design be reconsidered for future versions.
Or maybe even open it up for debate - there may be other issues I have not considered - like expensive licensing on the part of Oracle / Microsoft - cause they may require another connection to a new database.
-
- Posts: 116
- Joined: Sat Oct 25, 2008 3:16 pm
Error persisting business Space
This problem results when:Exception changing business space version Aware IM server encountered the following error .Error persisting business space Coul not find stored procedure '#jtds00003'.
The length of an Attribute is changed and Data truncation could occur. For eg: Length of sDescription = 50 and is changed to sDescription=10 for example.
Should you have a published bsv, it warns you that data may be truncated occur and should you publish the modification it will most likely clear all data from the corresponding field in the Live DB, however when you have Data in the Test DB that could be truncated, and you try to test it returns the Above mentioned Error. Hence when you drop all initial data it will resolve the problem
Hope this helps all who may come across this error.