kix32.exe has generated errors - KiXtart.org

You are not logged in. [Log In] KiXtart.org website » Forums » KiXtart » Advanced Scripting » kix32.exe has generated errors

Page 1 of 1

Topic Options

#66997 - 2002-06-14 01:31 PM kix32.exe has generated errors
John McPoyle John McPoyle Lurker Registered: 2002-06-14 Posts: 4	We have a Windows 2000 server with Kixtart v4.02 installed with about 50 workstations that are a mix of Win 98 and Win 2000. The script is fairly straight forward with just a handful of "If InGroup" statements to map a drive accordingly. Everything is working fine except on one workstation which gets the following error: "kix32.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created." Once that message appears, the logon script hangs. If you close it, the computer logs itself out. Once in a while the script works for some reason. Any suggestions would be appreciated.
Top

#66998 - 2002-06-14 01:43 PM Re: kix32.exe has generated errors
Howard Bullock Howard Bullock KiX Supporter Registered: 2000-09-15 Posts: 5809 Loc: Harrisburg, PA USA	You failed to tell us which OS and version level the failing computer is. _________________________ Home page: http://www.kixhelp.com/hb/
Top

#66999 - 2002-06-14 01:56 PM Re: kix32.exe has generated errors
John McPoyle John McPoyle Lurker Registered: 2002-06-14 Posts: 4	The problem machine is Windows 2000 Pro - Service Pack 2.
Top

#67000 - 2002-06-14 02:08 PM Re: kix32.exe has generated errors
Lonkero Lonkero KiX Master Guru Registered: 2001-06-05 Posts: 22346 Loc: OK	is it's configuration different from other wksta's? like, if it's old win9x which has been updated to win2k. this may be an issue. also, if the service pack installation has failed or some files are replaced with other perhaps older ones. also, if you have your kix ran from wksta, the installation may have failed. perhaps reinstalling may help. nothing explicit comes to my mind. but if only one machine is failing, the problem also is related to that wksta somehow and it's diff from the others. cheers, _________________________ ! download KiXnet
Top

#67001 - 2002-06-14 02:13 PM Re: kix32.exe has generated errors
BrianTX BrianTX Korg Regular Registered: 2002-04-01 Posts: 895	I think the key to your problem is the statement: "Everything is working fine except on one workstation" If you can't figure it out fairly quickly, the simplest solution may be to reload the software (image, or whatever you use). There are a few things that I've seen cause this error. 1. Permission problems on the machine. 2. Something running in the background (startup)while KiXtart runs. You can synchronize the logon script and try to run it.. sometimes this helps. 3. Your script assumes something that isn't the case on this machine. 4. The KiXtart files aren't in sync (You have different versions in different places.) .... I'm sure I'm forgetting something here.. but to troubleshoot, try: 1. verify all versions of kix by copying over fresh copies and deleting all other kixtart files but the ones you copied. 2. creating a dummy script with nothing in it and see if that runs. 3. Add the account of the user to the local administrator group and try it. 4. If those fail, try taking the script out of user manager and just running it locally from themachine. This should get you started at least. Brian
Top

#67002 - 2002-06-14 02:25 PM Re: kix32.exe has generated errors
Kdyer Kdyer KiX Supporter Registered: 2001-01-03 Posts: 6241 Loc: Tigard, OR	John, To add to Brian's response.. In a non-native environment, we have used Robocopy to replicate the scripts, batch files, etc. to all member DCs.. However, with our 2000 environment, we have replication partners setup and this is all done automatically (we are shutting down all of the NT BDC machines over the next week - woohoo!). Are you running the scripts local to the workstation or on the server? Thanks, Kent _________________________ Utilize these resources: UDFs (Full List) KiXtart FAQ & How to's
Top

#67003 - 2002-06-14 02:43 PM Re: kix32.exe has generated errors
John McPoyle John McPoyle Lurker Registered: 2002-06-14 Posts: 4	All scripts are being run from the server
Top

#67004 - 2002-06-14 02:46 PM Re: kix32.exe has generated errors
Kdyer Kdyer KiX Supporter Registered: 2001-01-03 Posts: 6241 Loc: Tigard, OR	John, Did you try the things that Brian suggested? If so, what is the outcome? Kent _________________________ Utilize these resources: UDFs (Full List) KiXtart FAQ & How to's
Top

#67005 - 2002-06-14 03:36 PM Re: kix32.exe has generated errors
Sealeopard Sealeopard KiX Master Registered: 2001-04-25 Posts: 11165 Loc: Boston, MA, USA	Put a code: BREAK ON DEBUG ON in the first lines of the login script and run it on that particular workstation. It might show you where it fails. You might also want to send your script through MCA's KiXStrip program (download at http://home.wanadoo.nl/scripting/ ) _________________________ There are two types of vessels, submarines and targets.
Top

