ERROR: Subreport: msg

Showing posts with label msg. Show all posts

Thursday, March 22, 2012

Errror 8144

I get following error
Server: Msg 8144, Level 16, State 2, Procedure pPMEmployeeUpdate, Line 0
[Microsoft][ODBC SQL Server Driver][SQL Server]Procedure or function
pPMEmployeeUpdate has too many arguments specified.
Any Ideas Why can it appear?
Following are NOT the reason:
1. C# code is correct
The error appears even if I debug the procedure in QA with the same error.
Thanks
ShimonI suggest that you post the TSQL signature of the procedure and use a Profil
er trace to catch the
call of the procedure and post that as well. It sounds like you have called
the procedure with more
parameters than was defined in the CREATE PROC statement.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Shimon Sim" <estshim@.att.net> wrote in message news:%23a5b7MnGFHA.1740@.TK2MSFTNGP09.phx.gb
l...
>I get following error
> Server: Msg 8144, Level 16, State 2, Procedure pPMEmployeeUpdate, Line 0
> [Microsoft][ODBC SQL Server Driver][SQL Server]Procedure or function pPMEmployeeUpdat
e has too
> many arguments specified.
> Any Ideas Why can it appear?
> Following are NOT the reason:
> 1. C# code is correct
> The error appears even if I debug the procedure in QA with the same error.
> Thanks
> Shimon
>|||You have given more parameters than required
Madhivanan|||Thanks,
create PROCEDURE pPropertyManagerUpdate
(
@.PropertyManagerID int,
@.FirstName varchar( 25 ),
@.LastName varchar( 25 ),
@.Phone varchar( 15 ),
@.Fax varchar( 15 ),
@.WirelessPhone varchar( 15 ),
@.Email varchar( 25 ),
@.UserName varchar( 25 ),
@.Password binary( 24 )
)
AS
UPDATE PropertyManager
SET FirstName = @.FirstName, LastName = @.LastName, Phone = @.Phone,
Fax = @.Fax, WirelessPhone = @.WirelessPhone, Email =
@.Email,
UserName = @.UserName, [Password] = @.Password
WHERE PropertyManagerID = @.PropertyManagerID
RETURN
GO
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uxjsVVnGFHA.4032@.TK2MSFTNGP12.phx.gbl...
>I suggest that you post the TSQL signature of the procedure and use a
>Profiler trace to catch the call of the procedure and post that as well. It
>sounds like you have called the procedure with more parameters than was
>defined in the CREATE PROC statement.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Shimon Sim" <estshim@.att.net> wrote in message
> news:%23a5b7MnGFHA.1740@.TK2MSFTNGP09.phx.gbl...
>|||It is imporsible to do if you debug SP in QA.
Thanks
Shimon
<madhivanan2001@.gmail.com> wrote in message
news:1109252093.459864.275520@.l41g2000cwc.googlegroups.com...
> You have given more parameters than required
> Madhivanan
>|||Shimon,
The Error is for the sp pPMEmployeeUpdate and you
posted the code for pPropertyManagerUpdate !!!
BTW, do you have a trigger on the PropertyManager table?
Roji. P. Thomas
Net Asset Management
https://www.netassetmanagement.com
"Shimon Sim" <estshim@.att.net> wrote in message
news:%23h7dQbnGFHA.3912@.TK2MSFTNGP10.phx.gbl...
> Thanks,
> create PROCEDURE pPropertyManagerUpdate
> (
> @.PropertyManagerID int,
> @.FirstName varchar( 25 ),
> @.LastName varchar( 25 ),
> @.Phone varchar( 15 ),
> @.Fax varchar( 15 ),
> @.WirelessPhone varchar( 15 ),
> @.Email varchar( 25 ),
> @.UserName varchar( 25 ),
> @.Password binary( 24 )
> )
> AS
> UPDATE PropertyManager
> SET FirstName = @.FirstName, LastName = @.LastName, Phone = @.Phone,
> Fax = @.Fax, WirelessPhone = @.WirelessPhone, Email =
> @.Email,
> UserName = @.UserName, [Password] = @.Password
> WHERE PropertyManagerID = @.PropertyManagerID
> RETURN
> GO
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:uxjsVVnGFHA.4032@.TK2MSFTNGP12.phx.gbl...
>|||My best guess is that you are calling pPMEmployeeUpdate
From the Insert trigger for the table PropertyManager.
Roji. P. Thomas
Net Asset Management
https://www.netassetmanagement.com
"Shimon Sim" <estshim@.att.net> wrote in message
news:eravnbnGFHA.2616@.tk2msftngp13.phx.gbl...
> It is imporsible to do if you debug SP in QA.
> Thanks
> Shimon
> <madhivanan2001@.gmail.com> wrote in message
> news:1109252093.459864.275520@.l41g2000cwc.googlegroups.com...
>|||Wow
How come I didn't notice that.
Thanks, let me look again.
Shimon.
"Roji. P. Thomas" <thomasroji@.gmail.com> wrote in message
news:ees1thnGFHA.3088@.tk2msftngp13.phx.gbl...
> Shimon,
> The Error is for the sp pPMEmployeeUpdate and you
> posted the code for pPropertyManagerUpdate !!!
> BTW, do you have a trigger on the PropertyManager table?
>
> --
> Roji. P. Thomas
> Net Asset Management
> https://www.netassetmanagement.com
>
> "Shimon Sim" <estshim@.att.net> wrote in message
> news:%23h7dQbnGFHA.3912@.TK2MSFTNGP10.phx.gbl...
>

