PDA

View Full Version : Change the System Search order



basher590
10-05-2010, 10:08 AM
Hey,

I'd like to know if it's possible to change the system search order?

I am using 2 registry searches. The first one is to find the instance name of a SQL Reporting Server. This search works fine. The second registry search is to find the value of an entry using the property from the previous search.

the search runs and finds the instance name for me and stores it in [RS_INSTANCE]

I then want to run a search for this registry key.
SOFTWARE\Microsoft\Microsoft SQL Server\[RS_INSTANCE]\setup
Value: SQLPath
Store it in the property [ZRS_INSTANCE_PATH]
Then use that value as a destination for some files.

When I check the log file after install though it always runs the [ZRS_INSTANCE_PATH] search first and obviously cannot find it.
The error log is below. Does anybody know if it's possible or how I can do that?

Action start 11:01:14: INSTALL.
MSI (c) (D8:C8) [11:01:14:344]: UI Sequence table 'InstallUISequence' is present and populated.
MSI (c) (D8:C8) [11:01:14:344]: Running UISequence
MSI (c) (D8:C8) [11:01:14:344]: PROPERTY CHANGE: Adding EXECUTEACTION property. Its value is 'INSTALL'.
MSI (c) (D8:C8) [11:01:14:345]: Doing action: AppSearch
Action 11:01:14: AppSearch. Searching for installed applications
Action start 11:01:14: AppSearch.
AppSearch: Property: ZRS_INSTANCE_PATH, Signature: NewSignature12
MSI (c) (D8:C8) [11:01:14:345]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (D8:C8) [11:01:14:345]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\\Setup 3: 2
AppSearch: Property: RS_INSTANCE, Signature: NewSignature11
MSI (c) (D8:C8) [11:01:14:345]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (D8:C8) [11:01:14:346]: PROPERTY CHANGE: Adding RS_INSTANCE property. Its value is 'MSRS10.MSSQLSERVER'.
AppSearch: Property: SSRS_INSTALLED, Signature: NewSignature1
MSI (c) (D8:C8) [11:01:14:346]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (D8:C8) [11:01:14:346]: PROPERTY CHANGE: Adding SSRS_INSTALLED property. Its value is '#6'.
AppSearch: Property: DOTNETVERSION35SP1, Signature: DotNet35SP1
MSI (c) (D8:C8) [11:01:14:346]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (D8:C8) [11:01:14:346]: PROPERTY CHANGE: Adding DOTNETVERSION35SP1 property. Its value is '#1'.
Action ended 11:01:14: AppSearch. Return value 1.
MSI (c) (D8:C8) [11:01:14:346]: Doing action: LaunchConditions
Action 11:01:14: LaunchConditions. Evaluating launch conditions
Action start 11:01:14: LaunchConditions.
Action ended 11:01:14: LaunchConditions. Return value 1.

basher590
10-05-2010, 10:18 AM
Hmm it seems not after doing some more digging.

http://blogs.msdn.com/b/windows_installer_team/archive/2005/08/27/454302.aspx


Chris

badzoy07
10-20-2010, 04:47 AM
I'm also looking for the same registry entry for SQL Report Server using the System Search but I can't even successfully get the value for RSINSTANCENAME( HKEY_LOCAL_MACHINE32\Software\Microsoft\Microsoft SQL Server\Instance Names\RS). So I cant proceed with finding the value for RSPATH(HKEY_LOCAL_MACHINE32\SOFTWARE\Microsoft\Microsoft SQL Server\[RSINSTANCENAME]\Setup).

Though I have found some error description pertaining to the logfile number 1402 that says... (Could not open key[2]. {{system error [3].}} Verify that you have sufficient access to that key, or contact your support personnnel)

Are there any workaround for this one? I appreciate any help.

Tim Mayert
10-20-2011, 08:18 AM
Hey Chris, did you ever get an answer to the System Search order?

I normally just create the entries in the order that I want them to run in, but then if you later create new entries that you actually want to have triggered first then it would be great if there was a way to make sure they were triggered first instead of having to rebuild the entire table from scratch and putting them back into the order that you need.

Thanks,

Cary R
10-20-2011, 11:38 AM
I posted a bit on this sort of thing a while back on the InstallTalk blog. Check out the section on "Making Order from Chaos":

http://blogs.flexerasoftware.com/installtalk/2011/02/i-didnt-know-installshield-could-do-that.html