Apologize for the delay in sending this.

I tried to reproduce the problem in my local end by testing the "export to pdf" feature of WebScheduler from one of WebScheduler sample but my efforts were not successful - everything worked smoothly and the export result was accessed without any issues.

This probably caused by the data binded to WebScheduler, since the reported problem doesn't persist when test the export feature on WebScheduler sample file. Please switch to "Year" view and test the WebScheduler export to pdf feature. Is there any specific year which has the problem?
Try to test the export feature using Month view to determine which part of data that causing the problem.

Hi Yudi -

Thanks for the reply which helped us to move a step further in troubleshooting this issue. Below are the  steps undertaken and our findings :

1) We get rid of all the data binded to the webscheduler which inturn make the export PDF functionality   to work,which means it is definitely something with the binded data or how webscheduler is interpreting   data.

2) Strangely we notice some bizzare things with the exported PDF which you can also see in the attached exported PDF in the reply.

     a) We have set the webscheduler to only show time starting from   "07:00 AM - 11:00 PM" but if you          see the exported PDF it actually exported from "12:00 AM - 04:00 PM". It looks like it is some how            shifting the time to -7 hrs,might be a timezone shift ?

     b) We also believe that this might be the reason we are getting a "date error" for export since it might        be shifting the time on the color bars like it is doing with the header times.

3) Also the layout seems to be odd. It only shows 3 times horizontaly when there is space for more.

Hope we have provided all the information required to reproduce and get this issue fixed. Looking           forward for a prompt reply.

Thanks!

After checks Sample_ExportPDF_WebScheduler.pdf file (attached in Frank Gary's post on May 15, 2015), it seems that you are using WebScheduler with following configuration (please correct if I'm wrong).

• Timeline view is enabled.
• Timeline-StartTime is t0700.
• Timeline-EndTime is t2300
• SelectedTimelineViewMode is set to Day15Minutes

I managed to reproduce the reported problem in my local end by applying the above configuration to my WebScheduler sample. The detail of the problems are:

• Problem 1: Hour,minute and second parameters describe an Un-Representable Date Time.
  I found that this problem is related with the EndTime. Try to set the value of EndTime to any value but t2300. Problem 1 should no longer persist. Could you please confirm if you have the same result on your end?
  I have submitted problem 1 to WebScheduler development team. The report is filed under ASPNET-166.
• Problem 2: the exported PDF it actually exported from "12:00 AM - 04:00 PM". It looks like it is some how shifting the time to -7 hrs,might be a timezone shift ?
  I found that this problem is related with the SelectedTimelineViewMode. Try to set the value of SelectedTimelineViewMode to any value but Day15Minutes. Problem 2 should no longer persist. Could you please confirm if you have the same result on your end?
  I have submitted problem 1 to WebScheduler development team. The report is filed under ASPNET-167.

Look forward to hearing back from you.

Hi Yudi -

Thanks for the reply. The above suggested fixes do help us to resolve the problem but only partially. Firstly We can't have  SelectedTimeLineViewMode set for Hourly (since this is the only option other than Day15Minutes) due to bussiness requirement and secondly if you see in the attached exported pdf report the design is quite messed up and is very hard to interpret.

Hope the webscheduler development team will resolve these issues on priority and also will address the above mentioned issues.

Thanks