Wednesday, March 21, 2012

Errors while running DBCC CheckDb

I get the following errors when DBCC CheckDb is executed
on 'fmcomp003' database :
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1881) with latch type SH.
sysindexes failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
Values are 82 and 0.
DBCC results for 'fmcomp003'.Hi
DBCC CHECKDB has few arguments which you can use in this case
For more details please refer to BOL.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Hi,
I didn't understand the error as well as the severity of
the error. And please tell what is BOL.
Amit Chaudhary
>--Original Message--
>Hi
>DBCC CHECKDB has few arguments which you can use in this
case
>For more details please refer to BOL.
>
>"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
wrote in message
> news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
SH.[vbcol=seagreen]
row[vbcol=seagreen]
>
>.
>|||Amit
Seems your table is corrupted. Do you have a last backup of the database?
Books OnLine comes with SQL Server installation.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2afca01c467e7$5fbe4d70$a401280a@.phx
.gbl...[vbcol=seagreen]
> Hi,
> I didn't understand the error as well as the severity of
> the error. And please tell what is BOL.
> Amit Chaudhary
> case
> wrote in message
> SH.
> row|||BOL is SQL Server documentation (Books On Line)..
Open BOL and search from the message# ( which is the SQL Error number)
8966...
You can also often get good information by simply googling the error number
as well...
To find the table name (from object id 2)
in query analyzer, use the database and
select object_name(2)
Object IDs < 100 are system tables..
IndexID of 0 means it is a table with no clustered index...
You will probably have to restore... You can also open a call to Microsoft
product Support ( PSS) ... I think the call now costs about $249.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||> And please tell what is BOL.
Books OnLine.
http://www.aspfaq.com/2229
http://www.aspfaq.com/
(Reverse address to reply.)|||What is the version of SQL used here?
If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if not
check event viewer for any information on hardware issues on the SQL server
.
--
Satya SKJ
"Amit Chaudhary" wrote:

> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Your sysindexes table has a corruption at the leaf level of the clustered
index. This is not repairable and your only option is to restore from your
last known good backup.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Repair cannot fix this error.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Satya SKJ" <satyaskj@.yahoo.co.uk> wrote in message
news:53F0C4CC-F7AE-4F72-8AE3-256FEB2C169B@.microsoft.com...
> What is the version of SQL used here?
> If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
> Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if
not check event viewer for any information on hardware issues on the SQL
server.[vbcol=seagreen]
> --
> --
> Satya SKJ
>
> "Amit Chaudhary" wrote:
>

