error in updating field thru stor_proc

I'm trying to update 'password' field in a table thru a stored procedure which is called from my program.

I'm passing the values for password and the key fields.

While debugging I can see the values in each parameter, but I get an error that the 'value for password was not passed'.

Here's the program snippet for calling the stored proc.

All three parameters are 'varchar' type

dbConn.Open();

dbConn.CreateParameters(3);

dbConn.AddParameters(0, Pwd, newPwd);

dbConn.AddParameters(1, Login, pwd_Login);

dbConn.AddParameters(2, IdNum, pwd_IdNum);

result = dbMgr.ExecuteNonQuery(CommandType.StoredProcedure, SP_UPDPWD);

--

EXEC @.return_value = [dbo].[usp_UsrMstUpdPwdParaPwdEmailCaseNum]

@.Pwd = N'3Sg7vqowIBRdfgdfgrgdjykFTjTFt5hfHfhFtFghzIG1haWRliBuYW1lPw==',

@.Login = N'xyz@.abc.com',

@.IdNumber = N'00009'

--

What am I missing?

Is Pwd a variable or constant set to "@.Pwd", login to "@.Login", IdNum to "@.IdNum", and "SP_UPDPWD" to the appropriate string for your stored procedure?

Also, is this using an IDBManager pattern?

Thanks,

John

|||

Never mind. found the problem

The parameter for Password was not spelt right!

Error in Locale when passing datetime parameter?

Hello!
I am using RS supplied with SQl Server 2005. I have one report and two
subreports inside it. One of the subreports is embedded and another one can
be navigated using hypertext link. All reports have one datetime parameter
which is entered by user in the main report and passed to subreports. But
when in the main report I enter 1-st of november 2006 in subreports it
becomes 10-th of january 2006. All reports have language = default. When
debugging report (F5) everything is ok. The problem comes out when publishing
report to report server.
Any suggestions/advises are welcome.What is the build number of the Report Server?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Alexander Korol" <AlexanderKorol@.discussions.microsoft.com> wrote in
message news:63910111-34C6-4B1C-A34E-E52FCFA0CE00@.microsoft.com...
> Hello!
> I am using RS supplied with SQl Server 2005. I have one report and two
> subreports inside it. One of the subreports is embedded and another one
> can
> be navigated using hypertext link. All reports have one datetime parameter
> which is entered by user in the main report and passed to subreports. But
> when in the main report I enter 1-st of november 2006 in subreports it
> becomes 10-th of january 2006. All reports have language = default. When
> debugging report (F5) everything is ok. The problem comes out when
> publishing
> report to report server.
> Any suggestions/advises are welcome.|||Hello Lev
Can not say for sure - I looked bin folder - version of most libraries is
9.00.2047.00
others are have 9.00.1399.00.
"Lev Semenets [MSFT]" wrote:
> What is the build number of the Report Server?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Alexander Korol" <AlexanderKorol@.discussions.microsoft.com> wrote in
> message news:63910111-34C6-4B1C-A34E-E52FCFA0CE00@.microsoft.com...
> > Hello!
> >
> > I am using RS supplied with SQl Server 2005. I have one report and two
> > subreports inside it. One of the subreports is embedded and another one
> > can
> > be navigated using hypertext link. All reports have one datetime parameter
> > which is entered by user in the main report and passed to subreports. But
> > when in the main report I enter 1-st of november 2006 in subreports it
> > becomes 10-th of january 2006. All reports have language = default. When
> > debugging report (F5) everything is ok. The problem comes out when
> > publishing
> > report to report server.
> >
> > Any suggestions/advises are welcome.
>
>|||Lets figure out details. Could you please reply via e-mail?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Alexander Korol" <AlexanderKorol@.discussions.microsoft.com> wrote in
message news:13DAE456-72AB-4F13-999F-E23165227726@.microsoft.com...
> Hello Lev
> Can not say for sure - I looked bin folder - version of most libraries is
> 9.00.2047.00
> others are have 9.00.1399.00.
> "Lev Semenets [MSFT]" wrote:
>> What is the build number of the Report Server?
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Alexander Korol" <AlexanderKorol@.discussions.microsoft.com> wrote in
>> message news:63910111-34C6-4B1C-A34E-E52FCFA0CE00@.microsoft.com...
>> > Hello!
>> >
>> > I am using RS supplied with SQl Server 2005. I have one report and two
>> > subreports inside it. One of the subreports is embedded and another one
>> > can
>> > be navigated using hypertext link. All reports have one datetime
>> > parameter
>> > which is entered by user in the main report and passed to subreports.
>> > But
>> > when in the main report I enter 1-st of november 2006 in subreports it
>> > becomes 10-th of january 2006. All reports have language = default.
>> > When
>> > debugging report (F5) everything is ok. The problem comes out when
>> > publishing
>> > report to report server.
>> >
>> > Any suggestions/advises are welcome.
>>

Error handling with MDX and Reporting Services

I have having trouble with an MDX Statement. There are some instances where the MDX statement I am passing in isn't correct or invalid. The report takes in serveral default parameters and creates an MDX statement from it. When this error happens I get an error similiar to

Formula error - cannot find dimension member ("[Time].[2005]") - in a name-binding function

on the report page. I would like to be able to handle this error in reporting services so how. Essientially, I would want to be able to just say if this error happens just take me the plain page and do not load up any defaults.You might consider this a hack, but this can be solved from outside Reporting Services with the new missing member functionality in 2005 (ie invalid member lookups wont generate errors),|||I am using RS 2005 and AS 2005 RTM.

I am having the report to accept a parameter UserUserID that accepts values such as [User].[User ID].&[1].

This is working fine when the front-end calls it with a correct/valid UserID.

When it is the calling the report with a valid UserID, two things that I observe happening:
a) when the Parameter is set to Hidden (on the Report Parameters properties), this error will be displayed "The 'UserUserID' parameter is missing a value"
b) when the Parameter is not set to Hidden, a blank page is shown with the parameter prompt <Select a Value>.

Is there any way to better handle situation a)? Since I need to hide the parameters from the end-users....

Thanks.

Error handling with MDX and Reporting Services

I have having trouble with an MDX Statement. There are some instances where the MDX statement I am passing in isn't correct or invalid. The report takes in serveral default parameters and creates an MDX statement from it. When this error happens I get an error similiar to

Formula error - cannot find dimension member ("[Time].[2005]") - in a name-binding function

on the report page. I would like to be able to handle this error in reporting services so how. Essientially, I would want to be able to just say if this error happens just take me the plain page and do not load up any defaults.

You might consider this a hack, but this can be solved from outside Reporting Services with the new missing member functionality in 2005 (ie invalid member lookups wont generate errors),|||I am using RS 2005 and AS 2005 RTM.

I am having the report to accept a parameter UserUserID that accepts values such as [User].[User ID].&[1].

This is working fine when the front-end calls it with a correct/valid UserID.

When it is the calling the report with a valid UserID, two things that I observe happening:
a) when the Parameter is set to Hidden (on the Report Parameters properties), this error will be displayed "The 'UserUserID' parameter is missing a value"
b) when the Parameter is not set to Hidden, a blank page is shown with the parameter prompt <Select a Value>.

Is there any way to better handle situation a)? Since I need to hide the parameters from the end-users....

Thanks.