Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
OK, I posted too soon and have found a solution myself :) There is an option during the SQL Server installation that defaults to installing a named instance (rather than a default instance) of the db engine. Annoyingly there doesn't seem to be any way to change this after it's installed so I removed and reinstalled SQL Server, this time selecting the 'default instance' option and it works fine. Might be something that needs to be allowed for in the EVS install process I guess. Another small improvement would be a message saying 'success' when the initialisation finished as the web page just navigated back to the home page and I wasn't sure if it had worked or not. Colin "Colin Fraser" <cfraser at levelfour.com> wrote in message news:gsa7i5$lkd$1 at paris.nodomain.org... > Hi, > > I've been trying to install the trial of EVS to evaluate it but I can't > get the DB to initialise when I go through Express Setup. > > I'm running Win 2003 server with SQL Server 2005 Express installed and EVS > build 3292. > > I get the following message at the foot of the webpage: > > Repository initialisation failed : No error: Database error: Unable to > create database: Microsoft OLE DB Provider for SQL Server: > [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection. at > .VirtualFs.cpp:490 at .FileInfoFile.cpp:1568 : no error > > Error appears to be something to do with the SQL server instance name. > How does EVS pick up the SQL server details? I can't find an obvious > config file that would need to be changed to set the connection string > etc. > > Regards, > > Colin > >