static report creation date and time since moving to IIS8

Avatar
Leon Kammer
  • updated
  • Answered
I have been using WLE for a while, we have just upgraded to IIS8 on Windows Server 2012 from IIS7 (2008) and have noticed something fairly peculiar...
The report creation date is static at 12th November 2011 from when we moved over to WS2012, anyone had similar issues?

I have checked the date and time on the servers within the web cluster, updated to WLE 8.2, none of them are using the time.windows service and both are reporting the correct time and date on ILO , so I am at a loss to what is going on here.
7.8 8.2 windows server 2012 iis8 report creation time weblogexpert
Replies 12
Avatar
0
Michael
You should check how the report are updated and information on what log range is included in the databases. If you use the built-in scheduler to update the reports, you should check the schedule log. You can also try to run the analysis manually to check if the reports are updated in this case.
Avatar
0
Leon Kammer
Hi Michael,

I use the professional edition.
Currently a VM installation of 2012 is used for report creation, the inbuilt scheduler is used for the report creation.

The IIS logs are archived to the VM running WLE on the 1st of every month at 09:00, after the MTD reports are processed (beginning at 03:00), the report is sent via email as a PDF

Both of the reports display the same static date at midnight, whether I use the scheduler or manually create the reports.
I have tried to manually run a report, and the same date and time is displayed on the report when run manually.

I have set the time server, turned it off, reset the time, after uninstalling and re-installing WLE, it displays today's date, but still midnight...

Perplexed.

Cheers

Leon
Avatar
0
Michael
It's quite strange - the time shown as "Generate on" should be just the current computer time.

Is the time range shown in the report correct? And what is the time shown in the PDF report file properties ("Created" and "Modified")?
Avatar
0
Leon Kammer
Hi Michael,

This is the strange thing, the time range is correct.
It's just the "generated on" time and date that is off.

Cheers

Leon
Avatar
0
Leon Kammer


This is the report from last night before the re-installation.
Avatar
0
Michael
Could you check what creation and modification time is shown in the PDF file properties? You can view it in File > Properties in Adobe Reader,

Could you also check what time is shown if you create HTML reports?
Avatar
0
Leon Kammer
Hi Michael,

The PDF Creation Properties are as follows (from the explorer document/properties)
Creation date: 05/12/2013 01:05
Modification Date: 05/12/2013 01:05
Accessed Date: 05/12/2013 01:05

However, the PDF Complete Document properties are as follows:
Created: 2012/11/15 01:00:00
Modified: 2012/11/15 01:00:00
Application: wPDF by wpdfCubed Gmbh

What's going on here?

I created a HTML report at the same time, this is showing the creation date as 15th November 2012 00:00 also

I have double checked the date and time on ILO, the BIOS and the Windows System, everything seems to be ok there.
Avatar
1
Michael
It seems that for some reason the program gets incorrect date and time from Windows, so it uses it when creates reports. We have never received information on some problems before.

Maybe it is related to the way drivers in the virtual machine affect the way Windows works. It is interesting if other software works correctly, as such problem should also affect other tools.

BTW what virtualization software do you use?
Avatar
0
Leon Kammer
Hi Michael,

Windows HyperV is used for virtualisation.

I will try to install WLE on a separate workstation running Windows 8.1 and see if that works.

Cheers

Leon
Avatar
0
Leon Kammer
Hi Michael.

Moving the WLE installation to another machine worked and the creation date for both the PDF and the HTML reports is now displayed correctly.

I will look into the issue from my end and try to diagnose the error, could be a permissions issue, but I am not 100% certain.
I will move the installation to the parent OS and see if that helps, else I will have to run this from a dedicated workstation.

Cheers

Leon