Msg 6532, Level 16, State 49, Procedure clrsp_RetailPriceOnDate, Line 0
.NET Framework execution was aborted by escalation policy because of out of memory.
System.Threading.ThreadAbortException: Thread was being aborted.
System.Threading.ThreadAbortException:
at Data_SQLCLR.StoredProcedures.clrsp_RetailPriceOnDate(SqlInt32 iSQLsysid_Individual, SqlInt32 iSQLStore, SqlInt32 iSQLGroup, DateTime dtPriceDate, SqlInt32 iSQLInclude)
Msg 6532, Level 16, State 49, Procedure clrsp_RetailPriceOnDate, Line 0
.NET Framework execution was aborted by escalation policy because of out of memory.
Problem is that it is intermittent - runs fine several times(takes c 30 secs to run, returns 15k records), then fails, then runs ok, fails/runs/runs/fails etc... etc...
I have this problem occuring intermittently:When I try to add a package to the project, and click on the Packagepath button. I get a oledb error x080004005 (client unable toestablish connection)...After I click ok, and click on the Package path again 2 or 3 times,the error goes away and I get the list of packages displayed. Sometime I get an empty list box.Similar to this happens when I execute a package also. When I executeit 2nd or 3 rd time it works fine. The error happens only when I amtrying to connect to the serverdatabase. Once it is in the databaseI do not get any error message.This is what I have:I have sql 2005 installed.Microsoft SQL Server ManagementStudio9.00.1399.00Microsoft Analysis Services ClientTools2005.090.1399.00Microsoft Data Access Components(MDAC)2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)Thank you in advance!!!
When I try to add a package to the project, and click on the Package path button. I get a oledb error x080004005 (client unable to establish connection)...
After I click ok, and click on the Package path again 2 or 3 times, the error goes away and I get the list of packages displayed. Some time I get an empty list box.
Similar to this happens when I execute a package also. When I execute it 2nd or 3 rd time it works fine. The error happens only when I am trying to connect to the serverdatabase. Once it is in the database I do not get any error message.
This is what I have:
I have sql 2005 installed. Microsoft SQL Server Management Studio 9.00.1399.00 Microsoft Analysis Services Client Tools 2005.090.1399.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
I have a classic ASP app that loops through a record set and calls another query based on each record returned. Something like:
sSql = User Query
rsUser = conn.execute(sSql)
do while not rsUser.eof sSql = Select [Type] From [User Types Display] Where UserId = rsUser(€œUserid€?) rsType = conn.execute(sSql) €˜ Put information into HTML table rsType.Close rsUser.MoveNext loop
In general, at around 3575-4000 loops, the system kicks back :
Microsoft OLE DB Provider for SQL Server error '80004005' [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. UserList.asp Line 300
I get no error message in the SQL Server Logs (according to the server, nothing happened), just this message on my ASP page. This happens about 90% of the time. 5% it runs completely, the other 5% bombs after 1-100 loops.
This only started happening when we took our app from a local Server 2000/SQL 2000 setup to separate Server 2003/SQL 2005 setup.
In SQL Profiler I see the loops hitting with only two reads per batch (TCP/IP). This seems very low compared to named pipes (when in a local server configuration) reads of 15-30 reads per batch.
I know it is not a hardware issue; this behavior is observed in both our test and production environments. All of our other ASP page queries work fine, just the 2 or 3 of hundreds that loop like above. cause the error.
Client Details (as best I could):
Connection String (in .inc file): conn.Open "Provider=SQLOLEDB;Network=DBMSSOCN;Data Source=10.0.1.100;Initial Catalog=€™TestDB';User ID='XXXX';Password='XXXX'"
The Client is Remote to the SQL machine and connects through TCP/IP only.
I force no encryption on the back and forth between the servers.
Server Details: SQL Server 2005 Standard with SP1
Only Named Pipes and TCP/IP are enabled
I think this is all the info relative to my issue. Thank you so much for any help,Smith
I'm getting an intermittent error 'DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER' when attempting to connect to an Access mdb. We have a weekly package that fails almost every other week. The package uses a FileSystem task to copy an Access mdb which we use as a template. It has a single table structure which is empty. The FileSystem copy task creates the 'clone' in a different folder with a new file name. The new file name has the current date embedded in it. The next task is a DataFlow task which fills the single Access table with data. It uses an OLE_DB connection to the Access mdb. Since the destination mdb is created at runtime in the FileSystem task, I have set the DelayValidation = True for the DataFlow task. The package is called from a 'master' package via an Execute Package Task. The master package is launched from a web application. Interestingly, when I use the 'restart from checkpoint' feature it restarts the package at the DataFlow task and runs it successfully. I have used the 'restart from checkpoint' after each failure and it has always worked. When I try to isolate the problem in a test package I am unable to reproduce the error. Our SqlServer version is Enterprise Edition (64-bit) with SP2.
Anyone have a similar experience? Thanks in advance.
We have a SQL 2005 clustered server (Microsoft Cluster Services) that is queried from 4 IIS6 Windows Server 2003 frontends. Each frontend runs both classic ASP apps connection with SQL Server ODBC and .NET2 apps connecting with System.Data.SqlClient. Ocassionaly we get a string of errors/timeouts opening a connection lasting maybe 2 minutes.
One the classic ASP apps we log one of these two errors:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation
or
Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC SQL Server Driver]Timeout expired on the ADODB.Connection.Open On the .NET2 apps we log Message Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
StackTrace at
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at System.Web.SessionState.SqlSessionStateStore.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo)
I'm in the process of writing a fairly complex SSIS package that reads csv files and goes on to load the content into a SQL Server 2005 database.
I am testing the package by executing it from within a Nant script. My test process resets the data in the target database and then loads data from a known set of test data files. Because it's scripted I can be sure that SSIS is being asked to do the same thing, every time in a consistent way.
When I execute the package I frequently (although not always) get an error message dialog mid-ececution that reads:
Code Snippet
Microsoft Visual c++ Runtime Library
Runtime error!
Program: C...
The application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
When I click OK the VS Just-In-Time debugger tells me about an unhandled win32 exception in DTExec.exe [4696] and asks me if I wish to debug (which I do not).
No error is reported by SSIS itself, it literally just stops in its tracks.
I will appreciate any help that can be offered here
I am trying to generate a SQL CLR stored procedure and i have done it too. Now the next step is to convert that *.dll file in to assembly. I am getting erro that. My server Database is on the LAN, not on my PC.
Here is the code which i have tried to register an assembly...
/* CREATE ASSEMBLY MyAssembly FROM 'C:Documents and SettingsAdministrator.ORC80My DocumentsVisual Studio 2005ProjectsMyDB1MyDB1inDebugMyDB1.dll'
WITH PERMISSION_SET=SAFE
GO */
and here is the error that i am getting...
/* Msg 6585, Level 16, State 1, Line 1
Could not impersonate the client during assembly file operation. */
Help,I am running a pass through query to oracle from SQL server 2000 asfollows;select * from openquery(nbsp, 'select * from FND_FLEX_VALUES')I have run this query through both DTS and the query analyzer and getthe foloowing error;Server: Msg 7357, Level 16, State 2, Line 3Could not process object 'select * from FND_FLEX_VALUES'. The OLE DBprovider 'MSDASQL' indicates that the object has no columns.OLE DB error trace [Non-interface error: OLE DB provider unable toprocess object, since the object has no columnsProviderName='MSDASQL',Query=select * from FND_FLEX_VALUES'].The really strange thing is, I'll get this error the first time Iexecute the query but if I execute it immeadiatley after it will runfine.Any help would be most appreciated!Cheers
We are experiencing intermittent authentication errors "Error: 18456, Severity: 14, State: 10" on a customer's production server. This is a new server that has just been rolled out in the past several months. Rebooting the server appears to make the problem go away. We are using SQL authentication from a separate server that is running IIS. The application always uses the same username and password to connect.
Server info:
select @@version Microsoft SQL Server 2005 - 9.00.2047.00 (X64) Apr 14 2006 01:11:53 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
select @@version SP1
Sample error from SQL Server errorlog:
Date 7/7/2006 10:53:24 AM Log SQL Server (Archive #2 - 7/7/2006 12:20:00 PM) Source Logon Message Error: 18456, Severity: 14, State: 10.
MSDN (http://msdn2.microsoft.com/en-us/library/ms366351.aspx) lists various states for this error message but 10 is not included, and it says "Other error states exist and signify an unexpected internal processing error."
Note: This was not a case of a transient error that occurs only when SQL Server is starting up - these errors occurred at a variety of times, two months after the server was last rebooted / SQL Server last restarted.
I have a VB 2003 .NET application that I wrote for a customer that connects to a named instance of SQL 2000. Until recently it has been working fine. Lately the program either pops a timeout failure within a few seconds or a general network error. I've increased the connection timeout settings to 90 seconds but the error still pops within a few seconds. I'm thinking something has changed in the environment that prevents a clean connection to the named instance of SQL server.
How should this issue be troubleshoot to determine the problem and what areas need to be looked at?
Using the Microsoft Patterns and Practices "Object Builder" (Dependency Injection/Builder library), I wrote an SQL CLR Stored Procedure (using VS 2005 Professional).
All compiles and deploys ok (to SQL Server 2005 Express).
However, at run-time, I get the following error upon a "BuilderContext" object's instantiation: {"Attempted to perform an operation that was forbidden by the CLR host."}
Thoughts on how to get ObjectBuilder working in the SQLCLR?
Thanks!
Andy
(posted below is the sample code...with the run-time exception occuring on the ...BuilderContext cxt = new ... call)
Microsoft.Practices.ObjectBuilder.BuilderStrategyChain chain = new Microsoft.Practices.ObjectBuilder.BuilderStrategyChain();
Microsoft.Practices.ObjectBuilder.Locator locator1 = new Microsoft.Practices.ObjectBuilder.Locator(null);
// Get error when new'ing BuilderContext: "Attempted to perform an operation that was forbidden by the CLR host." Microsoft.Practices.ObjectBuilder.BuilderContext cxt = new Microsoft.Practices.ObjectBuilder.BuilderContext(chain, locator1, null);
The VB code was complied into a DLL called totalmem.dll and call following TSQL to map it into a SQL function:
create assembly totalmem from '!WORKINGDIR! otalmem.dll'
WITH PERMISSION_SET=UNSAFE
go
create function fnGetTotalMem()
returns int
as external name totalmem.SqlClrVB.GetTotalPhysicalMemory
go
When I call this function, it returned following error:
select dbo.fnGetTotalMem()
Msg 6522, Level 16, State 2, Line 0
A .NET Framework error occurred during execution of user defined routine or aggregate 'fnGetTotalMem':
System.IO.FileNotFoundException: Could not load file or assembly 'System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException:
at Microsoft.VisualBasic.MyServices.Internal.ContextValue`1.get_Value()
at My.MyProject.ThreadSafeObjectProvider`1.get_GetInstance()
at SqlClrVB.GetTotalPhysicalMemory()
.
Anyone knows why I'm hitting this error? I didn't reference any System.Web interface why it needs to load System.Web assembly? The same code runs OK if I compile it as a separate VB application out side of SQL Server 2005.
I receive an error message when I try to Push data that the table is not tracked. However, when I try to turn on the tracking option it gives me an error that the table is a multi query table and therefore cannot be tracked. Here is my code to Pull the table.
string TPDAPull = string.Format("SELECT Table1.Field1,Table1.Field2, Table1.Field3, Table1.Field4, from Table1 Left Join Table2 on Table1.Field1 =Table2.Field1 WHERE Table2.Field12='{0}'", this.FindWorker(var));
This table does not have a primary key. I was wondering what can I do in this situation? I do not want to Pull the whole table. Any suggestions would be greatly appreciated. I am working in VS 2005, NCF2.0, C#, WM5.0.
I am trying to execute a SSIS package from a client through BIDS, but when I start BIDS, I am getting the error -
SqlWb.exe : Application error - The instruction at "0X77D...." referenced memory at "0X00000002". The memory could bot be "read". Click on OK to terminate the program. Click on CANCEL to terminate the program.
Please help.
Other information:
I have tried running the package on the server and it executes properly. I really dont know why this is a problem with the SQL Server clients alone. I have also tried googling around and could not find any resolution. Can anyone point me to the right direction please!!!
I am getting error 8645 on a two processor 1GB RAM machine with SQL server 7.0 svcpack 1 on Windows NT svcpack 4. It has a 4GB db which is used by a VB. application running on another server. Initially I left the memory setting to dynamic, getting error 8645 when more users try to access the server. Upon lot of complains I changed the memory configuration and fixed it to 800MB, other application running on the server is Seagate backupexec but the problem exists even before this application. I stopped the service just to make sure if problem occurs because of backup software. Server is completely dedicated SQL server. Number of users are set to 400. I can see average 200 connections every day but active connections are almost 20. When error pops up in SQL agent display log, users complain about screen freezing up and cannot do anything. Machine of this size should be able to handle that many users without any glitch. Page file size is 1.5GB.
After careful examination I made following changes on SQL Server
1. Configured to use "Boost SQL Server priority on Windows NT" 2. Configured to use "Use NT fibers" 3. Dropped number of connections from 500 to 400. 4. Changed memory option back to dynamic allocation.
After these options changed there was no problem for couple of days and users were happy that not a single downtime occurs. But this morning it started to acting up again, it does not show any error message in SQL server error log but in SQL agent error log. My questions are: What areas I need to look into to improve performance and to avoid these memory errors? Why these messages appearing in SQL Agent error log? Should I apply service pack 5 on NT and service pack 2 on SQL server? Do I need to increase RAM.
I will really appreciate if you address this problem on priority.
I use linkedserver to get data from Oracle, but sometimes I get the error below:
Server: Msg 7399, Level 16, State 1, Procedure GetDataFromERP, Line 21 OLE DB provider 'OraOLEDB.Oracle' reported an error. 2006-02-09 [OLE/DB provider returned message: ] [OLE/DB provider returned message: ROW-00001: Cannot allocate memory] OLE DB error trace [OLE/DB Provider 'OraOLEDB.Oracle' ICommandText::Execute returned 0x80004005: ].
I think maybe it is because the data is very large. How do I solve this problem?
I'm trying to generate a very large report. My server's got 32 gigs of memory though, so memory shouldn't be an issue. However, when I try to generate my report, I get the following outofmemory error message in the error log on the server:
The w3wp.exe process maxes out at ~1,250 MB. I imagine I just have to change a setting somewhere to allow this to grow beyond that, but I can't seem to find that setting. What do I have to do??
I have log shipping setup to 2 different servers. Every once in a while I get the
Server: Msg 3201, Level 16, State 1, Line 1 Cannot open backup device 'E:fac.dat'. Device error or device off-line. See the SQL Server error log for more details. Server: Msg 3013, Level 16, State 1, Line 1 Backup or restore operation terminating abnormally.
Checked MSDN which said it was a permissions error, which isn't right, because the same account works for this db and several others all the time. Anyone else seen this?
I've a SQL server that intermittently restarts itself mostly during. Its a SQL Server 6.5 SP4 running NT 4.0 SP6. It really has no rhyme or reason to it happening. The are no indications in either the SQL or the Nt events logs. Has anyone heard of this?
We recently migrated a SQL 2000 DB to SQL Server 2005 SP2. We have a VB 6 executable that uses the SQL Server 2005 DB. Immediately we began getting intermittent errors when trying to run a Stored Proc on SQL 2005 DB. The two errors we see are:
Timeout expired
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
If you immediately try to run the same query, it usually will work. The queries are random and so are the errors. I have gotten the time out error in Server Management Studio a couple of times.
In the VB 6 App we are using MDAC 2.81. Her is the connection string: Provider=SQLOLEDB.1;User ID=user;password=password;Initial Catalog=OASIS;Data Source=servername, portnumber
We added the port number to the DataSource in an attempt to troublshoot the issue, but it made no difference.
We have run sysinternals Process Monitor on a PC with the app running and we saw NAME NOT FOUND Results for Query Open actions for these DLLS: C:Program FilesOASISCLUSAPI.DLL C:Program FilesOASISRESUTILS.DLL C:Program FilesOASIStdsapi.dll
C:Program FilesOASIS is the application path. Of course, they are not in the application path but they are in C:WindowsSystem32. They do not seem to be registered.
Here is an example of the code we use in a class to run a SP:
Public Function FetchPostings() As ADODB.Recordset Dim cmFetch As ADODB.Command
On Error GoTo HandleError Set cmFetch = New ADODB.Command With cmFetch .Name = "FetchObligations" .ActiveConnection = gobjSecurity.Connection 'This is a connection string not a connection object .CommandText = "spClaimFetchObligations" .CommandType = adCmdStoredProc .Parameters.Append .CreateParameter("ClaimID", adInteger, adParamInput, , mlngClaimID) Set FetchObligations = .Execute End With
ExitSub: Set cmFetch = Nothing Exit Function
HandleError: gobjError.HandleError Err.Number, Err.Description, App.EXEName, "clsClaim", "FetchObligations", gobjSecurity.UserID Resume ExitSub End Function
I have VS 2005 and SQL CE 3.0. I sometimes get the a FileNotFoundException when I first use ExecuteReader. I believe this is because a dll has not been copied across because if I restart the emulator I can get it to work again.
Do I need to add a cab file/dll to my project to stop this happening?
I have developed a report that pulls its data from an SSAS cube. The report is grouped on Fields!FacilityName. On each "page" of the report, I have information for the displayed facility.
At the top of each page in my report I have a textbox whose value is =Fields!FacilityName. Further down on the report I have another text box whose value is set exactly the same. When I preview the report, I always have a value in the upper box, but only sometimes have a value in the lower box. If I change the value in the lower box to just a text string, it will always display, but when I put in the actual field reference it does not. It always doesn't display for the same facility names. Remember, the upper textbox on the form always displays 100% of the time.
I have a Dundas chart in the middle of the page on the report between these textboxes, but another field that pulls parameters and even a matrix all render correctly below that chart.
They both have the same parent according to the properties. I have even copied and pasted the working textbox further down the screen, with no improvement. When I changed the value of the textbox to "=cstr(len(Fields!FacilityName))", on the pages when it wants to be blank, it reads 0, and on other pages it shows a larger number. But the other textbox on the screen will always properly show the FacilityName.
I have also tried changing the name of the textbox, settings output to YES instead of Auto. If I slide the non-working textbox up to the top of the page and the working textbox down to the bottom area of the page, the bevavior switches.
Does anybody know of rendering issues with textboxes showing the same infomation?
We are using HTTPS anonymous merge subscriptions....
Sometimes when trying to synchonise, we will get the following error messages returned to the subscriber....
The upload message to be sent to Publisher '**thewebserver**' is being generated The merge process is using Exchange ID '0F65CFCB-AF17-47DC-8D98-493A44C243E0' for this web synchronization session. The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable. The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable. The Merge Agent received the following error status and message from the Internet Information Services (IIS) server during Web synchronization: [401 :'Unauthorized']. When troubleshooting, ensure that the Web synchronization settings for the subscription are correct, and increase the internet timeout setting at the Subscriber and the connection timeout at the Web server.
If I then go to a web brower, put in the HTTPS address, it brings up the logon dialog - I put in the admin username and password to confirm the connection and that's fine.
We try and synchronise again, and this time it works - it's as though I have 'woken' it up again and it's happy to play.
Is increasing the timeouts as suggested by the error message the way to go ? If so, where does one set the 'internet timeout setting at the subscriber', and the 'connection timeout at the webserver' ?
I currently run a nightly replication from a windows server 2003 machine with sql server 2000 sp3 to a windows 2003 server machine with sql server 2005 sp1. I run a snapshot replication as merge is not supported from 2000 to 2005.
2 out 5 snapshots weekly fail with the following error:
2006-08-09 17:00:06.97 Message Code: 10054 2006-08-09 17:00:06.97 2006-08-09 17:00:06.97 [0%] The replication agent had encountered an exception. 2006-08-09 17:00:06.97 Source: Replication 2006-08-09 17:00:06.97 Exception Type: Microsoft.SqlServer.Replication.ConnectionFailureException 2006-08-09 17:00:06.97 Exception Message: TCP Provider: An existing connection was forcibly closed by the remote host.
I have setup the sql server 2005 agent service to automatic with a 'log on as' domain admin account. The sql server agent on the 2000 machine uses the local system account.
I'm having an issue with what appears to be SQL Server 2005 deciding to randomly ignore new connections.
I currently have two virtual servers - one running just SQL Server 2005, the other running Reporting Services, Windows Sharepoint Services and Team Foundation Server.
For 3 weeks, it was all working perfectly, then on Wednesday night the server (and both Virtual Servers) was rebooted after installing the latest updates for Windows. Since then, I've had this issue.
It will work fine for a while, then it'll start throwing loads of Errors and Warnings into the Event Log, all along the lines of unable to connect to the database. The Reporting Services Configuration utility throws up the same problem. Then randomly, it'll start working again.
If anyone has any ideas, they would be much appreciated as this is driving me crazy!
I have gotten two 614 error messages over the past two weeks. I also have a known memory leak problem on my production server. After I have identified the data on the page, I have gone back to requery that page and have not had a problem. I am unable to run checkdb on the db, because it is to big, and I am 24x7. My question/assumption is, the data on this page gets loaded into cache, and because of the memory leaks I am getting glitches like this, has anybody out there, had this type of problem?
From BOL Error 614 is as follows:
Message Text A row on page %Id was accessed that has an illegal length of %d in database `%.*s`.
Explanation This error occurs when an attempt is made to access a row on a page and the actual length of the row is greater than expected. The error indicates that there is a structural problem on the database page accessed during a read or write operation, and it involves a specific row from that page. This structural problem can occur as a result of the following: ·Hardware problem related to but not limited to the hard drive, controller, or the controller`s implementation of write caching ·A structural problem determined when loading a database dump; it may indicate a integrity problem with the database dump file
My company has a database that is throwing a weird error. We've tried reinstalling both the OS and the SQL instance, and the error still persists. We think this error might have to do with some .NET code we've written to run on the box, but I cannot find anything out on the internet about it. Here is the Enterprise Manager Error Log:
Insufficient memory available.. Error: 17803, Severity: 20, State: 4 Query Memory Manager: Grants=0 Waiting=0 Maximum=97638 Available=97638 Global Memory Objects: Resource=912 Locks=42 SQLCache=67 Replication=2 LockBytes=2 ServerGlobal=20 Xact=12 Dynamic Memory Manager: Stolen=2138 OS Reserved=1048 OS Committed=1026 OS In Use=1022 Query Plan=1777 Optimizer=0 General=1066 Utilities=12 Connection=262 Procedure Cache: TotalProcs=488 TotalPages=1787 InUsePages=542 Buffer Counts: Commited=5168 Target=131072 Hashed=1917 InternalReservation=191 ExternalReservation=0 Min Free=128 Visible= 131072 Buffer Distribution: Stolen=351 Free=1113 Procedures=1787 Inram=0 Dirty=599 Kept=0 I/O=0, Latched=23, Other=1295 WARNING: Failed to reserve contiguous memory of Size= 65536.
I can find information if I do a Google search on "Error: 17803, Severity: 20" But as soon as I add "State: 4" to the query I get no results. Also, the articles that I have seen that give the same error messages (but different states) tend to deal with servers that have more than 4GB of memory. This server has ONLY 4GB of memory and in order to try and resolve this issue, we have limited the server to 1GB of physical memory to no avail.
