Hide / Disable Report Parameter

Hi

I am using reporting services 2005. (sql server 2005 Sp2).

I have two parameters on the reports. Both parameter are not related to each other.

If user selects first parameter value I want to Hide or Disable second parameter drop down.

Is it possible in Reporting services?

Thanks for everyone's help.

Regards

Swam

I am guessing a big NO

You could simply not use the 2nd parameter in the report

and have a text with "2nd parameter will not be used if 1st parameter is used"

|||

Swam wrote:

If user selects first parameter value I want to Hide or Disable second parameter drop down.

You can't do that, but what you can do is make the default value and even the *contents* of the second parameter dependant on what is selected in the first parameter. I would have the second dropdown default to null or an empty string if a value was selected in the first dropdown.

|||Thanks for your help..|||Thanks for your help....

HELP:SQL Port lost or never set on new install

I just installed SQL Server on XP (SP2) attempted to access the Server
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility
.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:

> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utili
ty.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:
>

HELP:SQL Port lost or never set on new install

I just installed SQL Server on XP (SP2) attempted to access the Server
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>
|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:

> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>
|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:

Help:MS SQL 2000 SP4 dont run !

I have installed MS SQL 2000 Personal Edition on XP SP2 and It works !
I verified its version :
SQL Server 2000 Original Release 8.00.194 RTM

When I try to install SP4 after extracting locally I see the first windows for a moment and then nothing appens !

x86\setup\setupsql.exe process remain in task manager without make nothing.

Someone can help me ?Check windows event log & SQL error lgo for any information.
Also try to download the file again, make sure you're using correct SP4 file from MS.|||Thank you !

I have found only this warning in eventlog

SuperSocket info: (SpnRegister) : Error 1355.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

But I think it's because I have no SP4 installed .
When I try to install SP4 I have no message in any logs.
Process do nothing because, I suppose , It's waiting for a Dialog Window that I don't see :-(|||There was a problem on the Clustered environment previously as per KBA http://support.microsoft.com/?id=303411 , but yours it not that case. Anyway try downloading SP3a for SQL 2000 and apply, then use SP4.

BTW mention the filename of SP4 you're using to apply.|||I have the same problem with SP3.
File name is SQL2000-KB884525-SP4-x86-ENU.EXE
May be MSI ? I have 3.1
Or IIS ? I have 5.1
How can I remove IIS ?

Help: Replication stops with no error or warnings!

hi all,
I have sql server 2005 sp2 running transactional replication between 2
production servers on different domains. Every once in a while
transaction stop being delivered to the target with no warnings or
errors being generated by any of the servers involved. Using
replication monitor on the the publisher and viewing the tab "
Publisher to Distributor" shows transactions being delivered
successfully ("n transaction(s) with n command(s) were delivered
successfully") but the transactions do not show up on the target
server?
Any thoughts much appreciated as the only resolution i've found is to
wait until off hours and reinitialize the subscriptions. i'm going to
have to put a custom alert system in place to check table counts but i
really need to find the cause of this.
-Thanks! DF
Difficult to tell exactly what is getting replicated in repl monitor. Best
tool to troubleshoot is to run profiler on subscriber and see if you can find
anything. Best to do after hours if you can repeat problem w/ just you as
user.
What is your distribution agent profile? How did you initialize subscriber -
snapshot agent or backup/restore? If backup init - make sure you disable
triggers or set to NFR and drop FK's at subscriber. Perhaps your agent is
ignoring errors caused by FK constraints and not delivering rows changes...
ChrisB MCDBA
MSSQLConsulting.com
"dfateman@.yahoo.com" wrote:

> hi all,
> I have sql server 2005 sp2 running transactional replication between 2
> production servers on different domains. Every once in a while
> transaction stop being delivered to the target with no warnings or
> errors being generated by any of the servers involved. Using
> replication monitor on the the publisher and viewing the tab "
> Publisher to Distributor" shows transactions being delivered
> successfully ("n transaction(s) with n command(s) were delivered
> successfully") but the transactions do not show up on the target
> server?
> Any thoughts much appreciated as the only resolution i've found is to
> wait until off hours and reinitialize the subscriptions. i'm going to
> have to put a custom alert system in place to check table counts but i
> really need to find the cause of this.
> -Thanks! DF
>

HELP: FAILED ASSERTION

Hello,
I have a concern about 2 errors "Failed Assertion". We're using SQL Server
2005 SP2. May anyone help me to fix these errors?
It says:
SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion = '!m_updNestedXactCnt' Trying to use the transaction while there are 1
parallel nested xacts outstanding. This error may be timing-related. If the
error persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion = 'NULL
== m_lockList.Head ()'. This error may be timing-related. If the error
persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.I would run a checkdb but this is almost always a bug in SQL Server. You
ought to open a case with PSS.
--
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> Hello,
> I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> 2005 SP2. May anyone help me to fix these errors?
> It says:
> SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion => '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> parallel nested xacts outstanding. This error may be timing-related. If
> the
> error persists after rerunning the statement, use DBCC CHECKDB to check
> the
> database for structural integrity, or restart the server to ensure
> in-memory
> data structures are not corrupted.
> SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion => 'NULL
> == m_lockList.Head ()'. This error may be timing-related. If the error
> persists after rerunning the statement, use DBCC CHECKDB to check the
> database for structural integrity, or restart the server to ensure
> in-memory
> data structures are not corrupted.
>|||So I have to report these case to PSS. Ok, thanks for the advice.
"jason" wrote:
> I would run a checkdb but this is almost always a bug in SQL Server. You
> ought to open a case with PSS.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
> "Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
> news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> > Hello,
> >
> > I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> > 2005 SP2. May anyone help me to fix these errors?
> >
> > It says:
> >
> > SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion => > '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> > parallel nested xacts outstanding. This error may be timing-related. If
> > the
> > error persists after rerunning the statement, use DBCC CHECKDB to check
> > the
> > database for structural integrity, or restart the server to ensure
> > in-memory
> > data structures are not corrupted.
> >
> > SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion => > 'NULL
> > == m_lockList.Head ()'. This error may be timing-related. If the error
> > persists after rerunning the statement, use DBCC CHECKDB to check the
> > database for structural integrity, or restart the server to ensure
> > in-memory
> > data structures are not corrupted.
> >
>|||We experience the same problem. How can we solve it ?
"Maxim" wrote:
> So I have to report these case to PSS. Ok, thanks for the advice.
> "jason" wrote:
> > I would run a checkdb but this is almost always a bug in SQL Server. You
> > ought to open a case with PSS.
> >
> > --
> > Jason Massie
> > www: http://statisticsio.com
> > rss: http://feeds.feedburner.com/statisticsio
> >
> > "Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
> > news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> > > Hello,
> > >
> > > I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> > > 2005 SP2. May anyone help me to fix these errors?
> > >
> > > It says:
> > >
> > > SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion => > > '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> > > parallel nested xacts outstanding. This error may be timing-related. If
> > > the
> > > error persists after rerunning the statement, use DBCC CHECKDB to check
> > > the
> > > database for structural integrity, or restart the server to ensure
> > > in-memory
> > > data structures are not corrupted.
> > >
> > > SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion => > > 'NULL
> > > == m_lockList.Head ()'. This error may be timing-related. If the error
> > > persists after rerunning the statement, use DBCC CHECKDB to check the
> > > database for structural integrity, or restart the server to ensure
> > > in-memory
> > > data structures are not corrupted.
> > >
> >

HELP: FAILED ASSERTION

Hello,
I have a concern about 2 errors "Failed Assertion". We're using SQL Server
2005 SP2. May anyone help me to fix these errors?
It says:
SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion =
'!m_updNestedXactCnt' Trying to use the transaction while there are 1
parallel nested xacts outstanding. This error may be timing-related. If the
error persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion = 'NULL
== m_lockList.Head ()'. This error may be timing-related. If the error
persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
I would run a checkdb but this is almost always a bug in SQL Server. You
ought to open a case with PSS.
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> Hello,
> I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> 2005 SP2. May anyone help me to fix these errors?
> It says:
> SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion =
> '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> parallel nested xacts outstanding. This error may be timing-related. If
> the
> error persists after rerunning the statement, use DBCC CHECKDB to check
> the
> database for structural integrity, or restart the server to ensure
> in-memory
> data structures are not corrupted.
> SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion =
> 'NULL
> == m_lockList.Head ()'. This error may be timing-related. If the error
> persists after rerunning the statement, use DBCC CHECKDB to check the
> database for structural integrity, or restart the server to ensure
> in-memory
> data structures are not corrupted.
>
|||So I have to report these case to PSS. Ok, thanks for the advice.
"jason" wrote:

> I would run a checkdb but this is almost always a bug in SQL Server. You
> ought to open a case with PSS.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
> "Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
> news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
>