[Riyad Kalla]

1. It’s possible that Pulse is trying *really* hard to have you avoid the redownload each time by detecting the existing Common dir and re-using it. Can you check your user.home directory for any .pulse2 files? Also if you are on Vista double check under <User Home>\AppData\Local\Genuitec for Pulse install/configuration files that it might keep picking update data up from incorrectly.

2. Ahh good deal, the 443 > 80 fallback occurs cause a secure HTTPS connection was not possible, but if you are seeing the optional component listings, then all is well and if you don’t see a “Pulse Services” update, you have 7.0.1

3. So in a new workspace, the behavior it eventually correct, but in an old one, it goes stupid and cannot get the component listings like UML2 and so on? Very strange…

4. Yes 7.0.1 is the actual bundled version on the download page. It was a micro-update that we released right after we did the 7.0 update.

5. Separate drives, that is a known issue we are working on fixing in Pulse. Right now if you install to a different drive than your main windows boot drive, the uninstaller doesn’t work, which might explain why you are getting old copies of Pulse stuff laying around.

[Marc]

@support-rkalla wrote:

1. It’s possible that Pulse is trying *really* hard to have you avoid the redownload each time by detecting the existing Common dir and re-using it. Can you check your user.home directory for any .pulse2 files? Also if you are on Vista double check under <User Home>\AppData\Local\Genuitec for Pulse install/configuration files that it might keep picking update data up from incorrectly.

Found .pulse2.locator in my home directory. Should I delete that?

@support-rkalla wrote:

2. Ahh good deal, the 443 > 80 fallback occurs cause a secure HTTPS connection was not possible, but if you are seeing the optional component listings, then all is well and if you don’t see a “Pulse Services” update, you have 7.0.1

Even if the version shows up as 7.0 in the About screen?

@support-rkalla wrote:

3. So in a new workspace, the behavior it eventually correct, but in an old one, it goes stupid and cannot get the component listings like UML2 and so on? Very strange…

That is correct.

@support-rkalla wrote:

5. Separate drives, that is a known issue we are working on fixing in Pulse. Right now if you install to a different drive than your main windows boot drive, the uninstaller doesn’t work, which might explain why you are getting old copies of Pulse stuff laying around.

So the only problem doing that is when uninstalling? Is there a way to manually change the location of the Common folder, i.e. post-install?

[Marc]

More fun…

I installed v7.0.1 again. I selected the same configuration as above (Common in d:\Genuitec\Common and MyEclipse in D:\Genuitec\MyEclipse 7.0). The installer screwed up again and put the Common folder in C:\Program Files\Genuitec\Common, but the myecilpse.ini file in d:\genuitec\MyEclipse 7.0\ looks like this:

-startup
../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
--launcher.library
../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731
-clean
-configuration
configuration
-vm
D:\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll
-vmargs
-Xmx512M
-XX:MaxPermSize=192M

Notice that it thinks the Common folder is in D:\Genuitec? That’s messed up.

[Riyad Kalla]

Ah! It’s the .pulse2.locator file that keeps causing this screwup, it defines the base install location for Pulse and that’s why it keeps selecting that dir.

I don’t know if you have any patience left to try this again (I don’t blame you if you don’t), but if you uninstalled MyEclipse and did:

1. Erase all .pulse* files and directories under <user.home>
2. Erase the D:\Genuitec and C:\Program Files\Genuitec directories
3. Re-run the installer

If that doesn’t work, I’m going to hang myself…

[Marc]

It gets even stranger…

I tried it again, exactly as you had outlined. During the install, I set the application folder to D:\Genuitec\MyEclipse 7.0, and the Common folder to D:\Genuitec\Common. Here’s what I ended up with:

C:\Program Files\Genuitec\Common\
C:\Program Files\Genuitec\Common\configuration
C:\Program Files\Genuitec\Common\logs
C:\Program Files\Genuitec\Common\properties
C:\Program Files\Genuitec\Pulse Explorer
D:\Genuitec\Common\binary
D:\Genuitec\Common\configuration
D:\Genuitec\Common\features
D:\Genuitec\Common\plugins
D:\Genuitec\MyEclipse 7.0

[Ton Huisman]

Hm, guess we are going to have to do without Riyad, pitty us 🙁

[Marc]

I would say that I stumped them, but I think that, technically, they stumped themselves!

[Ton Huisman]

This obviously wasn’t as light an undertaking as they thought…

[steve hodge]

Sometimes with proxies set for forward and reverse proxy config (for VPN’s maybe) you get strange headers like the one below. What happens is that the forward proxy may fail for NTLM and work for Basic. (We actually do Basic authentication, despite the strange NTLM first configuration below). In the case of Pulse, the failure of NTLM is messing up the config files in Pulse and Eclipse (org.eclipse.core.net.prefs). At least I think that is what is happening. Pulse changed the org.eclipse.core.net.prefs from “Basic” to “Use System Configuration” while I had the file open in an editor.

HTTP/1.0 407 Proxy Authentication Required
Date: Fri, 12 Aug 2005 16:30:18 GMT
Content-Length: 257
Content-Type: text/html
Server: NetCache appliance (NetApp/5.6.1D25DEBUG3)
Proxy-Authenticate: NTLM
Proxy-Authenticate: Basic realm=”*************”

<HTML>
<HEAD><TITLE>407 Proxy Authentication Required</TITLE></HEAD>

[steve hodge]

This is a serious problem. Please, please put every effort to fix it or offer a version without Pulse (where we can use the standard eclipse update). It has made myEclipse frustrating to the point that i am ready to give up on it. Other folks here have already given up.

[Riyad Kalla]

Guys the additional information has been very helpful, at this point the bug reports and communication logs have all gone back to the Pulse team for evaluation/integration into Pulse. I’m sorry for the delay in getting updates to you, we are working as fast as we can.

[Riyad Kalla]

MWThomas, I was on the verge of smashing my hand in my desk drawer until I asked the installer team why this was happening, and as it turned out this is *known* behavior. To remove the confusion of “what’s Pulse?!” from MyEclipse users, when MyEclipse installs, it lays down Pulse quietly to the default app location (C:\Program Files) without pestering the user.

You can *manually* get this stuff to all install to a single location by uninstalling everything, updating the pulse2-locator file to point at the base dir you want and re-running the installer. This will put Pulse and MyEclipse into that dir for you.

God I wish I had dug this up earlier, I’m really sorry about that.

[Ton Huisman]

Ah, we get to keep Riyad. That’s good 😀 😉

Not so good that the installer guys took the liberty of ‘laying it down quietly’ to ease some ‘pain’. The same as assumptions, they always come back and bite you!

HTH
Ton

[jrmeyer_aspecta]

Hi,
it took some time until I could try the solutions but now I’m glad to confirm that the 2. solution, posted by support-rkalla on 22/01/2009-06:32PM worked for me.
Thank you and best regards,
Jochen..

[Marc]

@support-rkalla wrote:

You can *manually* get this stuff to all install to a single location by uninstalling everything, updating the pulse2-locator file to point at the base dir you want and re-running the installer. This will put Pulse and MyEclipse into that dir for you.

Thanks for the solution. I am going to try it as soon as I figure out where the pulse2-locator file is …any help there?

@jrmeyer_aspecta wrote:

jrmeyer, you said you did this already. How did you go about it?

[Author]

Posts