Software Deployment

1) Remove the start and stop service functions from your MSI
2) On a clean build install sqlserver 2005, as usual I assume
3) Stop the sql service
4) Install your MSI
5) Try and start the sql service

If this doesnt work then its your package, if it does work its your package but I would assume that you need to stop the serivce first, before installing the database and then start afterwards.

P

Thanks but we did try it and errror occurs. We had tried these ways-
1. Installing App with the same credentials SQL is using.
2. Manually stop SLQ service and install.
3. Delete service control from MSI and install.

Now we are in a situation where we don't know where to look.

I'm curious to know...if all the app needs to do is to attach the database,why on earth does it need to stop and restart SQL Server? Surely it should just attach the d/b?!? In fact, isn't there a pre-built script for use with OSQL for this very purpose? Or a stored procedure? If not, try http://www.databasejournal.com/features/mssql/article.php/1548361/Automating-SQL-Server-Management-with-WMI-Part-2.htm

Is this a vendor MSI or a snapshotted MSI?

If its a vendor MSI, has it ever worked, if its a snapshotted MSI does the vendor setup.exe work?

Is this a vendor MSI or a snapshotted MSI?IIRC, DLOMaintenanceSvc service belongs to Symantec NetBackup (or Backup Exec, whatever it's called this week). DLO is 'Desktop/Laptop Option'?

Yes you are right VBScrab.
Answering to Paul's question, this is completely a new installer having setup.exe and internally calling MSI. For your information I am into packaging where we build installers.

Jeeoo!
Santro

While analysing, I have noticed the below log file details.

MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: LocalAppDataFolder , Object: C:\Documents and Settings\mtk\Local Settings\Application Data\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: DesktopFolder , Object: C:\Documents and Settings\All Users\Desktop\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: CommonFilesFolder , Object: C:\Program Files (x86)\Common Files\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: ISCommonFilesFolder , Object: C:\Program Files (x86)\Common Files\InstallShield\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: CommonAppDataFolder , Object: C:\Documents and Settings\All Users\Application Data\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: ProgramFilesFolder , Object: C:\Program Files (x86)\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: MicrosoftSqlServer , Object: C:\Program Files (x86)\Microsoft SQL Server\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: Sql80 , Object: C:\Program Files (x86)\Microsoft SQL Server\80\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: SqlTools , Object: C:\Program Files (x86)\Microsoft SQL Server\80\Tools\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: SqlCommonBinn , Object: C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: MSSQL , Object: C:\Program Files (x86)\Microsoft SQL Server\MSSQL$DLO\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: Binn , Object: C:\Program Files (x86)\Microsoft SQL Server\MSSQL$DLO\Binn\
MSI (c) (2C:A0) [09:44:54:937]: Dir (target): Key: SQLBINNDIR.FBF6AB5B_373C_4CD4_B277_E08D4D444E2C , Object: E:\MSSQL\MSSQL.1\MSSQL\Binn\

It seems the installer looks for 32bit dirs of MSSQL server.

Aye, borked, but I aint packaged on x64 so am unable to help you further other than to say break it down bit by bit.

1) Does MSSQL install standalone properly?
2) Can you manually add and create the SQL database
3) When you say this is a new MSI, was it a snapshot or new MSI from scratch with source file added to the installer manually?

It seems the installer looks for 32bit dirs of MSSQL server....as will, unless I'm very much mistaken, every 32-bit app you install on x64....

Thanks guys!

The issue has been resolved.
Problem Description: -
The installer tries to stop SQL Service before executing some Extended SPs and attaching the DB. In AMD 64 machines the security/group policies are applied in such a way that it won't allow logged on users to stop the service, only a service account will have the permission. Hence installer fails.

Solution Description
Attaching the DB and Extended SPs doesn't need SQL Service to be stopped (As suggested by VBScab). So, we modified that way it has implemented and removed the action to stop SQLService on installation(As suggested by Paul).

Jeeoo!
Santro