Errors while running DBCC CheckDb

I get the following errors when DBCC CheckDb is executed
on 'fmcomp003' database :
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1881) with latch type SH.
sysindexes failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
Values are 82 and 0.
DBCC results for 'fmcomp003'.
Hi
DBCC CHECKDB has few arguments which you can use in this case
For more details please refer to BOL.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Hi,
I didn't understand the error as well as the severity of
the error. And please tell what is BOL.
Amit Chaudhary
>--Original Message--
>Hi
>DBCC CHECKDB has few arguments which you can use in this
case
>For more details please refer to BOL.
>
>"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
SH.[vbcol=seagreen]
row
>
>.
>
|||Amit
Seems your table is corrupted. Do you have a last backup of the database?
Books OnLine comes with SQL Server installation.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2afca01c467e7$5fbe4d70$a401280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> I didn't understand the error as well as the severity of
> the error. And please tell what is BOL.
> Amit Chaudhary
> case
> wrote in message
> SH.
> row
|||BOL is SQL Server documentation (Books On Line)..
Open BOL and search from the message# ( which is the SQL Error number)
8966...
You can also often get good information by simply googling the error number
as well...
To find the table name (from object id 2)
in query analyzer, use the database and
select object_name(2)
Object IDs < 100 are system tables..
IndexID of 0 means it is a table with no clustered index...
You will probably have to restore... You can also open a call to Microsoft
product Support ( PSS) ... I think the call now costs about $249.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||> And please tell what is BOL.
Books OnLine.
http://www.aspfaq.com/2229
http://www.aspfaq.com/
(Reverse address to reply.)
|||What is the version of SQL used here?
If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if not check event viewer for any information on Hardware issues on the SQL server.
--
Satya SKJ
"Amit Chaudhary" wrote:

> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Your sysindexes table has a corruption at the leaf level of the clustered
index. This is not repairable and your only option is to restore from your
last known good backup.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Repair cannot fix this error.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Satya SKJ" <satyaskj@.yahoo.co.uk> wrote in message
news:53F0C4CC-F7AE-4F72-8AE3-256FEB2C169B@.microsoft.com...
> What is the version of SQL used here?
> If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
> Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if
not check event viewer for any information on Hardware issues on the SQL
server.[vbcol=seagreen]
> --
> --
> Satya SKJ
>
> "Amit Chaudhary" wrote:
sql

Errors while running DBCC CheckDb

