/build/static/layout/Breadcrumb_cap_w.png
11/16/2018 143 views

my scripts has 1245 character , it not running in MSI custom action . I have taken log for this msi, only 879 characters of the script i can find in log file, remaining skipped . Do anyone have idea about this? 

0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

1

Humm, havent used a CA that long before, but it could be the MSI logging just truncating it.

Whack a simple file write at the end of the CA, then check - you find out pretty quick of its log truncating or a char limitation in the CA.

Be very surprised if it was the latter.

Answered 11/17/2018 by: rileyz
Red Belt

  • vbs is running manually , but not working when it is implented in msi.

All Answers

0

The output of most CAs is truncated by the logging function. There's an amazing class file for logging in VBS that's a snap to add to your script(s) so you can output your own log.  Google for 'CLogger.vbs'

Answered 11/19/2018 by: VBScab
Red Belt

  • actually,truncating is not the issue . My vbs is working manually but it is not working when implemented in msi
0

In which context is the CA running? If user, does the user have appropriate rights to perform the functions that it's executing? Do you have it only in the UI sequence? If so, it won't run at all if the MSI is executed silently.


It might be easier to post the content of the relevant tables.

Answered 11/19/2018 by: VBScab
Red Belt