Hi All,

Just wondering if anyone has come across running a scheduled task, which calls a vbscript which then in turns runs subroutines that install MSI.

Usually this works fine, but got Information Mapping 3.0f and when I log on to the server and run the VBScript it installs with out a problem. Checked all log files and spot on, but when it run via scheduled task, it just sits there running. The log file stops and I am out of ideas. Why would it not work in schedule task but will run when I double click on it.

Any ideas?
[align=center] [/align]
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Scheduled tasks run in System context with no UI. I suspect your installer is popping up a dialog to the non-existent user. Check it out by running the script via a 'CMD /interactive' call.

BTW, is the script adding any value? Could the package be run by directly calling MSIExec (if it's an MSI) or the set-up stub?
Answered 08/18/2010 by: VBScab
Red Belt

Please log in to comment
0
To do the interactive command, the run field in the Scheduled Task will be

C:\Windows\System32\cmd.exe /interactive "C:\install\Installinfomap3.0f.vbs"

I did that, left it to run for a bit then logged in to the box and didnt see anything.

A box does pop up when I double click on the vbs script and disappear again.
[align=left] [/align]
Answered 08/18/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
FYI,

To get the schuduled task added to the server, we have a batch files that does the following

schtasks /create /S \\%1 /RU <domain>\<user> /RP <password> /SC once /TN "InstallApp" /TR "path of script" /ST 12:00:00
[align=left] [/align]
Answered 08/18/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
Any ideas, still having the same issue.

I have tried C:\windows\system32\cscript.exe //nologo "C:\install\installinfomap3.0f.vbs"

Didnt complete in scheduled tasks, but worked when I logged in to the server and ran it manually.
[align=left] [/align]
Answered 08/23/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
Does the command line you're passing to MSIExec include creating a log? If so, what does the log tell you? And does it include the correct switch to run WI completely silently, i.e. /QN
Answered 08/24/2010 by: VBScab
Red Belt

Please log in to comment
0
[align=left]Here is part 1 of the log, it is in two part due to it begin 1.3mb
[/align]

Attachment

Answered 08/24/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
Part 2 of the log file.
[align=left] [/align]

Attachment

Answered 08/24/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
The log - even in 2 parts- is incomplete. Also, part 1 has been reformatted somehow. Paths have no backslashes, the time field has been rearranged and so on.

Lastly, my question was, what does the log tell YOU?
Answered 08/25/2010 by: VBScab
Red Belt

Please log in to comment
0
[align=left]The formatting probably changed when I copied it. Will upload it again.

The log tells me it is failing on the Custom Actions, registering the DLL's. Been using a tool to compare the log files of a complete installation and the failed one.

Still not sure why it is failing via Scheduled Tasks, its more than likey it is the Customs Actions that is causing it.

Been speaking to the Vendor, they will be getting in contact soon.


[/align][align=left] [/align]
Answered 08/25/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
Part 1 again
[align=left] [/align]

Attachment

Answered 08/25/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
Part2
[align=left] [/align]

Attachment

Answered 08/25/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
Custom Actions, registering the DLL's.Amateurs...

To compound their idiocy, I wonder if the CA is set to run in user context? That will be easy enough to fix in your transform but having them change their brain-dead package to register DLLs correctly is probably a battle for another day. Unless you want to sell them your fixed version, of course! LOL
Answered 08/26/2010 by: VBScab
Red Belt

Please log in to comment
0
[align=left]True that VBScab,

What I have ended up doing it repackaging their package and got it working, its going to go in to UAT on tuesday so will see what happens. From my testing it is doing it job, so, so far so good.

Cheers for you replies VBScab.
[/align][align=left] [/align]
Answered 08/26/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
Have you thought about how you're going to handle any update/patching to the app? Since you've repackaged it, the vendor's update/patch isn't going to be any use to you, unless you repackage that, too. And the next one. And the next one.
Answered 08/27/2010 by: VBScab
Red Belt

Please log in to comment
0
Due to the environment, we do uninstalls then install the new versions. Ideally that would be good, but its the way things are done.
[align=center] [/align]
Answered 08/28/2010 by: Thegunner
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity