Hi there,
We’ve run into a really odd situation with web updates on a particular PC (Win XP SP2).
Our other clients appear to be updating fine and we certainly can update using the /update switch.
Given that the majority of people are fine yet this one PC is not, is there a way that we can actually debug the process to find out where it is failing?
I’m assuming that it could be something to do with a firewall or anti-virus package blocking it but I’d like to be able to know for sure.
We know that we can browse to the location of the update file.
Let me know if you need any more info from me to help with this.
Thanks
Updater not working
-
Alex_Ronquillo
- Site Admin
- Posts: 364
- Joined: Mon Jul 30, 2007 11:51 am
- Location: USA
- Contact:
You can ask your client to log the installation. Ask him/her tp run the installer in the following way:
mysetup.exe /update /l=<logfile>
where mysetup.exe is your installer file, and logfile.log is the file where the log will be written to.
mysetup.exe /update /l=<logfile>
where mysetup.exe is your installer file, and logfile.log is the file where the log will be written to.
Alejandro Ronquillo
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Thanks for getting back to me.
I had the client run the installer the way you suggested. The output from the client (below) was the same as what I had got when I also ran the installer on my test box. The output was the same when there was an update for my test box and when there wasn't. Am I missing something here?
Thanks
I had the client run the installer the way you suggested. The output from the client (below) was the same as what I had got when I also ran the installer on my test box. The output was the same when there was an update for my test box and when there wasn't. Am I missing something here?
Thanks
Code: Select all
<InstallAware>
<SetupSplash>
<StubSize>
</StubSize>
<StubData>
</StubData>
<GlobalLists>
</GlobalLists>
<SupportDir>
</SupportDir>
<ExtractArchive>
</ExtractArchive>
<ExtractResource>
</ExtractResource>
<ResourcePath>
</ResourcePath>
<Dialogs>
</Dialogs>
</SetupSplash>
<RunScript>
<Variables>
</Variables>
<CompileScript>
</CompileScript>
<BootStrap>
</BootStrap>
<myah>
</myah>
<ExitScript>
</ExitScript>
</RunScript>
<Free>
</Free>
<CachedSupportDir>
</CachedSupportDir>
</InstallAware>
Hi there,
Just in case you missed this post I am doing it again.
I had the client run the installer the way you suggested. The output from the client (below) was the same as what I had got when I also ran the installer on my test box. The output was the same when there was an update for my test box and when there wasn't. Am I missing something here?
Thanks
Just in case you missed this post I am doing it again.
I had the client run the installer the way you suggested. The output from the client (below) was the same as what I had got when I also ran the installer on my test box. The output was the same when there was an update for my test box and when there wasn't. Am I missing something here?
Thanks
Code: Select all
<InstallAware>
<SetupSplash>
<StubSize>
</StubSize>
<StubData>
</StubData>
<GlobalLists>
</GlobalLists>
<SupportDir>
</SupportDir>
<ExtractArchive>
</ExtractArchive>
<ExtractResource>
</ExtractResource>
<ResourcePath>
</ResourcePath>
<Dialogs>
</Dialogs>
</SetupSplash>
<RunScript>
<Variables>
</Variables>
<CompileScript>
</CompileScript>
<BootStrap>
</BootStrap>
<myah>
</myah>
<ExitScript>
</ExitScript>
</RunScript>
<Free>
</Free>
<CachedSupportDir>
</CachedSupportDir>
</InstallAware> 
