Bug 7540 – User experiencing Rhapsody issues and receiving error

Bug 7540 - User experiencing Rhapsody issues and receiving error

Summary:

User experiencing Rhapsody issues and receiving error

Status:	CLOSED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	Rhapsody
Version:	unspecified
Platform:	PC All

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-03-17 15:56 UTC by Julius Dauz
Modified:	2008-12-15 12:16 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Julius Dauz 2008-03-17 15:56:55 UTC

We have a few customers that have called about this issue. When trying to play anything from Rhapsody library they receive the following error:

Internal Rhapsody Error: org.xml.sax.SAXParseException: Character reference &quot;&amp;#;&quot; is an invalid XML character

and this message just scrolls across the screen.

Comment 1 Andy Grundman 2008-03-17 17:50:10 UTC

Email me their SN email addresses.

Comment 2 Andy Grundman 2008-03-18 13:23:29 UTC

Fixed.  After the SN instances restart over the next hour or so, nobody should be seeing this error anymore.

Comment 3 Brian Griffin 2008-03-29 05:40:38 UTC

I am the customer who called customer service, and thus had this bug entered.  I'm still having issues.  I still get the same error described when trying to connect to Rhapsody through my SqueezeNetwork.  Any ideas?

Comment 4 Andy Grundman 2008-03-29 07:08:47 UTC

I can't reproduce this but I did fix another bug that might cause you to get an 'accountKey is of zero length' error.  Let me know if you still have problems.

Comment 5 Ross Levine 2008-03-31 12:48:34 UTC

Customer support to follow up with "org.xml.sax.parseexception" error.

Comment 6 Blackketter Dean 2008-04-01 11:37:55 UTC

The bug is resolved, according to andy.  Julius: please follow up with the customer.

Comment 7 Julius Dauz 2008-04-08 15:26:03 UTC

Sorry for the late reply to this bug. The customer verified that the issue was resolved last week. Thanks!

Comment 8 James Richardson 2008-12-15 12:16:44 UTC

This bug has been fixed in the latest release of SqueezeNetwork!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.