Hi all,

I am having a issue with the above software, I will start from the top.

I am using Wise Package Studio 5.1 Professional Edition to take a SetupCapture then used Wise Installer Editor review all settings. All goes ok, then I compile the software. All the above goes with out a problem. I then try and run the new MSI file on a blank machines and reboot. After the reboot, I login and get the following msg. "The specified service does not exist as an installed service." This occurrs while trying to start MSSQLServer service.

:::more info::::
If installed from installation files provided by Microsoft, "Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)" installation creates 3 services on the computer. (1) MSSQLSERVER, (2) SQLServerAgent, (3) MSSQLServerADHelper. However, the package I create fails to create MSSQLSERVER AND SQLServerAgent services and this is why I am getting the error about not being able to start a service.

I am not sure, why the captures and my app package is not creating the necessary services.

This is the second time I have tried, as the first time. I went through and copied all the files and registry in to it, just incase it missed some out.

Any help would be gratefully accepted.

RK
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi,

I didn't package this myself but my colleague did and it wasn't easy. He had problems snapping the services and ended up using a product called Prism Pack http://www.newboundary.com/ to get around it. He sent me this - hope it means something to you:

"Snapped the app using Wise Package Studio 4.5, had to stop some processes before msi would save. Services were missed out added back in via Services Install table. MSSQLSERVER was not added to H/W profile so resnapped in Prism and added in some missing ENUM HKLM-SYSTEM keys.

Will not snap in standalone Wise for windows app either. Pretty sure problem is related to the fact Wise uses the same files as the application and therefore is unable to fully snap it. Recommend snaping in Prism and then copying the tables to your Wise package so it conforms with your standards."


Good luck!
Rob.
Answered 11/11/2004 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
If at all possible I would try to avoid repackaging MSDE it is already an MSI.

Try using the following command lines to install the application:

<Source>\Setup.exe /settings <source>\setup.ini ALLUSERS=1 /l*i <Location of log file> /qb!-

and SP3

<sSource>\SQL2000-KB815495-8.00.0818-ENU.exe /s /a /q /allinstances

In my setup.ini I have the following parameter:
SAPWD=

A silent install requires a SA password.
Answered 11/11/2004 by: frisbiej
Senior Yellow Belt

Please log in to comment
0
Some things just shouldnt be repackaged like MS Office, Visio, Project and also MSDE.

It makes very low level changes to the OS and you can't capture those changes correctly. MS builds in dll's to carry out their Custom Actions so that the installations don't hurt the base OS.

Try the commandline options for the best result. You can also wrap the install in an msi if you are deploying with Group Policy.
Answered 11/13/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
I am not sure about Wise, but I know that Adminstudio offers a custom Merge Module that can be added to a MSI.
Answered 11/14/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
You can do a setup capture no problem as long as you use the SQL Server SP3 merge modules found on the MSDN CDs. For some reason the servicepack download from MS gives you the merge module that will fail on any system running IE 6.
Answered 11/15/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Be sure to check what version of MDAC is required, use the Merge Module for that as well, or deploy it first using command line and WIWW available from www.sywan.nl
Answered 11/15/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
After the feedback from the group, I do want to stay away from packaging this application. However I do want to do want to wrap this app into an msi.

MSIMaker, you had mentioned in your thread that the setup.exe and supporting files can be wrapped in a *.msi. Can you please elaborate how I can do this? Also, do you know if the *.msi that will wrap around the setup.exe will include all the supporting files. Basically I want to have one *.msi that can be used for deployment via GPO or SMS 2003?

thank you all for the feedback.

RK
Answered 11/17/2004 by: rajkumar
Yellow Belt

Please log in to comment
0
When I get to work on Monday I'll dig out my notes on MSDE and post them here for you.
Answered 11/19/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
From what I saw online it was not that hard, but it did require a "strong" SA Password. that could be set at the command line by modifying the SAPWD entry in the properies table with SAPWD=XXXXXXXXX.
Answered 11/19/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity