When I try to send Emotion Sounds it gives me a strange error, "The Custom Emotion Sounds feature is currently disabled. The server may be under maintenance, please try again later."

     I can send a few sounds, but not many. I am using the new 2009 Beta, but I think they used to work fine when I first installed it... Is there a fix for this, is the server actually being fixed or is there something wrong with the current release?

Also, sorry if this issue has been addressed already, I have tried searching, but found nothing.

New beta? Windows Live Messenger is final now. What version are you using? Help>About Messenger.

got the same problem m8

quote:

---

Originally posted by Moh Zayadi
New beta? Windows Live Messenger is final now. What version are you using? Help>About Messenger.

---

quote:

---

Originally posted by Joscpe

quote:

---

Originally posted by Moh Zayadi
New beta? Windows Live Messenger is final now. What version are you using? Help>About Messenger.

---

I mean the 2009 beta. Was that just released?
"Version 2009 (Build 14.0.8064.206)"

---

quote:

---

Originally posted by djdannyp

quote:

---

Originally posted by Joscpe

quote:

---

Originally posted by Moh Zayadi
New beta? Windows Live Messenger is final now. What version are you using? Help>About Messenger.

---

I mean the 2009 beta. Was that just released?
"Version 2009 (Build 14.0.8064.206)"

---

It's not a beta anymore, it's a final version.  It is the latest version, yes

---

That is a Plus! feature, not a WLM one. Some users reported the same issue at the spanish forum.

quote:

---

Originally posted by robert_dll
That is a Plus! feature, not a WLM one. Some users reported the same issue at the spanish forum.

---

quote:

---

Originally posted by Joscpe
Also, sorry if this issue has been addressed already, I have tried searching, but found nothing.

---

code:

---

http://shoutbox.menthix.net/showthread.php?tid=87660

---

code:

---

http://sounds.msgplus.net/

---

quote:

---

Originally posted by Joshua

quote:

---

Originally posted by Joscpe
Also, sorry if this issue has been addressed already, I have tried searching, but found nothing.

---

code:

---

http://shoutbox.menthix.net/showthread.php?tid=87660

---

Really, you should search properly before posting new posts, check out

code:

---

http://sounds.msgplus.net/

---

for the server (maintainence) updates.

---

I and other people haven't been able to use sounds for a few days now either.

I'm having the same problems.

The random sound feature still works though which is odd because it wouldn't work if the servers were down, and the sounds website says everything is fine. http://sounds.msgplus.net/

for those of you who are having problems, can you try doing this:
Start > Run > cmd
in the black command prompt window, type these 2 commands, and paste the results here

code:

---

ping 67.15.135.18
tracert 67.15.135.18

---

code:

---

Tracing route to ev1s-67-15-135-18.theplanet.com [67.15.135.18]
over a maximum of 30 hops:

1     *        *        *     Request timed out.
2    11 ms    12 ms     9 ms  blk-224-248-1.eastlink.ca [24.224.248.1]
3    12 ms     8 ms     9 ms  hlfx-asr1.eastlink.ca [24.222.226.85]
4    11 ms    11 ms    11 ms  hlfx-br1.eastlink.ca [24.222.79.205]
5    19 ms    21 ms    18 ms  xe-11-0-0.bar2.Boston1.Level3.net [4.79.2.89]
6    23 ms    25 ms    26 ms  ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
7    24 ms    35 ms    34 ms  ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
8    28 ms    49 ms    53 ms  ae-64-64.ebr4.NewYork1.Level3.net [4.69.134.113]
9    63 ms    71 ms    58 ms  ae-3.ebr2.Dallas1.Level3.net [4.69.137.121]
10    60 ms    70 ms    72 ms  ae-62-62.csw1.Dallas1.Level3.net [4.69.136.138]
11   167 ms   223 ms   220 ms  ae-14-69.car4.Dallas1.Level3.net [4.68.19.6]
12    60 ms    59 ms    80 ms  THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]
13    74 ms    73 ms    77 ms  et1-1.ibr02.hstntx1.theplanet.com [70.87.253.54]
14    72 ms    77 ms    73 ms  et1-3.ibr02.hstntx2.theplanet.com [70.87.253.58]
15    88 ms    70 ms    73 ms  po2.car12.hstntx2.theplanet.com [74.55.252.210]
16    76 ms     *       84 ms  ev1s-67-15-31-198.theplanet.com [67.15.31.198]
17     *        *       79 ms  ev1s-67-15-135-18.theplanet.com [67.15.135.18]

Trace complete.

Pinging 67.15.135.18 with 32 bytes of data:

Reply from 67.15.135.18: bytes=32 time=85ms TTL=48
Reply from 67.15.135.18: bytes=32 time=95ms TTL=48
Reply from 67.15.135.18: bytes=32 time=72ms TTL=48
Reply from 67.15.135.18: bytes=32 time=74ms TTL=48
Reply from 67.15.135.18: bytes=32 time=74ms TTL=48
Reply from 67.15.135.18: bytes=32 time=74ms TTL=48
Reply from 67.15.135.18: bytes=32 time=79ms TTL=48
Reply from 67.15.135.18: bytes=32 time=83ms TTL=48
Reply from 67.15.135.18: bytes=32 time=75ms TTL=48
Request timed out.
Request timed out.
Reply from 67.15.135.18: bytes=32 time=75ms TTL=48
Reply from 67.15.135.18: bytes=32 time=72ms TTL=48
Reply from 67.15.135.18: bytes=32 time=87ms TTL=48
Reply from 67.15.135.18: bytes=32 time=76ms TTL=48
Reply from 67.15.135.18: bytes=32 time=74ms TTL=48
Reply from 67.15.135.18: bytes=32 time=86ms TTL=48
Reply from 67.15.135.18: bytes=32 time=75ms TTL=48
Reply from 67.15.135.18: bytes=32 time=77ms TTL=48
Reply from 67.15.135.18: bytes=32 time=74ms TTL=48

Ping statistics for 67.15.135.18:
    Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 72ms, Maximum = 95ms, Average = 78ms

---

code:

---

Pinging 67.15.135.18 with 32 bytes of data:

Reply from 67.15.135.18: bytes=32 time=69ms TTL=47
Reply from 67.15.135.18: bytes=32 time=69ms TTL=47
Reply from 67.15.135.18: bytes=32 time=69ms TTL=47
Reply from 67.15.135.18: bytes=32 time=67ms TTL=47

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

C:\>tracert 67.15.135.18

Tracing route to ev1s-67-15-135-18.theplanet.com [67.15.135.18]
over a maximum of 30 hops:

  1     3 ms     1 ms     4 ms  192.168.1.1
  2    14 ms     8 ms    18 ms  10.160.0.1
  3    13 ms     7 ms    10 ms  24.215.3.130
  4    16 ms    19 ms    14 ms  216.191.57.177
  5    32 ms    31 ms    23 ms  eqix.chcg.twtelecom.net [206.223.119.36]
  6    49 ms    56 ms    65 ms  66.192.240.58
  7   256 ms   203 ms    75 ms  po1.car12.hstntx2.theplanet.com [74.55.252.170]

  8    72 ms    66 ms    67 ms  ev1s-67-15-31-198.theplanet.com [67.15.31.198]
  9    69 ms     *       64 ms  ev1s-67-15-135-18.theplanet.com [67.15.135.18]

Trace complete.

---

quote:

---

Originally posted by Joshua

quote:

---

Originally posted by Joscpe
Also, sorry if this issue has been addressed already, I have tried searching, but found nothing.

---

code:

---

http://shoutbox.menthix.net/showthread.php?tid=87660

---

Really, you should search properly before posting new posts, check out

code:

---

http://sounds.msgplus.net/

---

for the server (maintainence) updates.

---

This is what I get

code:

---

Pinging 67.15.135.18 with 32 bytes of data:
Reply from 67.15.135.18: bytes=32 time=135ms TTL=44
Reply from 67.15.135.18: bytes=32 time=130ms TTL=44
Reply from 67.15.135.18: bytes=32 time=135ms TTL=44
Request timed out.

Ping statistics for 67.15.135.18:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 130ms, Maximum = 135ms, Average = 133ms

C:\Users\Ramy>tracert 67.15.135.18

