/build/static/layout/Breadcrumb_cap_w.png

SoftGrid Virtual Application Server service immediately stops...

I have isntalled App-V (SoftGrid) 4.2 in my test environment and the installation process went smoothly. Unfortunately the 'SoftGrid Virtual Application Server' service is not running. It immediately stops when I manually try to start the service.

In the 'sft-server.log' file has "1219 System Dispatcher Successfully Shutdown" repeatedly (I can include the entire log file if necessary).

When I attempt to refresh the server from my desktop client I receive the following error:
"No connection could be made because the target machine actively refused it.
Error Code: 42200F-19D0472A-0000274D"

I believe the problem ultimately lies in the SoftGrid VAS service not running, but I'm not sure where to go from here. Any and all help is GREATLY appreciated!!!

0 Comments   [ + ] Show comments

Answers (5)

Posted by: kkaminsk 16 years ago
9th Degree Black Belt
0
Increase the log level in the registry on the virtual application server to Debug. It should be more descriptive as to what is broken.

http://support.microsoft.com/kb/931584
Posted by: srikanthkhatri 16 years ago
Senior Yellow Belt
0
Hi Tliffick,

Try to check Dependencies, follow the below links,I'm hopeful that it will resolve your issue.

http://support.microsoft.com/kb/931584

http://support.microsoft.com/kb/930730/en-us

Regards
Srikanth
Posted by: tliffick 16 years ago
Yellow Belt
0
I have followed the instructions and verified everything in KB931584 & KB930730 and my problems remains. It looks like it maybe a permissions issue attempting to connect to the database. After I increased the logging level I receive the following in the sft-server.log:

[2008-09-30 09:03:49.916] - 4032 3772 SW_MessageHandler::Open - - - - 5 - "Initialization complete."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::HandleError - - - - 5 - "Error 0x0, State: IM006, Text: [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed"
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::MapError - - - - 5 - "Got unknown error code: 5701."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::HandleError - - - - 5 - "Error 0x1645, State: 01000, Text: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'SOFTRICITY'."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::MapError - - - - 5 - "Got unknown error code: 5703."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::HandleError - - - - 5 - "Error 0x1647, State: 01000, Text: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.931] JHS-BOPP 4032 3772 SW_SQLDataConnection::SetTimeout - - - - 5 - "SetTimeout () called on unopened object."
[2008-09-30 09:03:49.947] JHS-BOPP 4032 3772 SW_ADSDataConnection::Open - - - - 5 - "Server on AD Domain"
[2008-09-30 09:03:49.994] JHS-BOPP 4032 3772 SW_ADSDataConnection::Open - - - - 5 41560 "Logon User Failed (0x569) (1385)"
[2008-09-30 09:03:49.994] JHS-BOPP 4032 3772 SW_DataConnectionPool::Open - - - - 5 - "Failed to open connection."
[2008-09-30 09:03:49.994] JHS-BOPP 4032 3772 SW_DataConnectionPool::Close - - - - 5 - "Close () called on closed object."
[2008-09-30 09:03:49.994] JHS-BOPP 4032 3772 SW_DataAccess::Initialize - - - - 5 - "Failed to open configuration pool."
[2008-09-30 09:03:49.994] JHS-BOPP 4032 3772 SW_SystemDispatcher::fini - - - - 4 41218 "Shutting down System Dispatcher ()"
[2008-09-30 09:03:49.994] JHS-BOPP 4032 3772 SW_SystemDispatcher::fini - - - - 0 41219 "System Dispatcher Successfully Shutdown."
[2008-09-30 09:03:50.009] JHS-BOPP 4032 3780 SW_MessageHandler::Close - - - - 5 - "Shutdown complete."

Where should I go from here?
Posted by: kkaminsk 16 years ago
9th Degree Black Belt
0
[2008-09-30 09:03:49.947] JHS-BOPP 4032 3772 SW_ADSDataConnection::Open - - - - 5 - "Server on AD Domain"
[2008-09-30 09:03:49.994] JHS-BOPP 4032 3772 SW_ADSDataConnection::Open - - - - 5 41560 "Logon User Failed (0x569) (1385)"

Based on what I see I would check the local secutiy event log on the VAS server. If you are using a service account for the virtual application server service it may not be set up correctly.
Posted by: kapil.kathuria 16 years ago
Orange Belt
0
Looks like it has to do something with Account which is being authenticated by SQL server. In your SQL server do you see user by name <Server_Name>$? For example if you have installed management server service on server "AppVirtSer" then "AppVirtSer$" user should be member of SQL server. And "AppVirtSer$" should have "db_owner" right on SoftGrid database.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