Groups | Blog | Home
all groups > sql server notification services > august 2004 >

sql server notification services : Memory


Anthony Small
8/13/2004 12:26:17 AM
Hi
When building an application (using the modified samples batch files) I get
the following error:
----------------------
**** Create the application databases
Microsoft Notification Services Control Utility (Standard) (SP1) 2.0.3008.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
Creating instance
WorkInfoInstance
An error occurred when creating the instance stored procedures.
FailedStoredProcedure: NSCreateMainTables
SqlServerError: Source: .Net SqlClient Data Provider Number: 701 State: 1
Class: 17 Server: Message: There is insufficient system memory to run
this query. Procedure: NSPopulateTimeZoneTables Line Number: 1779
There is insufficient system memory to run this query.
Project : error PRJ0019: A tool returned an error code from "Performing
Makefile project actions"
-----------------------------

There is plenty of memory so this message refers to something else.
I've seen this error before and fixed it and think it's to do with
permissions but can't remember the solution now.
Can anyone help with the solution to this?
Thanks in advance.

Tony S.

Diane Larsen [MSFT]
8/18/2004 2:24:10 PM
Hi Tony,

Are you running Notification Services 2.0 SP1 against a SQL Server 2005
Beta? If so, that is not a supported configuration. If not, what version and
edition of SQL Server are you using?

Thanks,
Diane Larsen [MSFT]
Technical Writer
SQL Server User Education

This posting is provided "AS IS" with
no warranties, and confers no rights.
Use of included script samples are
subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.


[quoted text, click to view]

Anthony Small
8/18/2004 11:11:29 PM
Hi Diane,

I am not running the SQL Server 2005 beta.
I have since partly solved this problem.
I got the same error when building the app on 2 different machines each with
512MB ram.
Task Manager showed that I had sqlservr.exe running 3 times. I tried
connecting to SQL Server and got a shared memory error and then it occurred
to me that somehow MSDE might have been installed. Even though there was
plenty of memory when I looked at the memory settings for (local) it showed
0mb min and 4mb max. That was the problem. I changed it to dynamic and it
worked.

Tony S.

[quoted text, click to view]

Anthony Small
8/19/2004 8:53:08 AM
Clarification: The 'Memory Setting' was already dynamic, I increased the
maximum and it worked.


[quoted text, click to view]

Diane Larsen [MSFT]
8/19/2004 1:30:31 PM
Thanks for the information on the resolution.

--
Diane Larsen [MSFT]
Technical Writer
SQL Server User Education

This posting is provided "AS IS" with
no warranties, and confers no rights.
Use of included script samples are
subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.


[quoted text, click to view]

AddThis Social Bookmark Button