I get the following errors when DBCC CheckDb is executed
on 'fmcomp003' database :
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1881) with latch type SH.
sysindexes failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
Values are 82 and 0.
DBCC results for 'fmcomp003'.Hi
DBCC CHECKDB has few arguments which you can use in this case
For more details please refer to BOL.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Hi,
I didn't understand the error as well as the severity of
the error. And please tell what is BOL.
Amit Chaudhary
>--Original Message--
>Hi
>DBCC CHECKDB has few arguments which you can use in this
case
>For more details please refer to BOL.
>
>"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
wrote in message
>news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
>> I get the following errors when DBCC CheckDb is executed
>> on 'fmcomp003' database :
>> Server: Msg 8966, Level 16, State 1, Line 1
>> Could not read and latch page (1:1881) with latch type
SH.
>> sysindexes failed.
>> Server: Msg 8944, Level 16, State 1, Line 1
>> Table Corrupt: Object ID 2, index ID 0, page (1:1881),
row
>> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
>> Values are 82 and 0.
>> DBCC results for 'fmcomp003'.
>
>.
>|||Amit
Seems your table is corrupted. Do you have a last backup of the database?
Books OnLine comes with SQL Server installation.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2afca01c467e7$5fbe4d70$a401280a@.phx.gbl...
> Hi,
> I didn't understand the error as well as the severity of
> the error. And please tell what is BOL.
> Amit Chaudhary
> >--Original Message--
> >Hi
> >DBCC CHECKDB has few arguments which you can use in this
> case
> >For more details please refer to BOL.
> >
> >
> >"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> >> I get the following errors when DBCC CheckDb is executed
> >> on 'fmcomp003' database :
> >> Server: Msg 8966, Level 16, State 1, Line 1
> >> Could not read and latch page (1:1881) with latch type
> SH.
> >> sysindexes failed.
> >> Server: Msg 8944, Level 16, State 1, Line 1
> >> Table Corrupt: Object ID 2, index ID 0, page (1:1881),
> row
> >> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> >> Values are 82 and 0.
> >> DBCC results for 'fmcomp003'.
> >>
> >
> >
> >.
> >|||BOL is SQL Server documentation (Books On Line)..
Open BOL and search from the message# ( which is the SQL Error number)
8966...
You can also often get good information by simply googling the error number
as well...
To find the table name (from object id 2)
in query analyzer, use the database and
select object_name(2)
Object IDs < 100 are system tables..
IndexID of 0 means it is a table with no clustered index...
You will probably have to restore... You can also open a call to Microsoft
product Support ( PSS) ... I think the call now costs about $249.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||> And please tell what is BOL.
Books OnLine.
http://www.aspfaq.com/2229
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Your sysindexes table has a corruption at the leaf level of the clustered
index. This is not repairable and your only option is to restore from your
last known good backup.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Repair cannot fix this error.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Satya SKJ" <satyaskj@.yahoo.co.uk> wrote in message
news:53F0C4CC-F7AE-4F72-8AE3-256FEB2C169B@.microsoft.com...
> What is the version of SQL used here?
> If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
> Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if
not check event viewer for any information on Hardware issues on the SQL
server.
> --
> --
> Satya SKJ
>
> "Amit Chaudhary" wrote:
> > I get the following errors when DBCC CheckDb is executed
> > on 'fmcomp003' database :
> > Server: Msg 8966, Level 16, State 1, Line 1
> > Could not read and latch page (1:1881) with latch type SH.
> > sysindexes failed.
> > Server: Msg 8944, Level 16, State 1, Line 1
> > Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> > 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> > Values are 82 and 0.
> > DBCC results for 'fmcomp003'.
> >
> >

Errors trying to retrieve large excerpts

hi again,
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
Cheers,This is a great error message, but can you provide more information? What
is the table structure? What is the code that causes the error? Where does
it live (Query Analyzer, an application, ...)?
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:15162A38-1922-4500-9197-118A544857D1@.microsoft.com...
> hi again,
>
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> [Microsoft][ODBC SQL Server Driver]TDS buffer length too large
> [Microsoft][ODBC SQL Server Driver]TDS buffer length too large
> [Microsoft][ODBC SQL Server Driver]TDS buffer length too large
> [Microsoft][ODBC SQL Server Driver]TDS buffer length too large
> Cheers,|||See if this helps:
http://support.microsoft.com/default.aspx/kb/176256
Anith

Friday, February 24, 2012

Error::"Server: Msg 7399, Level 16, State 1, Line 1"

Hi,
I am using link server btw. 2 SQL Servers.
From Server A to Server B it connected without any
problem.
But from Server B to Server A it is giving this error.
And idea'?Running out of choices..
Error msg :
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error. The provider
did not give any information about the error.
Thanks in advance,
SachiI did a very quick search on Google using your error message and there are
quite a few things that may cause this error. It may be worth your while
having a look through to see if any apply.
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Sachi" <sachiek_sachiek@.hotmail.com> wrote in message
news:0d6b01c372cf$4197f3e0$a101280a@.phx.gbl...
> Hi,
> Both as SQL 2k.
> Tks and Rgds,
> Sachi
> >--Original Message--
> >What versions of SQL Server are they ?
> >
> >--
> >
> >--
> >Allan Mitchell (Microsoft SQL Server MVP)
> >MCSE,MCDBA
> >www.SQLDTS.com
> >I support PASS - the definitive, global community
> >for SQL Server professionals - http://www.sqlpass.org
>

