Well, your custom action is deferred, no-impersonate, which means that it will be run under Local System credentials. Local System, albeit very powerful, has some limitations, like no access to network, etc. You can try to set Impersonate="yes".
Alex -----Original Message----- From: Tom Kazimiers [mailto:2voo...@gmx.de] Sent: Thursday, May 14, 2009 1:07 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX/MSI and CeAppMgr.exe (WinCe Application Manager) Hi there, as part of my WiX 3 setup the CeAppMgr.exe is looked up and executed. This application is used to install software on windows CE devices (like Windows Mobile 5/6, etc.). To do so one has to call CeAppMgr.exe with an ini file and the user should get the information that software is beeing installed on his or her mobile device. If I try this on the command line everything works fine. CeAppMgr.exe starts and begins to install the prvided ini (and thus the CAB-) file. The same done in WiX/MSI leads to a message box, coming from CeAppMgr.exe, that the sofware (the ini/cab) will be installed as soon as my mobile device gets connected again. The strange thing is: In both versions (command line and MSI) the mobile device is connected all the time. So, have you previously encountered this problem or have an idea what is going on? I want that CeAppMgr.exe behaves, when called from a MSI, execatly like when it is called from the command line. In WiX the relevant parts are (ignore the custom action conditions): <!--CeAppMgr.Exe Lookup--> <Property Id='SEARCH_CEAPPMGR'> <RegistrySearch Id="CeAppMgrSearch32" Root="HKLM" Type="raw" Key="Software\Microsoft\Windows\CurrentVersion\App Paths\CEAPPMGR.EXE" Win64="no"/> </Property> <!-- define the LaunchCeAppMgr_Install-Custom action --> <CustomAction Id='LaunchCeAppMgr_Install' Property='SEARCH_CEAPPMGR' ExeCommand='"[CESetupFolder]PDAAufmaß.ini"' Return='ignore' Impersonate='no' Execute='deferred' /> <!-- Schedule the custom actions--> <InstallExecuteSequence> <!-- launch CeAppMgr.exe install only when we make an installation but not when we remove the product --> <Custom Action='LaunchCeAppMgr_Install' Sequence='4400'><![CDATA[&PDAFeature=3 Or &PDAFeature=4]]></Custom> <!-- launch CeAppMgr.exe without ini parameter only when we remove the product --> <Custom Action='LaunchCeAppMgr_Deinstall' Sequence='4401'><![CDATA[&PDAFeature=2]]></Custom> </InstallExecuteSequence> Is there anything wrong? Regards, thanks in advance, Tom ---------------------------------------------------------------------------- -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
