Dear All,
I'm really puzzled by this one...
I've written an installshield package that installs a VB program and MSDE. It works perfectly on my test machine (blank install Windows XP).
At the client's offices it fails on two machines but works on a third. On ALL machines it seems to install fine, and you can see MSSQL$ABC (where ABC is the instance name) running in services. However, on the two non-working machines the vb program can't talk to the database & I know there is something very funny because if I try and register the servers in enterprise manager on another machine, they do not appear.
On the third machine (and my test machine) it works fine and you can register the instance in enterprise manager.
All machines have an existing MSDE (v7) already installed as the default instance, and I am installing MSDE 2000.
Why on earth would it work sometimes and not others, especially when it is installed and running on all of them?
Thanks in advance
Phil.
I'm really puzzled by this one...
I've written an installshield package that installs a VB program and MSDE. It works perfectly on my test machine (blank install Windows XP).
At the client's offices it fails on two machines but works on a third. On ALL machines it seems to install fine, and you can see MSSQL$ABC (where ABC is the instance name) running in services. However, on the two non-working machines the vb program can't talk to the database & I know there is something very funny because if I try and register the servers in enterprise manager on another machine, they do not appear.
On the third machine (and my test machine) it works fine and you can register the instance in enterprise manager.
All machines have an existing MSDE (v7) already installed as the default instance, and I am installing MSDE 2000.
Why on earth would it work sometimes and not others, especially when it is installed and running on all of them?
Thanks in advance
Phil.