Sunday, February 19, 2012

Error: The index entry exceeds the maximum length of 900 bytes

Hi,
while trying to insert I get the error msg. (despite of Microsoft SQL Server
2000 sp3)
"Server: Msg 1946, Level 16, State 4, Line 3
Operation failed. The index entry of length 986 bytes for the index
'IndexName' exceeds the maximum length of 900 bytes."
http://support.microsoft.com/default.aspx?scid=kb;EN-US;280744
The number of entries is about 11400, last id = 11889.
Any ideas? What is a temporary index? Is it possible to extend this limit?
Regards,
BerndBernd,
I suspect you have a varying column (n/varchar or varbinary) indexed. While
you can add these to an index, index rows cannot exceed 900 bytes.
Therefore, if the combined datalength of all columns in your insert that are
included in a single index is > 900, the insert will fail. Try the
following example to see what I mean:
CREATE TABLE #IndexTest(ColA INT, ColB VARCHAR(1000))
GO
CREATE INDEX VARCHARINDEX ON #IndexTest(ColB)
Go
INSERT #IndexTest VALUES (1, REPLICATE('0', 900))
INSERT #IndexTest VALUES (2, REPLICATE('0', 901))
GO
SELECT * FROM #IndexTest
GO
"Bernd Binder" <bernd@.binders.de> wrote in message
news:udocFIRkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> Hi,
> while trying to insert I get the error msg. (despite of Microsoft SQL
Server
> 2000 sp3)
> "Server: Msg 1946, Level 16, State 4, Line 3
> Operation failed. The index entry of length 986 bytes for the index
> 'IndexName' exceeds the maximum length of 900 bytes."
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;280744
> The number of entries is about 11400, last id = 11889.
> Any ideas? What is a temporary index? Is it possible to extend this limit?
> Regards,
> Bernd
>|||FYI - In SQL Server 2005 this restriction is lifted - kind of. The total
length of all key columns in an index cannot exceed 900 bytes but using the
new INCLUDE syntax, you can add extra columns of any length to an index
record - thus creating a query covering index.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:e3NOaiRkEHA.2340@.TK2MSFTNGP11.phx.gbl...
> Bernd,
> I suspect you have a varying column (n/varchar or varbinary) indexed.
While
> you can add these to an index, index rows cannot exceed 900 bytes.
> Therefore, if the combined datalength of all columns in your insert that
are
> included in a single index is > 900, the insert will fail. Try the
> following example to see what I mean:
>
> CREATE TABLE #IndexTest(ColA INT, ColB VARCHAR(1000))
> GO
> CREATE INDEX VARCHARINDEX ON #IndexTest(ColB)
> Go
> INSERT #IndexTest VALUES (1, REPLICATE('0', 900))
> INSERT #IndexTest VALUES (2, REPLICATE('0', 901))
> GO
> SELECT * FROM #IndexTest
> GO
>
> "Bernd Binder" <bernd@.binders.de> wrote in message
> news:udocFIRkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> > Hi,
> >
> > while trying to insert I get the error msg. (despite of Microsoft SQL
> Server
> > 2000 sp3)
> >
> > "Server: Msg 1946, Level 16, State 4, Line 3
> > Operation failed. The index entry of length 986 bytes for the index
> > 'IndexName' exceeds the maximum length of 900 bytes."
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280744
> >
> > The number of entries is about 11400, last id = 11889.
> >
> > Any ideas? What is a temporary index? Is it possible to extend this
limit?
> >
> > Regards,
> > Bernd
> >
> >
>|||"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> schrieb im
Newsbeitrag news:e3NOaiRkEHA.2340@.TK2MSFTNGP11.phx.gbl...
> Bernd,
> I suspect you have a varying column (n/varchar or varbinary) indexed.
While
Yes.
Thank you.
[...]
> >
> > "Server: Msg 1946, Level 16, State 4, Line 3
> > Operation failed. The index entry of length 986 bytes for the index
> > 'IndexName' exceeds the maximum length of 900 bytes."
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280744
> >
> > The number of entries is about 11400, last id = 11889.
> >
> > Any ideas? What is a temporary index? Is it possible to extend this
limit?
> >
> > Regards,
> > Bernd
> >
> >
>

