Posts Tagged ‘schema’

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
WHILE @Done=0  
    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 like N'sp%'
    and [name] < @LASTNAME
    order by [name] desc

    IF @@rowcount=0 
            SET @Done=1 
            exec ( 'print ''moving '+@LASTNAME+'''')
            exec ('ALTER SCHEMA '+@ToSchema+' TRANSFER '+@FromSchema+'.' + @LASTNAME  )

Planning for a Microsoft VDI Deployment

April 13, 2011 2 comments

In the past, desktop virtualization administrators have used Microsoft for only part of their VDI (virtual desktop infrastructure) while using solutions from VMWare of Citrix as the primary basis.

You may be already familiar with Microsoft’s client-hosted enterprise desktop virtualization solution – MED-V. VDI is Microsoft’s server-based desktop virtualization solution combining all of the following for engine support all the way to complete end-to-end management:

  • Hyper-V
  • Windows 7
  • Windows Server 2008 R2
  • System Center Virtualization Manager
  • Remote Desktop Services
  • RemoteFX

Windows Server 2008 R2 Service Pack 1 adds two new components (RemoteFX and Dynamic Memory) that fill two holes related to management flexibility and user experience that now make Microsoft almost a non-brainer choice for your VDI solution.

Microsoft’s virtualization main page is found here:

First things first,

Licensing Information regarding VDI. One of the first things customers want to know is what are the costs and the potential cost savings:

In terms of how it works, here is Microsoft’s VDI solution at a high level:

The next items of concern are often what infrastructure changes will need to be made. Moving to a VDI environment will require the presence of a Windows 2008 or Windows 2008 R2 domain controller (depending on the Hyper-V/RDS platform being used.) You will also need to update the schema accordingly to support these domain controllers and subsequent services required for the VDI environment.

Here are the outlines of the Windows 2008 and Windows 2008 R2 Schema changes:

Windows 2008:

Windows 2008 R2:

You will need to have Windows 2008 Schema changes minimally however, the minimum AD domain level supported is Windows 200 native. Windows 200 mixed or Windows 2003 interim are not supported.


The following are important considerations about assigning a personal virtual desktop to a user in AD DS:

  • To deploy personal virtual desktops, your schema for the Active Directory forest must be at least Windows Server 2008. To use the added functionality provided by the Personal Virtual Desktop tab in the User Account Properties dialog box in Active Directory Users and Computers, you must run Active Directory Users and Computers from a computer running Windows Server 2008 R2 or a computer running Windows 7 that has Remote Server Administration Tools (RSAT) installed.
  • You must use a domain functional level of at least Windows 2000 Server native mode. The functional levels Windows 2000 Server mixed mode and Windows Server 2003 interim mode are not supported.
  • Ensure that the RDVH-SRV computer meets the Hyper-V installation prerequisites (
  •  The user account and the virtual machine must both be members of an Active Directory domain.
  • Personal virtual desktops can only use Windows client operating systems. You cannot install Windows Server® 2008 R2 on a virtual machine and assign it as a personal virtual desktop.
  • A user can be assigned only one personal virtual desktop at a time.
  • A virtual machine can be assigned as a personal virtual desktop to only one user at a time.
  • The name of the virtual machine in the Hyper-V Manager tool must match the fully qualified domain name (FQDN) of the computer.

 Sizing Concerns:

Alongside of instructure changes and concerns is capacity planning. Here is a good webcast on planning and sizing session virtualization and bandwidth for VDI:

 And a good document as well:

 RD Web Access Information:

 RD gateway Information:

 Why VDI for Hyper-v Whitepaper:

 Windows 2008 R2 SP1’s RemoteFX feature for Hyper-V

 If you have time, also check out the VDI videos on technet Edge: