Archive
App-V: Certain Database tables not updating or empty post upgrade from 4.1
The likely scenario is that the database was updated from Softgrid 4.1. During the upgrade process for whatever reason, the tables, views, and/or stored procedures that were deprectaed for App-V Server 4.5 were left in the database.
The following tables are deprecated as of 4.5. They may still appear in a database that has been upgrade from a pre-4.5 release, but they are no longer actively updated or accessed.
ACTIVE_APPLICATIONS
APPLICATION_CAPABILITIES
APPLICATION_EXTENSIONS
DISCONNECTED_EXPIRIES
MANAGEMENT_SERVERS
SOFTGRID_USERS
Deprecated Views
The following views are deprecated as of 4.5. They may still appear in a database that has been upgrade from a pre-4.5 release, but they are no longer actively updated or accessed.
VW_MANAGEMENT_SERVERS
Deprecated Procedures
The following procedures are deprecated as of 4.5. They may still appear in a database that has been upgrade from a pre-4.5 release, but they are no longer actively updated or accessed.
sp_SFTrpt_systemusagebyuser
sp_SFTrpt_usergroupusage
sp_SFTsetdbaccess
This installation requires Windows 2000?!?!?!? Do What? Error when deploying MED-V Deployment Package . . . aka – did I just Travel back in Time?
Needless to say, getting this error on a Windows 7 computer was confusing. Luckily, the customer did not attmept to cretae a Versionlie AppCompat shim as this could have yielded even more trouble.
This was simply caused by the wrong MSI being selected during the packaging wizard. When you select the option to run the MED-V packaging wizard (From the Management Console – select Tools – Packaging Wizard.”In the MED-V Installation Settings, dialog box, the installation binary selected should be MED-V_1.0.105.MSI.
App-V: Here’s an example of “don’t do that – but if you must, here’s how.”
Here’s an example of “don’t do that – but if you must, here’s how.” Access 97 and the Access 97 run-time module is no longer supported by Microsoft. Therefore, custom applications that use the Access 97 run-time module are also technically unsupported. Virtualizing it with App-V does not change that fact although the isolation has led to some unintended positive consequences. Always remember that it is still a risk to use App-V in this manner as future releases and patches cannot be guaranteed to be regression free in terms of how it will affect an unsupported technology.
However, if you insist on sequencing an application that uses it, the following can be done to allow you to sequence Access 97 Run-time modules in versions 4.5 or later:
First, the registry key:
HKEY_CLASSES_ROOT\Licenses\8CC49940-3146-11CF-97A1-00AA00424A9F will be missing. This will result in a license error.
To rectify this, add the following registry entry
- HKEY_CLASSES_ROOT\Licenses\8CC49940-3146-11CF-97A1-00AA00424A9F
- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW]
“DefaultSeparateVDM”=”yes”
This must be done and rebooted on the sequencer prior to the start of sequencing.
Install to a Mount Drive during sequencing
Upon completion of the installation, DO NOT STOP MONITORING.
Open a command prompt rename %WINDIR%\fonts\hatten.ttf to hatten.xxx
Launch Application again.
Click Stop Monitoring.
App-V 4.5: Failed to Start App-V Management Server: Error 268480357
Here is the scene. An attempt to start App-V Management Server 4.5 fails with the following error:
“Windows could not start the Application Virtualization Management Server on “servername.” For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 268480357.”
You also then see the following in the SFT-SERVER.LOG file when it is set to VERBOSE:
[2010-07-10 15:23:21.909] - 4020 4080 SW_MessageHandler::Open - - - - 5 65535 "Initialization complete." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::MapError - - - - 5 65535 "Got unknown error code: 5701." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::HandleError - - - - 5 65535 "Error 0x1645, State: 01000, Text: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to APPVIRT." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::MapError - - - - 5 65535 "Got unknown error code: 5703." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::HandleError - - - - 5 65535 "Error 0x1647, State: 01000, Text: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::HandleError - - - - 5 65535 "Error 0x0, State: 01004, Text: [Microsoft][ODBC SQL Server Driver]String data, right truncation" [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::MapError - - - - 5 65535 "Got unknown error code: 229." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::HandleError - - - - 5 65535 "Error 0xe5, State: 42000, Text: [Microsoft][ODBC SQL Server Driver][SQL Server]The SELECT permission was denied on the object 'SYSTEM_OPTIONS', database APPVIRT, schema 'dbo'." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::MapError - - - - 5 65535 "Got unknown error code: 16945." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::HandleError - - - - 5 65535 "Error 0x4231, State: 42000, Text: [Microsoft][ODBC SQL Server Driver][SQL Server]The cursor was not declared." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::SearchInternal - - - - 5 65535 "Failed to execute statement. [SELECT * FROM SYSTEM_OPTIONS]" [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SQLDataConnection::GetRecord - - - - 5 65535 "No records found." [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_DataAccess::Initialize - - - - 5 65535 "Unable to retrieve value for system options record" [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SystemDispatcher::init - - - - 1 44901 "System dispatcher initialization error [-1]. System dispatcher startup will stop. " [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SystemDispatcher::fini - - - - 5 65535 "Shutting down System Dispatcher version 4.5.1.15580 (4020)" [2010-07-10 15:23:22.018] APPV01 4020 4080 SW_SystemDispatcher::fini - - - - 0 44952 "Successfully shut down Microsoft System Center Application Virtualization Management Server Version 4.5.1.15580 (4020) " [2010-07-10 15:23:22.018] APPV01 4020 1860 SW_MessageHandler::Close - - - - 5 65535 "Shutdown complete."
The best solution is to either stand up a new installation that creates a new installation or uninstall the App-V 4.5 server and install a 4.1 version of the Softgrid Virtual Application server and point to this database. Then proceed to attempt to upgrade the 4.1 server to 4.5 which in turn should upgrade the database from 4.1 to 4.5.
PLEASE NOTE: This is predicated on the fact the database is in a usable state.
App-V: 4.5 SP2 Server Fails to Connect to Failover Database Instance
Beginning with 4.5 Service Pack 2, the Microsoft App-V server now provides support for SQL Server mirroring. This allows for datastore redundancy via mirror failover in an enterprise environment. It also allows you to switch from native OS ADO over the SQL native client 10.0.
Information on how to configure this can be found here:
http://technet.microsoft.com/en-us/library/ff660790(printer).aspx
However, many have noticed that in spite of following these instructions, they were still having issues with the App-V server connecting to the failover instance.
When this failure occurs, you will see this in the server’s SFT-SERVER.LOG file:
[2011-4-07 16:33:29.212] APPVSERVER 2600 4100 SW_SQLDataConnection::PopulateConnectionString – – – – 5 65535 “Constructed ODBC connection string: DRIVER={SQL Server};DATABASE={APPVIRT};Network={DBMSSOCN};Server={APPVSQLM2,1433};”
[2011-4-07 16:33:29.259] APPVSERVER 2600 4100 SW_SQLDataConnection::MapError – – – – 5 65535 “Got unknown error code: 4060.”
[2011-4-07 16:33:29.259] APPVSERVER 2600 4100 SW_SQLDataConnection::HandleError – – – – 5 65535 “Error 0xfdc, State: 42000, Text: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database “APPVIRT” requested by the login. The login failed.”
[2011-4-07 16:33:29.259] APPVSERVER 2600 4100 SW_SQLDataConnection::Open – – – – 5 65535 “Failed to load requested driver.”
[2011-4-07 16:33:29.259] APPVSERVER 2600 4100 SW_SQLDataConnection::Open – – – – 5 65535 “Unable to open ODBC data source.”
[2011-4-07 16:33:29.259] APPVSERVER 2600 4100 SW_DataConnectionPool::Open – – – – 5 65535 “Failed to open connection.”
[2011-4-07 16:33:29.259] APPVSERVER 2600 4100 SW_DataConnectionPool::Close – – – – 5 65535 “Close () called on closed object.”
[2011-4-07 16:33:29.259] APPVSERVER 2600 4100 SW_DataAccess::Initialize – – – – 5 65535 “Failed to open configuration pool.”
[2011-4-07 16:33:29.259] APPVSERVER 2600 4100 SW_SystemDispatcher::init – – – – 1 44901 “System dispatcher initialization error [-1].
You will also see the following in the SQL ERRLOG file:
2010-12-29 13:55:27.18 Logon Error: 18456, Severity: 14, State: 38.
2010-12-29 13:55:27.18 Logon Login failed for user ‘domain\machineaccount$’. Reason: Failed to open the explicitly specified database. [CLIENT: x.x.x.x]
Cause
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Softgrid\4.5\Server\SQLFailOverServerName
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Softgrid\4.5\Server\SQLFailOverServerPort
and we are told to create them in Steps 7 and 8.
Problem is the value SQLFailOverServerName should be SQLFailoverServerName. That one lower case letter was preventing auto failover from occurring.
MED-V V1.0 SP1: Error when trying to open the MED-V Management Console: “The MED-V Management application was unable to initialize.”
- “The MED-V Management application was unable to initialize.”
- “The type initializer for ‘Kidaro.Foundation.Profile.UserProfile’ threw an exception.”
This is caused by either a blank or corrupt XML file containing the user settings: (WIndowsUserSettings.xml)
To resolve this, delete the %LOCALAPPDATA%\MED-V\ directory and restart the application.
MED-V 1.0: Windows Installer Service Retriggers MED-V Client installation When Trying to Start Workspace
Upon further investigation, I found that the installation was only installed for the user instead of the entire machine (the MED-V Client.) The MED-V Client was deployed silently using SCCM. The command line in the package to install the MSI did not have the ALLUSERS=1 flag properly set.
The resolution was to redeploy the client using the ALLUSERS=1 Flag. Due to the way the Windows Installer properties handle installations, this is the only remediation.
Refer to the following article:
SCCM 2007 R2/R3: Error when Streaming App-V Virtual Application from Distribution Point: 4xxxxxx-xxxxxx0a-00003004
On an App-V Client managed by Configuration Manager (SCCM), you may receive the following error when trying to launch a virtual application configured to stream from a distribution point.
The Application Virtualization Client does not support the authentication scheme requested by the server. Report the following error code to your System Administrator.
Error code: 4604EE8-24601B0A-00003004
You may get this error whether or not the application is 100 percent cached or not. In addition you will see one or more of the following errors in the SFTLOG.TXT:
[09/20/2010 11:14:57:287 AMGR WRN] {tid=58C}
Attempting Transport Connection
URL: http://serverfqdn:80/SMS_DP_SMSPKGD$/VirtualAppStreaming/<PKGID>/{GUID}/package.sft
Error: 24603B0A-40000191
[09/20/2010 11:14:57:366 TRAY ERR] {tid=58C:usr=username}
The Application Virtualization Client could not launch ApplicationName
The Application Virtualization Client does not support the authentication scheme requested by the server. Report the following error code to your System Administrator.
Error code: 4604EE8-24601B0A-00003004
To resolve this issue, make the following registry change and restart the App-V Client service:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration
RequireAuthorizationifCached = 0
App-V: Upgrade from Softgrid Server 4.1 to App-V Server 4.5 Fails with Error 25119
You may know the issue: You are trying to upgrade from the Softgrid VAS 4.1 to Microsoft Application Virtualization (App-V) 4.5 Management Server and it fails with the following error:
Error 25119:
“The installation program could not upgrade the configuration data store. Please see the installation log file for more information”
This is a generic database upgrade issue. there have been many causes of this as the error just means the database upgrade failed.
NOTE: There are several potential causes of this. Please take note that you will need to confirm this issue by examining specifically the softgrid-server-setup.log file. Please also refer to the Microsoft Knowledge base as many other possible causes have been documented.
In this particular instance, the database used split schemas where half of the stored procedures ran under a different schema than dbo.
The Softgrid-Server-setup.txt log reveals failure and further SQl Profiler Traces confirmed that it all went south as soon as it hits the stored procedures with user-defined schemas.
[2010-09-13 15:03:28] (11796:12004) SQL state: ``01000'', Native: 0, Text: ``[Microsoft][ODBC SQL Server Driver][SQL Server]<<< sp_SFTrepldel_... >>>''. [2010-09-13 15:03:28] (11796:12004) SQL state: ``42S02'', Native: 3701, Text: ``[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the procedure 'sp_SFTreplins_ACCOUNT_AUTHORITIES', because it does not exist or you do not have permission.''. [2010-09-13 15:03:28] (11796:12004) ::SQLExecDirectW error 0xffffffff. [2010-09-13 15:04:32] (11796:12004) Failed to execute SQL statement `` if exists (select * from sysobjects where type = 'P' and name = 'sp_SFTreplins_ACCOUNT_AUTHORITIES') drop proc [sp_SFTreplins_ACCOUNT_AUTHORITIES] [2010-09-13 15:04:32] (11796:12004) Directory ``C:\Program Files\Softricity\SoftGrid Server\schema\upgrade\4.1\'' failed!
————-
In this case, the non dbo schemas were owned by “Softricity_User.” What you do is use the following script to create a stored procedure called spMigrateStoredProcedures.sql.
NOTE: If you use this script just make sure to replace “Softricity_User” with the account specific to your customer’s database. After you use this script to create the stored procedure, execute it prior to upgrade. PLEASE BACK UP YOUR DATABASE BEFORE DOING SO.
—————————–
CREATE PROCEDURE [dbo].[spMigrateStoredProcedures] AS
DECLARE @FromSchema varchar(100)
DECLARE @ToSchema varchar(100)
SET @FromSchema = N'Softricity_User'
SET @ToSchema = N'dbo'
DECLARE @Done bit
DECLARE @LASTNAME varchar(1000)
SET @Done=0 -- insert top of tree
SET @LASTNAME = 'ZZZZZZ'
WHILE @Done=0
BEGIN
select top 1 @LASTNAME=[name] from sys.sql_modules sm
inner join sys.objects so on sm.object_id = so.object_id
where so.schema_id = schema_id(@FromSchema) and so.name like N'sp%'
and [name] < @LASTNAME
order by [name] desc
IF @@rowcount=0
begin
SET @Done=1
end
else
begin
exec ( 'print ''moving '+@LASTNAME+'''')
exec ('ALTER SCHEMA '+@ToSchema+' TRANSFER '+@FromSchema+'.' + @LASTNAME )
end
END
madvirtualizer
The Mad Virtualizer at Microsoft 