[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference necsc::paw

Title:POLYCENTER AssetWORKS + Microsoft Systems Management Server
Notice:See note 937.1 for kit access information access
Moderator:RDVAX::LEVYD
Created:Wed Feb 23 1994
Last Modified:Fri May 30 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:977
Total number of notes:3989

946.0. "Is SMS 1.2 sp1 bad for PAW 3.0? " by ESSB::RJOYCE () Mon Feb 10 1997 07:04

    
    Hi,
    
    How many of you have lab / test / live installs of PAW V3.0, 
    either the CA V3.0 or the Dec (on-hold) V3.0 running with 
    SMS V1.2??
    
    I'm trying to figure out if it is just on selected Alpha platforms 
    that when you put on SMS 1.2 sp1, problems occur with AssetWORKS 
    Reports not completing, PAW Services Configuration not working and 
    red events in NT Event Viewer. 
    
    The above has happened in three sites (two Alpha 2100s and an 
    Alpha 1000). So far, reinstalling without SMS 1.2 sp1 resolves the
    issue. Note: [An IPMT has been issued to CA on this one]. 
    
    I'm also interested to hear if PAW works well for you with SQL
    Integrated Security mode. 
    
    Many thanks,
    
    Richard
T.RTitleUserPersonal
Name		DateLines
946.1Input!!!ESSB::RJOYCETue Feb 11 1997 11:4615
    Input:
    
    Installing SMS 1.2, then SMS 1.2 sp1, then PAW V3.0 = Gave problems
    
    Installing SMS 1.2, then PAW V3.0 = O.K.
    
    Installing SMS 1.2, then PAW v3.0, then SMS 1.2 sp1 followed by PAW
    ReRegister = Gave Problems
    
    Installing SMS 1.2, then PAW v3.0, then SMS 1.2 sp1 without doing a PAW
    ReRegister = O.K.
    
    Installing SMS 1.2, then PAW v3.0, then SMS 1.2 sp1 followed by PAW
    ReRegister = Problems, then PAW Upgrade = fixes problems
946.2LJSRV2::JCNo friends on powder daysTue Feb 25 1997 18:0223
>    Installing SMS 1.2, then SMS 1.2 sp1, then PAW V3.0 = Gave problems
 
MS probably changed their DLLs.
   
>    Installing SMS 1.2, then PAW V3.0 = O.K.
 
that is what we tested on.
   
>    Installing SMS 1.2, then PAW v3.0, then SMS 1.2 sp1 followed by PAW
>    ReRegister = Gave Problems
 
DLL changes, i bet.
   
>    Installing SMS 1.2, then PAW v3.0, then SMS 1.2 sp1 without doing a PAW
>    ReRegister = O.K.
 
that is strange.
   
>    Installing SMS 1.2, then PAW v3.0, then SMS 1.2 sp1 followed by PAW
>    ReRegister = Problems, then PAW Upgrade = fixes problems
 
trhat is even more strange. what doesn't work?
946.3ZEKE::BURTONJim Burton, DTN 381-6470Wed Mar 05 1997 15:206
Please call the CSC and discuss your problem with them.  They have answers
to many common questions, plus they have an escalation directly to the
engineers at CA.

Jim
POLYCENTER P.M.
946.4Done that! Been there! Never going back!ESSB::RJOYCETue Mar 11 1997 08:4826
    Hi,
    
    Yes an IPMT was sent in ages ago and I have not been very happy with CA
    Engineering (aka C.E.) replies. 
    
    J.C.; sorry for the delay, been off-site trying to get SMS/PAW to work!!
    
    With SMS 1.2 sp1 installed in the standard manner on an Alpha 2100, three 
    problems were visable; 1) AssetWORKS Reports did not complete, 2) PAW
    Services Configuration did not appear and 3) NT Error Event from 4 PAW
    Services saying unable to obtain adequate configuration information
    from the registry. My workaround was to follow an install sequence as I
    previously described. If on an Alpha 1000, I installed SMS 1.2 sp1
    after PAW 3.0 and then did a PAW ReRegister, I remember two main
    errors, 1) NT Error Events saying PAW could not create a temp file in
    SMS's sitecfg.box directory and I think number two was again the
    AssetWORKS Reports never completing. 
    
    CA's response was to say something like the workaround is to not
    install the SMS sp!!! and secondly, can my Customer try working without
    using SQL Integrated Security mode!!! 
    
    The saga continues....
    
    Richard