#67006 - 2002-06-16 12:37 AM Re: kix32.exe has generated errors
John McPoyle John McPoyle Lurker Registered: 2002-06-14 Posts: 4	Thanks for all of your suggestions. I went back to try some of them but the machine started working fine without changing anything. Go figure.
Top

#67007 - 2002-06-16 07:31 AM

Re: kix32.exe has generated errors

MCA

KiX Supporter

Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU

Dear,

Welcome to the board.

Some questions:
- where are kixtart files located?
- where script located?
- how do you start kix32 or wkix32?

Our Suggestion:

A way to see what is going wrong can be done by our kixstrip
tool with option /debug.
At the end you only need to look at output file to see what was
executed and what were the error status.
The debugging file will not be overwritten.

QUESTIONs:
- is it possible to see what is happening during a logging on session.
- is it possible to see how long our script runs.

Advice: please run your script after adding our debugging code to it.
How:
- add debugging code?
- is debugging possible without user intervention? YES
- can is be usefull by logon or script problems? YES

A way of checking your script is by using our tool kixstrip on our site
http://home.wanadoo.nl/scripting
With the option /debug we add additional kixtart code, which shows

which line was executed.
what was the time of execution.
what was the error status of previous executed line.

So it is possible to catch the error status of kixtart statements during
a logon session.and
it will show the last executed before script is crashing.

An example.

For changing your script with debugging code use
f.e. kixstrip input.kix output.kix /debug
Change line.4 of this new script

code:

   IF RedirectOutput("")
   ENDIF

to f.e.

code:

   IF RedirectOutput("c:\kixdebug.log")
   ENDIF

and commented all lines with a RedirectOutput statement.
During the execution the information will be append to previous information.
So it is possible to check the differences.

be sure above RedirectOutput file has write permissions.

A kixstrip output example of our script os.kix (reduced version) is:

code:

                                            CLS
                                            COLOR C+/N
                                            AT (1,1) " "
                                            IF RedirectOutput("")
                                            ENDIF
                                            ? "-"+LCASE(@day)+" "+@date+" "+@time+"- kixtart "+@kix+"/3.04e script starting."
                                            ? "-"
                                            ? "-curdir:       "+LCASE(@curdir)
                                            ? "-scriptdir:    "+LCASE(@scriptdir)
                                            IF (instr("-4.1x-","-"+substr(@kix,1,3)+"x-") <> 0)
                                              ? "-scriptname:   "+LCASE(@scriptname)
                                            ENDIF
                                            ? "-startdir:     "+LCASE(@startdir)
                                            ? "-"
                                            ? "-userid:       "+LCASE(@userid)+"/"+LCASE(@wuserid)
                                            ? "-user priv:    "+LCASE(@priv)
                                            IF (instr("-4.xx-","-"+substr(@kix,1,2)+"xx-") <> 0)
                                              ? "-version:      inwin="+@inwin+"/dos="+@dos"/productsuite="+@productsuite+"/producttype="+@producttype"/csd="+LTRIM(RTRIM(@csd))
                                            ELSE
                                              ? "-version:      inwin="+@inwin+"/dos="+@dos
                                            ENDIF
                                            ? "-"
?"-     start-"+@time+"- @error @serror "? 

?"-         1-"+@time+"- @error @serror "?  $os=""
?"-         2-"+@time+"- @error @serror "?  SELECT
?"-         3-"+@time+"- @error @serror "?  CASE 
                                                  (@inwin = 1) AND (@dos = "5.1")   ; - Windows XP -
?"-         4-"+@time+"- @error @serror "?        $os="XP"
?"-         5-"+@time+"- @error @serror "?  CASE 
                                                  (@inwin = 1) AND (@dos = "5.0")   ; - Windows 2000 -
?"-         6-"+@time+"- @error @serror "?        $os="W2K"
?"-         7-"+@time+"- @error @serror "?  CASE 
                                                  (@inwin = 1)                      ; - Windows NT -
?"-         8-"+@time+"- @error @serror "?        $os="NT4"
?"-         9-"+@time+"- @error @serror "?  CASE 
                                                  (@inwin <> 1) AND (@dos = "4.90") ; - Windows ME -
?"-        10-"+@time+"- @error @serror "?        $os="ME"
?"-        11-"+@time+"- @error @serror "?  CASE 
                                                  (@inwin <> 1) AND (@dos = "4.10") ; - Windows 98 -
?"-        12-"+@time+"- @error @serror "?        $os="W98"
?"-        13-"+@time+"- @error @serror "?  CASE 
                                                  (@inwin <> 1) AND (@dos = "4.0")  ; - Windows 95 -
?"-        14-"+@time+"- @error @serror "?        $os="W95"
?"-        15-"+@time+"- @error @serror "?  CASE 
                                                  1
?"-        16-"+@time+"- @error @serror "?        $os="???" ; - undetermined -
?"-        17-"+@time+"- @error @serror "?  ENDSELECT
?"-        18-"+@time+"- @error @serror "?  ? "$$os      "+$os

