Hi,
I have a windows forms VB.NET app which I've been working on for a while.
I'm deploying updates via a standard windows installer package created in
Visual Studio. This has been going fine and I'm up to about the 20th
version that I've rolled out while I'm still developing parts.
Last week, I put some updates in place, created the installer, and used that
to install onto about 10 machines as an admin. 7 of these were fine. Two
of them popped up 'looking for windows installer' type messages on the
user's first run, but then the majority of the app (i.e. stuff where it's
just reading data from an SQL 2K server) worked but popped up a nonsensical
error message when it got to a part of the code requiring data writing. The
last of the machines popped up a 'unabled to find windows installer' message
when the user tried to run it, and then failed completely.
I rebuilt the installer package and used that to install onto another
machine - everything worked fine.
Went back to the three dodgy machines and ran the mdac component checker
against them. That reported lots of files missing - even though those files
were installed in the correct place. Rolled the mdac back by using dasetup
/u, reinstalled mdac 2.7 SP1. Reran the app (as the user). Fine.
Later, installed another windows forms app onto one of these machines using
another installer. That worked fine, but when the user went back to the
original app, it failed at the data writing stage again with the same
meaningless error. Rolled the mdac back and reinstalled again, but still
get the same error.
Anyone else had this kind of fun?
--
For real reply address, lose the cash
www.realuk.co.uk
