MSDE 2000 installation on Windows 2000 SP2 Professional using Windows Installer Merge Modules from SP1

MSDE 2000 installation on Windows 2000 SP2 Professional using Windows Installer Merge Modules from SP1

Post by William Brook » Sat, 18 Aug 2001 18:09:13



I am creating a Windows Installer installation using the MSDE merge modules.
The merge modules are from the SQL Server Desktop Engine Service Pack 1 CD.
During installation the following error occurs:

    "Setup failed to configure the sever. Refer to the server error logs and
setup error logs for more information."

This error is almost immediately followed by:

    "An error has occurred registering this installation of SQL Server
Desktop Engine with MDAC."

After the previous two errors are displayed, the installation appears to
properly roll back and terminate.

The following is an excerpt from the verbose MSI log containing the errors
and the surrounding information:

Action 4:43:13: ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
MSI (s) (08:0C): Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397
B,ActionType=1025,Source=BinaryServ,Target=ConfigServer,)
MSI (s) (08:0C): Creating MSIHANDLE (390) of type 790536 for thread 780
Loading extended custom action library sqlcax.dll
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -P "" -I "MSSQLSERVER" -Q
"SQL_Latin1_General_CP1_CI_AS""
Internal Error 2835. ErrorIcon, SetupError
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (08:0C): Executing op:
ActionStart(Name=RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
Action 4:44:46: RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
MSI (s) (08:0C): Executing op:
CustomActionSchedule(Action=RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C0643
97B,ActionType=1025,Source=BinaryWith,Target=RegSQLWithMDAC,)
MSI (s) (08:0C): Creating MSIHANDLE (395) of type 790536 for thread 780
Loading extended custom action library sqlcax.dll
Starting custom action RegSqlWithMdac
Internal Error 2835. ErrorIcon, SetupError
An error has occurred registering this installation of SQL Server Desktop
Engine with MDAC.
Action ended 4:44:56: InstallFinalize. Return value 3.

Having determined that the problem appears to occur in the ConfigureServer
custom action, I modified the sqlcax.dll image in SQLBASE.MSM to force the
action to call CnfgSvr.exe with "-V 0" rather than "-V 1". During
installation with the modified version, ConfigureServer indicates that it is
unable to connect to the SQL Server after successfully starting the service.
Further testing has allowed me to produce the following log file from
CnfgSrv.exe:

############################################################################
###

Starting Service ...

SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(GetOverLappedResult()).
driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(GetOverLappedResult()).
driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(GetOverLappedResult()).
SQL Server configuration failed.

############################################################################
###

Based on KB article Q285100, it appears that CnfgSrv should use the Shared
Memory protocol to connect to the newly installed service. Although in my
case it is obviously attempting to use named pipes. The remainder of Q285100
does not appear to apply in this instance as the computer name consists
entirely of uppercase characters.

From all of this I have three questions:

    1. What is causing the Configure Server custom action to fail?
    2. Is SQL Server designed to only allow Shared Memory connections during
setup?
    3. If the answer to 2 is yes, what controls the order in which the SQL
ODBC driver chooses connection protocols?

Thank you for any information,
William

 
 
 

MSDE 2000 installation on Windows 2000 SP2 Professional using Windows Installer Merge Modules from SP1

Post by Alain Sienaer » Thu, 23 Aug 2001 05:42:21


William,

A few months ago we had similar problems installing MSDE and turned out that
there was a misconfiguration in our ODBC files. We were able to trace the
problem by using the ComCheck tool which allows you diagnosing installation
issues with Microsoft Data Access Components (MDAC).
Hope this helps,
--
Prolix Webmaster
http://www.prolix.be
The best newsgroup archive available


Quote:> I am creating a Windows Installer installation using the MSDE merge
modules.
> The merge modules are from the SQL Server Desktop Engine Service Pack 1
CD.
> During installation the following error occurs:

>     "Setup failed to configure the sever. Refer to the server error logs
and
> setup error logs for more information."

> This error is almost immediately followed by:

>     "An error has occurred registering this installation of SQL Server
> Desktop Engine with MDAC."

> After the previous two errors are displayed, the installation appears to
> properly roll back and terminate.

> The following is an excerpt from the verbose MSI log containing the errors
> and the surrounding information:

> Action 4:43:13: ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
> MSI (s) (08:0C): Executing op:

CustomActionSchedule(Action=ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397
Quote:> B,ActionType=1025,Source=BinaryServ,Target=ConfigServer,)
> MSI (s) (08:0C): Creating MSIHANDLE (390) of type 790536 for thread 780
> Loading extended custom action library sqlcax.dll
> Starting custom action ConfigServer
> Executing "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -P "" -I "MSSQLSERVER" -Q
> "SQL_Latin1_General_CP1_CI_AS""
> Internal Error 2835. ErrorIcon, SetupError
> Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> MSI (s) (08:0C): Executing op:
> ActionStart(Name=RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
> Action 4:44:46: RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
> MSI (s) (08:0C): Executing op:

CustomActionSchedule(Action=RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C0643

- Show quoted text -

Quote:> 97B,ActionType=1025,Source=BinaryWith,Target=RegSQLWithMDAC,)
> MSI (s) (08:0C): Creating MSIHANDLE (395) of type 790536 for thread 780
> Loading extended custom action library sqlcax.dll
> Starting custom action RegSqlWithMdac
> Internal Error 2835. ErrorIcon, SetupError
> An error has occurred registering this installation of SQL Server Desktop
> Engine with MDAC.
> Action ended 4:44:56: InstallFinalize. Return value 3.

> Having determined that the problem appears to occur in the ConfigureServer
> custom action, I modified the sqlcax.dll image in SQLBASE.MSM to force the
> action to call CnfgSvr.exe with "-V 0" rather than "-V 1". During
> installation with the modified version, ConfigureServer indicates that it
is
> unable to connect to the SQL Server after successfully starting the
service.
> Further testing has allowed me to produce the following log file from
> CnfgSrv.exe:

############################################################################

- Show quoted text -

Quote:> ###

> Starting Service ...

> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659

> Connecting to Server ...

> driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (GetOverLappedResult()).
> driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (GetOverLappedResult()).
> driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (GetOverLappedResult()).
> SQL Server configuration failed.

############################################################################

- Show quoted text -

Quote:> ###

> Based on KB article Q285100, it appears that CnfgSrv should use the Shared
> Memory protocol to connect to the newly installed service. Although in my
> case it is obviously attempting to use named pipes. The remainder of
Q285100
> does not appear to apply in this instance as the computer name consists
> entirely of uppercase characters.

> From all of this I have three questions:

>     1. What is causing the Configure Server custom action to fail?
>     2. Is SQL Server designed to only allow Shared Memory connections
during
> setup?
>     3. If the answer to 2 is yes, what controls the order in which the SQL
> ODBC driver chooses connection protocols?

> Thank you for any information,
> William


 
 
 

MSDE 2000 installation on Windows 2000 SP2 Professional using Windows Installer Merge Modules from SP1

Post by pswif » Fri, 24 Aug 2001 10:00:20


Hello, William,

Sorry but I can't help with your problem. Where did you get the SQL Server
Desktop Engine Service Pack 1 CD? Does it contain a SQLBASE.MSM file dated
12/5/2000 or later? I downloaded the 3 sp1 files from the Web, but these do
not contain the file I need.

Thanks,
Patricia


Quote:> I am creating a Windows Installer installation using the MSDE merge
modules.
> The merge modules are from the SQL Server Desktop Engine Service Pack 1
CD.
> During installation the following error occurs:

>     "Setup failed to configure the sever. Refer to the server error logs
and
> setup error logs for more information."

> This error is almost immediately followed by:

>     "An error has occurred registering this installation of SQL Server
> Desktop Engine with MDAC."

> After the previous two errors are displayed, the installation appears to
> properly roll back and terminate.

> The following is an excerpt from the verbose MSI log containing the errors
> and the surrounding information:

> Action 4:43:13: ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
> MSI (s) (08:0C): Executing op:

CustomActionSchedule(Action=ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397
Quote:> B,ActionType=1025,Source=BinaryServ,Target=ConfigServer,)
> MSI (s) (08:0C): Creating MSIHANDLE (390) of type 790536 for thread 780
> Loading extended custom action library sqlcax.dll
> Starting custom action ConfigServer
> Executing "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -P "" -I "MSSQLSERVER" -Q
> "SQL_Latin1_General_CP1_CI_AS""
> Internal Error 2835. ErrorIcon, SetupError
> Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> MSI (s) (08:0C): Executing op:
> ActionStart(Name=RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
> Action 4:44:46: RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
> MSI (s) (08:0C): Executing op:

CustomActionSchedule(Action=RegSQLWithMDAC.2D02443E_7002_4C0B_ABC9_EAB2C0643

- Show quoted text -

Quote:> 97B,ActionType=1025,Source=BinaryWith,Target=RegSQLWithMDAC,)
> MSI (s) (08:0C): Creating MSIHANDLE (395) of type 790536 for thread 780
> Loading extended custom action library sqlcax.dll
> Starting custom action RegSqlWithMdac
> Internal Error 2835. ErrorIcon, SetupError
> An error has occurred registering this installation of SQL Server Desktop
> Engine with MDAC.
> Action ended 4:44:56: InstallFinalize. Return value 3.

> Having determined that the problem appears to occur in the ConfigureServer
> custom action, I modified the sqlcax.dll image in SQLBASE.MSM to force the
> action to call CnfgSvr.exe with "-V 0" rather than "-V 1". During
> installation with the modified version, ConfigureServer indicates that it
is
> unable to connect to the SQL Server after successfully starting the
service.
> Further testing has allowed me to produce the following log file from
> CnfgSrv.exe:

############################################################################

- Show quoted text -

Quote:> ###

> Starting Service ...

> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659

> Connecting to Server ...

> driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (GetOverLappedResult()).
> driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (GetOverLappedResult()).
> driver={sql server};server=WIN2KVERT;UID=sa;PWD=;database=master
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
> (GetOverLappedResult()).
> SQL Server configuration failed.

############################################################################

- Show quoted text -

Quote:> ###

> Based on KB article Q285100, it appears that CnfgSrv should use the Shared
> Memory protocol to connect to the newly installed service. Although in my
> case it is obviously attempting to use named pipes. The remainder of
Q285100
> does not appear to apply in this instance as the computer name consists
> entirely of uppercase characters.

> From all of this I have three questions:

>     1. What is causing the Configure Server custom action to fail?
>     2. Is SQL Server designed to only allow Shared Memory connections
during
> setup?
>     3. If the answer to 2 is yes, what controls the order in which the SQL
> ODBC driver chooses connection protocols?

> Thank you for any information,
> William

 
 
 

1. SQL 2000 Merge Modules with Windows Installer (Installshield Edition)

Hi,

Im trying to distribute MSDE 2000 in my setup package.  This is what i've
done:

Copied the files from MSM\*.* and MSM\1033\*.* from the CD to the objects
directory.

Referenced the following Merge Modules in the project:
Connectivity Merge Module (connect.msm)
DMO Core Files Merge Module (dmo.msm)
DMO Resource Files Merge Module (dmo_res.msm)
DTC Merge Module (dtc.msm)
DTS Core Files Merge Module (dts.msm)
DTS Resource Files Merge Module (dts_res.msm)
Replication Core Files Merge Module (repl.msm)
Replication Resource Files Merge Module (repl_res.msm)
SCM Developer Files Merge Module (dev_scm.msm)
Shared Merge Module (shared.msm)
SQL Agent Core Files Merge Module (sqlagent.msm)
SQL Agent Resource Files Merge Module (sqlagent_res.msm)
SQL Server Core Files Merge Module (sqlsvr.msm)
SQL Server Resource Files Merge Module (sqlsvr_res.msm)
SQL Server Setup Merge Module (sqlbase.msm)
SQL Server Tools Core Files Merge Module (tools.msm)
SQL Server Tools Resource Files Merge Module (tools_res.msm)

I've also set the following Properties in Advanced Views, Property Manager:
SqlInstanceName        instance1
SqlSecurityMode        SQL

The project builds ok but its rollbacks just after it says Installing
Services.

Has anybody got any ideas or maybe a sample project to help me get this
working?  I am using Installshield Pro - Windows Installer Edition 2.03.

Kind Regards,
Chris Bond

2. Sybase DBAs needed Nationwide-U.S.-(Recruiter)

3. MSDE 2000 Beta 2 installation fails using MSM merge modules

4. ODBC error

5. problems with MSDE installation on Windows 2000 professional

6. Populate Dropdown From Database?

7. MSDE-2000 SP1 Merge Modules

8. LOOKING FOR A ORACLE JOB

9. MSDE 2000 SP1 Merge Modules

10. MSDE 2000 SP1 merge modules

11. MSDE-2000-SP1 Merge Modules

12. MSDE-2000 SP1 Merge Modules