All Solutions are Gray

Classic Servoy
1

I’m running v4
All solutions are grayed out. I can’t do anything with them.

Just prior to opening servoy I was working on a solution i had just created. When I tried to run it, it was taking forever to bring up the client. I killed servoy and restarted. Now the solution I was working on it gone and all other solutions are gray…

Any ideas?

2

I can’t think of any reason why a solution would disappear.
Never happened to me.

What platform are you on?
Which 4.0.x and build are you running

3

You should find some errors in the log(s). Please check the “.log” file in your workspace’s “.metadata” folder.
Also check for problem markers in the problems view (in Eclipse).
If you still do not find any errors, please check the default Servoy log in the installation dir also.

Please post the errors or attach log file if you are not sure which one is relevant.

4

What JAVA version are you using?

I had the same problem in the past when using Java 6 with update 6.
Update 4 and 5 do not give this problem.
I’m using update 5.

I haven’t tested yet with update 7 (the most recent version)

When I had the problem it was with Servoy 3.5
I’m not using Servoy 4 yet.

5

Here are all of the log files… BTW - running windows xp

servoy_log.txt (80.4 KB)

.service_log.txt (204 Bytes)

6

here is the workspace log

log.txt (78.2 KB)

7

This is something more or less serious and probably has to do with your checkout process.
Nothing I can solve but Servoy should know where to point you to…

8

A solution in your workspace is supposed to be activated when developer starts (the last active solution in your previous development session). In your case I see that there is a problem with that solution - a file describing a script variable holds an illegal value for the variable type (don’t really know how this could have happened - did you modify .obj files in that project manually with a text editor? If not, do you remember what you did with one of the variables in your solution before this problem appeared?). This is why that solution is not activated.

But you should be able to activate other solutions in your workspace (if they have no problems) with right click + activate.
I will improve the solution activating at startup - to try and activate a valid solution if the one that should be activated has problems. Also made some small changes to avoid a NullPointerException that appears in such situations (no active solution) and to have better error reporting so we can identify the solution/variable that causes such problems in the future.

Are you able to activate other solutions? If not, do you see any new stack traces in the “.log” file after trying to activate other solutions?

9

There was a problem during and earlier checkout as well - as Marcel said, because one of the enabled servers on the remote (or developer started) repository was invalid - but that should not have generated too much trouble - just that the table/column information for that server would not be checked out.