Problems while repackaging SQL Server Express 05 SP2
Good day,
I need to repackage SQL Server Express 2005 SP2, but I'm having some serious problems.
First, according to my company's policy, I splitted this package in 3: MSXML, SQL Writer and Native Client (and another package for SQL Server) wrapping their MSI's, which are uncompressed by Microsoft's installer in a temporary directory.
MSXML, SQL Writer and Native Client were wrapped up without problems: using Microsoft SMS Installer to develop the script I could successfully install the MSI silently. Problem is with the main SQL Server package. I'm wrapping it up too (using SMS Installer, just like I did with the other packages).
On a Windows XP Professional SP2 machine, I install all the other packages first (.Net Framework 2.0, MSXML, SQL Writer and Native Client in this order) and then I install the SQL server package. After doing this and restarting the machine a message shows up before I login to the system:
Title: SQL Writer
Message: SQLDumper library failed initialization. Your installation is either corrupt or has been tampered with. Please, uninstall and then rerun setup to correct this problem.
This doesn't happen on a Windows 2000 Professional SP4 machine. If I uninstall only the SQL Server package this message doesn't show up anymore.
Does anyone have any idea of what may be the problem?
PS: I've already looked in the software KB but the solutions there didn't work on my case.
Regards,
Pedro.
I need to repackage SQL Server Express 2005 SP2, but I'm having some serious problems.
First, according to my company's policy, I splitted this package in 3: MSXML, SQL Writer and Native Client (and another package for SQL Server) wrapping their MSI's, which are uncompressed by Microsoft's installer in a temporary directory.
MSXML, SQL Writer and Native Client were wrapped up without problems: using Microsoft SMS Installer to develop the script I could successfully install the MSI silently. Problem is with the main SQL Server package. I'm wrapping it up too (using SMS Installer, just like I did with the other packages).
On a Windows XP Professional SP2 machine, I install all the other packages first (.Net Framework 2.0, MSXML, SQL Writer and Native Client in this order) and then I install the SQL server package. After doing this and restarting the machine a message shows up before I login to the system:
Title: SQL Writer
Message: SQLDumper library failed initialization. Your installation is either corrupt or has been tampered with. Please, uninstall and then rerun setup to correct this problem.
This doesn't happen on a Windows 2000 Professional SP4 machine. If I uninstall only the SQL Server package this message doesn't show up anymore.
Does anyone have any idea of what may be the problem?
PS: I've already looked in the software KB but the solutions there didn't work on my case.
Regards,
Pedro.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
IIRC, you need to stop, then disable the SQL VSS Writer service.
Posted by:
pogo
16 years ago
Hi VBScab,
It worked for me. Thank you very much.
What worked too was to install the program with this command line (using Microsoft's EXE):
sqlexpr32.exe -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPRESS SCCCHECKLEVEL=IncompatibleComponents:1 SQLAUTOSTART=1 ERRORREPORTING=2 /watsongenman=SQL???.mft ComponentType=3
Found it here: http://www.appdeploy.com/packages/detail_pf.asp?id=666
Thank you for your help. [:)]
It worked for me. Thank you very much.
What worked too was to install the program with this command line (using Microsoft's EXE):
Found it here: http://www.appdeploy.com/packages/detail_pf.asp?id=666
Thank you for your help. [:)]
Posted by:
pogo
16 years ago
Just another doubt,
Is there anyway to make ARPWrapper.exe (SQL Server's uninstaller) unattended? I need to make the removal of it completely silent.
Thanks for the help!
Is there anyway to make ARPWrapper.exe (SQL Server's uninstaller) unattended? I need to make the removal of it completely silent.
Thanks for the help!
Posted by:
anonymous_9363
16 years ago
That's not the uninstaller, the MSI which SQLEXP32.EXE extracts and executes is!
What you've not noticed is that the command-line arguments you used (apart from '-q') are the same as those passed to MSIExec which is all SQLEXP32 does eventually. Also, as a note for your future reference, properties used on a command line can only be public properties. They are easily recognised because they're all upper-case in the MSI's property table. Private properties are ignored. You also have some well-known public properties incorrectly specified. All of these :
reboot=ReallySuppress
addlocal=all
instancename=SQLEXPRESS
will be ignored because they're in lower-case and should be upper.
OK, moving on...here's how my current client's SSE install was done:
- captured the installation of SQLEXPS32 (possibly called simply Setup.EXE, depending on when and from where you obtained SSE) up to the point where it says that the Setup prerequisites have been installed and the green tick appears to the left of that line. The resulting MSI is installed as a prerequisite. This is required because some of the Custom Actions in the main SQL MSI look for files and registry entries which the stub puts down.
- installed, in this sequence:
. SetupPreRequisites.MSI
. SQLWriter.MSI with simplistic MST (client's properties added, etc)
. SQLCLI.MSI (ditto)
. SQLRun.MSI (ditto)
If your workstations don't already have it, you need to install XML 6 stuff from MSXML6.MSI, too.
What you've not noticed is that the command-line arguments you used (apart from '-q') are the same as those passed to MSIExec which is all SQLEXP32 does eventually. Also, as a note for your future reference, properties used on a command line can only be public properties. They are easily recognised because they're all upper-case in the MSI's property table. Private properties are ignored. You also have some well-known public properties incorrectly specified. All of these :
addlocal=all
instancename=
will be ignored because they're in lower-case and should be upper.
OK, moving on...here's how my current client's SSE install was done:
- captured the installation of SQLEXPS32 (possibly called simply Setup.EXE, depending on when and from where you obtained SSE) up to the point where it says that the Setup prerequisites have been installed and the green tick appears to the left of that line. The resulting MSI is installed as a prerequisite. This is required because some of the Custom Actions in the main SQL MSI look for files and registry entries which the stub puts down.
- installed, in this sequence:
. SetupPreRequisites.MSI
. SQLWriter.MSI with simplistic MST (client's properties added, etc)
. SQLCLI.MSI (ditto)
. SQLRun.
If your workstations don't already have it, you need to install XML 6 stuff from MSXML6.MSI, too.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.