[Hollis Inman]

This has used to work. I have six people in a group and i’m trying to add one more.

I’ve finished setting up our development environment and am sharing the ‘MyEclipse 8.6 pulse’ setup with you. You can follow the simple instructions below to quickly get up and going allowing us to collaborate on our development.

Thanks,
Hollis Inman

——————————————————————————–

You’ve been invited to use a shared MyEclipse configuration. To use this configuration, click the following link:

Run the MyEclipse 8.6 web-based installer
Your software will automatically be installed and configured for you!
If you have any shared components already installed, they will be reused.

Manual Install: If desired, you can manually install the software following these steps:

Download the MyEclipse 8.6 installer or start MyEclipse 8.6 if it is already installed.
After installing, use the Accept Invite action from the Collaboration tab of the Software and Workspace Center.
Enter 5215-fEe-3347 as your Invitation ID and thats it!
Need Help? Visit the MyEclipse forums online.

[support-joy]

Hollis Inman,

Sorry to hear you are running into this issue. Could you answer below queries to help me investigate further –
1. What is the OS and version of the team member who is unable to install using pulse invite?
2. Is he on a restricted network / firewall / proxy?
3. Can you attach a screenshot of the issue he is facing to help me get a visual
4. Also copy and paste the contents of the error here
5. You must be using an email-id to send the pulse invite. Could you use the same invite email to install on a different system? If he is able to install on a different system, it means that there is a restricted network which is prohibiting the user to connect to the server. Please investigate in these lines
6. Please ping http://www.myeclipseide.com and http://www.poweredbypulse.com from the user’s system
7. Also attach a tracert to http://www.myeclipseide.com from the user’s system to help me investigate

[Tony Higgs]

Windows XP service pack 3

not sure about restricted network / firewall / proxy

we do not have another systems to try this on.

F:\>ping http://www.myeclipseide.com

Pinging myeclipseide.com [209.135.140.138] with 32 bytes of data:

Reply from 209.135.140.138: bytes=32 time=44ms TTL=45
Reply from 209.135.140.138: bytes=32 time=44ms TTL=45
Reply from 209.135.140.138: bytes=32 time=44ms TTL=45
Reply from 209.135.140.138: bytes=32 time=44ms TTL=45

Ping statistics for 209.135.140.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 44ms, Average = 44ms

F:\>ping http://www.poweredbypulse.com

Pinging proxy.poweredbypulse.com [184.73.82.165] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 184.73.82.165:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

F:\>tracert http://www.poweredbypulse.com

Tracing route to proxy.poweredbypulse.com [174.129.75.215]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.171.22.2
2 <1 ms <1 ms <1 ms 172.16.168.181
3 2 ms 2 ms 2 ms dv-006-fw01-oir-fl01.tnet.state.tn.us [10.122.25
3.121]
4 4 ms 4 ms 4 ms 10.122.253.17
5 12 ms 12 ms 13 ms host.lightcore.net [208.110.240.33]
6 13 ms 14 ms 13 ms bb-nlrkargp-jx9-01-ae0.core.centurytel.net [206.
51.69.9]
7 25 ms 25 ms 25 ms bb-atlngamv-jx9-01-ae5-0.core.centurytel.net [20
6.51.69.197]
8 36 ms 46 ms 36 ms bb-rcmtncxa-jx9-01-ae3.0.core.centurytel.net [20
8.110.248.77]
9 37 ms 36 ms 36 ms bb-rcmtncxa-jx9-02-ae0.core.centurytel.net [208.
110.248.66]
10 45 ms 45 ms 45 ms bb-asbnvacy-jx9-02-ae3.0.core.centurytel.net [20
8.110.248.170]
11 45 ms 46 ms 45 ms bb-asbnvacy-jx9-01-ae0.0.core.centurytel.net [20
8.110.248.117]
12 46 ms 45 ms 45 ms equinix02-iad2.amazon.com [206.223.115.35]
13 46 ms 60 ms 46 ms 72.21.220.45
14 46 ms 46 ms 45 ms 72.21.222.149
15 46 ms 46 ms 46 ms 216.182.224.83
16 * * ^C
F:\>tracert http://www.myeclipseide.com

Tracing route to myeclipseide.com [209.135.140.138]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.171.22.2
2 <1 ms <1 ms <1 ms 172.16.168.181
3 2 ms 2 ms 2 ms dv-006-fw01-oir-fl01.tnet.state.tn.us [10.122.25
3.121]
4 4 ms 4 ms 4 ms 10.122.253.17
5 11 ms 11 ms 11 ms 12.94.72.221
6 15 ms 15 ms 15 ms cr81.brhal.ip.att.net [12.122.151.22]
7 17 ms 19 ms 19 ms cr2.attga.ip.att.net [12.122.151.33]
8 16 ms 15 ms 15 ms 12.122.117.121
9 15 ms 15 ms 15 ms ae15.edge5.atlanta2.level3.net [4.68.62.225]
10 15 ms 15 ms 15 ms vlan52.ebr2.Atlanta2.Level3.net [4.69.150.126]
11 44 ms 37 ms 37 ms ae-3-3.ebr2.Chicago1.Level3.net [4.69.132.73]
12 43 ms 43 ms 43 ms ae-4-4.car2.StLouis1.Level3.net [4.69.132.189]
13 54 ms 45 ms 43 ms ae-11-11.car1.StLouis1.Level3.net [4.69.132.185]

14 43 ms 42 ms 43 ms RIVER-CITY.car1.StLouis1.Level3.net [4.53.160.10
]
15 44 ms 44 ms 44 ms 216.91.36.210
16 44 ms 44 ms 46 ms r-1.core04.stl.rosehosting.com [206.196.99.250]

17 44 ms 44 ms 44 ms myeclipseide.com [209.135.140.138]

Trace complete.

F:\>

Attachments:

You must be logged in to view attached files.

[support-tony]

Hollis,

We had an outage during the time you may have been trying, so please try again. If it fails for you again, please submit a support bundle or send in your logs.

[Author]

Posts