[wpkg-users] wrapper settings path mismatch problem
Hi, I need some help to try and rectify a problem, of my making! I manually edited the settings.xml to change from server1 to server2 but missed the wrapper path and only changed the settings paths. Now I have the path for the wrapper \\server1\wpkg\wpkg.js and the settings/software as \\server2\wpkg\settings.xml so wpkg fails. Has anyone got a suggestion on how to change these? Where are the wpkgservice settings stored? Registry? Xml file? As I could try and change it via a DS group policy. BTW, thanks to everyone for the help on the downgrade version stuff, it worked great. Thanks Paul -- Paul McGrath, IT Manager, Leeds Institute of Molecular Medicine, St James's University Hospital, Beckett Street, Leeds, LS9 7TF, UK Ext.: Uni - 38630, NHS - (89)38630 Tel.: +44 113 34 38630 Email...: j.p.mcgr...@leeds.ac.uk Homepage: http://www.limm.leeds.ac.uk - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] wrapper settings path mismatch problem
Mandi! Falko Trojahn In chel di` si favelave... usually I do such upgrade things using a package, see attached. A little question: why use: cmd /c start /min msiexec on install and simply only 'msiexec' on upgrade? I'm curious... ;))) -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''http://www.sv.lnf.it/ Polo FVG - Via della Bontà , 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/chi_siamo/5xmille.php (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] wrapper settings path mismatch problem
Marco Gaiarin schrieb: Mandi! Falko Trojahn In chel di` si favelave... usually I do such upgrade things using a package, see attached. A little question: why use: cmd /c start /min msiexec on install and simply only 'msiexec' on upgrade? I'm curious... ;))) Hmm. I mean to remember a time where we had the transition from wpkg_start.bat-service to WPKG Client and there was another package for removing the old service. Perhaps this was a workaround for some timing issue ... don't know. Perhaps this can be removed. Falko - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
