Cisco Cisco StadiumVision Director
© 2011 Cisco Systems, Inc. All rights reserved.
42 of 26
ID
Headline
Description
CSCto26256
CSV save fails if SV Director is accessed using
the hostname instead of the IP address.
the hostname instead of the IP address.
Symptom: If a hostname to IP association was
made in (for Windows)
"C:\WINDOWS\system32\drivers\etc\hosts" and the
hostname is then used to access SV Director, the
CSV download in the Devices page will fail.
made in (for Windows)
"C:\WINDOWS\system32\drivers\etc\hosts" and the
hostname is then used to access SV Director, the
CSV download in the Devices page will fail.
For example if you add the line "192.168.0.10
svd1" to the windows hosts file and use
"http://svd1:8080" to access Director, you will get an
error when trying to save an exported CSV file in the
Devices page.
svd1" to the windows hosts file and use
"http://svd1:8080" to access Director, you will get an
error when trying to save an exported CSV file in the
Devices page.
Workaround: Instead of using a hostname to
access Director use the IP address. For example,
instead of using "http://svd1:8080" use
"http://192.168.0.10:8080".
access Director use the IP address. For example,
instead of using "http://svd1:8080" use
"http://192.168.0.10:8080".
CSCto08755
Disabled DMP appears in Content Staging page.
Symptom: A disabled DMP will appear in the
Content Staging page.
Content Staging page.
Workaround: Instead of selecting ‘All Devices’ use
‘Selected Devices’.
‘Selected Devices’.
CSCto5647
Editing a playlist that is part of a running script
impacts content replacement.
impacts content replacement.
Symptom: If you add content or modify content for
a playlist used in a running event script, the added
content may appear in the content replacement
window although it cannot be used to correctly
replace content.
a playlist used in a running event script, the added
content may appear in the content replacement
window although it cannot be used to correctly
replace content.
Conditions: This error occurs if an event script is
running and you modify a playlist that is used by the
event script.
running and you modify a playlist that is used by the
event script.
Workaround: Do not modify playlists associated
with a running event script.
with a running event script.
CSCto32254
Swf in one list impacts jpeg/png on another list.
Symptom: Changing game state that has swf with
animation to ad-hoc or another game state with
static contnet causes the pixels moves up on the
overlay.
animation to ad-hoc or another game state with
static contnet causes the pixels moves up on the
overlay.
Workaround: None.
CSCto27192
Non-video external swf w/ animation influence
static image in the list.
static image in the list.
Symptom: There were three non-video contents in
the list in the following order: (Sfw, jpg, swf) when
influence on static image was noticed.
the list in the following order: (Sfw, jpg, swf) when
influence on static image was noticed.
Workaround: None.
CSCtl53505
Symptom: After logging in to SV Director, you may
get a "session timeout" in the Control Panel. It is
possible to get this error especially when you have
multiple instances of StadiumVision Director running
on more than 1 server.
get a "session timeout" in the Control Panel. It is
possible to get this error especially when you have
multiple instances of StadiumVision Director running
on more than 1 server.
Workaround: Logout and login again.
CSCtn97763
Images in Liferay Image Gallery appear 'piled up'
Symptom: This is a known bug of Liferay 5.2. It
might happen when you manually change the max
image size setting in the Liferay control panel.
might happen when you manually change the max
image size setting in the Liferay control panel.
Workaround: Apply a sql patch to sv_liferay
database. The patch is at
/var/sv/db/menu/cleanpreference.sql
database. The patch is at
/var/sv/db/menu/cleanpreference.sql
CSCtn99464
Liferay Image Gallery add images shows "Image
Gallery is temporarily unavailable”
Gallery is temporarily unavailable”
Symptom: This is a known bug of Liferay. It might
happen when the Liferay server is running for longer
than a week.
happen when the Liferay server is running for longer
than a week.
Workaround: Restart the Liferay server.