PDA

View Full Version : Wupdate failures


NewsArchive
03-11-2005, 09:49 AM
[Wednesday, March 09, 2005 8:30 PM]

Freidrich,

Could you please explain what causes the following error...

WebUpDate

[!] The SetUpBuiilder WebUpDate client could not locate an
associated application to update.
Please make sure the software is installed properly.


One of my customers is reporting this from an NT4 installation. His XP
installs are working just fine though. This is for our webupdate, not
updating SB5.
--
Simon Craythorn
InterVations, Inc

NewsArchive
03-11-2005, 09:49 AM
[Thursday, March 10, 2005 9:29 AM]

I have the same problem on Win98.

Sim

NewsArchive
03-16-2005, 10:35 AM
[Tuesday, March 15, 2005 10:52 AM]

Simon,

Unfortunately, we cannot reproduce this problem :-( We have tested this on
a "server farm" (on 35 different Win98 and 31 different NT4 test machines).

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

NewsArchive
03-16-2005, 10:36 AM
[Tuesday, March 15, 2005 4:24 PM]

friedrich linder wrote:

> Simon,
>
> Unfortunately, we cannot reproduce this problem :-( We have tested this on
> a "server farm" (on 35 different Win98 and 31 different NT4 test machines).

No, I can't reproduce it either. Which is why I'm asking for what could
possibly cause that message so I can get my customer (who's also a
technical beta tester of ours) to look for the possible causes on his
system.

Note, the wupdate we are talking about is not for updating SB5, it's my
products wupdate which has been modified from your script. It is
working just fine on about 7 other beta testers systems, and all my test
OS's here.

If you can tell me what events could trigger that message, registry
entries, ini file, etc I can ask my customer what he has set for these.
--
Simon Craythorn
InterVations, Inc

NewsArchive
03-16-2005, 10:36 AM
[Tuesday, March 15, 2005 5:20 PM]

Simon,

Yes, I understand.

The wupdate.exe client is pure SetupScript code (see wupdate.sb5 script).
All information is stored in the Windows Registry.

1. wupdate.exe is started and gets its full path name (line 30)
2. The client uses the full path name to read the AppKey info from the
Registry (line 31)
3. This AppKey is used to read additional information.

The above method makes it possible to support an unlimited number of
WebUpdate applications on one machine.

I think 2.) failed on his machine.

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

NewsArchive
04-05-2005, 04:36 AM
[Wednesday, March 30, 2005 4:08 PM]

friedrich linder wrote:

> Simon,
>
> Yes, I understand.
>
> The wupdate.exe client is pure SetupScript code (see wupdate.sb5 script).
> All information is stored in the Windows Registry.
>
> 1. wupdate.exe is started and gets its full path name (line 30)
> 2. The client uses the full path name to read the AppKey info from the
> Registry (line 31)
> 3. This AppKey is used to read additional information.
>
> The above method makes it possible to support an unlimited number of
> WebUpdate applications on one machine.
>
> I think 2.) failed on his machine.

Correct. For some reason it stored

d:\program files\smartmail\\WUPDATE.EXE

in the registry. Any idea how it could have done that?

Once fixed his autoupdate started working.
--
Simon Craythorn
InterVations, Inc