Error 27502

Here is my situation... have an installation package that first installs
MSDE, then installs a client applicaton. Have used this installer dozens of
times with no problem. Now I have received the following error after MSDE
installs, but during the install of the client program: "Error 27502. Could
not connect to SQL Server (local)\MYINSTANCE". Then the client installation
rolls back.
Related info: this computer previously had MSDE and the client running, but
they were uninstalled. Tried to do a complete removal/uninstall of all
components through registry, etc. It is not practical for me to change
anything in the installer package, and besides it works fine on new
installations. Has something changed due to a previous installation that
would cause this error?
Any help is most appreciated! --RS
hi Rob,
Rob S wrote:
> Here is my situation... have an installation package that first
> installs MSDE, then installs a client applicaton. Have used this
> installer dozens of times with no problem. Now I have received the
> following error after MSDE installs, but during the install of the
> client program: "Error 27502. Could not connect to SQL Server
> (local)\MYINSTANCE". Then the client installation rolls back.
> Related info: this computer previously had MSDE and the client
> running, but they were uninstalled. Tried to do a complete
> removal/uninstall of all components through registry, etc. It is not
> practical for me to change anything in the installer package, and
> besides it works fine on new installations. Has something changed
> due to a previous installation that would cause this error?
> Any help is most appreciated! --RS
if you get an exception like "setup failed to configure the server" or the
like, you can only "change" the instance name or properly clean up the file
system and the registry...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Could you please help me identify all of the locations in the system and
registry files that could be affecting the MSDE installation.
As mentioned, the exact same installation routine normally detects and
connects to the server, but in this case there must be something left over
from a previous installation that is affecting the ability to detect the
server. I suspect it has something to do with translating the "(local)"
reference to the default server installation. Where, or how, does windows
translate the (local) reference into the actual host name?
Thanks again, RS
"Andrea Montanari" wrote:

> hi Rob,
> Rob S wrote:
> if you get an exception like "setup failed to configure the server" or the
> like, you can only "change" the instance name or properly clean up the file
> system and the registry...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Rob,
Rob S wrote:
> Could you please help me identify all of the locations in the system
> and registry files that could be affecting the MSDE installation.
there're 2 kb article that can help...
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991
the first one requires the Msizap.exe, part of the Windows Installer SDK to
remove Windows Installer related entries, while the second skip this sort of
cleanup... file system and SQL Server related registry entries to clean are
listed...
personally I used the second one (and still have an entry in the add/remove
applet for an orphaned MSDE installation entry)...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Thanks for all of your help. I ran both cleanup tools. Still did not solve
problem. I would not give up! After many hours of trial and error I
determine the problem was with a corrupted MDAC component. Reinstall MDAC on
XP sp2? Yes there is a way to do that (very simple). Once I reinstalled
MDAC the client application connected and installed just fine. --RS
"Andrea Montanari" wrote:

> hi Rob,
> Rob S wrote:
> there're 2 kb article that can help...
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991
> the first one requires the Msizap.exe, part of the Windows Installer SDK to
> remove Windows Installer related entries, while the second skip this sort of
> cleanup... file system and SQL Server related registry entries to clean are
> listed...
> personally I used the second one (and still have an entry in the add/remove
> applet for an orphaned MSDE installation entry)...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>