Error 823, Severity: 24

In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
Thanks
SalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default...b;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB)42147483647470470
min server memory (MB)02147483647256256
set working set size0111
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:

> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/default...b;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you should
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>

Error 823, Severity: 24

In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks

Error 823, Severity: 24

In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:

> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql

Error 8152: "String or binary data would be truncated"

I've been working with a sample database that the company is using for testing purposes. I (we) did not create the database - it was sent over to us by another company. I'm still a rank newbie at working with MS SQL Server, though I've worked with Access and MySQL in the past.
There is one table that contains bank information. At the moment, it is filled with information on imaginary (fake) banks. I need to change one record so that it contains the information of a real bank the company is using.
The problem is, I am unable to touch anything within this table. Any attempt to make changes gives me an error prompt that reads "String or binary data would be truncated". I ran the profiler, and it shows an Exception - Error: 8152 Severity 16 State 2.
Furthermore, I also get an error prompt stating: "The value you entered is not consistent with the data type or length of this column".
I've checked and checked again, and as far as I can tell, the value I entered _is_ consistent with the data type/length of the column.
I can make changes perfectly fine on the other tables in the database. Only this one table gives me trouble.
Could anyone shed some light on why exactly this is occurring, and why only on this one table?
Thank you :)
in order to shed some light, you would need to show us the schema and the statement you're issuing that's causing the failure.

also check if there are triggers on the table, if so, you should check out the code of those as well.|||Greg - I just had to say thanks. I've been trying to figure out my own similar problem for (way too many) hours. When you mentioned "triggers" a light went on and led me to the source of the problem - a field updated by a trigger was indeed too small. Now I can get some sleep. THANK-YOU!
Randy|||

Make sure that [Table] and ]TableX] are the same type and lenght.

I was getting the same error and I found out that the filed length was different in one table then another table that had the foreign key of the first table.

For example accountnumber field in the statement table was 400 but in statementx table it was set to 255. After I changed the accountnumber field in the statementx table to 400 the problem fixed.

|||

Hi Greg,

Have you ever seen this error occur on few (not all) records that been tried?

Here's the trigger code that get's called to archive the original data after it's been changed:

CREATE TRIGGER dbo.tuASSIGNMENT
ON dbo.ASSIGNMENT
AFTER UPDATE, DELETE AS

INSERT ASSIGNMENTHISTORY(assignmentID,
assignmentName,
assignmentDesc,
assigneeID,
assignDate,
dueDate,
completeDate,
crUser,
updUser,
updDate,
disposition)

SELECT assignmentID,
assignmentName,
assignmentDesc,
assigneeID,
assignDate,
dueDate,
completeDate,
crUser,
user,
getdate(),
disposition
FROM deleted

And here's the stored procedure code that works on all cases when executed directly on the SQL Server box, but blows up with the error occasionally when called with the same parameters from an Access 2002 form. All of the parmeter values are passed and read okay.

CREATE PROCEDURE dbo.updPROJECTtoNewDirector
(@.oldID int,
@.newID int,
@.assmtID int)

AS

UPDATE ASSIGNMENT
SET assigneeID = @.newID
WHERE assigneeID = @.oldID
AND assignmentID = @.assmtID

Thanks,

Mark

|||

In this case, it seems that Access 2002/VBA was having trouble with the trigger's behavior. When I diabled the trigger, all of the records that were showing up with the Error 8152 were suddenly updating ok. Bizarre behavior, but that's Access VBA for ya!

Happy New Year to all!

Error 8152: "String or binary data would be truncated"

I've been working with a sample database that the company is using for testing purposes. I (we) did not create the database - it was sent over to us by another company. I'm still a rank newbie at working with MS SQL Server, though I've worked with Access and MySQL in the past.
There is one table that contains bank information. At the moment, it is filled with information on imaginary (fake) banks. I need to change one record so that it contains the information of a real bank the company is using.
The problem is, I am unable to touch anything within this table. Any attempt to make changes gives me an error prompt that reads "String or binary data would be truncated". I ran the profiler, and it shows an Exception - Error: 8152 Severity 16 State 2.
Furthermore, I also get an error prompt stating: "The value you entered is not consistent with the data type or length of this column".
I've checked and checked again, and as far as I can tell, the value I entered _is_ consistent with the data type/length of the column.
I can make changes perfectly fine on the other tables in the database. Only this one table gives me trouble.
Could anyone shed some light on why exactly this is occurring, and why only on this one table?
Thank you :)in order to shed some light, you would need to show us the schema and the statement you're issuing that's causing the failure.

