Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MSDE Merge Moudles

63 views
Skip to first unread message

Yehonatan Levi

unread,
Oct 8, 2002, 3:08:53 PM10/8/02
to
Hello.

I am trying to create an installation with MSDE embedded in it. I have
already read
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q321283
which speaks about a problem with the order of GetSQLStates custom action
and StreamSupportFile custom action and used ORCA to change the order.

Happily after finding this article the setup actually starts running but
then stops again(after doing some stuff) with error code 2613
here's a snippet from the end of the setup log
===============
MSI (s) (50:88): Doing action: RemoveExistingProducts
Action start 21:31:35: RemoveExistingProducts.
MSI (s) (50:88): Note: 1: 2613
MSI (s) (50:88): Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2613: RemoveExistingProducts action sequenced incorrectly.
DEBUG: Error 2835: The control ErrorIcon was not found on dialog
ErrorDialog
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2835. The
arguments are: ErrorIcon, ErrorDialog,
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2613. The
arguments are: , ,
MSI (s) (50:88): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50:88): Product: SetupMultiLayer -- The installer has encountered
an unexpected error installing this package. This may indicate a problem
with this package. The error code is 2613. The arguments are: , ,

Action ended 21:31:55: RemoveExistingProducts. Return value 3.
MSI (s) (50:88): Machine policy value 'DisableRollback' is 0
MSI (s) (50:88): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollb
ack\Scripts 3: 2
MSI (s) (50:88): Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollb
ack\Scripts 3: 2
MSI (s) (50:88): Unlocking Server
Action ended 21:31:55: INSTALL. Return value 3.
==============

it seems there is a problem with the Action: RemoveExistingProducts :
DEBUG: Error 2613: RemoveExistingProducts action sequenced incorrectly.

It seems i have gone this far i am almost there, what seems to be the
problem? this is not in the knowledge base and this error repeats on two
computers that i have tested the installation on so far.

Any help will be really appreciated.

-Yehonatan


Phil Wilson

unread,
Oct 8, 2002, 3:56:16 PM10/8/02
to
Tell us where you sequenced RemoveExistingProducts? There are restrictions on where it can be
placed.

"Yehonatan Levi" <nic...@somewhere.com> wrote in message news:#ehvO1vbCHA.1808@tkmsftngp10...

Yehonatan Levi

unread,
Oct 8, 2002, 6:23:29 PM10/8/02
to
The sad part is that other than the GetSqlStates and StreamSupportFile
sequence changes i didn't do anything on my own, i would never choose to
play with this stuff why is it wrong? this is an installation i let VS.NET
Setup and Deploy do for me...

but to answer your question in orca i see it is inside
InstallExecuteSequence table with sequence number 1525

where should it be? is this really the answer? to move it?

"Phil Wilson" <phil....@unisys.spamcom> wrote in message
news:ONfjYSwbCHA.2188@tkmsftngp08...

Phil Wilson

unread,
Oct 8, 2002, 8:19:33 PM10/8/02
to
I don't think the raw number is much help. Perhaps I should refer you to the docs in the Platform
SDK about where RemoveExistingProducts can be sequenced:
Quoting.......

Sequence Restrictions
The RemoveExistingProducts action must be scheduled in the action sequence in one of the following
locations.

Between the InstallValidate action and the InstallInitialize action. In this case, the installer
removes the old applications entirely before installing the new applications. This is an inefficient
placement for the action because all reused files have to be recopied.

After the InstallInitialize action and before any actions that generate execution script.

Between the InstallExecute action, or the InstallExecuteAgain action, and the InstallFinalize
action. Generally the last three actions are scheduled right after one another: InstallExecute,
RemoveExistingProducts, and InstallFinalize. In this case the updated files are installed first and
then the old files are removed. However, if the removal of the old application fails, then the
installer rolls back both the removal of the old application and the install of the new application.

After the InstallFinalize action. This is the most efficient placement for the action. In this case,
the installer updates files before removing the old applications. Only the files being updated get
installed during the installation. If the removal of the old application fails, then the installer
only rolls back the uninstallation of the old application.

end quote.

"Yehonatan Levi" <nic...@somewhere.com> wrote in message news:uoIn8hxbCHA.1692@tkmsftngp09...

Yehonatan Levi

unread,
Oct 9, 2002, 6:29:43 AM10/9/02
to
Thank you VERY much phil,