Wednesday, February 15, 2012

ERROR: SQLSERVERAGENT COULD NOT BE STARTED(ERROR CREATING A NEW SESSION)

I keep on getting this msg on a active/passive win2003 cluster environment
with SQL 2005
ERROR: SQLSERVERAGENT COULD NOT BE STARTED (ERROR CREATING A NEW SESSION)
(sqagtres) online thread: error 435 brining Resource online.
(sqagtres) online Thread: ResUtilsStartResouceService failed (status 435)
Thank you in avance
>>> On 12/4/2006 at 10:16 AM, in message
<esNUSh8FHHA.3616@.TK2MSFTNGP06.phx.gbl>, Peter<Vik> wrote:
> ERROR: SQLSERVERAGENT COULD NOT BE STARTED (ERROR CREATING A NEW
> SESSION)
> (sqagtres) online thread: error 435 brining Resource online.
> (sqagtres) online Thread: ResUtilsStartResouceService failed (status
> 435)
If you are using AWE, you need to give the agent user (in Windows) the
lock pages in memory permission.
|||Thank you for your quick response, but what's AWE and which lock pages?
"Joel Maslak" <jmasla@.state.wy.us> wrote in message
news:4573F823.BB84.007F.0@.state.wy.us...
> <esNUSh8FHHA.3616@.TK2MSFTNGP06.phx.gbl>, Peter<Vik> wrote:
> If you are using AWE, you need to give the agent user (in Windows) the
> lock pages in memory permission.
|||>>> On 12/4/2006 at 10:41 AM, in message
<OtdTgv8FHHA.3468@.TK2MSFTNGP04.phx.gbl>, Peter<Vik> wrote:
> Thank you for your quick response, but what's AWE and which lock
> pages?
You probably aren't using AWE if you don't know about it. You have to
provide /PAE as a boot command-line option, and it only applies to 32
bit OS, 32 bit SQL, and > 2GB of memory allocated to SQL.

Error: Server: Msg 1101, Level 17, State 10 when I run script

