Categories: MSDN / DotNet / Java / Scripts / Linux / PHP Ask - La ask - La Answer

Problem with nested install of SQL 2005 Express...

I create Installer for my company, with using SQL 2005 Express and its files database. I used MS Build bootstrapper before to install MS SQL 2005 Express in my installer and it was installed before my product installed, and there is no problems...
But now I need to install Express during setup, because it must be installed NOT everytime (if user choose, in bootstrapper it is impossible).
I know that during execute sequence it is not possible: two installer are not lived simultaneously in memory and I move SQL 2005 Express installation to UISequence.

But everytime error occured during install (list from sql server install log):
MSI (s) (00:6C) [18:54:38:015]: Machine policy value 'DisableUserInstalls'
is 0 MSI (s) (00:6C) [18:54:38:015]: Note: 1: 1309 2: 5 3:
c:\03cae475d5363b997aa6d2d8\setup\sqlncli.msi
MSI (s) (00:6C) [18:54:38:015]: MainEngineThread is returning 110
The system cannot open the device or file specified.

So there is no error, "Another installer process in memory", but another
very strange error and I dont know what to do :(
I try quiet and usual SQL express install - but that doesnt matter.

It seems, that package sqlexpr32.exe after unpacking cant see its files... What must I do to install SQL 2005 Express during my UI of Installer?

Or may some other ways to install SQL 2005 Express, with some secret keys?
[1434 byte] By [drag79] at [2007-11-11 7:44:04]
# 1 Re: Problem with nested install of SQL 2005 Express...
I have a commercial application at work that has to do the same task as you ask.

The way they accomplish this task is by using two install applications. One is a server install or so it is called, but really is a more like a wizard application. It allows the user to set up a new application database and it has a few other DB utilities. Once this is done you can install as many client applications as needed since they assume a database has been installed and don't need to deal with that. You might have to reconsider how your client apps connect to the database (connection string or user prompting).

Hope this helps,

Xela220
Xela220 at 2007-11-11 23:47:47 >