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...
>

No comments:

Post a Comment