MSDE Installation Failures

We have a custom client/server application that runs against MSDE. This
application is distributed to the field through a Setup CD. We used the
Installshield to create the setup program. Most of the times when the user
tries to install the application it fails after MSDE install saying that
"Your SQL Server is either corrupt or has been tampered with.". We try to
install a named instance. I haven't been able to find a solution to this
persistent and annoying problem. Most of my users use xp sp2 os.
Sometimes i have noticed that there is already a default instance of MSDE on
their laptops that came with some other application or the laptop itself. If
I remove that installation and then re-run our installation process it goes
smoothly.
Any help is appreciated.
Thanks
Maan
hi Maan,
Maan Thakur wrote:
> We have a custom client/server application that runs against MSDE.
> This application is distributed to the field through a Setup CD. We
> used the Installshield to create the setup program. Most of the times
> when the user tries to install the application it fails after MSDE
> install saying that "Your SQL Server is either corrupt or has been
> tampered with.". We try to install a named instance. I haven't been
> able to find a solution to this persistent and annoying problem. Most
> of my users use xp sp2 os.
> Sometimes i have noticed that there is already a default instance of
> MSDE on their laptops that came with some other application or the
> laptop itself. If I remove that installation and then re-run our
> installation process it goes smoothly.
> Any help is appreciated.
> Thanks
> Maan
you usually get this kind of exception when machine name has been changed,
like reported in
http://www.karaszi.com/sqlserver/inf...erver_name.asp
do you perform some "strange" operation at MSDE install time?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Nothing "Strange". We actually use the installation package provided by
microsoft and ship it with our CD and it is called from inside of the
installation program.
"Andrea Montanari" wrote:

> hi Maan,
> Maan Thakur wrote:
> you usually get this kind of exception when machine name has been changed,
> like reported in
> http://www.karaszi.com/sqlserver/inf...erver_name.asp
> do you perform some "strange" operation at MSDE install time?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>