Endpoint Protection

 View Only
Expand all | Collapse all

Problem with LUA 2.2.2

Migration User

Migration UserOct 28, 2009 03:02 AM

Migration User

Migration UserOct 28, 2009 08:07 AM

Migration User

Migration UserOct 28, 2009 09:38 AM

Migration User

Migration UserOct 28, 2009 11:05 AM

Migration User

Migration UserOct 29, 2009 03:15 AM

Migration User

Migration UserOct 29, 2009 04:30 AM

Migration User

Migration UserOct 30, 2009 08:05 AM

Migration User

Migration UserOct 30, 2009 08:54 AM

  • 1.  Problem with LUA 2.2.2

    Posted Oct 27, 2009 11:39 AM
    After install this software (without errors) I open it and try configure Distribution Center and I see this error:
    Connection to **** failed. (Location: *****; URL: unc:\******\******; Status: unreacheble).
    I've checked permission on this share and it seems good.
    I think thi problem associated with unc name because in this name use one "\". How I can change it?
    For installing and configurig LUA I've used this links (http://www.symantec.com/connect/articles/installation-and-configuration-lua)


  • 2.  RE: Problem with LUA 2.2.2

    Posted Oct 27, 2009 01:27 PM
    Hi,

    can you please check if you have a folder called clu-prod at the installation location, i.e. \program files\Symantec\LiveUpdate Administrator. If you find that folder, please make a copy of it in a different location. Rename the original folder.

    Now, you can try to add a distribution centre again and let us know the status.

    Aniket


  • 3.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 02:41 AM

    Try collecting the logs on the LUA and paste it for us we would take a look and let you know the reason

    Open Internet Explorer on your LiveUpdate Administrator 2.x (LUA 2.x) server
    Login to LUA 2.x using valid account credentials.
    Open the following URL: http://127.0.0.1:7070/lua/debug.do  (note: LUA 2.1 uses port 8080 by default.)
    Click Ok when prompted
    When collection is complete, a link will be posted from which to download luadebuginfo.zip.

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009030211283748



  • 4.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 03:02 AM

    Hi,
    I've tried do it but no result.



  • 5.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 03:17 AM
    Please download this report. http://depositfiles.com/files/ieldlwej6


  • 6.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 07:35 AM
    So? Do you know what is it and what I need do with this problem?


  • 7.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 07:42 AM
     Well it shows it is unreachable
    \testserver\....
    try giing a double slash and check if it says ready

    are able to reach it via browser
    \testserver\...


  • 8.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:00 AM

    Pls refer the below doc for configuring distribution center using UNC protocol 

    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/31d992657aa601b2882574e100556c0a?OpenDocument

     


  • 9.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:01 AM
    Hi.
    Please see these screenshots maybe it help you with understanding what is it.

    1.JPG
     2.JPG


  • 10.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:06 AM
    I think this problem associated with one "\" in unc path but I cannot change it. What I do for resolve this problem?
    If I entired \\testserver during configuration Distribution Center I get following eroor: "Please enter a valid Hostname/IP address".
    Maybe this setting store in PG base and we can change it in PG base? If yes, we need credentials for connect PG base.


  • 11.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:07 AM
    Thank you for your help. I did it but no results.


  • 12.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:14 AM

    Can you give  full permission for the user to that share and try..

     


  • 13.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:31 AM
    Yes sure. I do it. Test user have Full access to this share (Sharing and security). But no results.


  • 14.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:38 AM
    Please see screenshot from documentation:
    21.JPG
    And screenshot from my test enviroment:
    12.JPG


  • 15.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:39 AM
    In the doc url "\\" is used for specifying the path and in your screen shot it is"\" 


  • 16.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:42 AM

    If my above suggestion not helps can you give  full permission for the user to that drive also and try..

     


  • 17.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:53 AM
    SAV LUA Account have FULL Access (Shared access and Security access) to ALL Symantec LiveUpdate Adminitration Utilities Folders and Folder for updates.


  • 18.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 08:57 AM
    You will need to add the webdav package for IIS in order to distribute content when using http or https.
    1. To add webdav:
    a. Open Control Panel, and select Add/Remove Programs.
    b. Click on "Add/Remove Windows Components".
    c. Double-click on "Application Server".
    d. Double-click on "Internet Information Services (IIS)".
    e. Double-click on " World Wide Web Service".
    f. Please check "WebDAV Publishing".
     


  • 19.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 09:09 AM
    After doing the above steps go to IIS manager---->Web service extensions and right click on webdav and click on allow

    These steps to be done for both Main LUA server and Distribution Center server
     


  • 20.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 09:17 AM
    Hi,
    I cannot use HTTP(s) or FTP for delivery updates.
    I can use only UNC path.


  • 21.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 09:21 AM
    Whether you noticed and corrected this problem
    In the doc url "\\"(double slash) is used for specifying the path and in your screen shot it is"\" (single slash)


  • 22.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 09:22 AM
    Also try by giving ip address instead of server name.. 


  • 23.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 09:33 AM
    I've started new CASE to Symantec Support. And we wait results. :-)


  • 24.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 09:38 AM
    PLease post your case id as well.

    Aniket


  • 25.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 09:50 AM
    One more thing
    While entring user name wheter you enterd as computername\username, where computername is the name of the computer
    where the UNC share resides.
    If no try it

     


  • 26.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 09:55 AM

    I'm useing Domain accountfor connect to this share because I have 8 Distribution points.



  • 27.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 10:04 AM
    Then you give the use name like this domain name\user name. Also add this user to local admin group of the server were the server resides  


  • 28.  RE: Problem with LUA 2.2.2

    Posted Oct 28, 2009 11:05 AM
    291-844-269


  • 29.  RE: Problem with LUA 2.2.2

    Posted Oct 29, 2009 03:15 AM
    Yes. This user has admin rights on these servers.


  • 30.  RE: Problem with LUA 2.2.2

    Posted Oct 29, 2009 04:00 AM

    Share ore folder in this Server itself and try to host LUA. If it is success something problem is with that remote folder if fails problem is with your configuration

     


  • 31.  RE: Problem with LUA 2.2.2

    Posted Oct 29, 2009 04:30 AM
    I can connect to this share from LUA server.


  • 32.  RE: Problem with LUA 2.2.2

    Posted Oct 29, 2009 04:57 AM
    IN Main LU server go to start--->run
    give \\<your share folder> and see whether it is accessible.
    Also assure you are able to resolve that testserver name to IP 


  • 33.  RE: Problem with LUA 2.2.2

    Posted Oct 30, 2009 08:05 AM
    Can you get update about this CASE?


  • 34.  RE: Problem with LUA 2.2.2

    Posted Oct 30, 2009 08:54 AM
    Hi,

    I think the CASE id is incorrect.