Hi guys,
A problem has come up with a solution that has been running beautifully since 2004. I am running 2.2.5 for two reasons: 1) It has been very stable, haven’t needed to add much to it since then and thus no need. 2) Ideally I’d like to have upgraded just in general but the MS SQL Server that stores the Servoy_repository is managed by hospital IT types and that will make if VERY difficult if there are any problems (when I created this I did it with a friend who ran that server). The Servoy server runs from a different building here at Stanford on a Windows XP box.
What I normally do if I want to access or alter the solution is I use Servoy Developer here and point it to the MS SQL Server Servoy Repository. I make my changes, save them and then flush those changes to the clients. A couple of weeks ago I noticed that an opening script wasn’t running correctly from my developer but I wasn’t getting any complaints from the users so I didn’t worry about it too much. Yesterday I had some time and went to take a look. What I found was that method was checking on a form if a particular db column (on that form/table) had a value. The method was choking because it said that the column was unknown. I thought that was weird and went to Designer and clicked on the form when I got the message: “Can’t make tree node for form: SignOutView”. There were no nodes showing at all (see image below) for that form and about 8 others - just a blank square labeled ‘TMP’. Most of them are unused forms (it was my first Servoy solution, OK?) but a number are constantly in use. At the same time I haven’t had any complaints from the users and this solution is in use every day. This is very worrying of course. Does anyone have any experience with this, seen it before? The .log.txt doesn’t record any event and as you can see the ‘Details’ button is greyed out on the message. The other very weird thing that happens with this is if I am on one of these forms I can go to Designer mode but clicking again to go back to browse mode doesn’t work. It just removes/shows the form properties every time you click it. Very concerned so any thoughts or ideas appreciated…
and also if you go to design mode and try to go back you dont get any errors at all in the log file?
Something seems missing or incomplete like the database.
Can you export this solution and import it in another repository?
and also if you go to design mode and try to go back you dont get any errors at all in the log file?
No, no errors when I do that.
Something seems missing or incomplete like the database.
But if that was the case wouldn’t the users on client also be having problems? I thought just now that maybe they were using an earlier release but that’s not the case. They are on the same one that my Developer is on.
Can you export this solution and import it in another repository
I’ll give that a try.
Thanks,
John
Hi Johan,
I’ve imported the solution into another repository (iAnywhere) also 2.2.5. Still get this strange behavior. Partly it is from the opening method that deals with user login. Mine seems to trigger it. I’ve got to play around more with disabling the opening login method and seeing what happens there. But even with the logins that the users use when I go to Designer mode I get this strange result mentioned above where I can’t get out of Designer mode from one of those forms. I can if I go to another form. When I use one of the user logins, enter successfully and go to the method editor WITHOUT going to Designer then the form tree node shows up fine. The method editor in debug mode acts very peculiar because only if I put a break point in the method can I step through the method (after the break point). If I don’t put a break point in then the method runs right through even when I just try to step through it. And as soon as I go to Designer mode I then lose the form tree node. Finally the method that is running on that form chokes every other time on this:
‘forms.SignOutView.foundset.clearFoundSet()’
It first chokes when there are records present with the message ‘java.lang.NullPointerException’. Then, if you run it again, there are no records visible and it runs fine.
Any thoughts? If I try and import it into a later version of a Servoy in a separate repository would that cause any problems for the existing version (that is at least running OK for the clients)? That should be OK shouldn’t it? Would there be anything to gain from that?
so if that exported and imported solution still have those problems
is it possible that you create a case with that solution so that we can import it and look at it?
Should I do it with data? or just the solution?
if you import it completely blank repo and also data (let it create the tables) do you have the problem then?
If so then without data that would be way easier…
OK. I’ll try it tomorrow. And otherwise I’ll create a minor set of data to go along with it. Thanks,
John
