AMS5 Std vhost vod signed apps

[Petro_O__Bochan]

Hello, I face a rather odd issue with the vhost on AMS Std. Whenever I try to change the signed vod app’s Application.xml <Streams> tag to point to alternative media location, I get this message:

Tue 07:24:51 PM: Invalid configuration file : {path}\vod\Application.xml

Inside the <Streams> tag I change the path to a physical one, not the one with the pound sign. Either way, I get the same message back. Moreover, when trying to modify ams.ini with the custom path, I get an error message as well. The <Streams> tag in Vhost.xml is blank. It turns out that the signed app can only digest _defaultVHost_ paths. How could this be resolved?

Thanks.

[SE_0208]

Can you paste your Application.xml - probably you are not setting things right. You should be able to configure Application.xml Virtual Directory settings to pick media assets from locations desired by you.

[Petro_O__Bochan]

Hello Rudresh, tell you what – every time you post a response in the forum the software just starts working by some magic J. Ok, so the setup that I’ve described actually works. I guess it didn’t originally work (I never changed anything) is that AMS needs some time to update some state as per vhosts. So the setup is as follows: vhost.xml - . Along with that, I’m facing another issue with a duplicate vod signed app – e.g. myvod. Application.xml inside that dir was updated accordingly but the streams fails to play, is there a reason for that?

[Petro_O__Bochan]

Hello again, I think some further studying needs to be done in here – I never changed anything since the time it worked, and now it’s not working again with the same message – Wed 11:59:50 PM: Invalid configuration file : c:\path\vod\Application.xml. what could that be?

[SE_0208 · Accepted solution]

Petro - i am considering this thread as closed as we reached resolution via private discussion. Just for information of other users - it was misconfiguration issue.