also check if there are triggers on the table, if so, you should check out the code of those as well.|||Greg - I just had to say thanks. I've been trying to figure out my own similar problem for (way too many) hours. When you mentioned "triggers" a light went on and led me to the source of the problem - a field updated by a trigger was indeed too small. Now I can get some sleep. THANK-YOU!
Randy|||

Make sure that [Table] and ]TableX] are the same type and lenght.

I was getting the same error and I found out that the filed length was different in one table then another table that had the foreign key of the first table.

For example accountnumber field in the statement table was 400 but in statementx table it was set to 255. After I changed the accountnumber field in the statementx table to 400 the problem fixed.

|||

Hi Greg,

Have you ever seen this error occur on few (not all) records that been tried?

Here's the trigger code that get's called to archive the original data after it's been changed:

CREATE TRIGGER dbo.tuASSIGNMENT
ON dbo.ASSIGNMENT
AFTER UPDATE, DELETE AS

INSERT ASSIGNMENTHISTORY(assignmentID,
assignmentName,
assignmentDesc,
assigneeID,
assignDate,
dueDate,
completeDate,
crUser,
updUser,
updDate,
disposition)

SELECT assignmentID,
assignmentName,
assignmentDesc,
assigneeID,
assignDate,
dueDate,
completeDate,
crUser,
user,
getdate(),
disposition
FROM deleted

And here's the stored procedure code that works on all cases when executed directly on the SQL Server box, but blows up with the error occasionally when called with the same parameters from an Access 2002 form. All of the parmeter values are passed and read okay.

CREATE PROCEDURE dbo.updPROJECTtoNewDirector
(@.oldID int,
@.newID int,
@.assmtID int)

AS

UPDATE ASSIGNMENT
SET assigneeID = @.newID
WHERE assigneeID = @.oldID
AND assignmentID = @.assmtID

Thanks,

Mark

|||

In this case, it seems that Access 2002/VBA was having trouble with the trigger's behavior. When I diabled the trigger, all of the records that were showing up with the Error 8152 were suddenly updating ok. Bizarre behavior, but that's Access VBA for ya!

Happy New Year to all!

Error 8152: "String or binary data would be truncated"

I've been working with a sample database that the company is using for testing purposes. I (we) did not create the database - it was sent over to us by another company. I'm still a rank newbie at working with MS SQL Server, though I've worked with Access and MySQL in the past.
There is one table that contains bank information. At the moment, it is filled with information on imaginary (fake) banks. I need to change one record so that it contains the information of a real bank the company is using.
The problem is, I am unable to touch anything within this table. Any attempt to make changes gives me an error prompt that reads "String or binary data would be truncated". I ran the profiler, and it shows an Exception - Error: 8152 Severity 16 State 2.
Furthermore, I also get an error prompt stating: "The value you entered is not consistent with the data type or length of this column".
I've checked and checked again, and as far as I can tell, the value I entered _is_ consistent with the data type/length of the column.
I can make changes perfectly fine on the other tables in the database. Only this one table gives me trouble.
Could anyone shed some light on why exactly this is occurring, and why only on this one table?
Thank you :)
in order to shed some light, you would need to show us the schema and the statement you're issuing that's causing the failure.

also check if there are triggers on the table, if so, you should check out the code of those as well.|||Greg - I just had to say thanks. I've been trying to figure out my own similar problem for (way too many) hours. When you mentioned "triggers" a light went on and led me to the source of the problem - a field updated by a trigger was indeed too small. Now I can get some sleep. THANK-YOU!
Randy|||

Make sure that [Table] and ]TableX] are the same type and lenght.

I was getting the same error and I found out that the filed length was different in one table then another table that had the foreign key of the first table.

For example accountnumber field in the statement table was 400 but in statementx table it was set to 255. After I changed the accountnumber field in the statementx table to 400 the problem fixed.

|||

Hi Greg,

Have you ever seen this error occur on few (not all) records that been tried?

Here's the trigger code that get's called to archive the original data after it's been changed:

CREATE TRIGGER dbo.tuASSIGNMENT
ON dbo.ASSIGNMENT
AFTER UPDATE, DELETE AS

INSERT ASSIGNMENTHISTORY(assignmentID,
assignmentName,
assignmentDesc,
assigneeID,
assignDate,
dueDate,
completeDate,
crUser,
updUser,
updDate,
disposition)