?"-       end-"+@time+"- @error @serror "? 
                                            ? "-"
                                            ? "-"+LCASE(@day)+" "+@date+" "+@time+"- kixtart "+@kix+"/3.04e script ending."
                                            ? "-"
                                            IF (instr("-4.1x-","-"+substr(@kix,1,3)+"x-") <> 0)
                                              ? "-"+@cpu+" ("+@mhz+" Mhz, memory "+MemorySize()+" MB)"
                                            ENDIF
                                            ? "-"
;($begin)
;
;                       sun 14-apr-2002 05:32:19       (kix 4.10 vs 3.04e)
;
;Informative KIXSTRIP:   no errors found (input=18 output=18 skip=0).
;
;Summary     KIXSTRIP:      block structures
;                           - do:until                 [0:0]
;                           - for|each:in|to:step|next [0|0:0|0:0|0]
;                           - function:endfunction     [0:0]
;                           - if:else:endif            [0:0:0]
;                           - select:case:endselect    [1:7:1]
;                           - while:loop               [0:0]
;Informative KIXSTRIP:    1 block_structure found.
;Informative KIXSTRIP:   no UDF's found.
;Informative KIXSTRIP:   no labels found.
;Summary     KIXSTRIP:      BREAK CALL DEBUG DISPLAY ENDFUNCTION EXECUTE EXIT FUNCTION GET GETS GOSUB GOTO OLExxx PLAY QUIT RETURN RUN SHELL SLEEP THEN USE
;
;($end)

An output example of kix32 run:

code:

-sunday 2002/04/14 05:32:38- kixtart 4.02/3.04e script starting.
-
-curdir:       d:\
-scriptdir:    
-startdir:     c:\windows
-
-userid:       MCA/MCA
-user priv:    guest
-version:      inwin=2/dos=4.0/productsuite=/producttype=Windows 95/csd=B
-
-     start-05:32:39- 0 The operation completed successfully. 

-         1-05:32:39- 0 The operation completed successfully. 

-         2-05:32:39- 0 The operation completed successfully. 

-        14-05:32:39- 0 The operation completed successfully. 

-        15-05:32:39- 0 The operation completed successfully. 

-        18-05:32:39- 0 The operation completed successfully. 

$os      W95
-       end-05:32:39- 0 The operation completed successfully. 

-
-sunday 2002/04/14 05:32:39- kixtart 4.02/3.04e script ending.
-
-

When you still have problems please:

put some code on the board.
put your logon batch file on the board.
put the output of a debugging run on the board.
put a DIR list of your NETLOGON directory on the board.
put a DIR list of your clients on the board with contains information
about: KIX32.EXE and KX*.DLL

Greetings.
btw: it is only some additional information about how you can debug your script.

btw: with kixstrip ? you get a summary of possible options.
The result will be something like this:

code:

 Kixstrip 4.10 (vs 3.04e)     (c) MCA - scripting@wanadoo.nl - 2000, 2001, 2002
 ------------------------------------------------------------------------------
 kixstrip   [input] [output]                                                   
            /Block_Check or /BC     /Combine                /Debug             
            /Headers                /License                /License=[var]     
            /Performance            /Print                  /Progress          
            /Show_Errors or /SE     /Show_Structure or /SS  /Translate         
            /TAB=[num] (def: 6)
 default:   /Combine /Headers /License             (other options are negative)
 other:   - options with prefix "/No" will be ignored. f.e. /NoDebug /NoTab    
          - /Block_Check /Tab=2  (auto set: /NoCombine /NoLicense /Print      )
            /Debug               (auto set: /NoLicense /Print /Show_Errors    )
          - /Block_Check         (reformat kixtart code inc. block structure  )
            /Combine             (combine lines to one line                   )
            /Debug               (insert "line numbers" for each printed line )
            /Headers             (insert summary report as footer             )
            /Performance         (insert "indicator"    for each executed line)
            /Print               (do not remove print statements              )
            /Progress            (insert "indicator"    for each printed line )
            /Show_Errors         (insert error messages in output file        )
            /Show_Structure      (insert block structures in output file      )
            /Translate           (convert keywords to upper/lower-case        )
 examples - kixstrip test.kix test.out /Block_Check /Debug                     
          - kixstrip test.kix test.out /Performance /Show_Structure

btw: Symbol

on our homepage has been linked to related http://kixtart.org topic.

_________________________
email scripting@wanadoo.nl homepage scripting@wanadoo.nl | Links | Summary of Site Site KiXforms FAQ kixtart.org library collection mirror MCA | FAQ & UDF help file UDF kixtart.org library collection mirror MCA | mirror USA | mirror europe UDF scriptlogic library collection UDFs | mirror MCA

Top

Page 1 of 1

Previous Topic View All Topics

Index Next Topic

Moderator: Glenn Barnas, NTDOC, Arend_, Jochen, Radimus, Allen, ShaneEP, Ruud van Velsen, Mart

Hop to:

Shout Box

Search the board with:
superb Board Search
or try with google:

	Web kixtart.org