About six months to a year ago I created an installer that contained a drop down list containing all the instances of sql server visible from the target machine. It worked just fine. On recent compilations I've noticed that it simply no longer works. I get a list of names of machines that contain sql server instances and that's all - no instance name and some machines simply aren't listed. For example on my test deployment machine there is one local instance of sql server express 2005 - the same instance that was there when this used to work - and the browse finds nothing. The only thing that could possible have changed is the version of Advanced Installer, does this mean that Caphyon have broken their own feature and not bothered to test properly? Or is there an acceptable explanation? If the former can I use my version 7.1.3 .aip file on an older version of Advanced Installer, I suspect not. Please help me, this issue is making me look incompetent.
Is the sql Browser service actually running on the machine on which you are testing this? I've had simililar problems before (not specifically with AI) where I have been expecting to see a list of sql instances only to find that it wasn't as I expected. Further investigations showed that I had inadvertently turned of the sql Browser service.
The instance on the test machine is definitely running. I can see it with Management Studio. It has all visibility options on. I repeat: Nothing has changed except the version of Advanced Installer. When I run it on a networked machine I see lots of names of computers that host a sql server instance, but none of the instance names.
Being able to see the instances in sql Management browser does not necesarrilty mean that the sql browser service is running (as I eventually found out the hard way!). Check the service first and then when you know for certain that it's running start to look at AI.
In truth having tried the AI approach to this, and others, I prefer to handle connection from within my own apps where I know I can verify all of the parameters I need to before encouraging the end user to make decisions that I might later come to regret. Sorry this isn't much direct help but I do understand your frustration.
I repeat AGAIN: The instance is definitely running!! I have also tried it on a network with lots of instances running. It's definitely running, it's definitely running - the problem is NOT with my sql server, the same thing happens with all instances.
I am not trying to manipulate or configure anything to do with any server instance in my install, I just want the user to choose an available instance so I can grab the name of that instance and place it in a configuration file. It now seems likely that I will have to re-implement this feature myself.
Please, if you have nothing to add, then don't reply.
You could try this from another computer on your network to see if the problem persists.
If it does, please send your .aip project files to support at advancedinstaller dot com so we can investigate the cause in more detail.