Installing MSDE SP3 to Win98 causes an error.

Ok I have an MSI file that installs an instance of the MSDE. I recently updated my install to used the SP3 MSMs of the MSDE. I have the installation working correctly on XP. However it fails rather quickly on install to Win98. I will paste the log file of the failure below.

To create the installation I used the VisualStudio installer. Afte the installtion I use ORCA and edit the MSI with the following values in the property table.

ProductLanguage = 1033
SqlBlankPwd = 1
SqlSecurityMode = SQL

No special actions are being used by my installer. Yet according to MS the reason for my error is that I am using a special action with a non-c++ dll (KB Article (http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B306627)) . I am guessing that this is something that MS is doing. Has anyone else gotten a successful install of SP3 onto Win98? Any info would be helpful.

Mike Villaronga
mike_villaronga@.yahoo.com

LogFile:

Internal Error 2737. StreamSupportFiles.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B, C:\WINDOWS\TEMP\MSI60B6.TMP, StreamSupportFiles
=== Logging stopped: 2/3/03 10:06:17 ===I have not gotten SP3 to install on win98. I have tried to do it manually as well as from an install shield application. I get an error message that there is a dll missing. It doesn't specify which dll or give any kind of clue.

[SIZE=1]Originally posted by mvillaronga
Ok I have an MSI file that installs an instance of the MSDE. I recently updated my install to used the SP3 MSMs of the MSDE. I have the installation working correctly on XP. However it fails rather quickly on install to Win98. I will paste the log file of the failure below.

I am guessing that this is something that MS is doing. Has anyone else gotten a successful install of SP3 onto Win98? Any info would be helpful.

Installation problem

I have installed SQL Server Express Edition using SQLServer2005_SSMSEE.msi.
All was fine.
But, when I managed to connect to the server when
I choosed <browse for more ...> in the server name combo
the application was unable to find a server (either local or remote. I think that the server should be a local one if I installed it locally on the machine).
I tried many combinations for the server name based on the machine and domain name:

MACHINE
MACHINE\MACHINE
DOMAIN\MACHINE

but all the times the following error occured:
TITLE: New Server Registration

Testing the registered server failed. Verify the server name, login credentials, and database, and then click Test again.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK
Can anyone help me to register a server?

Thanks,

Radu

Hi.

Try " (local)\SQLEXPRESS"

The default instant name of Sql Server 2005 Express Edition is SQLEXPRESS (case-insensitive)

".\SQLEXPRESS" Will work if you have TCP/IP access enabled (See your SQL Server service manager)

MACHINE\SQLEXPRESS should work too.

Hope this helps

|||

I having issues with SQL Express remote issues, I have turned remote on in the area configuration and enabled all protocols.

MachineName/SQLEXPRESS on remote machines worked for about a day and than on remote machines in the network no longer can use the Management tool to see SQL engine. I checked and the MachineName/SQLEXPRESS is definitely registered.

Everything seems to work as expected on the local machine. The puzzeling thing is it did work for about a day and nothing changes on the network.

Any help would be very appreciated

Installation problem

I have installed SQL Server Express Edition using SQLServer2005_SSMSEE.msi.
All was fine.
But, when I managed to connect to the server when
I choosed <browse for more ...> in the server name combo
the application was unable to find a server (either local or remote. I think that the server should be a local one if I installed it locally on the machine).
I tried many combinations for the server name based on the machine and domain name:

MACHINE
MACHINE\MACHINE
DOMAIN\MACHINE

but all the times the following error occured:
TITLE: New Server Registration

Testing the registered server failed. Verify the server name, login credentials, and database, and then click Test again.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK
Can anyone help me to register a server?

Thanks,

Radu

Hi.

Try " (local)\SQLEXPRESS"

The default instant name of Sql Server 2005 Express Edition is SQLEXPRESS (case-insensitive)

".\SQLEXPRESS" Will work if you have TCP/IP access enabled (See your SQL Server service manager)

MACHINE\SQLEXPRESS should work too.

Hope this helps

|||

I having issues with SQL Express remote issues, I have turned remote on in the area configuration and enabled all protocols.

MachineName/SQLEXPRESS on remote machines worked for about a day and than on remote machines in the network no longer can use the Management tool to see SQL engine. I checked and the MachineName/SQLEXPRESS is definitely registered.

Everything seems to work as expected on the local machine. The puzzeling thing is it did work for about a day and nothing changes on the network.

Any help would be very appreciated

Installation of SQL Express from my MSI

I've written an application that needs to also deploy SQL Express. In the MSI for my application, I want to install SQL Express. The problem is that when I call sqlexpr.exe, I eventually get an error that it can't install because another instance of MSI is currently running (my instance). I've seen posts on doing silent installs of SQL Express by extracting the setup package and calling setup.exe directly with a modified settings file, but this still does not solve my problem that it will start up a new instance of MsiExec.exe.

I think that I need to do a nested install of the SQL Express MSI from my MSI. I've found several msi's in the setup subdirectory, but which do I needs to call, in what order, and how do I configure them to install the engine in my own named instance of SQL Express?

ThanksMichael,

You need to write a bootstrapper for your application because SQL Server Express is ultimately an MSI based installation and Windows Installer cannot run more than a single MSI at a given time - in other words, an MSI cannot call another MSI. Don't let the fact that SQL Server Express is wrapped in a self-extracting executable fool you. SQLEXPR.EXE expands into a setup.exe and several MSIs. Setup.exe is launched automatically which will then call each of the MSIs in serial fashion. We're working on a white paper that walks through exactly how to embed Express in a custom application but it's not quite ready yet.

In the mean time, you should expand the SQLEXPR.exe package to a folder using SQLEXPR.exe /X, you'll be prompted for a folder to expand to. Once the package has been expanded take a look at the template.ini file. This will give you a list of command line parameters you can use for installing Express. These can be passed directly into SQLEXPR.exe which will in turn pass them to Setup.exe. Passing the /qn switch will cause SQL Server Setup to run in fill quiet mode - no GUI.

Your command line should look something like "sqlexpr.exe /qn ADDLOCAL=SQL_Engine INSTANCENAME=Foobar"

I believe that Visual Studio has help information on creating a setup bootstrapper.

Good luck and keep your eyes open for the white paper - it'll be posted to MSDN.

Cheers,
Dan