Hi All,
I can't not run the query to update data but it raice an error as below:
"Server: Msg 1101, Level 17, State 10, Line 1
Could not allocate new page for database 'TEMPDB'. There are no more pages
available in filegroup DEFAULT. Space can be created by dropping objects,
adding additional files, or allowing file growth."
HDD free space: 5GB
RAM: 1GB
CPU: 2.8MHz
SQL server 2000
Windows 2000 server
What should I do?
Please advice me on this.
Thanks in advance,
TNAs per the error message: Increate the size for your tempdb database (data, not log).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TN" <TN@.discussions.microsoft.com> wrote in message
news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
> Hi All,
> I can't not run the query to update data but it raice an error as below:
> "Server: Msg 1101, Level 17, State 10, Line 1
> Could not allocate new page for database 'TEMPDB'. There are no more pages
> available in filegroup DEFAULT. Space can be created by dropping objects,
> adding additional files, or allowing file growth."
> HDD free space: 5GB
> RAM: 1GB
> CPU: 2.8MHz
> SQL server 2000
> Windows 2000 server
> What should I do?
> Please advice me on this.
> Thanks in advance,
> TN
>|||My tempdb is umlimited file growth.
"Tibor Karaszi" wrote:
> As per the error message: Increate the size for your tempdb database (data, not log).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TN" <TN@.discussions.microsoft.com> wrote in message
> news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
> > Hi All,
> >
> > I can't not run the query to update data but it raice an error as below:
> >
> > "Server: Msg 1101, Level 17, State 10, Line 1
> > Could not allocate new page for database 'TEMPDB'. There are no more pages
> > available in filegroup DEFAULT. Space can be created by dropping objects,
> > adding additional files, or allowing file growth."
> >
> > HDD free space: 5GB
> > RAM: 1GB
> > CPU: 2.8MHz
> > SQL server 2000
> > Windows 2000 server
> >
> > What should I do?
> > Please advice me on this.
> >
> > Thanks in advance,
> > TN
> >
>
>|||Sometimes autogrow doesn't grow the files fast enough for the operation that needs the storage.
Solution is to pre-allocate storage.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TN" <TN@.discussions.microsoft.com> wrote in message
news:473EFAC4-F9E0-4CE8-A895-C146BCE11C6C@.microsoft.com...
> My tempdb is umlimited file growth.
> "Tibor Karaszi" wrote:
>> As per the error message: Increate the size for your tempdb database (data, not log).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "TN" <TN@.discussions.microsoft.com> wrote in message
>> news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
>> > Hi All,
>> >
>> > I can't not run the query to update data but it raice an error as below:
>> >
>> > "Server: Msg 1101, Level 17, State 10, Line 1
>> > Could not allocate new page for database 'TEMPDB'. There are no more pages
>> > available in filegroup DEFAULT. Space can be created by dropping objects,
>> > adding additional files, or allowing file growth."
>> >
>> > HDD free space: 5GB
>> > RAM: 1GB
>> > CPU: 2.8MHz
>> > SQL server 2000
>> > Windows 2000 server
>> >
>> > What should I do?
>> > Please advice me on this.
>> >
>> > Thanks in advance,
>> > TN
>> >
>>|||Dear All,
I have the same problem with HP insight Manager 5.1
I have System Errors 17052, 17055 which related to storage full or file log full , I don't know
I'd like to say that I don't know how to deal with SQL Server as I'm not a programmer
I'm a system and infrastructure engineer, but I stucked in that situation, and I will appreciate it much to some one to tell me how to do what u have said ( i.e increase file size, or change location or file growth increase)
thanks alo
From http://www.developmentnow.com/g/118_2005_3_0_0_482538/Error-Server-Msg-1101-Level-17-State-10-when-I-run-script.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||On Oct 6, 9:25 pm, Egyptian Mind<msaleh.m...@.gmail.com> wrote:
> Dear All,
> I have the same problem with HP insight Manager 5.1
> I have System Errors 17052, 17055 which related to storage full or file log full , I don't know
> I'd like to say that I don't know how to deal with SQL Server as I'm not a programmer
> I'm a system and infrastructure engineer, but I stucked in that situation, and I will appreciate it much to some one to tell me how to do what u have said ( i.e increase file size, or change location or file growth increase)
> thanks alot
> Fromhttp://www.developmentnow.com/g/118_2005_3_0_0_482538/Error-Server-Ms...
> Posted via DevelopmentNow.com Groupshttp://www.developmentnow.com
Does it help if you set the recovery mode to simple? Also you may want
to truncate the log file.

Thursday, March 22, 2012

Errror 8144

Wednesday, March 21, 2012

Errors while running DBCC CheckDb

Errors while running DBCC CheckDb

Errors while running DBCC CheckDb

Errors trying to retrieve large excerpts

Friday, February 24, 2012

Error::"Server: Msg 7399, Level 16, State 1, Line 1"

Sunday, February 19, 2012

Error: The index entry exceeds the maximum length of 900 bytes

Wednesday, February 15, 2012

ERROR: SQLSERVERAGENT COULD NOT BE STARTED(ERROR CREATING A NEW SESSION)

Error: Server: Msg 1101, Level 17, State 10 when I run script

Error: Server: Msg 1101, Level 17, State 10 when I run script

Error: Server: Msg 1101, Level 17, State 10 when I run script

ERROR: Subreport

Blog Archive

About Me