Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 High Availability (2005)
 Witness Server Stopped working

Author  Topic 

rikleo2001
Posting Yak Master

185 Posts

Posted - 2009-10-15 : 08:04:15
Hi

I have SQL Server 2005 SP2 on Windows 2003 with 4 GB memory and working as Witness server for 50 Databases from differant servers.

suddenly it stopped working. I can't logon to SSQL, I checked the services are running but I can't connect to instance, Login Handshake error come up, so I re-started the service and all backup and online.

Here is error detail.

009-10-14 06:30:01.62 spid55 Error: 701, Severity: 17, State: 123.
2009-10-14 06:30:01.62 spid55 There is insufficient system memory to run this query.
2009-10-14 06:30:01.86 Backup Log was backed up. Database: model, creation date(time): 2003/04/08(09:13:36), first LSN: 57:112:1, last LSN: 57:112:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\SQLdumps\MSSQLSERVER\Scheduled\model\model_tlog_200910140630.TRN'}). This is an informational message only. No user action is required.
2009-10-14 07:24:49.83 spid54 Error: 701, Severity: 17, State: 123.
2009-10-14 07:24:49.83 spid54 There is insufficient system memory to run this query.
2009-10-14 07:24:49.83 spid54 Error: 701, Severity: 17, State: 123.
2009-10-14 07:24:49.83 spid54 There is insufficient system memory to run this query.
2009-10-14 07:24:51.73 spid54 Error: 701, Severity: 17, State: 123.
2009-10-14 07:24:51.73 spid54 There is insufficient system memory to run this query.
2009-10-14 07:24:51.73 spid54 Error: 701, Severity: 17, State: 123.
2009-10-14 07:24:51.73 spid54 There is insufficient system memory to run this query.
2009-10-14 07:24:52.25 spid54 Error: 701, Severity: 17, State: 123.
2009-10-14 07:24:52.25 spid54 There is insufficient system memory to run this query.
2009-10-14 07:24:52.25 spid54 Error: 701, Severity: 17, State: 123.
2009-10-14 07:24:52.25 spid54 There is insufficient system memory to run this query.
2009-10-14 08:30:01.56 spid55 Error: 701, Severity: 17, State: 123.
2009-10-14 08:30:01.56 spid55 There is insufficient system memory to run this query.
2009-10-14 08:30:01.73 Backup Log was backed up. Database: model, creation date(time): 2003/04/08(09:13:36), first LSN: 57:112:1, last LSN: 57:112:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\SQLdumps\MSSQLSERVER\Scheduled\model\model_tlog_200910140830.TRN'}). This is an informational message only. No user action is required.
2009-10-14 10:30:01.18 spid55 Error: 701, Severity: 17, State: 123.
2009-10-14 10:30:01.18 spid55 There is insufficient system memory to run this query.
2009-10-14 10:30:01.72 Backup Log was backed up. Database: model, creation date(time): 2003/04/08(09:13:36), first LSN: 57:112:1, last LSN: 57:112:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\SQLdumps\MSSQLSERVER\Scheduled\model\model_tlog_200910141030.TRN'}). This is an informational message only. No user action is required.
2009-10-14 12:30:01.80 spid55 Error: 701, Severity: 17, State: 123.
2009-10-14 12:30:01.80 spid55 There is insufficient system memory to run this query.
2009-10-14 12:30:02.33 Backup Log was backed up. Database: model, creation date(time): 2003/04/08(09:13:36), first LSN: 57:112:1, last LSN: 57:112:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\SQLdumps\MSSQLSERVER\Scheduled\model\model_tlog_200910141230.TRN'}). This is an informational message only. No user action is required.
2009-10-14 14:30:02.24 spid55 Error: 701, Severity: 17, State: 123.
2009-10-14 14:30:02.24 spid55 There is insufficient system memory to run this query.
2009-10-14 14:30:02.60 Backup Log was backed up. Database: model, creation date(time): 2003/04/08(09:13:36), first LSN: 57:112:1, last LSN: 57:112:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\SQLdumps\MSSQLSERVER\Scheduled\model\model_tlog_200910141430.TRN'}). This is an informational message only. No user action is required.
2009-10-14 16:30:02.62 spid55 Error: 701, Severity: 17, State: 123.
2009-10-14 16:30:02.62 spid55 There is insufficient system memory to run this query.
2009-10-14 16:30:02.86 Backup Log was backed up. Database: model, creation date(time): 2003/04/08(09:13:36), first LSN: 57:112:1, last LSN: 57:112:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\SQLdumps\MSSQLSERVER\Scheduled\model\model_tlog_200910141630.TRN'}). This is an informational message only. No user action is required.
2009-10-14 18:30:03.53 spid55 Error: 701, Severity: 17, State: 123.
2009-10-14 18:30:03.53 spid55 There is insufficient system memory to run this query.
2009-10-14 18:30:03.67 Backup Log was backed up. Database: model, creation date(time): 2003/04/08(09:13:36), first LSN: 57:112:1, last LSN: 57:112:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\SQLdumps\MSSQLSERVER\Scheduled\model\model_tlog_200910141830.TRN'}). This is an informational message only. No user action is required.
2009-10-14 19:30:56.92 spid17s Error: 9650, Severity: 16, State: 36.
2009-10-14 19:30:56.92 spid17s A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error '8(error not found)'.
2009-10-14 19:30:56.93 spid17s Error: 1474, Severity: 16, State: 1.
2009-10-14 19:30:56.93 spid17s Database mirroring connection error 4 'An error occurred while sending data: '(null)'.' for 'TCP://xxxx.xx.z.com:5022'.
2009-10-14 19:30:56.93 spid17s Error: 17054, Severity: 16, State: 1.
2009-10-14 19:30:56.93 spid17s The current event was not reported to the Windows Events log. Operating system error = 8(error not found). You may need to clear the Windows Events log if it is full.
2009-10-14 19:31:53.97 spid27s Error: 9650, Severity: 16, State: 36.
2009-10-14 19:31:53.97 spid27s A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error '8(error not found)'.
2009-10-14 19:31:53.97 spid27s Error: 1474, Severity: 16, State: 1.
2009-10-14 19:31:53.97 spid27s Database mirroring connection error 4 'An error occurred while sending data: '(null)'.' for 'TCP://xxxx.xx.z.com:5022'.
2009-10-14 19:31:54.06 Logon Database Mirroring login attempt by user 'xxxx\$aaaaaa' failed with error: 'Connection handshake failed. The login 'xxxx\$aaaaaa' does not have CONNECT permission on the endpoint. State 91.'. [CLIENT: xx.xx.x.x.x]
2009-10-14 19:31:54.06 spid16s Error: 1474, Severity: 16, State: 1.


Any ideas how to get rid of this problem in future?

Many Thanks in advance.







SKR

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-10-15 : 13:26:30
Looks like you need to grant the SQL Server service account the "lock pages in memory" computer policy. There's a KB article on it, but I don't have time to look it up. Google search it.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

rikleo2001
Posting Yak Master

185 Posts

Posted - 2009-10-16 : 07:09:49
Hi
Thanks for that, but I already have service account configured for that.
Any further thoughts and recommendations please?
Thanks


SKR
Go to Top of Page

rikleo2001
Posting Yak Master

185 Posts

Posted - 2009-10-16 : 07:13:28
Sorry my Bad, was looking in differant server. Yes that was missing there. I configured it now. Hopefully it will resolve this issues. Many Thanks

SKR
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-10-16 : 12:19:23
You're welcome. It resolved it for us, hopefully it'll work out for you.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

leoc50
Yak Posting Veteran

54 Posts

Posted - 2010-11-15 : 19:58:58
quote:
Originally posted by tkizer

Looks like you need to grant the SQL Server service account the "lock pages in memory" computer policy. There's a KB article on it, but I don't have time to look it up. Google search it.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."



Sr. SQL server & Oracle
Go to Top of Page
   

- Advertisement -