Alaska Software Inc. - Help
Username: Password:
AuthorTopic: Help
Alex KarnozgitskyHelp
on Thu, 11 Dec 2008 18:16:51 +0200
Alex
Karnozhitsky
WG SoftPro
Alex KarnozgitskyRe: Help
on Tue, 16 Dec 2008 12:14:20 +0200
Alex
Karnozhitsky
WG SoftPro 

  "Alex Karnozgitsky" <alexey@kiev.wgsoftpro.com> сообщил/сообщила в новостях следующее: news:24f4035f$5e782114$356@news.alaska-software.com...
  Hi, All

  We need the help.  
  Our application runs via WAA.
  Sometimes we have stange error on server (WAA closed - more often without any notifications). 
  And we have only xppfatal.log :( 
  And any ideas. In waaxxx.logs we can not find any unclosed tasks.
  We created own logs but without any success.

  Can somebody help me?

  ==============================================
  FATAL ERROR LOG
  Not recoverable Error!
  SYS Thread-ID: 1360
  Module: EH
  Error Codes: EH: 900 Sub: 0(0) OS: 0 XPP: 0
  Call Stack of Thread 1 (1404):
  SRVSERVEFRONTEND(714)
  MAIN(148)
  Call Stack of Thread 2 (1160):
  Call Stack of Thread 3 (748):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 4 (712):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 5 (668):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 6 (624):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 7 (580):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 8 (536):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 9 (492):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 10 (448):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 11 (404):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 12 (360):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 13 (316):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 14 (272):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 15 (228):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 16 (184):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 17 (140):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 18 (96):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 19 (52):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 20 (4):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 21 (2092):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 22 (2136):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 23 (2180):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 24 (2224):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 25 (2268):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 26 (2312):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 27 (2356):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 28 (2400):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 29 (2444):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 30 (2488):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 31 (2532):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 32 (2576):
  @WAA1JOBQUEUE@I@GETJOB(609)
  SERVEJOB(271)
  SERVEJOBPROTECTION(208)
  Call Stack of Thread 33 (2620):
  @CGICHANNEL@I@CONNECT(109)
  @WAAGATEWAY@I@CGICONNECT(75)
  @WAA1REQUESTER@I@EXECUTE(177)
  Call Stack of Thread 34 (2680):
  File: D:\ALASKA\WAA1W32\SERVER\WAA1SRV.EXE
  TimeStamp: 20081211 15:24
  End of FATAL ERROR LOG.

  ==============================================

  -- 
  Alex
  Karnozhitsky
  WG SoftPro

error.jpg
Steffen F. PirsigRe: Help
on Tue, 16 Dec 2008 12:36:15 +0100

error.jpg
Alex KarnozgitskyRe: Help
on Wed, 17 Dec 2008 09:16:35 +0200
Alex
Karnozhitsky
WG SoftPro 
  "Steffen F. Pirsig" сообщил/сообщила в новостях следующее: news:5d7c7884$333f0c51$b43c@news.alaska-software.com...
  Alex,

   which Add-Ons are you using? Are you using ADS DatabaseEngine
   with the ACE32 layer for example? If so most likely the error is from
   that DLL. As a matter of fact the Xbase++ runtime does not use the
   MS VC++ compiler and therefore is not able to post that type of
   runtime-error.

   In other words, to get an idea about the root of your isse, identify
   all the dlls/libs you are linking / adding to your package dlls.You
   can post them here - so eventually somebody else can 
   contribute.

   Hope this helps or at least provides you an hint,
   regards
   Steffen F. Pirsig
   Alaska Software

    "Alex Karnozgitsky" <alexey@kiev.wgsoftpro.com> wrote in message news:31e0f965$e9c96c1$bca3@news.alaska-software.com...
    Hi All

    Sometimes before close application we have this message





    Any ideas?


    -- 
    Alex
    Karnozhitsky
    WG SoftPro 

      "Alex Karnozgitsky" <alexey@kiev.wgsoftpro.com> сообщил/сообщила в новостях следующее: news:24f4035f$5e782114$356@news.alaska-software.com...
      Hi, All

      We need the help.  
      Our application runs via WAA.
      Sometimes we have stange error on server (WAA closed - more often without any notifications). 
      And we have only xppfatal.log :( 
      And any ideas. In waaxxx.logs we can not find any unclosed tasks.
      We created own logs but without any success.

      Can somebody help me?

      ==============================================
      FATAL ERROR LOG
      Not recoverable Error!
      SYS Thread-ID: 1360
      Module: EH
      Error Codes: EH: 900 Sub: 0(0) OS: 0 XPP: 0
      Call Stack of Thread 1 (1404):
      SRVSERVEFRONTEND(714)
      MAIN(148)
      Call Stack of Thread 2 (1160):
      Call Stack of Thread 3 (748):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 4 (712):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 5 (668):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 6 (624):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 7 (580):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 8 (536):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 9 (492):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 10 (448):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 11 (404):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 12 (360):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 13 (316):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 14 (272):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 15 (228):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 16 (184):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 17 (140):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 18 (96):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 19 (52):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 20 (4):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 21 (2092):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 22 (2136):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 23 (2180):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 24 (2224):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 25 (2268):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 26 (2312):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 27 (2356):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 28 (2400):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 29 (2444):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 30 (2488):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 31 (2532):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 32 (2576):
      @WAA1JOBQUEUE@I@GETJOB(609)
      SERVEJOB(271)
      SERVEJOBPROTECTION(208)
      Call Stack of Thread 33 (2620):
      @CGICHANNEL@I@CONNECT(109)
      @WAAGATEWAY@I@CGICONNECT(75)
      @WAA1REQUESTER@I@EXECUTE(177)
      Call Stack of Thread 34 (2680):
      File: D:\ALASKA\WAA1W32\SERVER\WAA1SRV.EXE
      TimeStamp: 20081211 15:24
      End of FATAL ERROR LOG.

      ==============================================

      -- 
      Alex
      Karnozhitsky
      WG SoftPro

error.jpg
Bruce AndersonRe: Help
on Tue, 16 Dec 2008 12:04:12 -0600
Alex KarnozgitskyRe: Help
on Wed, 17 Dec 2008 09:18:27 +0200
Alex
Karnozhitsky
WG SoftPro 
  "Bruce Anderson" <banderson@graphical-db.com> сообщил/сообщила в новостях следующее: news:34bda13$323e0a0c$597@news.alaska-software.com...
  I think I had this problem long ago.  If my memory is correct, this is what caused it.  I had an error in my code. 
  Here is a pseudocode sample:
  <form name="myform" onsubmit="return true" action="/cgi-bin/waa1gate.isa" method="POST">
  ...blah, blah, blah code
  <input type="button" value="Continue" onClick="document.submit();" />
  </form>

  This caused the form to be submitted twice, once by the javascript function, and once by the form method.  I think it was confusing many tasks, and eventually WAA1SRV.exe was giving up.

  My solution was to change the form tag attribute to onsubmit="return false" and suppress the second instance.
  I do not use <input type="submit"...>; I prefer the flexibility of using javascript for this task.