SELECT assignmentID,
assignmentName,
assignmentDesc,
assigneeID,
assignDate,
dueDate,
completeDate,
crUser,
user,
getdate(),
disposition
FROM deleted

And here's the stored procedure code that works on all cases when executed directly on the SQL Server box, but blows up with the error occasionally when called with the same parameters from an Access 2002 form. All of the parmeter values are passed and read okay.

CREATE PROCEDURE dbo.updPROJECTtoNewDirector
(@.oldID int,
@.newID int,
@.assmtID int)

AS

UPDATE ASSIGNMENT
SET assigneeID = @.newID
WHERE assigneeID = @.oldID
AND assignmentID = @.assmtID

Thanks,

Mark

|||

In this case, it seems that Access 2002/VBA was having trouble with the trigger's behavior. When I diabled the trigger, all of the records that were showing up with the Error 8152 were suddenly updating ok. Bizarre behavior, but that's Access VBA for ya!

Happy New Year to all!

Error 26 - SQL Connection Error

I was working on my office computer where I had Visual Web Developer Express Edition installed. I moved to my home office and installed Visual Web Developer and tried to run my application on my new computer and I get the following error message:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Please let me know if you need further information, any help would be appreciated.

Thanks.

Never mind, I just realized I had issues with my SQL Server....I reinstalled it and it all works fine now.

Thanks.

Error 22272: Cannot load the DLL xpstar.dll,...

Hi,

I'm running SQL Server 2000 on a Windows 2003 server.

About some days ago, my automatic backups stopped working, and whenever I try to edit or set up a new maintenance plan or export or import data through Enterprise Manager, I get the following error:

Error 22272: Cannot load the dll xptar.dll, or one of the dll's it references. Reason: 126 (the specified module could not be found.)

Any Idea why ?

Look for MSVCR71.DLL in SYSTEM32 directory whether it is present or not.

If no luck then you have to reinstall client tools.

|||Hi,

MSVCR71.DLL in SYSTEM32 directory is present ,. but still i am getting the same error what should i do ?

Please help
|||

That's only one of the files you'd want to look for. You would want to check what files xpstar.dll has dependencies on and search based on all the files. You can use a dependency tool to check the dependencies - try this one:

http://www.dependencywalker.com/

and point it to xpstar.dll

You may also want to try reapplying the last service pack you have installed - that will sometimes find and install the missing files, depending on what is missing.

-Sue

Error 22272: Cannot load the DLL xpstar.dll,...

Hi,

I'm running SQL Server 2000 on a Windows 2003 server.

About some days ago, my automatic backups stopped working, and whenever I try to edit or set up a new maintenance plan or export or import data through Enterprise Manager, I get the following error:

Error 22272: Cannot load the dll xptar.dll, or one of the dll's it references. Reason: 126 (the specified module could not be found.)

Any Idea why ?

Look for MSVCR71.DLL in SYSTEM32 directory whether it is present or not.

If no luck then you have to reinstall client tools.

|||Hi,

MSVCR71.DLL in SYSTEM32 directory is present ,. but still i am getting the same error what should i do ?

Please help
|||

That's only one of the files you'd want to look for. You would want to check what files xpstar.dll has dependencies on and search based on all the files. You can use a dependency tool to check the dependencies - try this one:

http://www.dependencywalker.com/

and point it to xpstar.dll

You may also want to try reapplying the last service pack you have installed - that will sometimes find and install the missing files, depending on what is missing.

-Sue

Error -2147467259 in Open Method

We have a SQL Server 2000 in a Windows 2003 Server, and we were working very well with the VB 6.0, but after an update in the Windows 2003, the Open method in ADO results in an error -2147467259 sometimes, but if we try the same code in a computer with another domain there are not any problem, some advice?I'd be inclined to suggest KB #168336 (http://support.microsoft.com/default.aspx?scid=kb;en-us;168336) as a first guess. Note that it is very important to retrieve ALL of the error objects returned, not just the first one!

-PatP

Error 213: Insert Error: Column name or values don't match table definition

Hello,
I have had the below procedure working and in use for some time now,
and suddently i started getting the below error:
"Eorror 213: Insert Error: Column name or number of supplied values
does not match table definition"
Thank you
CREATE PROCEDURE bat_LogData (
@.ComputerName varchar(50),
@.UserDomain varchar(50),
@.UserName varchar(50),
@.Date_Time datetime,
@.Message varchar(128),
@.SubMessage varchar(128),
@.ErrorText varchar(128),
@.ErrorCode nvarchar(15),
@.smsguid nvarchar(41),
@.locale int,
@.scriptver nvarchar(15),
@.wshver nvarchar(15)
)
AS
INSERT INTO LogonScript_data VALUES (
@.ComputerName,
@.UserName,
@.UserDomain,
GetDate(),
@.Date_Time,
@.Message,
@.SubMessage,
@.ErrorText,
@.ErrorCode,
@.smsguid,
@.locale,
@.scriptver,
@.wshver
)
SELECT @.@.IDENTITY AS 'MessageID'
GOrdixon5652@.hotmail.com wrote:

