Comments on: Sharepoint and SQL Server error 18456 (Severity: 14, State: 16)

By: Sudhir Kesharwani

Sudhir Kesharwani — Thu, 04 Mar 2010 12:09:12 +0000

Guys,

Many thanks for such a useful post.

I had been struggling to find some resolution to this… and your post really helped me.

You are rocking…

Sudhir

By: Cindy

Cindy — Tue, 17 Nov 2009 15:51:12 +0000

One way to figure out which are the old jobs and which ones are valid for the new MOSS install:
run SCRIPT JOB AS..CREATE TO..NEW QUERY EDITOR WINDOW in SQL Server Management Studio. That way, you can see the script and which database a particular job is trying to access. Then you’ll know which jobs are legit and which you can delete.

By: Renata

Renata — Fri, 25 Sep 2009 08:17:29 +0000

Guys, that is what I was looking for! Excelent job, thanks.

By: Franklin

Franklin — Wed, 09 Sep 2009 19:02:04 +0000

Thanks, resolved my issue, thought I’d never get rid of that error!

By: Jason

Jason — Wed, 01 Jul 2009 16:41:23 +0000

Awesome find! Thanks a bunch!
William, make sure the SQLServer Agent service is started.

By: William

William — Fri, 26 Jun 2009 20:11:56 +0000

Have the same problem like Paul. There is no scheduled job to delete in SQLServer Agent.

Anyone can advise???

By: Reddy Kiran

Reddy Kiran — Mon, 01 Jun 2009 20:04:57 +0000

Thanks Jaap it worked, deleting “SharedServices_DB_job_deleteExpiredSessions” fixed the issue

By: Rick CAin

Rick CAin — Fri, 22 May 2009 13:53:03 +0000

Thank you! I had uninstalled-reinstalled MOSS twice, ran through the registry trying to find out why it kept generating errors like this. I love simple fixes like this.

By: Mai Omar

Mai Omar — Tue, 28 Oct 2008 12:08:55 +0000

thanks…. it worked here too

By: Santiago Aulestia

Santiago Aulestia — Mon, 25 Aug 2008 14:54:37 +0000

You did help me! I had this problem and I was not finding any reason why…
Well thanks to our “Delete SSP” process in MOSS!