Still trying to migrate to 3.5.1: invalid identifier error

[Thorsten Hohage]

Hi,

after the "official" response from Ruslan I want to add some remarks,  
base on my personal experience especially with RB and Valentina

On 2008-01-22, at 04:27, Robert Nichols wrote:

> Still working on bringing a 3.0 config (v4rb, vserver, vstudio, mac  
> osx) up to date . I've made things work as far as 3.3, but then  
> tried 3.5.1.
>
> With 3.5.1, I get the following error:
>
> 22:06:49.088182 (4028125184): (14) ERROR 0x82513: An invalid  
> identifier (0x0) was specified while processing client request.
>
> Is it choking on something in the sql statement?

1.	Yes, and you should check your table, columns, ... definitions  
really carefully first. It was possible to use accented chars in  
identifier names for some versions and it was possible to "import" the  
names. There are several version of Valentina out there that work (on  
the first view) with these names. But during the last releases these  
error are not "overseen" by Valentina anymore.

2.	Check all your strings you send to the server. I encountered issues  
with worng encoded strings, RB trying to send.

3.	There are some cases, where "defect values" (like really wrong  
datetimes) are tolerated by V4RB/Valentina but during the last version  
these "issues" are fixed, so they might pop up now.

I debugged through all my code to find calls to tables which then  
contains these "defect values", after fixing these values everything  
becomes fine for me. IMHO these values was imported from mySQL and not  
entered directly.



> Also, vStudio for mac 3.5.1 won't even launch on my machine. 3.5,  
> also won't launch.  3.3 launches but can't complete a clone.

Additional to Ruslan suggestion you should remove ALL files related to  
VStudio, including Preferences, ... (perhaps save them before). For me  
some updates caused more issues and these are related to two different  
points

a)	Wrong rights on the LIbrary/VServer_.../... folders for my user /  
setup

b)	Issues in the databases, especially the master.vdb. Sometimes it  
was necessary to remove ALL these db's from the folder (make  
backups!!!), check the rights, start server and VStudio


Furthermore in some rare situations VStudio try to open last openend  
(local) db's even when preferences say it shouldn't. When such a local  
opened db is damaged / have only slightly issues VStudio won't open.  
So a last try would to rename / move all the local openend db's and  
see what happened.


> Are others seeing these behaviours?

Yes.

But in most cases it turned out, that the issues was due to imported  
data, issues with rights and so on and it was all necessary to fix,  
beside migration issues. And furthermore regarding the last updates,  
they was all worth the work I need to do to solve issues.

Even if this email may sound different, I currently serviced several  
customers with custom applications and only few of them had few of the  
issues, it was not allways for all customers - most of the migrations  
was just install and restart.


regards

Thorsten Hohage
--
objectmanufactur.com - Hamburg,Germany