Endpoint Protection

  • Private Community
 View Only
Back to discussions
Expand all | Collapse all

Failed to create a 32-bit Package Error Code:2

Migration User

Migration UserSep 28, 2010 01:08 AM

Can you prove us a screen shot of the error?
Migration User

Migration UserSep 28, 2010 10:27 AM

There was nothing included in your post. sandra
Migration User

Migration UserOct 14, 2010 10:19 AM

Any update did you tried the above tip

  • 1.  Failed to create a 32-bit Package Error Code:2

    Posted Sep 27, 2010 04:00 PM

    Hi all,

     

    I am testing out Symantec Endpoint Protection 11.0.6 MP1, I have it installed on a Windows Server 2008 R2 STD machine (64-bit, 4GB).

     

    After the installation, I could not logon to SEPM so I ran a repair using the installation disk, after the repair, I was able to login to SEPM.

     

    Then, I was trying to push the packages to the client using Migration and deployment Wizard, I chose my options and an error message comes up saying "Failed to create a 32-bit package for SEPT27.  Error Code: 2"

     

    Anyone has any ideas why it is happening? I tried to create a 64-bit package and the result is the same.

     

    Please advise. Thanks.



  • 2.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 27, 2010 05:18 PM

    I can find no information on 'Error code: 2'.  When you did your installation of the SEPM, were you logged in locally or via RDP?  If RDP, was it a console-equivalent connection (/admin switch)?

    If you run the Support Tool, does it return any errors or warnings?

    Support Tool: http://www.symantec.com/docs/TECH105414

    sandra



  • 3.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 27, 2010 06:34 PM

    If you try to export the packaged from within the console, what happens?

    To export a package using the console:

    Start -> SEPM -> Admin -> Install Packages - Right click on the desired OS version -> Hit Export - Select the options that goes better for

    your case and hit Ok

    And as Sandra well requested try to check the Support Tool

    Jb



  • 4.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 01:08 AM

    Can you prove us a screen shot of the error?



  • 5.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 01:20 AM

    I have read this some other blog it may work for you too..

     

    copy the SEP folder from the CD to a location on the target server, then selected 'Add new Install Package' and pointed to the SEP folder.

    After that the issue disappeared and able to create the client packages.



  • 6.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 10:24 AM

    @Sandra: I wasn't able to login at the first time (locally / RDP), it was okie after repair installation.

     

    I receive the following error message when I run the SEP Support Tool.



  • 7.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 10:27 AM

    There was nothing included in your post.

    sandra



  • 8.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 10:34 AM
      |   view attached

    @ Sandra.

    Here it is. Please click on the image to show the full image. Thanks.



  • 9.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 10:39 AM

    @ Jorge B.

    I am seeing no OS version that I can click onto under Start -> SEPM -> Admin -> Install Packages to export.



  • 10.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 10:41 AM

    @ AravindKM

     

    Here are the screenshots. Error1.jpg and Error2.jpg

     



  • 11.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 10:44 AM
      |   view attached

    @  Maheshroja

    Yes, you are correct.  After I copied the folder to the machine (Desktop) and actually selected the copied folder to deploy, the deployment went through without any problems.

    (Please see error3.jpg)

    Now the main problem is, after the successful deployment, I don't see the package runs on any of the 3 machines that I pushed out.  Please advice.  Thanks.



  • 12.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 10:46 AM

    "The version of this file is not compatible with the version of Windows you're running.  Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."

    As far as I know, the Support Tool tool should run on either 32-bit or 64-bit systems, as I have looked at the results from both 32- and 64-bit systems, and have never had to send a customer a separate executable.

    As the error message asks: What does your computer's System Information say?  What is your version of Windows?

    sandra



  • 13.  RE: Failed to create a 32-bit Package Error Code:2

    Broadcom Employee
    Posted Sep 28, 2010 11:35 AM

    run the dbvalidator on the sepm for presence of broken links if any,,



  • 14.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 01:41 PM

    I would check on the clients for the sep_inst.log. You can find this file by going to Start>Run type %temp% and click OK. This will open the temp directory where our install log is located. If you don't see the sep_inst.log in there this most likely indicates the installation never started on the clients.

    If there is an install log, please post it here as this will indicate why the installation never completed. You may also review the log yourself by searching for "value 3" without quotes in the log. Several lines above this should show why the install did not complete.



  • 15.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 02:47 PM

    Hi Kurt,

    I have 3 machines here and sep_inst.log only exists on the machine that I installed SEPM and I can't find "value 3" in sep_inst.log on the clients. 

     

    So why does the install package never start?

     

    Please advice.  Thanks.



  • 16.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Sep 28, 2010 05:02 PM

    Successful deployment only means the file is able to be copied to the remote machine.  As for why it is not installing, test using the install package locally.  If it still fails it will produce the installation log as noted above.  There may be a hint in the Windows Event Viewer as to why the installation failed to launch, so look there too.

    Something seems really broken if the SEP Support Tool can't even be run on the SEPM server.  See my previous comment.

    sandra



  • 17.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Oct 13, 2010 11:56 PM

    Copy that exported sep client package to the remote machine which you want to install .

    Go to add/remove Programs click on Add new Program-- CD or Floppy then browse for the package copied..click  I think this will help you.

    Same issue i have done..



  • 18.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Oct 14, 2010 10:19 AM

    Any update did you tried the above tip



  • 19.  RE: Failed to create a 32-bit Package Error Code:2
    Best Answer

    Posted Oct 15, 2010 11:38 AM

    Hey Maheshroja,

     

    ended up I removed 11.0.6 and re-installed 11.0.5, copy the sylink.xml from the server and paste it onto the client to have the client machines connected.

     

    At my client's location, only a few of the client machines can be deployed with the package for some reasons, I used the sylimk.xml method + find unmanaged computer under the default group to have all of them connected.

     

    More, I had to turn off the domain and network firewall on the AD server to have the client connect to the management console, any clue why?

     

    Thanks all.



  • 20.  RE: Failed to create a 32-bit Package Error Code:2

    Posted Oct 19, 2010 10:22 AM

    More, I had to turn off the domain and network firewall on the AD server to have the client connect to the management console, any clue why?

    Are there allowances for the communication ports in the firewall?

    This may be helpful:

    Which Communication Ports does Symantec Endpoint Protection 11.0 use?
    http://www.symantec.com/docs/TECH10241

    sandra