Tracing route to ev1s-67-15-135-18.theplanet.com [67.15.135.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms   334 ms   211 ms  10.7.180.1
  3   176 ms   114 ms    91 ms  herm-t2cam1-b-ge92.network.virginmedia.net [80.3
.34.129]
  4    91 ms   196 ms   206 ms  hers-t3core-1a-ge-010-0.network.virginmedia.net
[80.3.33.34]
  5   265 ms   268 ms   172 ms  pop-bb-b-so-110-0.network.virginmedia.net [213.1
05.175.41]
  6   177 ms   252 ms   201 ms  pop-bb-a-ae0-0.network.virginmedia.net [213.105.
174.229]
  7   431 ms   217 ms   170 ms  195.50.91.69
  8   152 ms   429 ms   269 ms  et1-1.ibr02.hstntx1.theplanet.com [70.87.253.54]

  9   304 ms   323 ms   356 ms  et1-3.ibr02.hstntx2.theplanet.com [70.87.253.58]

10   421 ms   438 ms   340 ms  po2.car12.hstntx2.theplanet.com [74.55.252.210]

11   221 ms   247 ms   348 ms  ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]

12   286 ms   288 ms   409 ms  ev1s-67-15-135-18.theplanet.com [67.15.135.18]

Trace complete.

---

I've actually had this problem for a couple months now

quote:

---

Originally posted by Joscpe

quote:

---

Originally posted by Joshua

quote:

---

Originally posted by Joscpe
Also, sorry if this issue has been addressed already, I have tried searching, but found nothing.

---

code:

---

http://shoutbox.menthix.net/showthread.php?tid=87660

---

Really, you should search properly before posting new posts, check out

code:

---

http://sounds.msgplus.net/

---

for the server (maintainence) updates.

---

Well this board doesn't have a great searching system, so I may have over looked something... I don't see why you're being rude here.

quote:

---

Not being rude, just asking in a different manner.

---

---

i'm having difficulty as well, here's what i got.

Pinging 67.15.135.18 with 32 bytes of data:
Reply from 67.15.135.18: bytes=32 time=54ms TTL=53
Reply from 67.15.135.18: bytes=32 time=53ms TTL=53
Reply from 67.15.135.18: bytes=32 time=53ms TTL=53
Reply from 67.15.135.18: bytes=32 time=53ms TTL=53

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

Tracing route to ev1s-67-15-135-18.theplanet.com [67.15.135.18]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms     8 ms  68.85.131.177
  4    12 ms    10 ms    11 ms  be-50-ar01.area4.il.chicago.comcast.net [68.87.2
30.53]
  5    11 ms    12 ms    11 ms  pos-0-6-0-0-cr01.chicago.il.ibone.comcast.net [6
8.86.90.53]
  6    32 ms    32 ms    32 ms  pos-0-6-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.85.62]
  7    52 ms    47 ms    49 ms  pos-1-12-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.157]
  8    46 ms    50 ms    47 ms  theplanet-cr01.dallas.tx.ibone.comcast.net [68.8
6.88.50]
  9    51 ms    52 ms    52 ms  et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]

10    54 ms    52 ms    52 ms  po1.car12.hstntx2.theplanet.com [74.55.252.170]

11    52 ms    52 ms     *     ev1s-67-15-31-198.theplanet.com [67.15.31.198]
12    54 ms    62 ms    53 ms  ev1s-67-15-135-18.theplanet.com [67.15.135.18]

Trace complete.

I don't have this problem but I get so many Request Timed Outs'
Microsoft Windows [Version 6.0.6001]
Copyright 2006 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>ping 67.15.135.18

Pinging 67.15.135.18 with 32 bytes of data:
Reply from 67.15.135.18: bytes=32 time=367ms TTL=51
Reply from 67.15.135.18: bytes=32 time=351ms TTL=51
Reply from 67.15.135.18: bytes=32 time=350ms TTL=51
Reply from 67.15.135.18: bytes=32 time=353ms TTL=51

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

C:\Windows\system32>tracert 67.15.135.18

Tracing route to ev1s-67-15-135-18.theplanet.com [67.15.135.18]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  192.168.1.1
  2    15 ms     *       11 ms  219.93.218.177
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.

Trace complete.

does the sound server use a specific port that may be getting blocked by other applications?

It has been happening to me too. But it is weird because it only happens with new sounds I've recorded, the old ones are sent fine, i'm just having trouble with new ones.

The soundserver is being worked on, should be fixed soon now