Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
479 Views 4 Replies Latest reply: Nov 13, 2013 9:08 AM by rmetzger RSS
sujitjha Newcomer 28 posts since
Jan 9, 2013
Currently Being Moderated

Oct 28, 2013 6:33 AM

Super Dat Issue

Hello there,

 

While installing Super Dat in a particular machine. I am getting below error.

 

Would any one help me...What & why is this.

Attachments:

Thanks,
Sujit Jha
  • wwarren McAfee SME 765 posts since
    Nov 3, 2009
    Currently Being Moderated
    1. Nov 11, 2013 11:26 AM (in response to sujitjha)
    Re: Super Dat Issue

    This was a package you created yourself using SDM 2.5, or one you downloaded from us?

    If the latter, I suggest retrieving the file again.

    If the former, you might want to try creating the package on another node.

  • Tristan Veteran 790 posts since
    Dec 8, 2009
    Currently Being Moderated
    3. Nov 13, 2013 6:19 AM (in response to sujitjha)
    Re: Super Dat Issue

    A few things you can try

     

    - Check your available free disk space

     

    - Make sure your temporary 'temp' folder isn't mapped to a network drive

     

    - Do a ram test. http://www.memtest.org/ is a simple way to do it. I had a similar issue when a single bit on a stick of ram was faulty. It was quite high up on the ram table (if that makes sense) as day to day use didn't hit it but a memory intensive job like unpacking and validating the SuperDAT would. The faulty bit of ram would generate a different checksum and the validation would fail.

  • rmetzger Champion 566 posts since
    Jan 4, 2005
    Currently Being Moderated
    4. Nov 13, 2013 9:08 AM (in response to sujitjha)
    Re: Super Dat Issue

    Sujit Jha wrote:

     

    I haven't created this package..it was downloaded from McAfee Security product download location.

    i had downloaded this again but it doesn't worked for me.

    Since you have downloaded again, I would suggest checking if %TMP% directory exists. As Tristan stated, the %TMP% folder should be local.

     

    Additionally, I would check the integrity of the downloaded file using SigCheck.exe. (from a cmd prompt)

    (see http://technet.microsoft.com/en-us/sysinternals/bb897441 )

    SigCheck.exe -accepteula -a -h -q "SDATxxxx.exe" (use whatever filename you have, within the quotes)

    If the file presents as unsigned or invalid, the file has been altered either during the download or on disk somehow.

     

    If the file is Signed, then the RAM issue mentioned by Tristan might be a good place to start. Again, make sure %TMP% (or %TEMP%) exists. Additionally, you might consider clearing the temporary space, ensuring that it is empty.

     

    Alternatively, attempt to extract the sdat manually to the directory you have downloaded (from a cmd prompt):

    "SDATxxxx.exe" /E

     

    Hopefully this is helpful.

    Ron Metzger

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 5 points
  • Helpful Answers - 3 points