> Hello,
> I have had the below procedure working and in use for some time now,
> and suddently i started getting the below error:
> "Eorror 213: Insert Error: Column name or number of supplied values
> does not match table definition"
> Thank you
> CREATE PROCEDURE bat_LogData (
> @.ComputerName varchar(50),
> @.UserDomain varchar(50),
> @.UserName varchar(50),
> @.Date_Time datetime,
> @.Message varchar(128),
> @.SubMessage varchar(128),
> @.ErrorText varchar(128),
> @.ErrorCode nvarchar(15),
> @.smsguid nvarchar(41),
> @.locale int,
> @.scriptver nvarchar(15),
> @.wshver nvarchar(15)
> )
> AS
> INSERT INTO LogonScript_data VALUES (
> @.ComputerName,
> @.UserName,
> @.UserDomain,
> GetDate(),
> @.Date_Time,
> @.Message,
> @.SubMessage,
> @.ErrorText,
> @.ErrorCode,
> @.smsguid,
> @.locale,
> @.scriptver,
> @.wshver
> )
> SELECT @.@.IDENTITY AS 'MessageID'
> GO
I expect the table changed. Did you add or drop a column?
Always list the column names in an INSERT statement. Leaving them out
as you have done will inevitably make your code less reliable and
harder to debug. For example:
INSERT INTO LogonScript_data (
computername, username, userdomain, dt, date_time, message,
submessage,
errortext, errorcode, smsguid, locale, scriptver, wshver)
VALUES
(@.computername, @.username, @.userdomain, GETDATE(), @.date_time,
@.message,
@.submessage, @.errortext, @.errorcode, @.smsguid, @.locale, @.scriptver,
@.wshver
)
David Portas
SQL Server MVP
--

Error 208: Invalid object name 'sysextendedarticlesview'

hi,
for maintainance tasks (converting database from SQL_Latin to Latin_General)
we scripted a working merge replication and removed it with Enterprise
Manager (3 servers, 1 database, SQL 2000 SP3 on all 3 Servers).
Now, when trying to reinstall the replication (via script or EM), the
publication seems to be installed ok, snapshot passed without error. But the
setup of a new subscription fails with the following error message (raw
translation from german message):
Error 208: Invalid object name 'sysextendedarticlesview'.
(Original Errormessage: Server: Nachr.-Nr. 208, Schweregrad 16, Status 1,
Prozedur sp_addmergesubscription, Zeile 325
Ungltiger Objektname 'sysextendedarticlesview'.)
This view indeed cannot be found on one of the participating servers, but on
a different set of servers, where the same kind of replication is still
running, this view can't be found either.
Any help / suggestions would we appreciated.
TIA
Frank Linde
find a server/database that has this view on. In EM, right click on the view
and select copy. Then connect to the database you are having this problem
using EM. select tools, Query Analyzer and then hit ctrl v.
Then run this script. You may encounter more missing object problems but
they can be solved in the same way.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"A.Hoff" <z100@.gmx.org> wrote in message
news:cbk6a5$j6m$01$1@.news.t-online.com...
> hi,
> for maintainance tasks (converting database from SQL_Latin to
Latin_General)
> we scripted a working merge replication and removed it with Enterprise
> Manager (3 servers, 1 database, SQL 2000 SP3 on all 3 Servers).
> Now, when trying to reinstall the replication (via script or EM), the
> publication seems to be installed ok, snapshot passed without error. But
the
> setup of a new subscription fails with the following error message (raw
> translation from german message):
> Error 208: Invalid object name 'sysextendedarticlesview'.
> (Original Errormessage: Server: Nachr.-Nr. 208, Schweregrad 16, Status 1,
> Prozedur sp_addmergesubscription, Zeile 325
> Ungltiger Objektname 'sysextendedarticlesview'.)
> This view indeed cannot be found on one of the participating servers, but
on
> a different set of servers, where the same kind of replication is still
> running, this view can't be found either.
> Any help / suggestions would we appreciated.
> TIA
> Frank Linde
>