Menu
▾
▴
wpkg-users — please use http://lists.wpkg.org
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(20) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(16) |
Feb
(26) |
Mar
(4) |
Apr
|
May
(33) |
Jun
(141) |
Jul
(49) |
Aug
(18) |
Sep
(23) |
Oct
(13) |
Nov
(73) |
Dec
(62) |
| 2006 |
Jan
(38) |
Feb
(74) |
Mar
(77) |
Apr
(87) |
May
(64) |
Jun
(93) |
Jul
(48) |
Aug
(34) |
Sep
(53) |
Oct
(67) |
Nov
(108) |
Dec
(66) |
| 2007 |
Jan
(142) |
Feb
(91) |
Mar
(122) |
Apr
(108) |
May
(94) |
Jun
(144) |
Jul
(51) |
Aug
(68) |
Sep
(55) |
Oct
(116) |
Nov
(271) |
Dec
(190) |
| 2008 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Tomasz C. <ma...@wp...> - 2008-01-08 16:14:19
|
Christian Böse schrieb: >>> Oh it installs when I set the "Show GUI". But when this is disabled it >>> produce these mistakes.... >> So, DirectX installer bails out when it can't access the real display. >> >> Similar will happen when trying to change resolution with some >> resolution-changing tools. >> >> >> Are you 100% sure that it worked with a previous version of WPKG Client? >> And that it's exactly the same DirectX installer with exactly the same >> installation flags? > > > I tested it again and sorry the previous version also produce this mistake. > It only solves the problem to enable the gui. Here installation instructions / silent flags are a bit different from the ones used by you - you might try those: http://wpkg.org/DirectX It works for me. -- Tomasz Chmielewski |
|
From: Tomasz C. <ma...@wp...> - 2008-01-08 15:43:28
|
Christian Böse schrieb: >>> But when WPKG Service wants to install it, it doesn´t work :( >> Hmm. Apart from being started as a non-Administrator, could be confused >> because WPKG Client starts everything on a "fake" display (so that users >> can't interact with the installers). >> >> Try this: >> >> 1) set "Show GUI" in WPKG Client >> 2) set "notepad" as a pre-command in WPKG Client >> 3) reboot, log in, exit notepad, and watch what happens >> >> Also, you can put "cmd.exe" as a pre-command, and start "cscript wpkg.js >> /synchronize /debug" manually from there. > > > > Oh it installs when I set the "Show GUI". But when this is disabled it > produce these mistakes.... So, DirectX installer bails out when it can't access the real display. Similar will happen when trying to change resolution with some resolution-changing tools. Are you 100% sure that it worked with a previous version of WPKG Client? And that it's exactly the same DirectX installer with exactly the same installation flags? >>> In the DirectX.log I find these lines: >> DirectX log doesn't tell me anything, sorry. Try asking Microsoft, they >> should know more ;) > > I also don´t tell me anything :) > >>> This also happens when changing WPKG Service to start as Administrator. >> Did you change it in Control Panel, or by changing settings in WPKG >> Client? If in Control Panel, it's wrong. > > I changed it with using wpkginst.exe. Or is it also wrong? This is fine. -- Tomasz Chmielewski http://wpkg.org |
|
From: Tomasz C. <ma...@wp...> - 2008-01-08 13:42:00
|
Christian Böse schrieb: > Hi, > > sorry my mistake. > I changed nothing on the WPKG service. It starts as SYSTEM but I don´t have > change there anything. > > When starting it directly it works fine and installs DirectX :) Does it display any GUI? Did you use silent flags etc.? > But when WPKG Service wants to install it, it doesn´t work :( Hmm. Apart from being started as a non-Administrator, could be confused because WPKG Client starts everything on a "fake" display (so that users can't interact with the installers). Try this: 1) set "Show GUI" in WPKG Client 2) set "notepad" as a pre-command in WPKG Client 3) reboot, log in, exit notepad, and watch what happens Also, you can put "cmd.exe" as a pre-command, and start "cscript wpkg.js /synchronize /debug" manually from there. > In the DirectX.log I find these lines: DirectX log doesn't tell me anything, sorry. Try asking Microsoft, they should know more ;) > This also happens when changing WPKG Service to start as Administrator. Did you change it in Control Panel, or by changing settings in WPKG Client? If in Control Panel, it's wrong. -- Tomasz Chmielewski http://wpkg.org |
|
From: Tomasz C. <ma...@wp...> - 2007-12-14 19:45:32
|
wpkg-users mailing list archive is being moved from sourceforge.net to lists.wpkg.org. Every subscriber will be unsubscribed from wpkg-users on sourceforge.net and then will be subscribed to that list on lists.wpkg.org. You will receive two emails: - one confirming unsubscription from wpkg-announce on sourceforge.net - one confirming subscription to wpkg-announce on lists.wpkg.org The interface and search on lists.wpkg.org is faster and should not return dead links, eat mail or unsubscribe people without reason. -- Tomasz Chmielewski http://wpkg.org |
|
From: <bug...@bu...> - 2007-12-14 15:55:23
|
http://bugzilla.wpkg.org/show_bug.cgi?id=92 --- Comment #6 from Falko Trojahn <ftr...@sm...> 2007-12-14 16:55:10 --- Created an attachment (id=83) --> (http://bugzilla.wpkg.org/attachment.cgi?id=83) patched wpkg.js and the sorted debug messages as text -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-14 15:54:29
|
http://bugzilla.wpkg.org/show_bug.cgi?id=92 --- Comment #5 from Falko Trojahn <ftr...@sm...> 2007-12-14 16:54:06 --- Created an attachment (id=82) --> (http://bugzilla.wpkg.org/attachment.cgi?id=82) Patch for more loglevels Ok, found some time to create a patch for more loglevels. Now we have: 8 : log audit success 16: log system details (found this unused, am I wrong?) 32: log package details and the corresponding functions: dinfo() sinfo() pinfo() The next attachment has the patched wpkg.js and the files alldebugmessages.txt allsystemmessages.txt allpackagemessages.txt grepped together. Please go through these files and tell me, if you want something sorted into another one of (dinfo|sinfo|pinfo) level. Some small spelling correction are in there, too. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-14 07:48:16
|
http://bugzilla.wpkg.org/show_bug.cgi?id=92 Leon Hedding <leo...@ic...> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leo...@ic... --- Comment #4 from Leon Hedding <leo...@ic...> 2007-12-14 08:48:03 --- I also require log rotation. There is a patch in http://bugzilla.wpkg.org/show_bug.cgi?id=79 for a slightly older version of the new release. Just search through the attachments for one added by Leon Hedding. It should be pretty simple to add it to your wpkg.js file. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: Tomasz C. <ma...@wp...> - 2007-12-14 07:14:54
|
Nicolas Lepot schrieb: >>> In my case: no reboot. >>> >>> If rebootCmd="standard" in wpkg.js : >>> The GUI WPKG disappears and Windows XP continue booting and displays the >>> login. >>> And there, nothing happens (no reboot). >>> >>> if rebootCmd="special" in wpkg.js : >>> The startup is blocked indefinitely on the GUI of WPKG-Client and >>> nothing happens (no reboot). >> What do you mean by blocked? You can't login? > > > > Yes, Exactly. Unable to login on Windows because the boot stop at WPKG moment. At startup, I see indefinitely the window of WPKG-Client. I waited 1 hour, but nothing happens. I still see the window of WPKG-Client. This blocking (called "logon delay") will appear only as long as: 1. wpkg.js runs commands, *AND* 2. logon delay still didn't pass This means that if you have a broken installer that got stuck and hangs for user input, and you set logon delay to 90 minutes, the logon delay will block user for 90 minutes. On the other hand, if installation is quick and takes only 1 minute, it will block logon only for 1 minute. What's your logon delay in WPKG Client? I guess it's bigger than 1 hour? And it hangs probably on psshutdown "accept window" you're talking about earlier. To debug it, set "show GUI" in WPKG Client, decrease logon delay, and use /debug instead of /quiet for wpkg.js - you should see where it got stuck. There are also some badly written applications which install fine from Administrator account, but show errors or unexpected behaviour when started from an account which has a name other than Administrator (other administrator, SYSTEM user etc.), and that could be your other problem (or, you accepted psshutdown license as Administrator, but not as SYSTEM etc.). (...) >>> How to verify that the customer WPKG tries to restart? >>> Is there a debug mode in Client-WPKG to analyze what happens? >> As always, read point 1 of http://wpkg.org/FAQ > > I have read the FAQ, but I always my problem. > > In the local administrator environment, if I run manually the command : "CSCRIPT \\MAJ01\WPKG\wpkg.js /synchronize /debug", psshutdown.exe run. But it is blocked by the special licence "EULA" of Sysinternals because it is the first usage. > > If I click "ok", the computer reboot correctly. > > The psshutdown tool want a flag in the register key : > HKCU\Software\Sysinternals\PsShutdown\EulaAccepted=1. > > > With the user SYSTEM, psshutdown run well or is it blocked by the Eula Licence ? I've no idea. I don't use that tool. When Microsoft acquired Sysinternals, they introduced this helpful "accept license", which seems to confuse everyone. With WPKG Client, you don't need to use this tool; WPKG Client can reboot perfectly fine. -- Tomasz Chmielewski http://wpkg.org |
|
From: <bug...@bu...> - 2007-12-13 21:13:38
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 --- Comment #44 from Tomasz Chmielewski <ma...@wp...> 2007-12-13 22:13:25 --- Jens, WPKG Client throws this error (Zugriff verweigert, or Access denied) if it has access denied to some network share (i.e., in Samba, one can easily reproduce it for a share with something like "hosts allow = 1.1.1.1"). As this is reported by the system, I guess you had some network or configuration problem? -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 21:02:17
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 --- Comment #43 from Tomasz Chmielewski <ma...@wp...> 2007-12-13 22:01:52 --- Is it always reproducible? Fails twice after installation, but then works fine? Could it be it was some network-related problem? -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 18:52:19
|
http://bugzilla.wpkg.org/show_bug.cgi?id=92 --- Comment #3 from Falko Trojahn <ftr...@sm...> 2007-12-13 19:51:54 --- More loglevels is a good idea, and appending the logfile, too. But I remember there has been lot of discussion about this with Rainer on the mailinglist, and he has no time atm. So, I think we should wait for his opinion. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 18:45:24
|
http://bugzilla.wpkg.org/show_bug.cgi?id=92 --- Comment #2 from Jens Geile <jen...@mz...> 2007-12-13 19:44:57 --- What i actually want is loglevel=27 without lines like this: 2007-12-13 19:20:59, DEBUG : Adding package with ID '7zip' to profile packages. 2007-12-13 19:20:59, DEBUG : Found package node '7zip (7zip) in package database 2007-12-13 19:20:59, DEBUG : Adding package with ID 'adobereader' to profile packages. 2007-12-13 19:20:59, DEBUG : Found package node 'Adobe Reader 8 (adobereader) in package database 2007-12-13 19:20:59, DEBUG : Adding package with ID 'cccp' to profile packages. ... ... ... 2007-12-13 19:20:59, DEBUG : Found installed package '7zip' (7zip). 2007-12-13 19:20:59, DEBUG : Package '7zip' (7zip) found in profile packages. 2007-12-13 19:20:59, DEBUG : Found installed package 'Adobe Reader 8' (adobereader). 2007-12-13 19:20:59, DEBUG : Package 'Adobe Reader 8' (adobereader) found in profile packages. 2007-12-13 19:20:59, DEBUG : Number of packages to remove: 0 2007-12-13 19:20:59, DEBUG : Going to install package '7zip' (7zip), Revision 451, (execute flag is '', notify flag is 'false'). 2007-12-13 19:20:59, DEBUG : Package '7zip' (7zip): Not yet processed during this session. 2007-12-13 19:20:59, DEBUG : Checking existence of package: 7zip 2007-12-13 19:20:59, DEBUG : Uninstall entry for 7-Zip 4.45 was found: test successful 2007-12-13 19:20:59, DEBUG : Package '7zip' (7zip): Already installed. Skipping. 2007-12-13 19:20:59, DEBUG : Going to install package 'Adobe Reader 8' (adobereader), Revision 80, (execute flag is '', notify flag is 'false'). 2007-12-13 19:20:59, DEBUG : Package 'Adobe Reader 8' (adobereader): Not yet processed during this session. 2007-12-13 19:20:59, DEBUG : Checking existence of package: Adobe Reader 8 2007-12-13 19:20:59, DEBUG : Uninstall entry for Adobe Reader 8 - Deutsch was found: test successful 2007-12-13 19:20:59, DEBUG : Package 'Adobe Reader 8' (adobereader): Already installed. Skipping. ... ... ... and so on. I don't want all the DEBUG messages related to packages. Just loglevel=19 + all the misc wpkg output stuff about starting, which files it loaded, and so on... > If I try this, only errors are written to logfile. Perhaps you could provide an example or a patch to make clear what you would like to have? I don't have the time to write a patch atm but I'll try once i have some free time at hand. > I use <param name='logfilePattern' value='wpkg-[HOSTNAME]-[PROFILE]-[mm].log' /> so it's nearly like logfile rotation, since the chance to overwrite the last logfile (must have same minute) is small. I have environments with 10 up to 350 machines ... that would be a maximum of 60*350=21000 log files instead of a maximum of 350 log files... Appending all logs for one client shouldnt be that hard and saves a lot of sanity. ;) -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 18:19:05
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 --- Comment #42 from Jens Geile <jen...@mz...> 2007-12-13 19:18:44 --- Created an attachment (id=81) --> (http://bugzilla.wpkg.org/attachment.cgi?id=81) eventlog here's the eventlog -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 18:18:04
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 Jens Geile <jen...@mz...> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #41 from Jens Geile <jen...@mz...> 2007-12-13 19:17:49 --- Ok, I think we need to reopen this right after closing it. :/ I just installed a WinXP SP2 test machine and found a new problem. 13.12.2007 19:02:01 WpkgService Fehler Keine 1 Nicht zutreffend TEST-RECHNER1 WNetAddConnection2-> Zugriff verweigert This happens right after the unattended install and shows up twice in the eventlog. When you reboot one more time it works as expected. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 18:17:26
|
http://bugzilla.wpkg.org/show_bug.cgi?id=92 Falko Trojahn <ftr...@sm...> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ftr...@sm... --- Comment #1 from Falko Trojahn <ftr...@sm...> 2007-12-13 19:17:06 --- "The logging I'm actually looking for is a log of all errors (1), all warnings (2), all audit failures (16)" So, this means you have to set logLevel=19. If I try this, only errors are written to logfile. Perhaps you could provide an example or a patch to make clear what you would like to have? Regarding "There's always only the last log file available": that's only a matter of configuration. I use <param name='logfilePattern' value='wpkg-[HOSTNAME]-[PROFILE]-[mm].log' /> so it's nearly like logfile rotation, since the chance to overwrite the last logfile (must have same minute) is small. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 16:33:02
|
http://bugzilla.wpkg.org/show_bug.cgi?id=92 Summary: Enhanced Logging Product: WPKG Version: other Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: wpkg.js AssignedTo: ma...@wp... ReportedBy: jen...@mz... QAContact: wpk...@li... I was just playing around with the loglevel setting in config.xml when I noticed that certain loglevels log too much stuff and some stuff should be moved into their own loglevel. The logging I'm actually looking for is a log of all errors (1), all warnings (2), all audit failures (16) and some basic info that wpkg was started, which files it read but not all the Checking, Finding and Skipping of packages (basically 8 minus all the package output). The whole package processing should be moved to its own loglevel. Another thing I noticed is that there is no log from earlier executions. There's always only the last log file available. :/ Could we get a <param name='log_append' value='true'> setting for config.xml? (With maybe two empty lines after each log block) Thanks in advance. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 16:03:33
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 Tomasz Chmielewski <ma...@wp...> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #40 from Tomasz Chmielewski <ma...@wp...> 2007-12-13 17:03:17 --- Didn't I tell it already? Jens, you have a broken computer ;) Nothing spectacular - it was a disallowed signal to Service Control Manager (SCM) - SERVICE_ACCEPT_SESSIONCHANGE, which can be only sent on Windows XP and above. I'm closing the bug, please reopen or comment if there are similar issues. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 15:57:56
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 --- Comment #39 from Jens Geile <jen...@mz...> 2007-12-13 16:55:58 --- Just came back only to find my Win2k test machine running with wpkg successfully executed and all packages installed. Read: It seems to work now. At least on my test machine. ;) Tomasz, any word on what the problem was in the end? -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: Tomasz C. <ma...@wp...> - 2007-12-13 14:08:14
|
Nicolas Lepot schrieb: > Hello, > > Thank you very much for your answer. > > If I understand, because I use Windows XP, the Client WPKG make the > reboot of the computer (and not the script wpkg.js). Client WPKG knows > he must do the reboot of the machine because the script wpkg.js ended > with a code 3010. > > > Normally, the Client-WPKG launches a reboot what moment ? > Directly after the run of wpkg.js ? > Just before the user logon? > After the user logon? It reboots right after wpkg.js quits with 3010. > Here is a sample package just to test the reboot option: > > <Package id = "test" > Name = "test" > Revision = "1" > Reboot = "true" > Priority = "0"> > <Check type = "file" status = "exists" path = "C: \ TOTO.TXT" /> > <Install cmd = '% comspec% / c SET> C: \ TOTO.TXT' /> > </ Package> What's "% comspec%"? Looks like an invalid variable to me (space after %). > In my case: no reboot. > > If rebootCmd="standard" in wpkg.js : > The GUI WPKG disappears and Windows XP continue booting and displays the > login. > And there, nothing happens (no reboot). > > if rebootCmd="special" in wpkg.js : > The startup is blocked indefinitely on the GUI of WPKG-Client and > nothing happens (no reboot). What do you mean by blocked? You can't login? > I added the "Psshutdown.exe" in the folder "\\Server\WPKG\tools > <file://\\Server\WPKG\tools>" and in \\client\c$\windows\system32 > <file://\\client\c$\windows\system32>. > > > Is it correct ? > > if it is correct, how to verify that the Client-WPKG receives much an > exit code 3010 of wpkg.js? > In the logs, except "service wpkg start and stop", I have only messages > of wpkg.js. > > How to verify that the customer WPKG tries to restart? > Is there a debug mode in Client-WPKG to analyze what happens? As always, read point 1 of http://wpkg.org/FAQ -- Tomasz Chmielewski http://wpkg.org |
|
From: <bug...@bu...> - 2007-12-13 13:29:04
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 Jens Geile <jen...@mz...> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jen...@mz... --- Comment #38 from Jens Geile <jen...@mz...> 2007-12-13 14:28:37 --- I'm currently installing a new Win2k test machine with unattended and wpkg-client 1.2-rc6. Will report back asap. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: Falko T. <nos...@sm...> - 2007-12-13 13:28:52
|
Jens Geile schrieb: > Hi, > >> Please try WPKG 1.0-rc4 from http://wpkg.org/Download and provide a log file with logLevel=0xFF. > Loglevels ... could someone rewrite the help in config.xml? I don't quite understand it or I'm just too stupid. I tried a few combinations of loglevels but it always resulted in wpkg not logging anything at all. The only setting i got to work was was loglevel=0xFF :/ You didn't use loglevel instead of logLevel, did you? Explanation from Rainer seems pretty clear to me. In config.xml: <param name='logLevel' value='7' /> or as parameter: wpkg.js /logLevel:7 normally is enough to see what errors,warning,info messages wpkg gives. Excerpt from config.xml or http://wpkg.org/WPKG_flags#Rarely_used_parameters ... /logLevel:[0-16] Level of detail for log file. Log level is defined as a bitmask. Just sum up the values of each log severity you would like to include within the log file and add this value to your config.xml or specify it at /logLevel:<num>. 0 disable logging. 1 log errors only 2 log warnings 4 log information 8 log audit success 16 log audit failure Examples: 31 log everything (1+2+4+8+16=32) 13 logs errors, information and audit success (1+4+8=13) 3 logs errors and warnings only (1+2=3) Default is 0 which will suppress all messages printed before log level is properly initialized by config.xml or by /logLevel:<#> parameter. Falko |
|
From: <bug...@bu...> - 2007-12-13 12:01:52
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 --- Comment #37 from Tomasz Chmielewski <ma...@wp...> 2007-12-13 13:01:44 --- > Test gives: > > Testing complete > > 4 - OK > 0 - failed > 4 - not tested > (why's that last line?) If you didn't fill some values (like -post script, offline mode etc.), it will not be tested. So, I guess it works. Let's keep this bug open to get some more confirmations. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: <bug...@bu...> - 2007-12-13 11:51:39
|
http://bugzilla.wpkg.org/show_bug.cgi?id=89 --- Comment #36 from Falko Trojahn <ftr...@sm...> 2007-12-13 12:51:23 --- Test gives: Testing complete 4 - OK 0 - failed 4 - not tested (why's that last line?) When rebooting, I get: Service is starting with "Unknown error" in eventlog. When manually starting wpkgsrv.exe /debug I get Ereignistyp: Fehler Ereignisquelle: WpkgService Ereigniskategorie: Keine Ereigniskennung: 1 Datum: 13.12.2007 Zeit: 10:47:37 Benutzer: Nicht zutreffend Computer: FT2KDEV Beschreibung: Script pre action execution: failure. Exit code: 2 Script pre action is: net use w: \\server\install /user:server\wpkg password So I've created a script \\server\install\netuse.cmd @echo off net use w: \\server\install /user:server\wpkg password echo ok which worked finally ... -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
|
From: Tomasz C. <ma...@wp...> - 2007-12-13 10:37:58
|
Jens Geile schrieb: > Hi, > >> So, you still had the <package id="CofA"... entry in wpkg.xml? That's the expected behaviour. >> wpkg.js checks if the application is in its "database" (wpkg.xml), and if it is, it assumes it is installed. > How about a /recheck parameter? Rainer? :p > I can already see the problems with administrators that remove software through the control panel of Windows and then wondering about why wpkg doesn't work as expected anymore. With /recheck you could make sure that noone uninstalls any wpkg-maintained packages or at least that it re-installs them if someone removed them. Did you check /force? It's exactly that. -- Tomasz Chmielewski http://wpkg.org |
|
From: <bug...@bu...> - 2007-12-13 10:01:52
|
http://bugzilla.wpkg.org/show_bug.cgi?id=3D89 --- Comment #35 from M=C3=A9d=C3=A9ric RIBREUX <med...@gm...> = 2007-12-13 10:08:25 --- Hello, rc6 seems to be good ! I completly reinstalled it and it works: all actions= are launched and the event log is correctly filled... I'll do another test with a complete reinstall of the computers... Thanks ! --=20 Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=3Demail ------- You are receiving this mail because: ------- You are the QA contact for the bug.= |
31 messages has been excluded from this view by a project administrator.
