SoftGrid Application server Service does not start
All,
I recently installed SoftGrid 4.5 for testing, the install went well without any problems, however, the service for the server wil not start. I've been having trouble getting my 4.5 client to connect with the 4.5 server and I'm am certain that the issue is do ti the service not running.
I recieve this error
"Service cannot start..refer to service-specific error code 268480357"
Can anyone help?
Answers
1. Is the VAS service still running with the "NT AUTHORITY\NetworkService" login as it is intalled with?
2. If so, go to your SQL Server Management Studio and check if the VAS machine account is
still listed under security --> logins. You should find something
like <domain>\<VAS hostname>$
I think your VAS hostname is VFASWS023 so it would be something like <domain>\VFASWS023$
or
If the VAS service is running with another account please check the database for this account.
3. Verify if the database account mentioned above has still access to your SOFTGRID database and with the correct roles.
Joop wrote:
Apperently it used the HOSTNAME to query. But in the database table SERVER the FQDN for the host was registrered.
My intstall did not put the FDQN into the database. Is is possible you installed the VAS as a local admin instead of as a domain admin?
All Replies
Hi,
Can you tell someting about the messages beeing logged at service start on the VAS.
The messages are logged in: C:\Program Files\Microsoft SoftGrid\Microsoft System Center Virtual Application Server\SoftGrid Server\logs\sft-server.log
I had a similar issue because I installed from a standard RDP connection instead of console 0. If you happen to have made the same mistake, login to the console session with the following command line:
mstsc /v
ervername /console /w:1024 /h:768
The article I found about this, then had me uninstall and reinstall SAVS 4.5. I did not remove the DB and it was intact for the reinstall. This still did not fix my problem until I deleted and recreated the server under Default Server Group in the Management Console.
Good luck!In my case I saw in the log file a message that "the server was not found in the datastore".
That VAS service tried to do a query in the database table SERVER to obtain some information for the service.
Apperently it used the HOSTNAME to query. But in the database table SERVER the FQDN for the host was registrered.
I have changed this in the database. But it is of course also possible from the Management Console.
So during installation of the VAS it is registered in the datase with its FQDN. But why the VAS service used the HOSTNAME to query the database on startup is not clear.
Here is what I recieve
[2008-01-18 14:06:14.217] - 3360 2788 SW_MessageHandler:
pen - - - - 5 65535 "Initialization complete."
[2008-01-18 14:06:14.374] VFASWS023 3360 2788 SW_SQLDataConnection:pen - - - - 2 41494 "Failed to establish a connection to the data source: (Server: ipe016, Database: SoftGrid4.5_DB).
"
[2008-01-18 14:06:14.374] VFASWS023 3360 2788 SW_SystemDispatcher::init - - - - 1 44901 "System Dispatcher initialization error [-1]. System Dispatcher startup will stop.
"
[2008-01-18 14:06:14.374] VFASWS023 3360 2788 SW_SystemDispatcher::fini - - - - 0 41219 "System Dispatcher Successfully Shutdown.
"
[2008-01-18 14:06:14.374] VFASWS023 3360 2816 SW_MessageHandler::Close - - - - 5 65535 "Shutdown complete."1. Is the VAS service still running with the "NT AUTHORITY\NetworkService" login as it is intalled with?
2. If so, go to your SQL Server Management Studio and check if the VAS machine account is
still listed under security --> logins. You should find something
like <domain>\<VAS hostname>$
I think your VAS hostname is VFASWS023 so it would be something like <domain>\VFASWS023$
or
If the VAS service is running with another account please check the database for this account.
3. Verify if the database account mentioned above has still access to your SOFTGRID database and with the correct roles.
Joop wrote:
Apperently it used the HOSTNAME to query. But in the database table SERVER the FQDN for the host was registrered.
My intstall did not put the FDQN into the database. Is is possible you installed the VAS as a local admin instead of as a domain admin?
All,
Thanks for the Help, When I ran the installation that first time I was on a RDC. I uninstalled and re-installed connected to service consol and I'm ok now.
Thanks
Hi Robert, I am facing exactly the same problem as yours. My VAS service is not started when I checked under Services.
I am running Windows 2003 server on a VM machine.
I am not sure what do you mean by reinstalling and connecting to service console?
How do you install without using RDC option? Is it through not checking that when running VAS setup?
Thanks!
A Softgrid wannabe user.
Best regards,
Daniel
I also got the same error when I reinstalled a server and connected it to the same database.
I had to remove the [softgridservername$] in the database under Logins the user object.
Then I could re-install it.
BR
Pierre Eriksson
Daniel Foo wrote: Hi Robert, I am facing exactly the same problem as yours. My VAS service is not started when I checked under Services.
I am running Windows 2003 server on a VM machine.
Your problem may be different. We often see the service fail to start in a test VM environment. The issue is that the service dispatcher sets a 60 second timer before starting the cores. If the cores do not fully come up within the 60 seconds (due to performance on an underpowered VM infrastructure) the service shuts down. In such an environment, let things settle before and after turning on the VAS VM, or just expect to have to check if the service started and restart it.
But check your server log file (program files/.../softgrid server/Logs/ folder) to see what it says.
Hi Daniel,
Can you manually start your service? If it does start manually but not automatically on reboot, you can create a simple scheduled task to start the service post boot. This works well in lab VM environments and I have a simple batch file that I configured to run as a scheduled task.
"net start <service display name>"
If your service does not start when you attempt to start it manually, do you get the same error reported by others earlier in this thread? If not, post your error and we will see if we can track it down.
Regards,
Michelle
- I get the same errors in my test environment, it looks like all these errors (at least for me) boil down to the MSSQLADHelper service. The Application Event Log error states '0' is an invalid number of startup parameters. This service takes two start up parameters.
When you try to start the service manually you get an error code -1073741724
This is the only SQL service that will not start. However, the 2 App-V services that don't start seem to be related to this SQL service. - Hello.
I had the same problem on my Application Virtualization Managemet Server. Anyway, very often, i need to move my virtual machines to another phyisical server, and one time I moved App-V Management server, and virtual machine didn't get IP addres from my DHCP, and network name was not like the domain in which App-V management server was installed first. So I changed IP address and preferred DNS server manualy, and after that everything worked fine, I was able to start App-V Management Server service normaly.
Anyway problem ID in event viewer was: " The Application Virtualization Management Server service terminated with service-specific error 268480357 (0x1000AF65)... Event ID 7024.
