I did a fresh install of 4.1 and got the same issue.
My error came in assuming that VCDB and UMDB would use the same collation, given that VCDB is documented to use "SQL_Latin1_General_CP1_CI_AS" as shown in the example script in "vsp_41_esxi_i_vc_setup_guide.pdf". None of the documentation i can find specifies the correct collation for UMDB, but apparently it needs "Latin1_General_CI_AS"
So now my script does this-
USE
GO
CREATE DATABASE ON PRIMARY
(NAME = N'vcdb', FILENAME = N'D:\MSSQL.1\DB\VCDB.mdf', SIZE = 10000KB, FILEGROWTH = 10% )
LOG ON
(NAME = N'vcdb_log', FILENAME = N'D:\MSSQL.1\Logs\VCDB.ldf', SIZE = 1000KB, FILEGROWTH = 10%)
COLLATE SQL_Latin1_General_CP1_CI_AS
GO
CREATE DATABASE ON PRIMARY
(NAME = N'umdb', FILENAME = N'D:\MSSQL.1\DB\UMDB.mdf', SIZE = 10000KB, FILEGROWTH = 10% )
LOG ON
(NAME = N'umdb_log', FILENAME = N'D:\MSSQL.1\Logs\UMDB.ldf', SIZE = 1000KB, FILEGROWTH = 10%)
COLLATE Latin1_General_CI_AS
GO
USE
GO
CREATE USER FOR LOGIN
GO
USE
GO
EXEC sp_addrolemember N'db_owner', N'BUILTIN\Administrators'
GO
USE
GO
CREATE USER FOR LOGIN
GO
USE
GO
EXEC sp_addrolemember N'db_owner', N'BUILTIN\Administrators'
GO
USE
GO
CREATE USER FOR LOGIN
GO
USE
GO
EXEC sp_addrolemember N'db_owner', N'BUILTIN\Administrators'
GO
I've got no idea if you can change the collation in your situation or if you need to delete the database and start again. In my case thats what I did.
