Error from Using Report Parameters

Hi,
When I tried to preview my report, I have this error that says: "The report
parameter (field name) has a DefualtValue that depends on the report
parameter (field name). Foward dependencies are not valid"
Was wondering if someone knows what I'm doing wrong here; I can't see
straight right now?Gonna need more information. Is this in reporting services?
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"Ben Cole" <BenCole@.discussions.microsoft.com> wrote in message
news:4EADBCF0-8D09-46CF-B58C-150F64941172@.microsoft.com...
> Hi,
> When I tried to preview my report, I have this error that says: "The
> report
> parameter (field name) has a DefualtValue that depends on the report
> parameter (field name). Foward dependencies are not valid"
> Was wondering if someone knows what I'm doing wrong here; I can't see
> straight right now?|||Yes Louis, it is in Reporting Services.
"Louis Davidson" wrote:

> Gonna need more information. Is this in reporting services?
> --
> ----
--
> Louis Davidson - http://spaces.msn.com/members/drsql/
> SQL Server MVP
> "Arguments are to be avoided: they are always vulgar and often convincing.
"
> (Oscar Wilde)
> "Ben Cole" <BenCole@.discussions.microsoft.com> wrote in message
> news:4EADBCF0-8D09-46CF-B58C-150F64941172@.microsoft.com...
>
>|||Ah. There is a newsgroup for that microsoft.public.sqlserver.reportingsvcs.
That would probably be the best place to take this, but I will guarantee you
that unless this is a very common question they are probably going to want
to know more about what you are doing before they can decide what you are
doing wrong.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"Ben Cole" <BenCole@.discussions.microsoft.com> wrote in message
news:5F606FFD-350A-4324-9E18-B12F8917079A@.microsoft.com...
> Yes Louis, it is in Reporting Services.
> "Louis Davidson" wrote:
>

error changing subscription properties

Hi

Made a change to the publisher security parameters, tried to save and got the following message:

"An error occurred saving the changes to the subscription.

Additional information.

"Value" is longer than 128 that it should not exceed.
Parameter name: value (Microsoft.sqlserver.rmo)

Doesn't make much sense to me.
Tried to change it back and all I get is this error (i had set the userid to domain/userid which was obviously an error).Hi, Bruce

Would you like provide more repro steps? And which version of SQL server are you using?

BTW, did you really input authentication login/password which is londer than 128 characters or any change will cause this error?

Also, when you tried to change back, were you stucked with this error or you succeeded in changing back.

Thanks
Yunjing|||

SQL 2005 standard - current release version

No it wasn't longer than 128

I'm stuck with it - I can't change it back....

Steps:
a) Well I had a 2005 subscription which was working fine (anonymous merge over HTTPS)
b) I made the mistake of changing the subscription properties-> publisher connection -> Use sql server authentication-> Login to domain\userid
c) pressed ok + ok - then got that error

Thanks

Bruce

|||

Hi, Bruce

Thanks for the info you provided.

I tried with 2005 anonymous merge pull sub with sync through web. But I couldn't reproduce the problem by following the steps you showed. I also read the product related source code and didn't find any code work different for changing login no matter for standard or enterprise SKU.

Did you change other sub properties value besides this login? Could you check if the issue was caused by other changes?

Thanks a lot

Yunjing

|||

Hi

It's a bit hard now to provide further info - I'm pretty sure it was the only thing I changed at the time....

thanks for your help anyway - this is a great service....
Bruce

|||

Thanks for all info you provided. If I can reproduce the issue in the future, I will let you know as well.

-Yunjing

error changing subscription properties

Hi

Made a change to the publisher security parameters, tried to save and got the following message:

"An error occurred saving the changes to the subscription.

Additional information.

"Value" is longer than 128 that it should not exceed.
Parameter name: value (Microsoft.sqlserver.rmo)

Doesn't make much sense to me.
Tried to change it back and all I get is this error (i had set the userid to domain/userid which was obviously an error).

Hi, Bruce

Would you like provide more repro steps? And which version of SQL server are you using?

BTW, did you really input authentication login/password which is londer than 128 characters or any change will cause this error?

Also, when you tried to change back, were you stucked with this error or you succeeded in changing back.

Thanks
Yunjing|||

SQL 2005 standard - current release version

No it wasn't longer than 128

I'm stuck with it - I can't change it back....

Steps:
a) Well I had a 2005 subscription which was working fine (anonymous merge over HTTPS)
b) I made the mistake of changing the subscription properties-> publisher connection -> Use sql server authentication-> Login to domain\userid
c) pressed ok + ok - then got that error

Thanks

Bruce

|||

Hi, Bruce

Thanks for the info you provided.

I tried with 2005 anonymous merge pull sub with sync through web. But I couldn't reproduce the problem by following the steps you showed. I also read the product related source code and didn't find any code work different for changing login no matter for standard or enterprise SKU.

Did you change other sub properties value besides this login? Could you check if the issue was caused by other changes?

Thanks a lot

Yunjing

|||

Hi

It's a bit hard now to provide further info - I'm pretty sure it was the only thing I changed at the time....

thanks for your help anyway - this is a great service....
Bruce

|||

Thanks for all info you provided. If I can reproduce the issue in the future, I will let you know as well.

-Yunjing

Error changing startup parameters after 8patch

Please help! Here is what happened in details:
----
Originally, the SQL Server install placed the data and log files in
d:\Program Files\Microsoft SQL Server\MSSQL\Data\ folder and the error
logs in d:\Program Files\Microsoft SQL Server\MSSQL\Log folder.
----
For syntactical (commands that do not like spaces in folder or file
names) and security and organizational (separate data and logs to
different drives) reasons, I decided to place them in various
locations. Using http://support.microsoft.com/?kbid=224071 as a
guide, I moved the data file to d:\mssql\data\ and log files to
e:\mssql\transaction_log\ and error logs to e:\mssql\error_log\ by
changing the startup parameters:
-dD:\MSSQL\Data\master.mdf
-lE:\MSSQL\Transaction_Log\mastlog.ldf
-eE:\MSSQL\Error_Log
I followed the exact steps detailed from the link ("Moving the Master
Database").
No problems occurred.
----
I remember I ran the above procedures twice because I renamed one of
the Tlog folder to Transaction_Log. Again, that did not pose any
problems.
----
From time to time, Window updates and this patch were installed on
this machine:
- - ---
Title: Cumulative Patch for Microsoft SQL Server (815495)
Date: 23 July 2003
Software:
- Microsoft SQL Server 7.0
- Microsoft Data Engine (MSDE) 1.0
- Microsoft SQL Server 2000
- Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
- Microsoft SQL Server 2000 Desktop Engine (Windows)
Impact: Run code of attacker's choice
Max Risk: Important
Bulletin: MS03-031
Microsoft encourages customers to review the Security Bulletins at:
http://www.microsoft.com/technet/security/bulletin/MS03-031.asp
http://www.microsoft.com/security/security_bulletins/ms03-031.asp
- ---
----
The next time, I again attempted to change the location of the error
log file by changing the startup parameters to
-eD:\MSSQL\Process_Log\SQL_Error_Log. On step 8 of the "Moving the
Master Database" instructions, SQL Server was having problems starting
up. The error message received was:
initerrlog: Could not open error log file
'D:\MSSQL\Process_Log\SQL_Error_Log'. Operating system error = 5(Access is denied.).
You could not start SQL Server from anywhere except I found that
running sqlservr.exe from the command prompt with the temporary
startup parameters of the error log file of the original location
worked (sqlservr.exe -eD:\Program Files\Microsoft SQL
Server\MSSQL\Log). SQL server runs under this mode, but SQL Server
Agent cannot start up even still.
While the SQL Server is running using the above command, I attempted
to change the Master Start Parameters of the Error Log back to
-eE:\MSSQL\Error_Log
and even -ed:\Program Files\Microsoft SQL Server\MSSQL\Log
but found no success starting the SQL Server with Enterprise Manager
or Services interfaces (sqlservr.exe was shutdown prior to attempt).
----
I am led to believe that the patch 815495 may have been involved with
the error. There have been times where Enterprise Manager freezes up
and automatically shuts down (occurs at least once a week) when
working within EM such as opening properties of Database Maintenance
Plan. This had not occurred before. In addition all the SQL logs
have been wiped out.
I have installed the same patch to my personal WinXP machine and the
Enterprise Manager no longer works (unable to open and receive an
error message to forward error to Microsoft) even with a reinstall.
These same results occurred on two server machines which were prepared
for production and standby. I don't know what else to do? Please
help!
Thanks so much,
JuneThe Error message you are receiving is access is denied to the log files.
Check your NTFS permissions, and make sure that the SQL Server account has
full control of the log files and the folder that they are in.
--
Denny Cherry
DBA
GameSpy Industries
"June" <jnguyen@.harbourcg.com> wrote in message
news:29f6d8aa.0309121232.54032ff@.posting.google.com...
> Please help! Here is what happened in details:
> ----
--
> Originally, the SQL Server install placed the data and log files in
> d:\Program Files\Microsoft SQL Server\MSSQL\Data\ folder and the error
> logs in d:\Program Files\Microsoft SQL Server\MSSQL\Log folder.
> ----
--
> For syntactical (commands that do not like spaces in folder or file
> names) and security and organizational (separate data and logs to
> different drives) reasons, I decided to place them in various
> locations. Using http://support.microsoft.com/?kbid=224071 as a
> guide, I moved the data file to d:\mssql\data\ and log files to
> e:\mssql\transaction_log\ and error logs to e:\mssql\error_log\ by
> changing the startup parameters:
> -dD:\MSSQL\Data\master.mdf
> -lE:\MSSQL\Transaction_Log\mastlog.ldf
> -eE:\MSSQL\Error_Log
> I followed the exact steps detailed from the link ("Moving the Master
> Database").
> No problems occurred.
> ----
--
> I remember I ran the above procedures twice because I renamed one of
> the Tlog folder to Transaction_Log. Again, that did not pose any
> problems.
> ----
--
> From time to time, Window updates and this patch were installed on
> this machine:
> - - ---
> Title: Cumulative Patch for Microsoft SQL Server (815495)
> Date: 23 July 2003
> Software:
> - Microsoft SQL Server 7.0
> - Microsoft Data Engine (MSDE) 1.0
> - Microsoft SQL Server 2000
> - Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
> - Microsoft SQL Server 2000 Desktop Engine (Windows)
> Impact: Run code of attacker's choice
> Max Risk: Important
> Bulletin: MS03-031
> Microsoft encourages customers to review the Security Bulletins at:
> http://www.microsoft.com/technet/security/bulletin/MS03-031.asp
> http://www.microsoft.com/security/security_bulletins/ms03-031.asp
> - ---
> ----
--
> The next time, I again attempted to change the location of the error
> log file by changing the startup parameters to
> -eD:\MSSQL\Process_Log\SQL_Error_Log. On step 8 of the "Moving the
> Master Database" instructions, SQL Server was having problems starting
> up. The error message received was:
> initerrlog: Could not open error log file
> 'D:\MSSQL\Process_Log\SQL_Error_Log'. Operating system error => 5(Access is denied.).
> You could not start SQL Server from anywhere except I found that
> running sqlservr.exe from the command prompt with the temporary
> startup parameters of the error log file of the original location
> worked (sqlservr.exe -eD:\Program Files\Microsoft SQL
> Server\MSSQL\Log). SQL server runs under this mode, but SQL Server
> Agent cannot start up even still.
> While the SQL Server is running using the above command, I attempted
> to change the Master Start Parameters of the Error Log back to
> -eE:\MSSQL\Error_Log
> and even -ed:\Program Files\Microsoft SQL Server\MSSQL\Log
> but found no success starting the SQL Server with Enterprise Manager
> or Services interfaces (sqlservr.exe was shutdown prior to attempt).
> ----
--
> I am led to believe that the patch 815495 may have been involved with
> the error. There have been times where Enterprise Manager freezes up
> and automatically shuts down (occurs at least once a week) when
> working within EM such as opening properties of Database Maintenance
> Plan. This had not occurred before. In addition all the SQL logs
> have been wiped out.
> I have installed the same patch to my personal WinXP machine and the
> Enterprise Manager no longer works (unable to open and receive an
> error message to forward error to Microsoft) even with a reinstall.
> These same results occurred on two server machines which were prepared
> for production and standby. I don't know what else to do? Please
> help!
> Thanks so much,
> June