Quantcast
Viewing all articles
Browse latest Browse all 7696

Feature Changes: Media Version Required

Hi,

I recently added new SQL 2008 R2 instances to a couple of production systems.  To do so, I ended up using the original slipstream media that was used to do the first SQL install.  (I still had the media on a file share.)  The PowerShell script that handled the install was much the same as the original install, but specified a different instance name.  Then I ran the patches to bring the new instance up to the version of the other instances. 

I could not use a more recent slipstream (at the same level of the other existing instances) to add the new instance.  I could not even run a discovery report with the new media.  I just noticed the PID value in the DefaultSetup.ini file was not the same in the media of the two slipstreams.  The error:

An error occurred during the SQL Server 2008 R2 Setup operation.
Error result: -2067529698
Result facility code: 1220
Result error code: 30

Anyway, with this in mind, how should I be handling adding or removing features on an existing system via script?  Do I need to retain the original media used to do the first install?  Should it work with more recent slipstream media?  Is is safe to include common features even if adding a new instance?  Perhaps I should specify the PID in script to insure it is the same as the original install?  If I leave the PID out, will it default to the one already used?   

Thanks.


Randy in Marin


Viewing all articles
Browse latest Browse all 7696

Trending Articles