Project Lite #2

Homepage discussions Free Templates Forum Project Lite #2

This topic contains 8 replies, has 2 voices, and was last updated by Profile photo of Michael Downing Michael Downing 12 months ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #24310
    Profile photo of kev del
    kev del
    Participant

    Hello
    I am having trouble getting project lite to work on SharePoint Foundation 2010 , the other one works fine but too complex for our users, I have attached the error, can you assist ? Regards Kev

    #24318
    Profile photo of Michael Downing
    Michael Downing
    Keymaster

    Hi Kev,

    Thanks for reaching out. Could you provide the correlation ID and time stamp to your SharePoint admin to see if they could see if they can narrow down the source of the error and we’d be more than happy to help in any way we can.

    Thanks,
    Michael

    #24317
    Profile photo of Michael Downing
    Michael Downing
    Keymaster

    Hi Kev,

    Meant to mention that when you provide them with the ID and time stamp to have them glance at the SharePoint ULS logs for that time frame.

    Thanks!
    Michael

    #24316
    Profile photo of kev del
    kev del
    Participant

    Hi
    If you open the attachment the correlation ID is there and also the date stamp

    #24314
    Profile photo of kev del
    kev del
    Participant

    Hi
    If you open the attachment the correlation ID is there and also the date stamp

    #24315
    Profile photo of kev del
    kev del
    Participant

    Hi
    If you open the attachment the correlation ID is there and also the date stamp

    #24313
    Profile photo of kev del
    kev del
    Participant

    This is what the ULS logs says but nothing to do with the attached correlation

    Timestamp : 30/09/2016 13:37:36
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 376
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : nasq
    Level : Medium
    Message : Entering monitored scope (Timer Job job-timer-locks)
    Correlation : 4342db0c-2a61-4480-9b7f-82e5c03ad5cf
    Context : {}

    Timestamp : 30/09/2016 13:37:36
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 376
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : b4ly
    Level : Medium
    Message : Leaving Monitored Scope (Timer Job job-timer-locks). Execution T
    ime=1.45828589946488
    Correlation : 4342db0c-2a61-4480-9b7f-82e5c03ad5cf
    Context : {}

    Timestamp : 30/09/2016 13:38:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 5456
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : nasq
    Level : Medium
    Message : Entering monitored scope (Timer Job job-email-delivery)
    Correlation : 8740983b-0819-4176-a8ac-b50d97beb16c
    Context : {}

    Timestamp : 30/09/2016 13:38:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 5456
    Area : SharePoint Foundation
    Category : E-Mail
    EventID : 6871
    Level : Information
    Message : The Incoming E-Mail service has completed a batch. The elapsed
    time was 00:00:00. The service processed 0 message(s) in total.
    Correlation : 8740983b-0819-4176-a8ac-b50d97beb16c
    Context : {}

    Timestamp : 30/09/2016 13:38:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 5456
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : b4ly
    Level : Medium
    Message : Leaving Monitored Scope (Timer Job job-email-delivery). Executio
    n Time=1.77676213038249
    Correlation : 8740983b-0819-4176-a8ac-b50d97beb16c
    Context : {}

    Timestamp : 30/09/2016 13:38:36
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 4836
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : nasq
    Level : Medium
    Message : Entering monitored scope (Timer Job job-timer-locks)
    Correlation : d9b4a4cf-d8d3-4669-9f45-d03ede33b23f
    Context : {}

    Timestamp : 30/09/2016 13:38:36
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 4836
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : b4ly
    Level : Medium
    Message : Leaving Monitored Scope (Timer Job job-timer-locks). Execution T
    ime=4.57963232757236
    Correlation : d9b4a4cf-d8d3-4669-9f45-d03ede33b23f
    Context : {}

    Timestamp : 30/09/2016 13:39:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 1104
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : nasq
    Level : Medium
    Message : Entering monitored scope (Timer Job job-email-delivery)
    Correlation : 388ff995-fe8f-48ce-87b9-bf357cbd3a67
    Context : {}

    Timestamp : 30/09/2016 13:39:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 1104
    Area : SharePoint Foundation
    Category : E-Mail
    EventID : 6871
    Level : Information
    Message : The Incoming E-Mail service has completed a batch. The elapsed
    time was 00:00:00. The service processed 0 message(s) in total.
    Correlation : 388ff995-fe8f-48ce-87b9-bf357cbd3a67
    Context : {}

    Timestamp : 30/09/2016 13:39:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 1104
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : b4ly
    Level : Medium
    Message : Leaving Monitored Scope (Timer Job job-email-delivery). Executio
    n Time=1.51192400151416
    Correlation : 388ff995-fe8f-48ce-87b9-bf357cbd3a67
    Context : {}

    Timestamp : 30/09/2016 13:39:36
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 5620
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : nasq
    Level : Medium
    Message : Entering monitored scope (Timer Job job-timer-locks)
    Correlation : b109ef36-9b80-42d3-a5b5-1239dfc816fd
    Context : {}

    Timestamp : 30/09/2016 13:39:36
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 5620
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : b4ly
    Level : Medium
    Message : Leaving Monitored Scope (Timer Job job-timer-locks). Execution T
    ime=1.38118112776903
    Correlation : b109ef36-9b80-42d3-a5b5-1239dfc816fd
    Context : {}

    Timestamp : 30/09/2016 13:40:00
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 376
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : nasq
    Level : Medium
    Message : Entering monitored scope (Timer Job job-diagnostics-event-log-pr
    ovider)
    Correlation : 8f02fa34-02d7-4712-963d-6121330cbe3a
    Context : {}

    Timestamp : 30/09/2016 13:40:00
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 376
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : b4ly
    Level : Medium
    Message : Leaving Monitored Scope (Timer Job job-diagnostics-event-log-pro
    vider). Execution Time=205.332521312066
    Correlation : 8f02fa34-02d7-4712-963d-6121330cbe3a
    Context : {}

    Timestamp : 30/09/2016 13:40:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 4836
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : nasq
    Level : Medium
    Message : Entering monitored scope (Timer Job job-email-delivery)
    Correlation : efd7c182-0bf1-4fa6-9f74-36f7736b28d3
    Context : {}

    Timestamp : 30/09/2016 13:40:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 4836
    Area : SharePoint Foundation
    Category : E-Mail
    EventID : 6871
    Level : Information
    Message : The Incoming E-Mail service has completed a batch. The elapsed
    time was 00:00:00. The service processed 0 message(s) in total.
    Correlation : efd7c182-0bf1-4fa6-9f74-36f7736b28d3
    Context : {}

    Timestamp : 30/09/2016 13:40:07
    Continuation : False
    Process : OWSTIMER.EXE (0x03D8)
    ThreadID : 4836
    Area : SharePoint Foundation
    Category : Monitoring
    EventID : b4ly
    Level : Medium
    Message : Leaving Monitored Scope (Timer Job job-email-delivery). Executio
    n Time=2.41706697359581
    Correlation : efd7c182-0bf1-4fa6-9f74-36f7736b28d3
    Context : {}

    #24312
    Profile photo of kev del
    kev del
    Participant

    Is anybody looking at this ?

    #24311
    Profile photo of Michael Downing
    Michael Downing
    Keymaster

    Unfortunately, the provided doesn’t really have much information where we are able to pin point anything that could be causing the error. Could you repeat the same process (produce error, capture timestamp and provided a complete verbose ULS log during the time? and email the log directly to support@brightwork.com?

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.