Cannot Update App-V 5.0 SP3 DB Server 'the specified name already in use'

Question

We planned to update our App-V  server from App-V 5.0 SP1 to App-V 5.0 SP3
2 Servers (Both are Management Servers and Publishing Servers) with a remote SQL (2008 R2)
we verified that all the registry keys exists according to the the
Technet Document
when we ran the setup file on the server we chose to install all of the roles and we got to the error:
the specified name is already in use. you must provide a unique name database name
The DB is already exist! we just want to update it to SP3 as well...
So we installed all the roles but Management Server DB and the installation completed successfully,
but now we still have a problem as the server can't connect to the DB (probably because it hasn't been updated)
now we get this error:
there were problems interacting with the database on the server. The error was: Invalid culomn name 'PackageOptional'.
Invalid culomn name 'VersionOptional'
we ran the setup with a domain admin that has full admin priviledges either on the App-V Servers and the SQL.
we can't run the setup.exe on the SQL Server itself as it hosts many other DBs and doesn't have .Net Framework 4.5.1... besides the fact the DBAs don't really want to do it.
we tried to backup the DB, attach it on a local SQL (under the App-V Server) , changed the registry keys to direct to the local DB and we got the same errors when we tried to run the upgrade!
how come the documentation doesn't have anything about updating the DB?
another question I couldn't figure out. can I use App-V Server 5.0 SP3 with App-V Client 5.0 SP2 HF4?
anyway - please help!
thanks!!
Tamir Levy

Answer 1

One more thing, I know how to expand the DB Scripts and run them manually on the SQL Server,
but from my understanding, it is only to create new DBs and not to update the DB Tables...
anyhow, I don't think the DB update should be such a complex and unfriendly method, especially when I took the DB and put it on a local SQL! this should be updated with a simple "Next , Next" Setup...
Thanks
Tamir Levy
At the current time, there is some contradictory information available on technet.  On one side, the Planning for High Availability document describes how
to extract the database scripts and run them against a SQL host so you don't have to run the EXE directly on the SQL host (yes, this does upgrade the tables too, not just create new ones, apparently the order to execute them is wrong).  On the other side,
the App-V 5.0 SP3 Support Configurations indicates that any installation where you do not run the EXE on the SQL server is unsupported.
As an enterprise customer who has SQL in a failover cluster, this confuses me.  I cannot run the installer on the SQL server (like you, and many other enterprise customers).  And even if I could, it doesn't mean the database would exist on the
SQL server that it was run against, as the database can failover and nodes could be rebuilt!
In regards to versions, when I said SP2 it was actually SP1.  You are correct, there were no server upgrades for SP2.
Please be aware, I did not get the instructions to edit the database from Microsoft.  I provided them the steps I performed to get the application to work and I'm sharing them.  I am still waiting to hear back from them to see if this will be a
supported path or not.  The setup was written to be executed directly on the SQL box, which is an unrealistic expectation for enterprise customers.  Even previous versions had to be extracted and applied via SQL scripts!
The command above, from Alan, is part of the database scripts.  If you extract the scripts using /layout and /layoutdir (as described in Planning for High Availability),
you will see a script called UpdateTables.sql.  This is a part of the script, not the whole thing.  There is more logic in this script that is required to get your publishing server up and running:
It deletes all the daat from SchemaVersion then inserts a value of 2 into it.  If this doesn't happen, you'll get weird errors when trying to receive publishing information.
If you can wait a few days for the upgrade, I would recommend that.  I expect some more documentation from Microsoft to come out and clear some of this up.