[wpkg-users] Problems with the WOW64 mess

heiko.helmle at horiba.com heiko.helmle at horiba.com
Mon Jun 7 12:14:07 CEST 2010


Hello Tomasz, List,

> > Are you sure? Shouldn't the "Connecting" stage fail first?
> 
> Can you try:
> 
> net use /delete *
> 
> prior to any tests (to make sure you're not trying to be connected twice 

> anywhere)?
> 

Tried,  - net use list is empty. I switched to a Win7 VM (32bit) for 
testing and the error gets more confusing:
Details:

Action: Offline mode - connecting to wpkg.head.de
Result: [OK]
Message: 

Action: Executing as wpkg
Result: [OK]
Message: 

Action: Connecting to \\wpkg.head.de\wpkg\wpkg.js as HEAD\wpkg
Result: [OK]
Message: 

Action: Trying to read \\wpkg.head.de\wpkg\wpkg.js
Result: [FAILED]
Message: An unknown error occurred while accessing 
\\wpkg.head.de\wpkg\wpkg.js.

Well process monitor actually logs this:
11:55:12,7514484        wpkginst.exe    3696    CreateFile 
\\wpkg.head.de\wpkg\wpkg.js     LOGON FAILURE   Desired Access: Generic 
Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory 
File, Attributes: N, ShareMode: None, AllocationSize: n/a WIN7-VDEV\root 
Verbindliche Beschriftung\Hohe Verbindlichkeitsstufe

Interesting from my point of view is, that this failure gets logged on 
behalf of user "root" (the user running wpkginst.exe) instead of user 
"wpkg". But this may be the nature of ProcMon - because user wpkg doesn't 
show up in the log at all.


BTW: 
While this MAY be due to bad credentials, it actually isn't. If I put in 
bad credentials, the process fails on the connect stage (which is 
correct):
Action: Offline mode - connecting to wpkg.head.de
Result: [OK]
Message: 

Action: Executing as wpkg
Result: [OK]
Message: 

Action: Connecting to \\wpkg.head.de\wpkg\wpkg.js as HEAD\wpkg2
Result: [FAILED]
Message: WNetAddConnection2-> Zugriff verweigert

Action: Trying to read \\wpkg.head.de\wpkg\wpkg.js
Result: [FAILED]
Message: Access to \\wpkg.head.de\wpkg\wpkg.js was denied.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20100607/44526a2c/attachment-0002.html>


More information about the wpkg-users mailing list