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

Conference mvblab::alphaserver_4100

Title:AlphaServer 4100
Moderator:MOVMON::DAVISS
Created:Tue Apr 16 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:648
Total number of notes:3158

301.0. "ServerWorks features on 4000?" by COPCLU::GREG (Greg Parker @DMO, 857-2454) Fri Oct 18 1996 05:42

T.RTitleUserPersonal
Name
DateLines
301.1PCBU WWW pageSTAR::jacobi.zko.dec.com::jacobiPaul A. Jacobi - OpenVMS Systems GroupFri Oct 18 1996 15:088
301.2A pointer to THE document???COPCLU::GREGGreg Parker @DMO, 857-2454Mon Oct 21 1996 04:3014
301.3MPOS01::naiad.mpo.dec.com::mpos01::cerlingI'[email protected]Wed Oct 23 1996 10:485
301.4ServerWORKS Manager AdvisoryMOVMON::DAVISMon Feb 24 1997 14:08128
    Prioris Server and AlphaServer Systems
    
    ServerWORKS Manager Advisory
    ER-SER02-AA.A01
    
    
    
    Please review the following important technical information. These tips
    can make your installation of ServerWORKS Manager and StorageWorks
    Command Console software much easier. 
    
    "Handle is Null" message 
    ------------------------
    Problem:
    After performing an IP Autodiscovery and selecting an AlphaServer
    system from the resulting map, an error dialog box stating "Handle is
    Null" may be displayed The message box does not close on acknowledgment
    of the error message. 
    
    Solution: 
    To address this problem, follow these steps: 
    
    1. Using Notepad, open up the swextomm.ini file in the directory
       in which ServerWORKS is installed (generally c:\mworks). 
    2. Under the [KCRCM] section, find the line which begins BitmapFile= 
    
    3. Change this to read BitmapFile=c:\mwworks\rcm.bmp 
    
      Note: If ServerWORKS is installed in a directory other than c:\mworks, 
      you will need to substitute that directory name. 
    
    
    
    "Runtime Error" when connecting StorageWorks Command Console 
    ------------------------------------------------------------
    Audience: 
    StorageWorks Command Console software running on a management console 
    with Windows NT 4.0 and Service Pack 2 
    
    Problem:
    Receive "Runtime Error" when attempting to connect a Command Console
    client in direct mode on Windows NT 4.0 with Service Pack 2 installed.  

    Solution: To fix this problem, replace the Service Pack 2 OLEPR032.DLL 
    file with the version included with Command Console 1.1 or 1.1b 
    (V4.2.6068).  Follow these steps:
    
    1. Install Command Console software and Windows NT Service Pack 2.
    
    2. Launch Windows NT Explorer. Select "Options" from the View Menu.  Set 
       the "Show All Files" button.
    
    3. Close all other applications.
    
    4. From the Explorer window, open Windows NT's \System32 directory and
       locate the OLEPRO32.DLL file. Save this to a different file by renaming
       it or by copying it to another directory.
    
    5. Replace with the correct OLEPRO32.DLL file (V4.2.6068).  A
       compressed copy of this file is included in the \client\clnffils
       directory of your RAID platform kit CDROM.  An uncompressed version can
       be found in the StorageWorks web site (www.storage.digital.com) in the
       'technomania', 'tech tips and updates', 'raid solutions'.
       (www.storage.digital.com/swrks/homepage/sup_html/techtips/raid/raid.htm) 
    
    6. Command Console can now be launched in the direct serial mode
       without error 
    
    Note: OLEPRO32.DLL has to be replaced each time Window NT 4.0 Service Pack 
    2 is reinstalled.
    
    
    
   "Newer version of DLL" on install of StorageWorks Command Console
    ----------------------------------------------------------------
    Audience: 
    SWCC V1.1 installed on a Windows95 or Windows NT management console.
    
    Problem: 
    During installation, dialog boxes display which indicate that
    newer versions of required DLLs are already installed on the PC. You
    are asked whether you wish to keep them.
    
    Solution:  
    Run the installation to determine which DLL is in conflict and then
    exit the installation. Rename the conflicting DLL to another name.
    Repeat this process until StorageWorks Command Console installs
    successfully. After completing the install, rename the conflicting DLLs
    back to their original file name. Follow these steps:
    
    1. Run the StorageWorks Command Console installation program. Each time
       a dialog box displays with the name of a conflicting DLL, write down
       the name of the DLL. When prompted to keep the existing DLL, click on
       Yes. Then exit the installation program. 
    
    2. Launch Windows Explorer. Locate the conflicting file in the
       WINDOWS\SYSTEM file, and rename it. 
    
       For example, if the conflicting file is c:\windows\system\MSVCIRT.DLL,
       rename it to c:\windows\system\MSVCIRT.BAK. Or copy it to a different
       directory. 
    
    3. Run the StorageWorks Command Console installation program again.
       Repeat steps one and two until the installation program no longer
       displays any dialog boxes indicating the existence of newer DLLs.
    
    4. After you have completed the install, rename the DLLs back to their
       original names. For example, rename c:\windows\system\MSVCIRT.BAK back
       to c:\windows\system\MSVCIRT.DLL. Or copy the original DLLs back into
       the WINDOWS\SYSTEM directory.
    
    Restart Windows. You have now successfully installed StorageWorks
    Command Console software. ServerWORKS Advisory

ServerWORKS Advisory



3

	Prioris( Server and AlphaServer( Systems
	ServerWORKS Manager Advisory
	ER-SER02-AA. A01