After installing a newer version of NW Studio (2004S/700)from an older 640 SP11, the startup of the studio is very slow. In the taskmanager I see that sapide.exe is always started twice, one of those consuming 99% CPU time, other nearly idlde. This seems strange to me. An ideas on that?
the log contains following:
Command-line arguments: -os win32 -ws win32 -arch x86 -feature com.sap.java.ide -consolelog -data C:\projects\SO\dev\dev C:\j2sdk1.4.2_06\bin\javaw.exe
-DallUserDir='C:\Documents and Settings\All Users\Application Data'
-cp C:\Program Files\SAP\IDE\IDE70\eclipse\SapStartup.jar com.sap.ide.eclipse.startup.Main
-showsplash C:\Program Files\SAP\IDE\IDE70\eclipse\SapIde.exe -showsplash 600
-data C:\projects\SO\dev\dev -data C:\projects\SO\dev\dev -install file:C:/Program Files/SAP/IDE/IDE70/eclipse/
I just encountered a similar problem after updating my local Developer Workplace to NW04 SP15 (from SP14). There were two Sapide.exe processes, one consuming close to 100% CPU usage, and no splash screen would appear. After a long time NWDS would finally start, but ending the Sapide.exe process would make it start faster.
I found out that a file called "buildnum.txt" was missing after patching. I added the file from a previous SP and changed the "Build: XXXXXXXXXXXX" line to contain the new build number (it can be found in the About box), and now NWDS starts normally again.
On another note, another file (.eclipseproduct) was also missing, causing an error during the install. Adding the file from the previous SP stopped the error from happening.