Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
1356 Views 5 Replies Latest reply: Jun 1, 2012 1:30 PM by cgrim RSS
ritch Newcomer 31 posts since
Feb 21, 2012
Currently Being Moderated

Mar 5, 2012 6:11 AM

Inconsistent Date Formats in Scans

Hi

 

Has anyone else come across the one, we have a 4 server model for scanning.

 

Enterprise Manager

API Server

Scan Engine

SQL Server

 

In the Enterprise Manager interface (and reporting) we are seeing

 

EngineNameJob IDStartStopDurationProgressStatusHosts FoundAction
GMSTPSSE01Test - Hi Non-Int Cred52012-1-3 11:34:152012-3-1 12:05:591392:31:44100%Complete 8


As you can see, the actual date should be in UK format and was actually 1st March 2012 (both start and stop), not sure where to start looking for this one!

 

Many thanks guys

 

Ritch

 

Message was edited by: ritch on 05/03/12 06:11:29 CST
  • Community Leader 479 posts since
    Nov 3, 2009
    Currently Being Moderated
    1. Mar 13, 2012 12:06 PM (in response to ritch)
    Re: Inconsistent Date Formats in Scans

    Hi Richard,

     

    I know the dates sometimes differ in the product.  Since we introduced the "use local time" for scans, the deveopers did it to be *consistent*.

     

    Please refer to the following KB Article, and let me know if it addresses your question(s).

     

    https://kc.mcafee.com/corporate/index?page=content&id=KB73641

     

    Thanks!
    Cathy

  • Community Leader 479 posts since
    Nov 3, 2009
    Currently Being Moderated
    3. Apr 26, 2012 6:53 PM (in response to ritch)
    Re: Inconsistent Date Formats in Scans

    Hi Ritch,

     

    Did you get a solution yet?

     

    If you're still working on it, let me know the SR # and I can look into it.

     

    Have a great day!
    Cathy

  • Community Leader 479 posts since
    Nov 3, 2009
    Currently Being Moderated
    5. Jun 1, 2012 1:30 PM (in response to ritch)
    Re: Inconsistent Date Formats in Scans

    Hi Richard,

     

    Looks like I got this SR anyway, and we're working on it now.

     

    As you can attest, the *solution* isn't a simple one.

     

    The problem is the Database Collation.  MVM only supports "SQL_Latin1_General_CP1_CI_AS".  So, anybody who might have a different collation would be well served to switch to a supported one earlier than later.

     

    So, sorry you didn't get that answer sooner!

     

    -Cathy

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

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