0

I'm investigating an issue on a Timer Job.

In the ULS log file I noticed below error message which is thrown by OWSTIMER.Exe.

"The following error occured while trying to read the ConnectionString property. Object reference not set to an instance of an object."

And idea about the problem?

1 Answer 1

0

If its your custom timer job & if you are using the on-premises version of SharePoint 2013 than please debug the code first as this can be an error of the code.

You can debug the timer job by attaching the same OWSTIMER.Exe from the visual studio.

3
  • In addition to this, perhaps a misplaced WFE join and detach may leave the configuration database in an inconsistent state.In such situations , the timer do complain about the same connectionString issue in the ULS
    – ArkoD
    Commented Apr 8, 2016 at 13:48
  • No, it's a built in timer jobs which manages alerts in SharePoint.
    – doganak
    Commented Apr 8, 2016 at 14:05
  • it simply means you have configuration error in SharePoint
    – Hardik
    Commented Apr 8, 2016 at 14:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.