Serwer terminali Winflector - alternatywa dla aplikacji Zdalny Pulpit, Citrix XenApp

Forum > Product technical support > Small apps errors

Autor: Roberto
Data: 2013-03-01 20:03:14

Hi,

I've got 2 tiny no-installation apps showing errrors.

1. Process Explorer: a common Task Manager replacement which fails to open, logging this error:

"[APP v3520a|W32] 2013.03.01 12:33:38: Admin: 12a4 :Error 81: Cannot create process. Loc [CreateProcessW] Info [lpAppName=[C:\Users\ADMIN.ADM\AppData\Local\Temp\procexp64.exe] lpCommandLine=["d:\it\procexp.exe"],2,0] SysErr [5] Mod [d:\it\procexp.exe]"

2. WinAudit: a software and hardware auditor which closes abruptly when begins scanning, logging this error:

"[APPv3520a|W32] 2013.03.01 12:34:35: Admin: 1318 :Error64: Function not supported (yet). Loc [EAppGetPrinterW] Info [3] SysErr [0] Mod [d:\it\winaudit.exe]"

You can download apps from:

http://download.sysinternals.com/files/ProcessExplorer.zip

http://winaudit.zymichost.com/winaudit.zip

Thanks,

Bar.
Autor: Bob
Data: 2013-03-05 02:01:34

Hi Roberto--

I downloaded winaudit just to see if I could recreate your issues.  I was able to successfully run WinAudit using WinFlector if I uncheck the "Map Printers" option.  This seems to be an issue with Winaudit and I am guessing it has to do with Winaudit performing an "audit" on the printers.  I also tested ProcessExplorer and it also worked without errors.

 

The Winflector server is running on a Windows 7 desktop and my client is also a Windows 7 desktop.

 

 
Autor: Roberto
Data: 2013-03-05 15:44:03

Hi,

WinAudit run successfully after your "Map Printers" tip.  Great!

And thanks to your Windows 7 client-server comment I was able to pinpoint ProcessExplorer issue.

All of my servers are 64-bit architecture, so I investigated procexp.exe compatibility, and found (amazingly) that main exe contains both 32- and 64-bit exe.

If CPU architecture is 64-bit, procexp64.exe version is spawned into user's temp directory and deleted when app finishes.

I think Winflector is always expecting running process to be the same as published app.

When I published procexp64.exe directly it worked flawlessly.

Would be very nice if Winflector could catch all child spawned processes and execute accordingly.

Thanks,

Bar.
Autor: Jacek (staff)
Data: 2013-03-06 13:10:06

1. Just to confirm GetPrinter(level 3) is not supported yet. Will add it in the nearest future.

2. Winflector always checks the type (32/64bit) of the secondary process right before starting it. It is possible to start 32-bit published process that in turn starts 64-bit process and vice-versa. Possibly procexp64.exe is started with some method not hooked by Winflector. Will have a look at this.

Regards,

Jacek
1


Zaloguj się aby móc pisać na forum.