Eclipse.Net 31/01/2008 Release issues

[Nexus-6]

Hi,

Is anyone else having problems with the install of the Eclipse.Net release that was issued yesterday?

This new version fixes the squid proxy issue + other "bugs", but the install insists you remove the previous version, and towards the end of the installation it throws up an error message "There was a problem upgrading your database, Please check the error log for more details". Even a clean install on a server with no previous Eclipse database produces the same message (using SQL 2005 Express for the database - as per their CD).

[Gerry]

I showed my colleague this thread as he's been trying to get Eclipse.NET working too. He says it might work if you stop the SQL service first and/or compress the DB.

[Ric_]

It just worked for me... surprising considering the amount it doesn't work!

I was a little annoyed that I had to reboot the server mind after the uninstallation part (none of the previous upgrades did this).

[john]

Sorry to be a random here, but whats it like for server resource useage? I have the specs for it and can read them, but there flipping high requirements really, my SharePoint 2007 box is the only box I have that has a similar spec to there needs, and if its purchased it wont be living with my SharePoint box. Does it really need 4gb of ram and 2.0ghz dual core CPU (Think it was 2ghz)

[j.mills]

For what it's worth, Eclipse.Net is running okay on our server (performance-wise - bugs and problems a different story). It's a 3.2GHz P4 with 2GB RAM. Task Manager is showing the SQLServer (that comes as part of Eclipse) hogging 148MB, but scarcely any CPU time.

[Ric_]

Just a note... I use anonymous access with Eclipse (to allow usage from a couple of non-domain-member OPAC machines). The upgrade re-enables the authentication!

@john: Eclipse doesn't need massive resources to run... the database is ridiculously big though.

[meastaugh1]

As Ric said, Eclipse isn't too bad for resources. I did have an issue with the scheduler endlessly consuming resources, but that was fixed.

I have it running on my WSS box, although admittedly that isn't as resource consuming as MOSS.