VMware Horizon Community
shabaazmohammad
Contributor
Contributor

unable to start app volume manager 2.16 after installing

unable to start app volume manager

28000 18456 Micrcrosoft ODBC SQL server Driver SQL server login failed for user (domain\computername$)

after installing app volume manager we tried to launch the appvol manager we are getting the above error, what we observed is it is trying to connect to database server using computer name.

please advice how we can solve this.

Reply
0 Kudos
5 Replies
mchadwick19
Hot Shot
Hot Shot

Do you have access to the SQL server? Is the account enabled + granted permission to log in and access the database you are requesting to use?

Or are you using a local SQL express instance for a test/pilot environment?

VDI Engineer VCP-DCV, VCP7-DTM, VCAP7-DTM Design
Reply
0 Kudos
shabaazmohammad
Contributor
Contributor

Hi yes we have access to data base and permission is given to DB, we are using external data base for installation and installed is successful. but when we try to launch the appvolume manager we are getting below error.

unable to start app volume manager

28000 18456 Microsoft ODBC SQL server Driver SQL server login failed for user (domain\computername$)

what we observer is sql server is trying to login with computer name instead of db user

Reply
0 Kudos
mchadwick19
Hot Shot
Hot Shot

Have you checked the ODBC connection that was created by the installer? Can you double check that it contains the correct username/password information and test the connection?

Also make sure that you are using a supported version of SQL otherwise the service cannot start properly.

VDI Engineer VCP-DCV, VCP7-DTM, VCAP7-DTM Design
Reply
0 Kudos
shabaazmohammad
Contributor
Contributor

the sql version when we are using is not compatible with 2.16 we have already build the connection and composer with 7.8 version and sql server version is (we are using SQL 2016 RTM)

can we use the older app volume version with horizon 7.8 please advice.

or we have to destroy the sql and create new sql 2016 sp1 

Reply
0 Kudos
mchadwick19
Hot Shot
Hot Shot

It looks like the documentation is recommending SQL 2016 SP2 only, SP1 is not explicitly on the support list. You can also go with 2014 SP1 or SP2. I know AV does a check on the server version. When I was last installing 2.14 and trying to use SQL 2016, the web server would not start with SQL errors. You couldn't even put the database in compatibility mode.

VDI Engineer VCP-DCV, VCP7-DTM, VCAP7-DTM Design
Reply
0 Kudos