SQL 2008 deployment Errors

[Mike S]

I am trying to deploy SQL Server 2008 R2 with SP1 slip-streamed using SCCM2007 (Version: 4.00.6487.2000)to a Windows 7 32-bit box and am having absolutely no luck. I have tested the install for functionality and correctly created a package in SCCM. Everything looks correct. The problem is; when I run the advertisement it bombs out. I noticed that the cache size was too small, so I fixed that...still no luck. Thinking I would be slick, I created a completely new O/S install package to include SQL 2008. The new installation worked great...until it was trying to install SQL 2008. Again, SQL bombed. I know I am missing something, but I cannot for the life of me figure out what it is. Any insight to this irritating problem is greatly appreciated. If more info is needed, please ask and I will give what knowledge I have.

 

Thanks

[anyweb]

ok when trying to deploy the application, what errors are you getting, are you wrapping it in a vbs script or a straight msi install ?

[Mike S]

ok when trying to deploy the application, what errors are you getting, are you wrapping it in a vbs script or a straight msi install ?

 

The package is run using a command line entry to incorporate a customized install (setup.exe /ConfigurationFile=sql2008_x86.ini). Basically, I am running the install as it appears in the installation DVD. Snapshot attached.

 

When I run the installation manually, everything works perfectly.

 

The errors (4 errors) are as follows:

 

Error ID: 10006

The program for advertisement "MAD20060" failed ("MAD00077" - "MS SQL 2008 Workstation"). A failure exit code of -2068578304 was returned.

 

Error ID: 11135

The task sequence execution engine failed executing the action (SQL Server 2008) in the group (Install Software) with the error code 2226388992

 

Error ID: 11141

The task sequence execution engine failed execution of a task sequence.

 

Error ID: 11170

The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned.

 

Hope this info helps, if you need more, let me know.

 

Thanks for your assistance.

Mike

[Mike S]

I have resolved the problem. I had to manually edit the configuration file to point to the PCU folder (used in slip-streaming the SP). After much irritation, I noticed that I had forgotten to put a "." in front of the folder location. Funny how a "." is powerful enough to bring down an entire package. Lesson learned I guess.