I have changed the location of the RemoveExistingItems to be right after
InstallFinalize and it works now. The installation progress bar acts a bit
strange, when the installation is finished its only filled half way, but
that doesn't matter. as long as it works...

There are still some issues: The installation does prompt the user to
reboot. But if the user does not reboot then the sql server is not started
and my application fails to run.. why?
and secondly the Sql Server Service Manager(tray icon) is not started either
where it should (even after reboot) because i have used ALL the .msm's in my
installation

I thank you a lot for your help.

-Yehonatan

I wanted to ask if you might know why the SQL Server Service Manager is not


"Phil Wilson" <phil....@unisys.spamcom> wrote in message

news:OSlCglybCHA.2172@tkmsftngp08...

Eric Youngdale

unread,
Oct 10, 2002, 8:45:51 AM10/10/02
to

"Yehonatan Levi" <nic...@somewhere.com> wrote in message
news:uy9Lt33bCHA.1512@tkmsftngp08...

> There are still some issues: The installation does prompt the user to
> reboot. But if the user does not reboot then the sql server is not started
> and my application fails to run.. why?

It appears that you have to do this manually. Not quite sure why this
is the case, but we ran into this as well.

For this type of thing, we sometimes have to start services with custom
actions - it gets tricky with all of the different combinations of install,
uninstall, upgrade, patch, etc, etc. Usually what I end up doing is writing
the custom action to check to see if the service is present and registered
and then start it if this is the case. Otherwise just return success.

In looking at the resulting .msi file, it looks like the MSDE merge
modules will automatically stop and deregister the thing on uninstall
however.

-Eric

Michael D Edwards (Microsoft)

unread,
Oct 10, 2002, 1:25:03 PM10/10/02
to
Prompt for reboot can mean:
- windows installer needed to be updated (this will happen before the msde
.msi or .msp runs)
- mdac component needs to be updated (it is always loaded, so must be
replaced at startup)
- one of replaced sql server components that is running needs to be updated
(I am not clear on how to determine in advance of running an msde install
when this condition will occur, but am working to figure that out)

Note that when msde setup completes, it does leave the sql server service
running, though it is marked for autostart on WinNT/Win2K/WinXP/Win.NET
systems, so will start upon subsequent reboots. The reason for this is to
allow time to change the service account for starting msde services -
LocalSystem is the default account, but runs with Admin privileges.
--
Michael Edwards
MSDE Program Manager
Microsoft Corp
This posting is provided "AS IS" with no warranties, and confers no rights.

"Eric Youngdale" <er...@andante.nOsPaM.org> wrote in message
news:3Eep9.188247$TX5.7...@news1.east.cox.net...

Yehonatan Levi

unread,
Oct 13, 2002, 4:13:46 AM10/13/02
to
I am not sure you understood my problem.

I am using the merge modules, but when the installation completes, The
SQLSERVER service does not get run, and only if i reboot(sometimes only if i
reboot twice) it is run. The installation does not prompt the user to
restart and thus the SQLSERVER will not get to run unless the user restarts
the system to get the SQLSERVER service to run...

What to do?
"Michael D Edwards (Microsoft)" <mich...@microsoft.com> wrote in message
news:3da5b7f5$1...@news.microsoft.com...

Phil Wilson

unread,
Oct 14, 2002, 2:32:25 PM10/14/02
to
There are two issues here:
1) Is the installation complete after you've run the installation and before the reboot? If there
are no pending renames or other system changes which need a reboot, then the installation is
complete.
2) You can start the service by simply putting the name of the sql service in the ServiceControl
table and marking it to be started on an install. If the only reason you need a reboot is to start
the SQL service (because it's marked automatic) that's overkill. Just start it during the install.

"Yehonatan Levi" <nic...@somewhere.com> wrote in message news:eEqLR#ocCHA.2456@tkmsftngp08...

Spencer

unread,
Oct 31, 2002, 7:15:39 AM10/31/02
to
I was wondering if anyone knew what the default instance name is, and how to
edit the servicecontrol table in order to have the sql service start without
a reboot? I now have orca and assume that you edit the servicecontrol table
with that tool but I do not know what row/rows to edit to enable the sql
service to start right away.
Thanks
Spencer

Marc Allard

unread,
Oct 31, 2002, 7:25:16 AM10/31/02
to
Perheaps you can try to execute a
net start serviceName
to start msde
Marc Allard

"Spencer" <spic...@globaltradingsystems.com> a écrit dans le message de
news: u40tJcNgCHA.3752@tkmsftngp08...

0 new messages