Bad boy Warrior Posted June 30, 2010 Share Posted June 30, 2010 (edited) I have a strange issue here. I set a schedule for an exe to run as another account (not admin) but one which has admin rights. When executing this app manually it gives me the UAC prompt and runs successfully.When i set this up as a schedule, i enabled run whether user is logged on or not, gave the account details (which it accepted) and run with highest privileges. When this runs on a schedule the app returns an error within a log which was listed under the Application log. The logs for scheduled tasks do not have any errors listed. All informational logs state the schedule ran successfully.The application log is:Version=1EventType=CLR20r3EventTime=129223860151321666ReportType=2Consent=1ReportIdentifier=c67d079d-845d-11df-9256-005056802d4bResponse.type=4Sig[0].Name=Problem Signature 01Sig[0].Value=SomeApplication.exeSig[1].Name=Problem Signature 02Sig[1].Value=1.0.0.0Sig[2].Name=Problem Signature 03Sig[2].Value=4b87adebSig[3].Name=Problem Signature 04Sig[3].Value=SystemSig[4].Name=Problem Signature 05Sig[4].Value=2.0.0.0Sig[5].Name=Problem Signature 06Sig[5].Value=4a275e12Sig[6].Name=Problem Signature 07Sig[6].Value=33c6Sig[7].Name=Problem Signature 08Sig[7].Value=273Sig[8].Name=Problem Signature 09Sig[8].Value=System.FormatExceptionDynamicSig[1].Name=OS VersionDynamicSig[1].Value=6.1.7600.2.0.0.272.7DynamicSig[2].Name=Locale IDDynamicSig[2].Value=2057UI[2]=C:\Program Files (x86)\Some Company\Application\SomeApplication.exeLoadedModule[0]=C:\Program Files (x86)\Some Company\Application\SomeApplication.exeLoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dllLoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLLLoadedModule[3]=C:\Windows\system32\KERNEL32.dllLoadedModule[4]=C:\Windows\system32\KERNELBASE.dllLoadedModule[5]=C:\Windows\system32\ADVAPI32.dllLoadedModule[6]=C:\Windows\system32\msvcrt.dllLoadedModule[7]=C:\Windows\SYSTEM32\sechost.dllLoadedModule[8]=C:\Windows\system32\RPCRT4.dllLoadedModule[9]=C:\Windows\system32\SHLWAPI.dllLoadedModule[10]=C:\Windows\system32\GDI32.dllLoadedModule[11]=C:\Windows\system32\USER32.dllLoadedModule[12]=C:\Windows\system32\LPK.dllLoadedModule[13]=C:\Windows\system32\USP10.dllLoadedModule[14]=C:\Windows\system32\IMM32.DLLLoadedModule[15]=C:\Windows\system32\MSCTF.dllLoadedModule[16]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dllLoadedModule[17]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_88dce9872fb18caf\MSVCR80.dllLoadedModule[18]=C:\Windows\system32\shell32.dllLoadedModule[19]=C:\Windows\system32\ole32.dllLoadedModule[20]=C:\Windows\system32\profapi.dllLoadedModule[21]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\9a017aa8d51322f18a40f414fa35872d\mscorlib.ni.dllLoadedModule[22]=C:\Windows\system32\CRYPTBASE.dllLoadedModule[23]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dllLoadedModule[24]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\247913fa7ae6fcf04ea33d28d24ab611\System.ni.dllLoadedModule[25]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Data\46a0336046744a9f29986b208b8d38d4\System.Data.ni.dllLoadedModule[26]=C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dllLoadedModule[27]=C:\Windows\system32\WS2_32.dllLoadedModule[28]=C:\Windows\system32\NSI.dllLoadedModule[29]=C:\Windows\system32\CRYPT32.dllLoadedModule[30]=C:\Windows\system32\MSASN1.dllLoadedModule[31]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Configuration\907b2b3dae591e0484acfc0ea63e8caa\System.Configuration.ni.dllLoadedModule[32]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\1fb1b14199d6aec70df1a0626a3ae5f2\System.Xml.ni.dllLoadedModule[33]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.VisualBas#\1ec65ef1b8265780b3a6e7f1855db885\Microsoft.VisualBasic.ni.dllLoadedModule[34]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Transactions\c92eb7f61e9703abbf85f340e4a38c54\System.Transactions.ni.dllLoadedModule[35]=C:\Windows\assembly\GAC_64\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dllLoadedModule[36]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.EnterpriseSe#\a3af29f85ea516622318918d501118d2\System.EnterpriseServices.ni.dllLoadedModule[37]=C:\Windows\system32\CRYPTSP.dllLoadedModule[38]=C:\Windows\system32\rsaenh.dllLoadedModule[39]=C:\Windows\system32\RpcRtRemote.dllLoadedModule[40]=C:\Windows\system32\security.dllLoadedModule[41]=C:\Windows\system32\SECUR32.DLLLoadedModule[42]=C:\Windows\system32\SSPICLI.DLLLoadedModule[43]=C:\Windows\system32\credssp.dllLoadedModule[44]=C:\Windows\system32\schannel.DLLLoadedModule[45]=C:\Windows\system32\kerberos.DLLLoadedModule[46]=C:\Windows\system32\cryptdll.dllLoadedModule[47]=C:\Windows\system32\msv1_0.DLLLoadedModule[48]=C:\Windows\system32\ntdsapi.dllLoadedModule[49]=C:\Windows\system32\netapi32.dllLoadedModule[50]=C:\Windows\system32\netutils.dllLoadedModule[51]=C:\Windows\system32\srvcli.dllLoadedModule[52]=C:\Windows\system32\wkscli.dllLoadedModule[53]=C:\Windows\system32\LOGONCLI.DLLLoadedModule[54]=C:\Windows\system32\mswsock.dllLoadedModule[55]=C:\Windows\System32\wshtcpip.dllLoadedModule[56]=C:\Windows\System32\wship6.dllLoadedModule[57]=C:\Windows\system32\DNSAPI.dllLoadedModule[58]=C:\Windows\system32\rasadhlp.dllLoadedModule[59]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\diasymreader.dllLoadedModule[60]=C:\Windows\system32\iphlpapi.dllLoadedModule[61]=C:\Windows\system32\WINNSI.DLLLoadedModule[62]=C:\Windows\system32\dhcpcsvc6.DLLLoadedModule[63]=C:\Windows\system32\dhcpcsvc.DLLLoadedModule[64]=C:\Windows\system32\VERSION.dllLoadedModule[65]=C:\Windows\system32\apphelp.dllFriendlyEventName=Stopped workingConsentKey=CLR20r3AppName=SomeApplicationAppPath=C:\Program Files (x86)\Some Company\Application\SomeApplication.exeReportDescription=Stopped workingAs i stated the app runs as this user when the same app is run manually but problems occurs when scheduled. Not sure if there are any other logs to take a look at? If it helps i also edited User Account Control: Behavior of elevation to prompt for the administrators and set it not to, but same issue.Thanks Edited June 30, 2010 by Bad boy Warrior Link to comment Share on other sites More sharing options...
Tripredacus Posted June 30, 2010 Share Posted June 30, 2010 What happens if you try to manually run it from the Tasks screen? I am betting you are getting an access denied when it tries to run. Can you try changing the account that it runs from, to say SYSTEM or something else just for testing? Link to comment Share on other sites More sharing options...
Bad boy Warrior Posted June 30, 2010 Author Share Posted June 30, 2010 What happens if you try to manually run it from the Tasks screen? I am betting you are getting an access denied when it tries to run. Can you try changing the account that it runs from, to say SYSTEM or something else just for testing?Manually running as another user has the same results. I changed it to System and had the same results again.... Link to comment Share on other sites More sharing options...
iamtheky Posted June 30, 2010 Share Posted June 30, 2010 are you messing with excel in this scheduled task? such that you may need to manually create "C:\Windows\System32\config\systemprofile\Desktop" folder first.http://social.msdn.microsoft.com/Forums/en/innovateonoffice/thread/b81a3c4e-62db-488b-af06-44421818ef91 Link to comment Share on other sites More sharing options...
Bad boy Warrior Posted June 30, 2010 Author Share Posted June 30, 2010 are you messing with excel in this scheduled task? such that you may need to manually create "C:\Windows\System32\config\systemprofile\Desktop" folder first.http://social.msdn.microsoft.com/Forums/en/innovateonoffice/thread/b81a3c4e-62db-488b-af06-44421818ef91No not using Excel or any Office product. Link to comment Share on other sites More sharing options...
coolcalimba Posted April 23, 2011 Share Posted April 23, 2011 I had this with an .exe I was trying to run using the Windows Server 2008 task scheduler. Task would run fine if I double clicked it but from the task scheduler it would fail with error "...... has stopped working."If the file is in C:\ or a close sub directory, try moving it onto the desktop and it might run. Its obviously a permissions thing but much easier to just move the file rather than mess about with windows' conveluted permissions system. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now