Conference necsc::paw

965.0. "PAW Error Events: Suggestions??" by ESSB::RJOYCE () Wed Apr 02 1997 12:19

Hi, 
    
Could someone shed some light on why these events occur, please? 
    
Environment: PAW V3.0 SMS V1.2
    
Event Type 1:  Report Driver problem on an S.S.S.
=============
    
    On a PAW/SMS Secondary Site Server Alpha 400, a new install. Its a
    secondary site, no user generated report activity was current.  

Event id: 5106	PAW   ERROR  @ 2:23:49 2:23:53 2:23:56 2:24:02 2:24:14 2:24:18 

(main.cpp:1783) Report driver could not parse its command line,  Parameters 
    parsed: SQLServer=, SQLDataBase=, SQLUser=. If you are running this 
    report by hand, verify that you are following the syntax for this 
    particular report driver. 

EVENT ID: 5106	PAW ERROR

(drvmmain.cpp:2354) Report driver could not parse its command line,  Parameters
     parsed: SQLServer=, SQLDataBase=, SQLUser=. If you are running this 
    report by hand, verify that you are following the syntax for this 
    particular report driver. 

    
EVENT Type 2: LSFC problem
===========
Before rebuilding the systems, I saw this event, checked the directories
    and they seemed O.K., also ran the command in DOS and it worked
    fine???? These events appeared soon after the rebuild. Have not yet
    implemented Metering at this site, so no CSUs to be collected as yet. 
    
On a Secondary Site Server: SMS 1.2, no SMS sp, PAW 3.0
    
EVENT ID 5072	PAW 	ERROR

(PAW System Mail:1286)
  EXPLANATION:
 Unable to launch LSFC.EXE to collect files from clients. The following command
    line was used:
     C:\SMS\site.srv\alpha.bin\LSFC.EXE /S:ISVMIF.BOX\PAW 
    /D:C:\PAW\sysmail\fromclnt /P:202 /T:5
 The Win32-specific error code returned by GetLastError() is 183.
 This is a serious error.  POLYCENTER AssetWORKS System Mail will not deliver 
    inbound files from clients until this is repaired.
 REMEDY:
 Verify that LSFC.EXE is located at the above path and that the directory 
    specified in the command line is the correct POLYCENTER AssetWORKS 
    directory.  Try executing LSFC.EXE manually with the above command line 
    and see if any errors are reported to the console.  This error is usually 
    caused by one or more of the above paths being incorrect.  Also verify 
    that there is adequate free disk space in the specified working directory.
    
                                              

On the PAW/SMS Central Site Server: Alpha 2100 SMS 1.2 no sp, PAW 3.0 

Event id: 5072	Source: PAW Type: Error

(PAW System Mail:1286)
  EXPLANATION:
 Unable to launch LSFC.EXE to collect files from clients. The following command
    line was used:
     E:\SMS\site.srv\alpha.bin\LSFC.EXE /S:ISVMIF.BOX\PAW 
    /D:E:\PAW\sysmail\fromclnt /P:163 /T:5
 The Win32-specific error code returned by GetLastError() is 183.
 This is a serious error.  POLYCENTER AssetWORKS System Mail will not deliver 
    inbound files from clients until this is repaired.
 REMEDY:
 Verify that LSFC.EXE is located at the above path and that the directory 
    specified in the command line is the correct POLYCENTER AssetWORKS 
    directory.  Try executing LSFC.EXE manually with the above command line 
    and see if any errors are reported to the console.  This error is usually 
    caused by one or more of the above paths being incorrect.  Also verify 
    that there is adequate free disk space in the specified working directory. 
    
    Many thanks,
    
    Richard

    Hello:
    
       We also have a site getting the event #5072. Did you ever solve the
    problem?
    
    REgards,
       Dan