Troubleshooting a SVS Streaming Package

You've taken your .VSA and used it with the Streaming Composer to create a streamable SVS package. However after uploading the package to your streaming server, it fails to stream on the client. What's going on, the VSA loads just fine?

Well, there could be a number of reasons for this, but the first thing to do is identify where the problem is. Here's how to do this.

When creating an SVS package, the Streaming Composer generates an optimized VSA. We need to take this VSA and try to import it using SVS Admin, since this is the same VSA that is streamed. This process will identify if there is a problem with the optimized VSA and/or the streaming process. If the optimized VSA imports and activates with no issues, then the streaming components need to be looked at to solve this problem. If the optimized VSA does not import, or imports but fails to activate, then something is wrong with the packaging process.

To get the optimized VSA:

• Browse to the location of the SVS package.
• Drill down to the following location in the package.
  • svs-dest\as_svsfiles_opt
• Copy the .vsa in this folder and try to import it using SVS Admin