Video Screencast Help

SWS Error - Streamlet Engine [Init Error]

Created: 21 Sep 2011 • Updated: 07 Oct 2011 | 2 comments
This issue has been solved. See solution.

Hey Everyone,

We are having a problem with our new Workspace Streaming Server.  The Back End was installed, but the Engine appears to not be functioning fully.  Database is Up, but Streamlet Engine shows [Init Error].

The Cluster shows all resources are online.

Services are up and we changed the Engine to run as a domain admin so that we can use it for access to network drives per our other streaming servers.

However, when logging in as the inital admin it won't let you configure anything, probably due to the Engine not being fully online.

We have tried changing the Host Name/IP Address from "All Local IPs" to the Cluster Service Name "AltirisCAP", but get a new error stating the GUID is incorrect.  Any ideas?

The link to download the dci_all.log is at http://www.owlnet.rice.edu/~fg2/dci_all.log

Thanks everyone!

Discussion Filed Under:

Comments 2 CommentsJump to latest comment

Palvaran's picture

Problem:  Noresponse from the Streaming Engine followed by a display of init-error

Answer:  Check the database server status. Start the server if the server does not respond.
■ Check the status of the LDAP server. Start the server if the server does not respond.
■ Restart the Streaming Engine only after all the depending components function properly.
This step is very critical because the Streaming Engine is able to start up if the admin tries to restart Streaming Engine before LDAP computer is active.
If this type of init-error occurs, complete the following steps:
■ Connect to your database server.
■ In AppStream database, run the following SQL command
update as_misc set param_value = 'SQL'
where param_name = 'appstream.user.datasource'.
■ Restart the Workspace Streaming Agent and database servers.
■ Restart Streaming Engine.
■ Navigate to Configure>StreamletEngine>Basic, and then set user data source back to LDAP.
■ Restart Streaming Engine again

Modified the database per the SQL Query and affected the row.  Restarted the services for the SQL instance and the Streamlet Engine on the Server.

Systems Administrator
Rice University

Remember, "The happiness of your life, depends on the quality of your thoughts."

Palvaran's picture

Thanks to Ganesh for helping me to troubleshoot this problem.

https://www-secure.symantec.com/connect/articles/s...

Systems Administrator
Rice University

Remember, "The happiness of your life, depends on the quality of your thoughts."

SOLUTION